This action might not be possible to undo. Are you sure you want to continue?
Salient features of our Program : * Training by a faculty who has over 5 years of real time experience * 45 Days Program. Very easy to learn. * Free CD with all the course material, Implementation steps and quick reference guides * Excellent lab facilities * Real time experience and case studies The following is the course contents : Oracle Applications * Users * Responsibilities * Menus * Form Functions * Concurrent Programs * Request groups * Flexfields * Value sets * System profiles Technical: Development Development Development Development and and and and Customization Customization Customization Customization of of of of Apps Apps Apps Apps Reports Forms Interfaces Forms
How to Implemente User Profiles?
Implementing User Profiles : You should define user profile options whenever you want your application to react in different ways for different users, depending on specific user attributes. You can decide whether your end users can view and update options you define at the User level or you can also define the option such that your end users could not see or change its value. Predefined User Profile Options :
Database Profile Options : Oracle Application Object Library provides many user profile options that the Oracle System Administrator or the users can see and update. Internally Generated Profile Options : Oracle Application Object Library also provides a set of profile options that you can access via the user profile routines. You can retrieve values for these profile options in your forms and programs. However, except for the profiles CONC_PRINT_OUTPUT and CONC_PRINT_STYLE, you cannot change their values. System administrators and end users cannot see the values for, nor change the values of, these profile options.
FND_PROFILE: User Profile APIs :
You can use the user profile routines to manipulate the option values stored in client and server user profile caches. On the client, a single user profile cache is shared by multiple form sessions. Thus, when Form A and Form B are both running on a single client, any changes Form A makes to the client’s user profile cache affect Form B’s run–time environment, and vice versa. On the server, each form session has its own user profile cache. Thus, even if Form A and Form B are running on the same client, they have separate server profile caches. Server profile values changed from Form A’s session do not affect Form B’s session, and vice versa. Similarly, profile caches on the server side for concurrent programs are separate. Also, note that the server–side profile cache accessed by these PL/SQL routines is not synchronized with the C–code cache. If you put a value using the PL/SQL routines, it will not be readable with the C–code routines. Any changes you make to profile option values using these routines affect only the run–time environment. The effect of these settings ends when the program ends, because the database session (which holds the profile cache) is terminated.
Summary procedure FND_PROFILE.PUT (name IN varchar2, value IN varchar2); Location FNDSQF library and database (stored procedure) Description Puts a value to the specified user profile option. If the option does not exist, you can also create it with PUT. Arguments (input) name The (developer) name of the profile option you want to set. Value The value to set in the specified profile option.
Summary procedure FND_PROFILE.GET (name IN varchar2, value OUT varchar2); Location FNDSQF library and database (stored procedure) Description Gets the current value of the specified user profile option, or NULL if the profile does not exist. Arguments (input) name The (developer) name of the profile optionwhose value you want to retrieve. Arguments (output) Value The current value of the specified user profile option as last set by PUT or as defaulted in the current user’s profile. Example FND_PROFILE.GET (’USER_ID’, user_id);
Summary function FND_PROFILE.VALUE (name IN varchar2) return varchar2; Location FNDSQF library and database (stored function) Description VALUE works exactly like GET, except it returns the value of the specified profile option as a function result. Arguments (input) Name The (developer) name of the profile option whose value you want to retrieve.
Posted by Nil at 2:23 PM 0 comments Labels: Profile Options
What is Profile Options in Oracle Apps:
A user profile is a set of changeable options that affects the way your applications run. Oracle Application Object Library establishes a value for each option in a user’s profile when the user logs on or changes responsibility. Your user can change the value of profile options at any time. Oracle Application Object Library provides many options that your users can set to alter the user interface of your applications to satisfy their individual preferences. Oracle Applications user profiles help you satisfy the following business needs. You should be able to: * Set options that affect your application’s behavior to your preference * Modify product–specific variables that affect the functionality of your application to suit your business environment User profile options exist at Site, Application, Responsibility and User levels. Oracle Application Object Library treats user profile levels as a hierarchy, where User is the highest level of the hierarchy, followed by Responsibility, Application and at the lowest level, Site. Higher–level option values override lower–level option values. Each user profile option ordinarily exists at each level. * Site Level is the lowest user profile level. Site–level option values affect the
way all applications run at a given installation. * Application : Application is the user profile level immediately above Site. Application–level option values affect the way a particular application runs. * Responsibility Level :Responsibility is the user profile level immediately above Application. Responsibility–level option values affect the way applications run for all users of a responsibility. * User Level : User is the highest user profile level and is immediately above Responsibility. User–level option values affect the way applications run for an application user.
Posted by Nil at 2:09 PM 0 comments Labels: Profile Options
Aug 30, 2008
Account Payables -> Account Payables Flow:
Account Payables -> Account Payables Flow: PO -> Receipt -> AP -> GL Invoice -> Payments-> Move Transactions from AP to GLIn AP there are 2 Thumb rules. • Without supplier there is no invoice. • Without invoice there is no payment. Invoice Types: 1. Standard: We will make all the payments based on the standard invoice. It will have the information of Invoice Number, Invoice Date, Invoice Amount, and Currency. 2. Credit Memo: We will create credit memo invoice whenever supplier is giving the discount and it will be adjusted in standard invoice. It is always negative amount. 3. Debit Memo: Sometimes Company will deduct some amount from the invoice amount. This will be adjusted in standard invoice. It is always negative amount.
4. With-Holding TAX: This type of invoice will be created to make the invoice tax to the Govt. on behalf of supplier. 5. Pre-Payment: If we want to make some payments to the supplier in advance then we create the Pre-Payment invoice. 6. PO Default: If we want to make the invoice as per the PO then we create PO default. We will give Po Number. System will pick up the complete PO information. 7. Mixed: Includes both positive and negative amount. We can match this invoice with PO’s and other invoices. 8. Expense Report: This will be applicable for the employees who are working in the Company where payables and internet expense and project account. Expense will be included. 9. Recurring invoice: We can enter invoice for periodic expense for which we may not receive. Invoice from supplier. To create a Recurring invoice first we will take template. As per that we will create the invoice.Once the invoice is successfully completed, we can go for payments. It is of 3 types. Manual Payment: Here we will be mentioning the Invoice Number, Bank Account, and Document Number, Payment Date and Currency. Refund payment: This is used for Employee expenses and for adjusting the Supplier account, Quick payment: In this payment, system will automatically generate checks. To print Checks there will be a concurrent program for each check format.Once the payment was done, we will move all the transactions to GL. Suppliers: Set up suppliers in the Suppliers window to record information about individuals and companies from whom you purchase goods and services. You can also enter employees whom you reimburse for expense reports. When you enter a supplier that does business from multiple locations, you store supplier information only once, and enter supplier sites for each location. You can designate supplier sites as pay sites, purchasing sites, RFQ only sites, or procurement card sites. For example, for a single supplier, you can buy from
several different sites and send payments to several different sites. Most supplier information automatically defaults to all supplier sites to facilitate supplier site entry. However, you can override these defaults and have unique information for each site. The system uses information you enter for suppliers and supplier sites to enter default values when you later enter transactions for a supplier site. Most information you enter in the Suppliers window is used only to enter defaults in the Supplier Sites window. When the system enters that information in a later transaction, it only uses supplier site information as a default, even if the supplier site value is null and the supplier has a value. If you update information at the supplier level, existing supplier sites are not updated. When you enter a supplier, you can also record information for your own reference, such as names of contacts or the customer number your supplier has assigned to you. Invoices: Invoice Type (LOV): The type of invoice. Standard and Credit are the only invoice types you can enter in this window. If you do not enter a value for this field then a value will be assigned during import based on the amount of the invoice. Standard: A trade invoice you receive from a supplier. The amount of a Standard invoice must be zero or greater. Credit: Credit Memo. A negative amount invoice you receive from a supplier representing a credit for goods or services purchased. Note that in the Invoice Gateway you can match a credit memo to a purchase order to perform a price correction, but you cannot match a credit memo to an invoice. If you want to match to an invoice, then use the Invoice Workbench. Debit Memo: Negative amount invoice created by you and sent to a supplier to notify the supplier of a credit you are recording. Usually send with a note explaining the debit memo. Purchase Order Matched Invoices: You can match Payables invoices to purchase orders to ensure that you pay only for the goods that you have ordered, or you can match to purchase order receipts to ensure that you pay only for goods that you have received. Purchase order matched invoices are invoices that you match to any of the following: • Purchase order shipments • Purchase order receipts
• Purchase order receipt lines • Purchase order distributions Foreign Currency Invoices: When you enter an invoice in a currency other than your functional currency, Payables uses an exchange rate to convert the invoice and invoice distributions into your functional currency for creating journal entries. You define your functional currency during setup for your set of books. Mixed Invoices: Mixed Invoices are invoices or credit/debit memos for which you can perform both positive and negative matching to purchase orders and to other invoices. For example, you can enter an invoice for –$100 with Invoice Type Mixed. You can match to an invoice for $–200, and match to a purchase order for $100. Prepayments:A prepayment is a type of invoice you enter to make an advance payment to a supplier or employee. For example, you need to pay a deposit on a lease, or pay an employee an advance for travel expenses. You can later apply the prepayment to one or more invoices or expense reports you receive from the supplier or employee to offset the amount paid to them. The supplier might send an invoice that references a prepayment. The supplier has reduced the invoice amount by the amount of the prepayment and associated tax. You can use the Prepayment on Invoice feature to enter the invoice. You can enter two types of prepayments: Temporary prepayments can be applied to invoices or expense reports you receive. For example, you use a Temporary prepayment to pay a hotel a catering deposit. When the hotel’s invoice arrives, apply the prepayment to the invoice to reduce the invoice amount you pay. Permanent prepayments cannot be applied to invoices. For example you use a Permanent prepayment to pay a lease deposit for which you do not expect to be invoiced. 2–way matching: The process of verifying that purchase order and invoice information matches within accepted tolerance levels. Payables use the following criteria to verify two–way matching: Invoice price <- Order price Quantity billed <- Quantity ordered 3–way matching: The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Payables use the following criteria to verify three–way matching: Invoice price <- Purchase
Order price, Quantity billed <- Quantity ordered, Quantity billed <- Quantity received. 4–way matching: The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Payables use the following criteria to verify four–way matching: Invoice price <- Order price Quantity billed <- Quantity ordered Quantity billed <- Quantity received Quantity billed <- Quantity accepted FOB (Free On Board): The point or location where the ownership title of goods is transferred from the seller to the buyer. This indicates that delivery of a shipment will be made on board or into a carrier by the shipper without charge, and is usually followed by a shipping point or destination (e.g. ’FOB Our warehouse in New York’). The FOB code is currently available only for reference purposes. Revenue and cost recognition is not currently determined by the value entered in this field. (Receivables Lookup) Purge : An Oracle Receivables Process, where you identify a group of records for Receivables to delete from the database. Receivables purge each record and its related records. Receivables maintain summary data for each record it purges.
Posted by Nil at 11:00 AM 0 comments Labels: Account Payables
Oracle Purchasing Tables Table
Oracle Purchasing Tables Table Name : PO_REQUISITION_HEADERS_ALL Columns: REQUISITION_HEADER_ID PREPARER_ID SEGMENT1 SUMMARY_FLAG ENABLED_FLAG Segment1: Is the system–assigned number you use to identify in forms and reports? Stores information about requisition headers. You need one row for each requisition header you create. Each row contains the requisition number, preparer, status, and description.SEGMENT1 is the number you use to identify
the requisition in forms and reports (unique). Table Name : PO_REQUISITION_LINES_ALL Columns: REQUISITION_LINE_ID REQUISITION_HEADER_ID LINE_NUM LINE_TYPE_ID CATEGORY_ID ITEM_DESCRIPTION UNIT_MEAS_LOOKUP_CODE UNIT_PRICE, QUANTITY DELIVER_TO_LOCATION_ID TO_PERSON_ID SOURCE_TYPE_CODE Stores information about requisition-lines. Line number, item number, item category, item description, need–by date, deliver–to location, item quantities, units, prices, requestor, notes, and suggested supplier information for the requisition line. LINE_LOCATION_ID - Purchase order shipment line on which you placed the requisition. It is null if you have not placed the requisition line on a purchase order. BLANKET_PO_HEADER_ID and BLANKET_PO_LINE_NUM store the suggested blanket purchase agreement or CATALOG quotation line information for the requisition line. PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID from the original requisition line if you exploded or multisourced this requisition line. Table Name : PO_HEADERS_ALL Columns: PO_HEADER_ID AGENT_ID TYPE_LOOKUP_CODE SEGMENT1 SUMMARY_FLAG ENABLED_FLAG Information for your purchasing documents. There are six types of documents that use PO_HEADERS_ALL. RFQs, Quotations, Standard purchase orders, planned purchase orders, Blanket purchase orders, Contracts can uniquely identify a row in PO_HEADERS_ALL using SEGMENT1 and TYPE_LOOKUP_CODE or using PO_HEADER_ID.BLANKET_TOTAL_AMOUNT for blanket purchase orders or contract purchase orders. If we use copy document Oracle Purchasing stores the foreign key to your original RFQ in FROM_HEADER_ID. Table Name : PO_LINES_ALL Columns: PO_LINE_ID PO_HEADER_ID
LINE_TYPE_ID LINE_NUM Stores current information about each purchase order line. CONTRACT_NUM reference a contract purchase order from a standard purchase order line. Table Name : PO_VENDORS Columns: VENDOR_ID VENDOR_NAME SEGMENT1 SUMMARY_FLAG ENABLED_FLAG Information about your suppliers. Purchasing, Receiving, Payment, Accounting, Tax, Classification, and General Information. Table Name : PO_VENDOR_SITES_ALL Columns: VENDOR_SITE_ID VENDOR_ID VENDOR_SITE_CODE Information about your supplier sites. A row for each supplier site you define. Each row includes the site address, supplier reference, purchasing, payment, bank, and general information. Oracle Purchasing uses this information to store supplier address information. Table Name : PO_DISTRIBUTIONS_ALL Columns: PO_DISTRIBUTION_ID PO_HEADER_ID PO_LINE_ID LINE_LOCATION_ID SET_OF_BOOKS_ID CODE_COMBINATION_ID QUANTITY_ORDERED DISTRIBUTION_NUM Contains accounting distribution information for a purchase order shipment line. You need one row for each distribution line you attach to a purchase order shipment. There are 4 - types of documents using distributions in Oracle Purchasing: · Standard Purchase Orders · Planned Purchase Orders · Planned Purchase Order Releases · Blanket Purchase Order Releases Includes the Destination Type, Requestor ID, Quantity Ordered and Deliver–To Location for the distribution.
Table Name : PO_RELEASES_ALL Columns: PO_RELEASE_ID PO_HEADER_ID RELEASE_NUM AGENT_ID RELEASE_DATE Contains information about blanket and planned purchase order releases. You need one row for each release you issue for a blanket or planned purchase order. Each row includes the buyer, date, release status, and release number. Each release must have at least one purchase order shipment. Table Name : PO_VENDOR_CONTACTS Columns: VENDOR_CONTACT_ID VENDOR_SITE_ID Stores information about contacts for a supplier-site. You need one row for each supplier contact you define. Each row includes the contact name and site. Table Name : PO_ACTION_HISTORY Columns: OBJECT_ID OBJECT_TYPE_CODE OBJECT_SUB_TYPE_CODE SEQUENCE_NUM Information about the approval and control history of your purchasing documents. There is one record in this table for each approval or control action an employee takes on a purchase order, purchase agreement, release, or requisition. · OBJECT_ID - Document header Identifier · OBJECT_TYPE_CODE - Document Type · OBJECT_SUB_TYPE_CODE - Document subtype · SEQUENCE_NUM - Sequence of the approval or control action for a document. Table Name : PO_REQ_DISTRIBUTIONS_ALL Columns: DISTRIBUTION_ID REQUISITION_LINE_ID SET_OF_BOOKS_ID CODE_COMBINATION_ID REQ_LINE_QUANTITY DISTRIBUTION_NUM Stores information about the accounting distributions associated with each requisition line.
Table Name : PO_LINE_LOCATIONS_ALL Columns: LINE_LOCATION_ID LAST_UPDATE_DATE LAST_UPDATED_BY PO_HEADER_ID PO_LINE_ID SHIPMENT_TYPE Contains information about purchase order shipment schedules and blanket agreement price breaks. You need one row for each schedule or price break you attach to a document line. There are 7- Types of documents that use shipment schedules: · RFQs · Quotations · Standard Purchase Orders · Planned Purchase Orders · Planned Purchase Order Releases · Blanket Purchase Orders · Blanket Purchase Order Releases Each row includes the location, quantity, and dates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information for purchase orders, and price break information for blanket purchase orders, quotations and RFQs.
Posted by Nil at 10:50 AM 0 comments Labels: Oracle Purchasing
Functional-- Purchase Order Flow
Functional --Purchase Order Flow Step 1:We will be raising the Requisitions for the items which are needed. Requisition is 2 types • Internal Requisition • Purchase Internal Requisition is used when we are getting the items from one organization to another organization of the same business group. Purchase Requisition is raised when we are getting the items from outside the business group. Step 2:Once the Requisition has been approved, we will be sending (Request For Quotes) RFQ’s to different Suppliers. It contains the information regarding the type of RFQ, terms and conditions, shipments, currency. RFQ is of 3 types
• Bid RFQ • Catalog • Standard BID: Used for a fixed specific quantity, Location and date. This will be used for large or expensive price of equipments. That you have never order before. There won’t be price any breaks for a BID Quotation. CATALOG: This will be used for high volume items for which your supplier sends information regularly. The CATALOG RFQ includes price breaks at different quantity levels. STANDARD: It is used for items we need only once or not very often for a specific fixed quantity, location and date. It includes price breaks at different quantity levels. Step 3:We will be receiving the quotations from different suppliers. Quotation is of 3 Types. • Bid • Catalog • Standard Step 4:Based on the quotations, we will be deciding the supplier and purchasing order is given to that supplier. Purchasing is of 4 types • Standard • Planned • Blanket • Contract Step 5:Once we receive the items from the Supplier we will issue the receipts to the Supplier. This is done in 3 ways. • Two-Way: In 2-way we will compare PO and Invoice.• Three-Way: In 3-way we will compare the PO, Receipt and Invoice.• Four-Way: In 4-way we will compare PO, Receipt, Inspection and Invoice.
2-Way Matching verifies that Purchase order and invoice information match within your tolerances as follows:Quantity Billed <-Quantity Ordered Invoice Price <- Purchase Order Price (<- Sign is used because of tolerances) 3-Way Matching verifies that the receipt and invoice information match with the quantity tolerances defined:Quantity billed Quantity received 4-Way Matching verifies that acceptance documents and invoice information match within the quantity tolerances defined:Quantity billed <- Quantity accepted. (Acceptance is done at the time of Inspecting goods).Whether a PO shipment has 2-way, 3-way or 4-way matching can be setup in the Shipment Details zone of the Enter PO form (character). RECEIPT REQUIRED INSPECTION REQUIRED MATCHING Yes Yes 4-Way Yes No 3-Way No No 2-Way In ‘More’ alternative region of Shipments block, you define the Invoice Matching option, where you can choose 2-way, 3-way or 4-way match. Step 6:Because of these Transactions Inventory and Payables get affected.
Posted by Nil at 10:40 AM 0 comments Labels: Oracle Purchasing
Jul 26, 2008
What is SQL* Loader?
SQL*loader is one of the Oracle tool which will be used to transfer the data from Flat-File to oracle Database table. We can find the fallowing files in SQL*loader 1. Flat or Data File 2. Control File 3. Bad File 4. Discard File 5. Log File Flat Or Data File: This file contains the records in a special format; these
records will be fetching for other legacy. The extension of these files might be .dat, .txt, or .csv (comma separated view). Control File: This is SQL loader execution file, which will be used to transfer the date from file to table. In side of these control file, we will mention the Data file path, table name, column mapping. The extension of control file is .ctl Control File Creation: Load data INFILE ‘Data File Path’ INSERT INTO ‘Table Name’ FIELD TERMINATED BY ‘,’ WHERE deptno = 10 TRAILING NULL COLS (column1 , empno column2, ename column3, deptno) Once we develop the control file we will execute this by using fallowing command C:\> sqlldr user/passward @ Database Control = name of control file (with extension .ctl) This command will start the control file execution, and it will try to read the data and inserting into table. After completion of this execution, automatically three files will gets created Bad file Discard file Log file Bad File: Bad file contain the records, which are rejected by the SQL*loader. SQL*loader will reject the records, when ever the Flat file format is not correct or if any internal error occurs it will rejected. The extension of bad file is .bad Discard File: Discard file contains the records which are rejected by the control file, control file reject the records, if record is not satisfying the conditions, which we have mentioned inside of control files the extension of discard file is .dis Logfile: It contains the complete info of the process, like no of records
successfully loaded in to the table No of records successfully loaded in to the bad file & discard file. And where the bad, discard file gets created and time taken to complete the process. Taking the complete log. SQL* Loader Modes: INSERT APPEND REPLACE We can replaced the data in to the table by using any one of the allowing method INSERT: When we are using this statement, table should be empty. SQL * loader will insert the new data form the file. APPEND: This mode will be use to attach the new record to the existing records. REPLACE: This will replace the existing records with new records. C:\> sqlldr userid/passward@Database control=text1.ctl path=direct SQL* Loader Paths: We can execution SQL* loader in two paths or nodes Direct Conventional By default SQL*loader will be running in conventional mode, if we want to run in direct mode will use the fallowing syntax C:\> sqlldr userid/passward@Database control=text1.ctl path=direct Direct mode will disable the table and column constrains and it will insert the data. Conventional path will check every constrains, if it is satisfied it will insert the record Conventional path is just like ‘insert statement’ SQL Commands Limitations: to_date, to_char, upper, lower, Initcap, string, decode, nvl when clause sequence_name.next_value, Ref-Cursor sysdate, ltrim, rtrim, constant
Posted by Nil at 4:29 PM 0 comments Labels: Concurrent programming, Working with SQL Loader
How to to make a PL/SQL procedure as a Concurrent Program?
PL/SQL Stored Procedures : If you want to make a PL/SQL procedure as a Concurrent Program, then we will define that procedure by using fallowing syntax Syntax: CREATE OR REPLACE PROCEDURE Procedure_Name (errbuf OUT VARCHAR2,
recoded IN VARCHAR2, x IN NUMBER, y IN NUMBER) AS BEGIN PL/SQL statements; Fnd_file.put_line (fnd_file.output, ’message’variables); Fnd_file.put.line (fnd_file.log, ’message’variables); END ; ERRBUF: Used to get the error messages in to the log file if any errors occur in side of procedure. RETCODE: Used to get the status of Concurrent Program The Status can be either 0 – for success 1 – for warning 2 – for error Inside of procedure body we can use all valid PL/SQL statements except DBMS_OTUPUT.PUT_LINE Instead of this we will use fallowing to API’S (Application Programming Interface). API is nothing but a package. • Fnd_file.put_line(fnd_file.output,’message’variables); - is write for the output file. • Fnd_file.put.line(fnd_file.log,’message’variables); - is used for log file. Steps for Developing the Procedure: 1. Develop the procedure as per client requirement. 2. Create an executable with execution method as PL/SQL stored procedure 3. Define the Concurrent Program at as • EXECUTION • PARAMETER • INCOMPATIBILITIES PROGRAM 4. Attach the Concurrent Program to the request group. 5. Attach the request group to the responsibility. 6. Attach the responsibility to user. 7. User will submit program from SRW window
Posted by Nil at 4:04 PM 0 comments Labels: Concurrent programming
How to Run the SQL script from the Concurrent Program?
If we want to run the SQL script from the Concurrent Program window then we should follow the below steps. 1. Develop the SQL*plus (.SQL) 2. Transfer the SQL script file (.sql) file from local machine to the server in to respectable path CUST_TOP/11.5.0/SQL/.SQL
Then we have to follow the steps to implement (to run from Concurrent Program window) in Oracle Applications. 1. Create executable by executable method SQL*plus 2. Define Concurrent Program, attach executable, parameters, incompatibilities 3. Attach Concurrent Program to request group. 4. Attach request to responsibility 5. Attach responsibility to user 6. User will submit from SRS window. Simple SQL Script: Column user_id format 99999999 Column user_name format a50 Column ucreation_date format a11 Prompt ***************************** Prompt This is SQL* Plus Script Prompt ***************************** SELECT user_id, user_name,creation_date FROM end_user; SQL Script with Parameter: Inside of SQL script we can receive the parameter value by using &1, &2, &3 and so on. First Concurrent Program parameter value will come in the place, where we have mention &1. Second Concurrent Program parameter in to &2 and so on… Note: We can define max of 100 PARAMETERS for a Concurrent Program. The Format Type of Concurrent Program output should be ‘TEXT’.
Posted by Nil at 4:00 PM 0 comments Labels: Concurrent programming
What Are Standards for Report Developments in Oracler Apps?
Oracle Applications Standards for New Report Developments... For developing a Report in Oracle Applications we should follow three standards. 1. Creation of Bind Variable - P_CONC_REQUEST_ID: We must create a Bind Variable called “P_CONC_REQUEST_ID” (We can’t change this name. It is standard name.). If we run Conc. Prgm. from SRS window, it will give a Request ID. It will get store in ‘P_CONC_REQUEST_ID” automatically. This Bind Variable is useful, when we call another Conc. Prgm. with in a Conc. Prgm.
2. FND SRWINIT in Before Report Trigger: We call the USER_EXIT (‘FND SRWINIT’) form Before Report Trigger. Syntax is SRW.USER_EXXIT(‘FND SRWINIT’): This USER_EXIT is initializing the user profiles in the report trigger i.e., before getting the date from the Database. Note: While executing the Conc. Prgm. the system allocate memory for the program which contains all details of user. In above syntax, SRW.USER_EXIT refers to D2K and purpose of this is, when we want to transfer the control from execution of report to other 3rd generation language and again transfer the control to report execution. FND SRWINIT refers to Oracle Applications. Purpose of this is to get the “User Profile”. 3. FND SRWEXIT in After Report Trigger: We call the USER_EXIT (‘FND SRWEXIT’) form After Report Trigger. Syntax is SRW.USER_EXXIT (‘FND SRWEXIT’): This USER_EXIT is frees the memory which is occupied by user profiles.
Posted by Nil at 3:14 PM 0 comments Labels: Report Developmet in Apps
Navigation Path for Value Set Creation?
Navigation Path for Value Set Creation: Application-> Validation -> Set. Once we create Independent & Dependent valueset then we can attach values to the valueset by using the following Navigation. Application -> -> Validation -> Values (To create values for value set) NOTE: Once we attach any value to Independent & Dependent we can’t delete that value, but we can disable that value. Duplicate values are not allowed in list of values. Develop a Report using Query and by creating valueset : Select USER_ID, USERNAME From FND_USER Where USER_ID Between :X AND :Y :$FLEX$ - It is One of the Oracle applications Key word which we use to get the prevents parameter value in current list of values “WHERE Clause”. We can be use Table Values in the “Where Clause Box”. Query Using: $FLEX$ Select VENDOR_SITE_ID From PO_VENDOR_SITE_ALL Where
VENODR_ID = :$FLEX$.VEN_TABLE Note: We can give Where Clause Condition in creation of Second Value Set. Practical: Query: Select * From ORF_ORGANIZATION_DEFINATIONS Where ORGANIZATION_ID = :P_ORG_ID And BUSINESS_GROUP_ID = :P_BUSINESS_GROUP_ID In Where Clause write the statement as Where BUSINESS_GROUP_ID = :$FLEX$.BUISINESS_GROUP Range: When ever we have to restrict the user with in the given values we use Range. For example when ever our parameter is having “From Date and To Date” we have to use Range option to restrict the user to enter the values between Low and High. Note: Pre defined value set for date is “FND_DATE” and its default format is “DDMON-YY”.Alias name is mandatory when we are specifying ‘:$FLEX$’ and Column Name in ‘Additional Column’.
Posted by Nil at 3:05 PM 0 comments Labels: Value Sets
Jul 22, 2008
What is Value Sets? What are Types Of Value Sets?
Oracle Application Object Library uses values; value sets and validation tables as important components of key FLEXFIELDs, descriptive FLEXFIELDs, and Standard Request Submission. This section helps you understand, use and change values, value sets, and validation tables. When you first define your FLEXFIELDs, you choose how many segments you want to use and what order you want them to appear. You also choose how you want to validate each of your segments. The decisions you make affect how you define your value sets and your values. You define your value sets first, either before or while you define your FLEXFIELD segment structures. You typically define your individual values only after your FLEXFIELD has been completely defined (and frozen and compiled). Depending on what type of value set you use, you may not need to predefine individual values at all before you can use your FLEXFIELD. You can share value sets among segments in different FLEXFIELDs, segments in different structures of the same FLEXFIELD, and even segments within the same FLEXFIELD structure. You can share value sets across key and descriptive FLEXFIELDs. You can also use value sets for report parameters for your reports that use the Standard Request Submission feature.
Because the conditions you specify for your value sets determine what values you can use with them, you should plan both your values and your value sets at the same time. For example, if your values are 01, 02 instead of 1, 2, you would define the value set with Right–Justify Zero–fill set to Yes. Value set is nothing but List of Values with validations. We can use the Value Sets when ever the Concurrent Program has parameters and while defining the Flex Fields. We have to attach the value sets to the Concurrent Program. Validations are depending on Client Requirement. Value sets are of 8 types. There are several validation types that affect the way users enter and use segment or parameter values: 1. None (not validated at all) 2. Independent 3. Dependent 4. Table 5. Special (advanced) 6. Pair (advanced) 7. Translatable Independent 8. Translatable Dependent You cannot change the validation type of an existing value set, since your changes affect all FLEXFIELDs and report parameters that use the same value set. None: You use a None type value set when you want to allow users to enter any value so long as that value meets the value set formatting rules. That is, the value must not exceed the maximum length you define for your value set, and it must meet any format requirements for that value set. For example, if the value set does not allow alphabetic characters, your user could not enter the value ABC, but could enter the value 456 (for a value set with maximum length of three). The values of the segment using this value set are not otherwise validated, and they do not have descriptions. Because a NONE value set is not validated, a segment that uses this value set does not provide a list of values for your users. A segment that uses this value set (that is, a non–validated segment) cannot use FLEXFIELD value security rules to restrict the values a user can enter. Independent > An Independent value set provides a predefined list of values for a segment. These values can have an associated description. For example, the value 01 could have a description of ‘Company 01’. The meaning of a value in this value set does not depend on the value of any other segment. Independent values are stored in an Oracle Application Object Library table.
You define independent values using an Oracle Applications window, Segment Values. Table > A table–validated value set provides a predefined list of values like an independent set, but its values are stored in an application table. You define which table you want to use, along with a WHERE cause to limit the values you want to use for your set. Typically, you use a table–validated set when you have a table whose values are already maintained in an application table (for example, a table of vendor names maintained by a Define Vendors form). Table validation also provides some advanced features such as allowing a segment to depend upon multiple prior segments in the same structure. Dependent > A dependent value set is similar to an independent value set, except that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the FLEXFIELD structure. You can think of a dependent value set as a collection of little value sets, with one little set for each independent value in the corresponding independent value set. You must define your independent value set before you define the dependent value set that depends on it. You define dependent values in the Segment Values windows, and your values are stored in an Oracle Application Object Library table. Special and Pair Value Sets: Special and pair value sets provide a mechanism to allow a”FLEXFIELD–within– a–FLEXFIELD”. These value sets are primarily used for Standard Request Submission parameters. You do not generally use these value sets for normal FLEXFIELD segments. Special and Pair value sets use special validation routines you define. For example, you can define validation routines to provide another FLEXFIELD as a value set for a single segment or to provide a range FLEXFIELD as a value set for a pair of segments. Translatable Independent and Translatable Dependent : A Translatable Independent value set is similar to Independent value set in that it provides a predefined list of values for a segment. However, a translated value can be used. A Translatable Dependent value set is similar to Dependent value set in that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the FLEXFIELD structure. However, a translated value can be used. FLEXFIELD Value Security cannot be used with Translatable Independent or Translatable Dependent value sets. For format validation, translatable value sets must use the format type Char. The maximum size must be no greater than 150. The Number Only option and the Right–justify and Zero–Fill Numbers option cannot
be used with translatable value sets. Range FLEXFIELDs cannot use Translatable Independent or Translatable Dependent value sets.
Posted by Nil at 9:33 AM 0 comments Labels: Value Sets
How to Develope Report with out Parameters?
Developing Report with out Parameters: To develop any report in Report-6i tool, select “Build a new Report Manually” option. Select SQL query object and write the Select Statement. It will ask the Database connection. Provide User id, Password and Connection string (DB host) – APPS/APPS@ORCL. Create Layout manually according to the given query. Compile the report with out errors. Save the report in Local Machine. Copy the Report and paste it in respective path (Respective TOP). Path - APPS/ D / Oracle / PROD_APPL / PO / 11.5.0 / Reports / US / .rdf Implementing Report in Oracle Applications: Connect to APPS Server. Create Executable for created report. Navigation: System Administrator ->Responsibility -> Concurrent Program ->Executable Mandatory Fields in this window are: Executable, Short Name, Application, Execution File Name Note: From here we can refer the Report (Executable) with Short Name; Create the Concurrent Program for this Executable. Navigation: System Administrator ->Concurrent -> Program -> Define Give the required information like Program, Short Name, Application, Executable (Name, Method), Output (Format…) etc. Create Request Group. Navigation: Security -> Responsibility -> Request Here we have to give information like Group (RG Name), Application (E.g.
Oracle Purchasing) Add the Concurrent Program as Request to Request Group which is created. Create Responsibility. Navigation: Security -> Responsibility ->Define While creating Responsibility we need to mention three things. · Data Group – Required. It is nothing but Oracle User ID · Menu – Required. Collection of Forms, which are related to specific business · Request Group – Optional. Collection of Concurrent Programs and Reports which are related to specific business Note: If we create Responsibility with Request Group, no need to add RG again to Responsibility. Create User. Navigation: Security -> User -> Define Attach the Responsibility to User. Run the Concurrent Program from SRS window. Note: All the Concurrent Programs should run from SRS (Standard Request Submission) window. How to go to SRS window: Select relative Responsibility (FILE à Switch Responsibility) Go to View à Requests à Submit New Request à Select the Report à Click Submit After Submission it will give Request ID. Here 2 fields View Report, View LOG File will give information of the Resultant file created by Concurrent Program. Note: · We can find all O/P and LOG files by the following query from the Database. Select LOGFILE_NAME, OUTFILE_NAME From FND_CONCURRENT_REQUESTS Where REQUEST_ID = ‘XXX’; · We can’t delete Concurrent Program but we can disable it. · Columns and Rows fields will be used to mention the O/P file Columns and Rows. · Save, This Check Box can use to save the O/P file in the server. · Use in SRS, if we uncheck this Check Box, then this we can’t run this program from SRS window. · Copy To, We can create new for the existing Report. Scheduling the Concurrent Program: We can schedule the Concurrent Program in 4 ways. · As Soon As Possible (Default)
· Once · Periodically · On Specific Days We can save the Schedule and can apply this Schedule to any other Concurrent Program. We can run with a message in the LOG File by using SRW.MESSAGE() function. Develop Report with Parameters: There are 2 types of Parameters. 1. Bind parameters 2. Lexical Parameters Bind Parameter: Bind parameter is a variable which we will use to pass the value. We should use ‘:’ before any variable in a query. Lexical parameter: Lexical parameter is a parameter which we will use inside of a query. By using this parameter we can replace any clause or any where inside of the statement like Select, From, Where, Order By clauses. If our report has parameters then we should define parameters from the report while creating Concurrent Program. While defining the parameters we should mention following fields. It is a list of values with validations. We have to use value set for a parameter. By using this we can restrict the invalid entries by the end-user. Prompt: This field will use to display the string while submitting the Concurrent Program in the Parameter Form. Token: It is a field which is use to give the link between Concurrent Program Parameter and report Bind Variable. When we create Bind Variables in report those may or may not be in the same sequence. So we can map these bind Variable with the Token fields. Required Check Box: If we uncheck this, the parameter is optional, otherwise it is mandatory. Default Types: There are 4 default types. · Constant · Profile · SQL Statement · Segment Constant: We can select this default type if we have to pass the constant value to parameter of the Concurrent Program. We can mention the value in the “Default Value Field” at right side. Profile: SQL Statement: If we have to set the default value as SQL Query result set then we should select default value type is SQL Statement and we have to enter the SQL Query in the ”Default Value field”. Segment: If we want to get previous parameter value as default to the next parameter, we have to select the default type as Segment and we have to give
the previous parameter name in “Default Value Field”. Note: The query which we have to enter in default value field should give only one value Using the format trigger we can hide or display the “Layout Object”. This layout object can be a Field or Text. We can display input parameter values in the first page (or any other pages) by using Bind Variables.
Posted by Nil at 9:24 AM 0 comments Labels: Report Developmet in Apps
Jun 29, 2008
What are Steps for Report Development in Apps?
Steps for Report Development.... 1. Develop the report as per client requirement using the Report-6i tool. 2. Move the report (.rdf) file from local machine to respective path in the server. If client have the CUST_TOP then move into Cust_Top else move it to the related Standard Top.Custom Top - CUST_TOP/ 11.5.0/ Report/ US/ .rdf Standard Top - PO_TOP/ 11.5.0/ Report/ US/ .rdf (For PO report) 3. Create “Executable” for that report (After log on to Oracle Applications and Select “System Administrator” responsibility) 4. Create “Concurrent Program” and attach Executable to Conc. Prgm. and define Parameters and Incompatibles if any.Concurrent Program: It is an instance of the executable file along with parameters & incompatible. 5. Create “Request Group” and attach Conc. Prgm. to Request Group.Request Group is nothing but a collection of Conc. Prgms. 6. Create “Responsibility” and attach the Request Group to Responsibility. 7. Create “User” attach Responsibility to User” so that the user can run this Conc. Prgm. form the “SRS Window” (Standard Request Submission).Note: All the Conc. Prgms. should run from the SRS window (Even if we run from BackEnd)By default the user has the rights of System Administrator or Application Developer responsibilities Every form in Oracle Applications contains 3-Types of Fields.1. Yellow color – Mandatory2. Green Color – Read-Only3. White Color – Optional User Creation:Open IE and type path of Oracle Application in address bar enter User Name and PasswordUser Name: OPERATIONSPassword: WELCOMESelect System Administrator Responsibility Select Security / User / DefineGive the required information and Save. Switch the user to newly created User.Note: When we create any User, the User stored at FND_USER. We can find throughHelp >Record-History >FND_USER Column Name: To find all column names: Help >Diagnostics >ExamineWHO Columns: 4 types of who columns for each table in Oracle ApplicationsCreated ByCreation DateUpdated ByUpdated Date
Posted by Nil at 6:29 PM 0 comments Labels: Report Developmet in Apps
What are Types of Documents in Oracle Applications :
AIM (Application Implementation Maintenance) developed by Oracle Applications. MD050 - Module Design - By Functional Consultants MD070 - Technical Document Design - By Technical Consultants MD020 - Testing Document Design - By Functional Consultants MD0120 - Migration/ User Training - By Technical Consultants CV040 - Conversion of Functional Document - By Functional Consultants CV060 - Conversion of Technical Document - By Technical Consultants Note: Conversion means, moving data from old Database to new Database. Example: Conversion from IBM to ORA APPS
Posted by Nil at 6:24 PM 0 comments Labels: AIM
This action might not be possible to undo. Are you sure you want to continue?