add

About Me

My photo
Oracle Apps - Techno Functional consultant

Monday, September 9

Oracle Applications Interview Questions (FAQS)



Q1. Is it possible to show more than two decimal places in the "PRICE" column that is currently being printed on the 'Printed Purchase Order Report - (Landscape or Portrait)'?

A: Currently, it is not possible to print more than two decimals in the 'PRICE' field without customizing the reports. There is currently an enhancement request (628857) under review that will, if approved, bring this desired functionality to future releases. This answer holds true to Releases 10.7, 11.0, and 11.5 (11i).

  
Q2. When I print out a purchase order from the Document Approval window, does it only print in Portrait style?

A: Currently this is the only way it will print from the Document Approval window. An enhancement request (466551) has been filed to allow the choice of either Portrait or Landscape as the format when printing purchase orders from the Document Approval window.

  
Q3. Why does the blanket purchase agreement print every time a release is printed?

A: This is the current functionality of the application. The blanket purchase agreement will be printed every time you choose to print an associated release. An enhancement request (432017) has been filed to allow only the release to be printed.

  
Q4. What is the name of the file that controls printing of reports related to Oracle Purchasing, and where is it located on the system?

A: The name of the file is porep.odf. This file creates the Oracle Purchasing views which generate the data that is printed by the reports. The file can be found in the following locations:

$PO_TOP/admin/odf This is where the base release version of the file is seeded by the install.
$PO_TOP/patch/110/odf This is where the most current version of the file resides on your system for Release 11.
$PO_TOP/patchsc/107/odf This is where the most current version of the file resides on your system for Release 10.7.
For Windows NT, it is best to use the FIND FILE utility to locate the various versions of the file.

  
Q5. How can a report file name and version be located?

A: There are two methods that can be used to find the report short (file) name:

1. Please see Note 106968.1, titled "Purchasing: PO Report Short Names". This note contains an alphabetical listing of all Oracle Purchasing reports and lists the short name for each one.

2. Each report is a concurrent process that can be found in System Administration.
- Responsibility: System Administrator
- Navigation: Concurrent > Program > Define
- Select the Program Name
Under the Program Name field, you will see a field called Short Name. This is the name of the report file. This name should be the same as the name of the file in the Executable field.

To find the version of the file:

For Unix
********
For Release 10.7, go to $PO_TOP/srw
For Release 11, go to $PO_TOP/reports

Type the following command at a Unix prompt:
strings -a <FILENAME.rdf>|grep Header:

For Windows NT
**************
Use the FIND FILE utility to locate the file. Use MS-DOS to navigate to the
file and type the following command at the prompt:
find /i "Header:" <FILENAME.rdf>

 
Q6. Why do asterisks (******) appear on report output in place of the quantity? 

A: Oracle Reports will allow a maximum of 13 characters to be printed in the Quantity column. These characters include a -/+ sign at the beginning and then a combination of 12 more characters, including commas, periods, and digits. Therefore, if the quantity on a report contains more than 13 characters, you will see the asterisks show in place of the quantity.

Examples:
 
9,999,999.00 actually contains 13 characters and will be displayed. Remember, the + sign is holding the first character position in the database.
-1.2245833524335 would print asterisks, as more than 13 characters are involved.

You do have the ability to change the way your reports print out the numbers in the Quantity region; this may make the difference in allowing you to see the actual quantity. You cannot change the number of characters in the field, but you can change the way they display. This will give you more options. To do this:
Responsibility: System Administrator
Navigation: Profiles/System
Query the profile 'INV: Dynamic Precision Option for Quantity on Reports'
Click on the List of Values and you will see the different options available for you to use on your reports. You will notice that all options still only represent 13 characters; it just changes the way they are represented.

See Note 1072855.6 for further clarification.

 
Q7. When a report has been submitted to print, the output can be viewed by using the View Output button, but no hard copies of the report print out. What causes this to occur?? 

A: The number of copies Oracle Reports will print is controlled in System Administration.
Responsibility: System Administrator
Navigation: Profiles/System
Query the profile 'Concurrent: Report Copies'
If this profile is not populated, Oracle will not print any copies of any report.
FAQ Details
Q1. How do the 'Accrued Receipts' and 'Include Online Accruals' parameters determine the output of this report?

A: The values of these parameters control which purchase orders are eligible to be printed on the report. Each of these parameters can be set to 'Yes' or 'No', thus giving four (4) combinations total; here are the four combinations possible and what the expected output can be:

A. Accrued Receipts = Yes
Include Online Accruals = No

Using these settings, the report output will include purchase orders that have a value in either the Item and Category fields or just the Category field. In this scenario, the PO_DISTRIBUTIONS_ALL table will have the following values:
ACCRUED_FLAG = Y
ACCRUE_ON_RECEIPT_FLAG = N

B. Accrued Receipts = Yes
Include Online Accruals = Yes

Using these settings, the report output will include purchase orders that have a value in both the Item and Category fields. In this scenario, the PO_DISTRIBUTIONS_ALL table will have the following values:
ACCRUED_FLAG = Y
ACCRUE_ON_RECEIPT_FLAG = Y

C. Accrued Receipts = No
Include Online Accruals = Yes

Using these settings, the report output will include purchase orders that have a value in either the Item and Category fields or just the Category field. In this scenario, the PO_DISTRIBUTIONS_ALL table will have the following values:
ACCRUED_FLAG = N
ACCRUE_ON_RECEIPT_FLAG = Y

D. Accrued Receipts = No
Include Online Accruals = No
 

Using these settings, the report output will include purchase orders that have a value in just the Category field. In this scenario, the
PO_DISTRIBUTIONS_ALL table will have the following values:
ACCRUED_FLAG = N
ACCRUE_ON_RECEIPT_FLAG = N

  
Q2. Does the Uninvoiced Receipts Report take the Currency Rate from the purchase order header or its individual distribution lines?


A: The Uninvoiced Receipts Report was initially designed to take the Currency Rate from the header of the purchase order. Bug 1396659 was logged, for Releases 10.7 and 11.0, initially as an enhancement request to change the report to look at the individual distribution lines; this enhancement will be enabled in Purchasing patch set P for Release 10.7, and in Purchasing mini-pack G for Release 11.0.

For Release 11i, this issue is currently being reviewed and the change may not be made since Release 11i allows the users to override the currency rate at the time a receipt is entered.

  
Q3. Will a cancelled purchase order line appear on the Uninvoiced Receipts Report?

A: Yes, a cancelled line will continue to show on the Uninvoiced Receipts Report.

  
Q4. Will a closed purchase order line appear on the Uninvoiced Receipts Report?

A: No, closed purchase order lines do not show on the Uninvoiced Receipts Report.

  
Q5. POXPORRA - Uninvoiced Receipts Report Returns No Data Or Wrong Data?

A: Ensure that the correct values used for the parameters Accrued Receipts and Include Online Accruals when running the report. These parameters are listed as optional but they are essential in determing which transactions are included in the report output.

1. For receipts (for expense items) that Accrue At Period-End and have not been accrued:
Accrued Receipts=No
Include Online Accruals=No

2. For receipts (for expense items) that Accrue At Period-End and have been accrued or have not been accrued:
Accrued Receipts=Yes
Include Online Accruals=No

3. To include receipts for expense or inventory items that Accrue On Receipt and have been accrued or have not been accrued:
Accrued Receipts=Yes
Include Online Accruals=Yes

4. To include receipts for expense or inventory items that Accrue On Receipt and have not been accrued:
Accrued Receipts=No
Include Online Accruals=Yes.

 
Q6. Uninvoiced Receipts Report Does Not Reconcile With Accrual Journals in General Ledger? 

A: Apply patch 2274733. Patch 2274733 contains updated versions of the Uninvoiced Receipts Report 
(POXPORRA.rdf 115.23) and the code used by the Receipt Accruals - Period-End process.

 
Q7. Uninvoiced Receipt Missing From the Uninvoiced Receipts Report? 

A: To correct this problem, take the following steps:
1. Under Purchasing responsibility > Purchase Order > Purchase Order Summary.
2. Query the PO of interest.
3. From the menu, navigate to Special > Control.
4. Select Open or Open for Invoicing.
5. Save.

 
Q8. The Uninvoiced Receipts Report does not Balance to the General Ledger?

A: Update the below files to the versions shown or higher. Apply Patch 1705773 or later. 
rvacj.lpc 115.23
rvcac.opc 115.8.

 
Q9. The Uninvoiced Receipts Report does not Calculate tax properly.

A: Apply patch 1977474. This will upgrade the version of POXPORRA.rdf to 115.15.
The patch modifies the formula column C_Dist_Amount_Accrual so as to pro-rate the tax amount based on dist_quantity ( dist qty ordered - dist qty cancelled) and dist_quantity_accrued.
FAQ Details
Q1. What does invoice price variance report show?

A: Invoice price variance report shows the variance between the invoice price and the purchase price. 
The layout is in the following format:
 
Vendor
 
Po Details
 
Invoice details and Variances
 
Charge and variance account.

  
Q2. Does the UOM in which the price and quantity is reported depends on the way the invoice is matched?

A: Yes, the UOM in which the price and quantity is reported depends on the way the invoice is matched.
1. If the invoice is matched to a PO then the UOM in which price and quantity is matched is as per the UOM of the PO or Invoice. Both are same in this case.
2. If the UOM is matched to a Receipt then the following fields are calculated as per the UOM of the receipt.
 
(The UOM of the receipt may or may not be the same as that of the PO).
The PO Functional Price and the Invoice price variance.
 
The Unit is still as per the PO UOM. This is because the Unit in the report is shown at the PO level.

  
Q3. Where do you set the Invoice match option? 

A: 1. Purchase orders shipment window or 
2. Supplier site.
 
The match option defined at the Purchase order shipment window has a preference over that of Supplier site.

  
Q4. Which PO rate is considered for calculating the variance? 

A: The rate at the distribution level is given preference. If this is null then only the rate from PO headers is taken to calculate the variance.

  
Q5. What are the main tables used in this report?

A: 1. ap_invoice_distributions 
2. ap_invoices
 
3. po_headers
 
4. po_distributions
FAQ Details
Q1. What does Receipt Traveler report show and how is it organized?

A: The Receipt Traveler facilitates receiving inspection and delivery of goods you receive within your organization. 
After you receive the goods, you can print receipt travelers and attach these tickets to the goods. You can enter selection criteria to specify the receipt travelers you want to print. One receipt traveler prints per distribution, and each traveler has space for you to record delivery comments.
 
It prints in the following format:
 
Item
 
Source (Supplier/Inventory/Internal requisition/RMA)
 
Receipt
 
Delivery Instructions
 
Lot and Serial Number
 
Wip Shortage

  
Q2. Which PO level does the report print? 

A: The report prints at the distribution level only if delivery has been made, else it prints the receipt transaction.

  
Q3. How many pages does the report print for single/multiple shipments and single/multiple distributions? 

A:


<ALIGN=LEFTPages
<ALIGN=LEFT<ALIGN=LEFTFor One shipment line and No distribution
1
<ALIGN=LEFT<ALIGN=LEFTFor One shipment line and One distribution
1
<ALIGN=LEFT<ALIGN=LEFTFor One shipment line and Two distributions
2
<ALIGN=LEFT<ALIGN=LEFTFor Two shipment lines with Two distributions each
4


  
Q4. Which are the most used views and tables in this report?

A: Views 
1. RCV_RECEIPTS_PRINT
 
2. RCV_DISTRIBUTIONS_PRINT
 
Table
 
1. RCV_TRANSACTIONS

  
Q5. Which transactions get printed on Receipt Traveler?

A: A receipt Traveler Report gets automatically printed under the following conditions: 
- A standard receipt is performed.
 
- A direct delivery is performed.
 
- Matching of an unordered receipt.

 
Q6. What are the profile options used for this report? 

A: Following are the two profile options used for this report: 
RCV: Print Receipt Traveler (Yes/No)
 
Concurrent: Report Copies (Number of copies you want to print).
 

 
Q7. What could be the problem for report printing a blank page? 

A: If the receipt is saved after the header information is added, the receipt traveler kicks off. 
Because the line information has not been completed. The report only prints the header information and a blank page. If the header information and the line information is complete the receipt traveler will print with all correct information.

 
Q8. Can Receipt Traveler be printed if the RMA is received in a different Operating Unit than where it was created? 

A: Yes.
FAQ Details
Q1. What are the different authorization_status can a requisition have? 

A: Approved, Cancelled, In Process, Incomplete, Pre-Approved, Rejected, or Returned. 

  
Q2. Can an approved requisition be viewed in the Requisition form?

A: No, an approved requisition cannot be viewed in the Requisition form. Approved or In Process requisitions can only be viewed in the Requisition Summary form. Only Requisitions, which have Incomplete, Returned, and Rejected status, can be viewed from Enter Requisition form.
  
Q3. Can an approved requisition be revised?

A: No, an approved requisition cannot be revised. 

  
Q4. Why is there no list of values for items in the requisition form after they have been defined in the item master? 

A: The list of values should be available. Please review Supplier-Purchasing information for the Financial Options to ensure the correct organization has been selected for the Inventory Org. Setup-> Organizations->Financial Options->Supplier-Purchasing 

  
Q5. Is the Supplier item field a validated field? 

A: No, the supplier item field is not a validated field. It is for reference only. 

  
Q6. How can you have specific Requestor defaulted on Requisition form? 

A: In order to have a specific requestor default onto the requisitions form, the user will have to set the following in the user will have to set the following in the user's requisition preferences. Navigation: /Purchasing -> Requisitions -> Requisitions Go to special ->preferences Click in the requestor field Choose a requestor from the list of values Click the 'apply' button, a message ' new preferences now in effect.' Close the requisitions form Re-open the requisitions form Click in the lines region, the requestor from requisition preferences should appear in the requestor field. The requisition preferences are only valid while working on it , user needs to re enter requisition preferences each time he starts the applications. 

  
Q7. Can I change the item number in requisition lines after saving the record? 

A: User is not allowed to change the item number of a saved record in Oracle Purchasing Requisition Form. If user finds that the item entered by him in a saved record is wrong then he has to delete that record and enter a new record for the required item. User is allowed to change the Type, Description, UOM, Quantity, Price, Need by date in a saved record in the Enter Requisition form. Also he can change the item category if item number of the saved record in the Enter Requisition Form is NULL. 

  
Q8. What all control actions I can perform on a requisition through Document control window? 

A: Cancel and Finally close.

  
Q9. What is the authorization_status of a requisition after Finally closing it? 

A: When we finally close the requisition from Requisition Summary form the authorization_status of the requisition does not change. Instead it's closed_code becomes 'FINALLY CLOSED'. 

  
Q10. Can I cancel or finally close any requisition from Document Control Window?

A: No. Purchasing lets you cancel or final close a requisition or requisition line before your manager approves it or before a buyer places it on a purchase order. No control actions can be performed on an Incomplete requisition. You cannot Finally close a 'Pre-Approved' Requisition. 

  
Q11. What happens if the requisition cancelled of finally closed through Document Control Window and encumbrance is on? 

A: If you are using encumbrance or budgetary control, Purchasing automatically creates negative debit encumbrance entries for the cancelled requisitions. When you final close a purchase order, Purchasing creates credit entries which reverse the encumbrances. 

  
Q12. How can I confirm that my requisition has sufficient funds? 

A: Go to (M) Special->Check for funds. 

  
Q13. How can I find out, which all requisition lines have went into purchase order?

A: In Requisition Summary form (M) Special-> View Purchase Order. In the 'Special' Menu itself you can see the option' View Sales Order'. 

  
Q14. What does the status Pre-Approved mean, and how does a document reach this status?

A: The status of Pre-Approved is the outcome of a person forwarding a document for approval even though the forwarding person has the necessary authority to approve it. The document may have been forwarded by mistake or for business reasons. It is not possible to perform a receipt against a document with a status of Pre-Approved.

  
Q15. When you try to 'Save' a requisition, the following message appears: PO_ALL_POSTING_NA.

A: This happens when you do not have a valid code combination for the accounts defaulting on the distribution account. Ensure that the account has a valid code combination.

  
Q16. While forwarding requisition for approval, error APP-14056: User exit po find_forward returned error. 

A: There is no Forward Method specified in the setup. The FIND_FORWARD function cannot find any rules to determine the forward to person. Navigate to the Document Types Form (POXSTDDT) in Purchasing Responsibility. Setup -> Purchasing -> Document Types. Select the document type of Requisition (Internal or Purchase) and make sure that the field 'Forward Method' is not blank. If it is blank, set it to either Hierarchy or Direct, then save. 

  
Q17. Unable to enter Project information on the Distribution line of a Requisition. 

A: You cannot enter project information for inventory destinations (unless you have Project Mfg installed). Setting Destination Type = Expense will resolve the problem. You will then be able to enter information in the remaining Project related fields.

  
Q18. When a requisition is autocreated to a purchase order, supplier information is not populated in the purchase order header. 

A: This happens when a requisition number is entered in the Find Requisition Lines window and document is autocreated. But if you enter the requisition number and supplier details in the Find Requisition Lines window and autocreated the document to purchase order. The purchase order now contains supplier details in the purchase order header. Supplier information at the requisition level is actually a suggested Supplier, and the buyer has an option to decide which supplier to pick on the PO header. Also, if you try to Autocreate multiple requisitions with different Suppliers Autocreate would not know which supplier to use. Hence the vendor information cannot be defaulted. This is the standard functionality of Oracle Applications. Workarounds: 1 - Enter the suggested supplier on the 'Find Requisition Lines' Search Criteria window and this is populated on PO header when autocreated. 2 - Enter the supplier information in the 'Select Purchase Order' zone. 

  
Q19. The system does not allow you to change the Price and / or quantity of an approved Requisition line before AutoCreating a Purchase Order. 

A: When you are using Encumbrance Accounting, by enabling the Budgetary Control flag for a set of books, the system automatically creates encumbrances from Requisitions, Purchase Orders and other transactions originating from modules such as Purchasing & Payables. 
In this case, the funds are checked at the Requisition Level. You cannot change the Price and Quantity once the requisition has been approved. This is the Standard functionality of Oracle Applications.
 
After Autocreating a Purchase Order, you can change the quantity and price.

  
Q20. Cannot find a Document in the Notifications form which has been forwarded by an intermediate Approver.

A: Several things with Oracle Workflow can cause documents to be stuck 'in process', however, this particular issue deals with duplicate data in your HR system. 
Using your SysAdmin responsibility, navigate to Security-->User-->Define and perform a query on the Person field using the employee name of the approver you are trying to forward the document to.
 
This should return a record for only 1 user. If the employee is assigned to more than 1 user name, Workflow will not know who to deliver the notification to and the document will hang with a status of 'in process'.
 

  
Q21. Cannot find cancel requisition option in requisition summary form. 

A: Please check for the sql script poxdocon.sql. This can be found under the following directory: $PO_TOP/admin/import/poxdocon.sql & You then have to run the script by logging on to SQL*PLUS as APPS/(PASSWORD). The control options will be created once you run the above script and you can then view all the Control Options under 'Special' in the Requisition Summary form after you log on to Applications once again. 

  
Q22. You are allowed to update 'Destination Type' from 'Inventory' to 'Expense' in the requisition form. 

A: If you setup destination type as "Inventory" in the item setup and in the Requisitions form if you change the destination type to "Expense", then this will override the destination type setup in item setup. The Destination type will carry over from the Requisition into the Purchase Order when autocreating. 

  
Q23. Clicking on the LOV to select an employee to forward the document gives error:FRM-41830: List Of Values contains no entries. 

A: You need to run the following sql: 
SQL>select can_preparer_approve_flag, default_approval_path_id
 
from po_document_types_all
 
where document_type_code = 'REQUISITION';
If the results return a NULL value for can_preparer_approve_flag then you need to perform the following: Navigation: Purchasing -> Setup -> Purchasing Document Types. In the document window type window use Requisition in the type field. Enable "Owner Can Approve" check box save it disable it save it and enable it. This is to set the flag accordingly. Now save the record. Now when you enter a requisition and forward the requisition for approval you can have LOV in the forward field. 

  
Q24. The requisition can be saved without the need-by date field being populated. 

A: Line items that are put on requisitions must be planned. It is necessary that the items are planned in order for the need-by date to be enforced. 
Step-by-step solution:
GUI - Query the item in the Item Master
 
- Choose the General Planning sub-region
 
- Make the item planned
 
Char - Navigate - Items - Update
 
- Query item
 
- In Item Details region choose select
 
- Make the item planned
 

  
Q25. In the Enter Purchase Order form and in the Enter Requisitions form, the List of Values in the Items field is not retrieving some of the items. 

A: In the Enter Purchase Order form and the Enter Requisitions forms, the List of Values (LOV) in the Items field is not based on what organization your purchasing responsibility is pointing to. Instead, it is based on the Inventory Organization entered in the Financial Options form under Supplier - Purchasing. In the Enter Purchase Order form and the Enter Requisitions forms, the List of Values (LOV) in the Items field is not based on what organization your purchasing responsibility is pointing to. Instead, it is based on the Inventory Organization entered in the Financial Options form under Supplier - Purchasing. Changing the Inventory Organization defined in the Financial Options to the Item Master organizations will permit you to select those items. 

  
Q26. The items with destination type as Inventory have the destination type as Expense defaulting in the Enter Requisitions form. 

A: The defaults do not come in for a requisition, if the inv_organization_id column is blank in HR_LOCATIONS table and does not get populated. The inv_organization_id is linked to location and this in turn is linked to employee and which explains why when you enter the item in requisition form the organization and Ship-To Location field were not get populated and therefore the destination type was not coming as inventory. You have to populate inv_organization_id in HR_locations table which will resolve the problem.
FAQ Details
Q1. Which Requisitions are processed via Create Internal Sales Order? 

A: Only Requisitions Lines which are Internally Sourced and Approved are picked by the Create Internal Sales Order process. Each Requisition Line is processed and picked up by the Create Internal Sales order process if the Source Type is �Inventory�. 

  
Q2. Why am I unable to select �Inventory� as my source type when I create a Requisition? 

A: The Item attribute has to be �Internal Orderable� for Item to be internally sourced. 

  
Q3. When I try to enter a Requisition line, which is internally sourced, I am unable to see my source Organization in the LOV? 

A: You need to define the Shipping Network between the Source Organization and the destination Organization. You can do this in Inventory>Setup>Organizations>Shipping Network and do the setup for the Shipping Network between the two organizations. Also make sure you set the �Internal Order Required� flag. 

  
Q4. Is the create Internal Sales Order process Operating Unit dependent? 

A: Yes. In Release 11i we have the enhance functionality of creating the Sales Order in the Source Organizations Operating Unit. All the Requisition line validations and Setup Validations are done in the source Organization�s Operating Unit. If the Create Internal Sales Order fails you need to check if the Setup is done properly in the Source Organization�s Operating Unit. 

  
Q5. Why is it that after creating and approving an Internal Requisition and running the Create Internal Sales Order process my Requisition line is not transferred to OE? 

A: This could be because of various setup Issues. From the PO side make sure you have done the Customer location associations for the location you select in the destination and Source Org�s Operating Unit. Also check if you have entered the Order Type and Order Source in the Purchasing>Setup>Organizations>Purchasing Options>�Internal Requisition� tab. From the OE side also make sure you have done the Setup related with Create Internal Sales Order. The Order type you entered in the PO system Parameters must have the Order type details defined in OE. 

  
Q6. Why is it that after Running �Create Internal Sales Order� process and Order Import the records are still there in the Interface tables? 

A: This is because the Sales Order will be created in the source Organizations Operating Unit. In Release 11 we created the Sales Order in the destination Org. But in the R11i we have the enhanced functionality of creating the Sales Order in the Source Organization�s Operating Unit. Therefore you have to run Order Import in the Source Organization. 

  
Q7. What are the ways to debug the �Create Internal Sales Order�? 

A: You have the Concurrent Log created for each �Create Internal Sales Order� process run. The log will have information related to the Source and destination Organization�s Operating Unit and whether the setups are done properly in the operating Units. It will also have information of whether the record was picked for processing but failed validations later. You need to get the Database level trace to check the code flow for the �Create Internal Sales Order� 

  
Q8. Why is the transferred_to_oe_flag at the headers updated to �Y� even if some of the records failed during the �Create Internal Sales Order� process? 

A: This is a known issue. Check Enhancement Bug# 2204076.
FAQ Details
Q1. What is the Basic Purchasing Setup for Requisition Import?

A: If importing requisitions from Inventory, input a value for the profile option INV: Minmax Reorder Approval. If the value of INCOMPLETE is selected, the result will be imported Requisitions that require an approval. If the value is APPROVED, then the requisitions cannot be queried in the Requisition entry form; rather, the Requisition Summary form will have to be utilized to view information on the imported approved requisitions.
If importing requisitions from MRP, input a value for the profile option MRP: Purchasing By Revision. This profile option is important if you are using multiple revisions per item and using sourcing rules to create Purchase Orders or Releases. This profile option indicates whether or not to pass on the item revision to the purchase requisition.
Setup/Organizations/Purchasing - Default Alternate Region Requisition Import Group-By Field. The Requisition Import process will first look at the Group By parameter selected when the process is submitted; should this parameter be left blank, the system will then look to the Group-By field residing in the Purchasing Options form. If you expect releases to be created from the requisitions, which you import, make sure the profile option PO: Release During Req Import is populated with the correct value. The choices for this profile are Yes or No. If the profile is set to Yes and all sourcing rule information is properly set up, then blanket releases will be created via the Create Releases process. If the profile is set to No, the Create Releases process will not run at the completion of Requisition Import and all releases will have to be created manually via Auto Create.

  
Q2. How does Requisition Import determine the grouping method for incoming pieces of data?

A: This function groups requisitions. It first assigns values to REQUISITION_LINE_ID and REQ_DISTRIBUTION_ID; the function then groups Requisitions based on the REQ_NUMBER_SEGMENT1 column. All requisitions with the same NOT NULL REQ_NUMBER_SEGMENT1 are assigned the same REQUISITION_HEADER_ID. The function then groups Requisitions based on the GROUP_CODE column. All requisitions with the same value in the GROUP_CODE column are assigned the same REQUISITION_HEADER_ID. It then groups based on the GROUP_BY parameter, which takes on the value of DEFAULT_GROUP_BY if not provided. GROUP_BY could be one of the following: BUYER, CATEGORY, ITEM, VENDOR, LOCATION or ALL. 

  
Q3. How is the PO_INTERFACE_ERRORS table purged and does this data have any dependencies?

A: Oracle Purchasing provides the Requisition Import Exceptions Report, which can be used to diagnose records in Error in the PO_REQUISITIONS_INTERFACE_ALL table. It also has an option to purge the Error records in PO_REQUISITIONS_INTERFACE_ALL and the corresponding Error message in the PO_INTERFACE_ERRORS table: - Responsibility: Purchasing Super User
- Navigation: Reports/Run, then select Requisition Import Exceptions Report
 
There is a parameter titled 'Delete Exceptions'. If you select 'Yes', then records in the PO_REQUISITIONS_INTERFACE_ALL table with a status of �ERROR' and the corresponding records in the PO_INTERFACE_ERRORS table will be deleted. You can also restrict the deleted records by selecting the Batch_id and the Interface Source code. The dependency is between PO_REQUISITIONS_INTERFACE_ALL (transaction_id) and PO_INTERFACE_ERRORS (interface_transaction_id)
 

  
Q4. How is the list of values derived for the Import Source column within the Requisition Import report parameters window?

A: The list of values for the Import Source parameter drives off of the records, which currently reside in the PO_REQUISITIONS_INTERFACE_ALL table. Within this table is the column, INTERFACE_SOURCE_CODE, which contains the source from where the data was created and in turn is the same value that shows in the list of values. Example: Say that there are currently 20 rows In PO_REQUISITIONS_INTERFACE_ALL.Ten of the rows have an INTERFACE_SOURCE_CODE of 'INV', and the other ten rows have an INTERFACE_SOURCE_CODE value of 'WIP'. When the user then goes to view the list of values, it will show 'INV' and 'WIP' in the list, as those are the only sources currently loaded and unprocessed in the interface table. 

  
Q5. What methods are available in the application to resolve errored records in the PO_INTERFACE_ERRORS table?

A: Oracle Purchasing provides the Requisition Import Exceptions Report, which can be used to diagnose problems with the records, which have currently errored out in the PO_REQUISITIONS_INTERFACE_ALL table. 
- Responsibility: Purchasing Super User
 
- Navigation: Reports/Run, then select Requisition Import Exceptions Report
 
There is a parameter titled 'Delete Exceptions�. If this is populated with 'Yes', then all records in the PO_REQUISITIONS_INTERFACE_ALL table with a status of �ERROR�will be deleted when the report is executed. If the parameter is set to �No', then you will see the errors from the report and be able to manually fix the data in the table, if so desired; then, upon completion of the data correction, run Requisition Import again to process the modified rows in the interface table.

  
Q6. Can Requisition Import handle multiple currencies?

A: Requisition Import is capable of handling multiple currencies, provided that all rate types and currency conversions have been defined.

  
Q7. Can Requisition Import handle multiple distributions?

A: Requisition Import can handle multiple distributions. 

  
Q8. Is it possible to have all requisitions created from MRP to be imported with a status of INCOMPLETE?

A: It is not possible to have Requisitions created from MRP imported into the Oracle Purchasing application with a status of INCOMPLETE. The MRP Application inserts all data into the PO_REQUISITIONS_INTERFACE_ALL table with an AUTHORIZATION_STATUS of APPROVED. Therefore, when the Requisition Import program runs, all requisition lines from MRP are created with a Status of APPROVED. If requisitions are created from MRP and the AUTHORIZATION_STATUS is not APPROVED, then please contact support for assistance. 

  
Q9. Is it possible to have all requisitions created from Inventory - Min-Max Planning to be imported with a status of INCOMPLETE?

A: Yes, it is possible to have all requisitions created from Min-Max Planning with a status of INCOMPLETE. If the desired outcome is Min-Max requisitions showing a status of INCOMPLETE, it is necessary to set the profile option: INV: MinMax Reorder Approval to Incomplete. Conversely, if this profile option is set to Approved, all requisitions imported from Min-Max Planning will be imported with an approval status based on the approval authority of the user initiating the Requisition Import process. 

  
Q10. How can I achieve creating 10 requisitions for 10 lines populated into the interface table, instead of 1 req. with 10 lines?

A: Requisitions are grouped according to the selection chosen by the initiator of the process, based on the parameter of 'GROUP BY�. If this parameter is left blank, the value will default from the Default alternate region of the Purchasing Options form. 
- Responsibility: Purchasing Super User
 
- Navigation: Setup -> Organizations -> Purchasing Options
 
Default alternate region
 
If the value selected is ALL, then all requisition lines will be on the same requisition. Any other value will group the lines on requisitions based on the value selected.
 

  
Q11. Is Requisition Import organization-specific?

A: Requisition Import is operating unit-specific. Within the PO_REQUISITIONS_INTERFACE_ALL table lies the column ORG_ID.Upon Initiating the Requisition Import program, the profile 'MO: Operating Unit' is queried to derive the value of ORG_ID tied to the login running the program. Then the Requisition Import program executes, all records in the interface table which are the same as the organization listed in the 'MO: Operating Unit' profile will be processed. If you don't see any valid Import source when you launch Reqimport but if you had already populated the Interface table then you have to check the org_id Column you populated. this org_id will be your operating unit tied to your Applications log-in responsibility. If the org_id is NULL then you can see you record in the Import Source. 

  
Q12. When using encumbrance, is there any validation on the GL Date, ensuring the appropriate periods are open?

A: The Requisition Import program will perform date integrity checks against the date value in the PO_REQUISITIONS_INTERFACE_ALL.GL_DATE field. This field GL_DATE, is reserved for systems operating under Encumbrance Accounting constraints. It is necessary to ensure that the encumbrance year is opened for the GL_DATE being specified. 

  
Q13. How can I achieve grouping by Vendors?

A: First check to see if any records in PO_REQUISITIONS_INTERFACE_ALL have a value for the GROUP_CODE or REQ_NUMBER_SEGMENT1 columns. If there is no value in either of these two columns, then the Requisition Import Program uses the Default Group By that you setup to group requisition lines. Also Navigate to Purchasing -> Setup -> Purchasing Options and Check the group by setting.

  
Q14. Why some times Requisition Import Process fails to create Requisitions when the Data is imported from MRP?

A: Ensure that you use revision number for the item. This is mandatory when you use the profile option �Purchasing by Revision�. The value will indicate whether to pass on item revision to the purchase requisition. You can update this profile at the site level. If this profile is set to Yes, then the item used for requisition import process should have a revision number. Now when you repeat the process the Requisition Import works and the requisitions will be created Successfully from MRP. 

  
Q15. How does Requisition Import Process generate Accounts? 

A: It can be either one of 2 methods for accounts to be generated:
1. By a valid CCID or
 
2. By a valid combination of account segments.
 
We do not generate the accounts using the Account generator process. We only validate the charge_account_id or by a valid combination of Account segments which are populated in the interface table. This is the existing functionality.

  
Q16. How can automatically approve the Requisitions I am creating?

A: There are two ways of doing this: 
1. You can populate records in the Interface table with status as APPROVED. In this case the Approval process is not called after creating the Req. with APPROVED status.
 
2. If you still want the Requisitions created to go through the approval process then you have to set Requisition Import Parameter 'Initiate Approval after Reqimport' to 'Yes' when Launching the Requisition Import Concurrent Program.
 

  
Q17. How will I get the trace and detailed log for the Requisition Import Process?

A: You have to set the profile 'PO: Set Debug Concurrent On' to 'Yes to get the detailed log and Database level for the Requisition Import Process. 

  
Q18. When I load the Requisition Interface and create Requisitions it always does Sourcing. How can I stop sourcing from happening?

A: You have to set the autosource_flag in the Requisition interface to 'N' to avoid vendor Sourcing

  
Q19. How can I avoid sourcing from overriding my vendor information?

A: You have to set the autosource_flag to 'P' for partial sourcing. 

  
Q20. How does Requisition Import process use the Group-By parameter while launching Requisition Import?

A: The Requisition Import process will first look at the Group By parameter selected when the process is submitted; should this parameter be left blank, the system will then look to the Group-By field residing in the Purchasing Options form. To setup in Purchasing option Form the Navigation is Setup/Organizations/Purchasing Options - Default Alternate Region Requisition Import Group-By Field. 

  
Q21. What does the 'MRP: Purchasing by Revision' and 'INV: Purchasing by Revision' do?

A: The profile 'MRP: Purchasing by Revision' is maintained by MRP and the'INV: Purchasing by Revision' profile is maintained by Inventory. This profile option is mainly used by the respective products to determine if the Item Revision needs to be populated while loading the Requisition Interface Tables. Most of the bugs related to these profiles are that sourcing gets affected during Req Import. If the Blanket PO has the Item Revision and the Item in the Interface table does not have the Item Revision field populated, then Sourcing could be a Issue and Releases will not be created.
FAQ Details
Q1. The information setup in the Purchasing Options form is not defaulting on to my purchase order.

A: Verify the PO Options have been setup for each Organization. The Options are specific to each Organization..

  
Q2. Why is my Purchase Order closing before a receipt is processed?

A: Check the Receipt Closed Tolerance and the Matching setup. 
If Matching is set to equal 2-way, the PO will close once the Purchase Order is approved.
If the line of the Purchase Order is received with in the tolerance the line will close..

  
Q3. When creating a Requisition or Purchase Order I am unable to see my items.

A: Check the Inventory Organization defined in the Financial Options:
Setup > Organization > Financial Options - Supplier > Purchasing region
The Inventory Org specified here should be the Master Inventory Org, otherwise only the items setup in the Org populated in this region will be viewable from the Requisition/Purchase Order forms.

  
Q4. When querying Requisitions the order in which they are returned is not in sequential order.

A: When using alphanumeric number type values can appear randomly. Consider entering all numeric values with the same number of digits. For example: If you can assume all numeric values contain six digits, you should enter the first value as 000001.

  
Q5. The Line Type value does not default or update the category if the Line type is changed from the initial defaulted value.

A: Changing the Line Type does not change any of the existing defaults. cause: <Bug:772492> This is the intended functionality for both the Purchase Order and Requisition forms. Whenever the line type is changed, all of the information which was entered was lost and needed to be entered again. The line information will change only if it is changed to a different family. If re-defaulting is needed, please clear the line and enter it again.

 
Q6. Cannot enter the Receiving Options form. Receive the error: 'No organizations Currently Defined'. 

A: From Inventory Responsibility Setup/Org/Organizations Access, the Purchasing Responsibility need to be defined.

 
Q7. Receiving the following error when you save a new Requisition APP-14142 get_po_parameters-10: ora-01403: no data found Cause: A SQL error has occurred in get_po_parameter @lsql_err.

A: You need to do the following:
1. Define the Purchasing Options and Financial Options for your Organization.
2. Ensure that the Master Organization, as well as the Child Organizations, have Receiving Options defined.

 
Q8. Create a Purchase Order. Input the Header and Line information and find that the Shipments button at the bottom of the form is grayed out.

A: Set-up the Receiving Options and to enable the Shipment Button in the Purchase Order form.
Navigation: Setup > Organizations > Receiving Options.
Once set-up these options for your Organization you will have the Shipments button enabled.
Ensure that the Purchasing Options and Financial Options are defined for your Organization.

 
Q9. Accessing the Purchase Order entry screen and getting the error: APP-14142 GET_WINDOW_ORG_SOB 040 ORA-1403 No Data Found.

A: 1. Attach the correct responsibility to the Operating Unit
2. Define Purchasing Options
3. Define Financial Options

 
Q10. Invoice Matching setting in POXPOEPO does not default to the setting in Purchasing Options form.

A: Invoice matching can be set in five different areas of Oracle Purchasing:
In the list below, a setting at any level will override the settings above it.
 

1. Oracle Purchasing Options
a. Navigate to: Setup > Organizations > Purchasing Options
b. Select Default Alternative Region

2. Supplier Information
 
a. Navigate to: Supply Base > Suppliers
b. Query on specific supplier
c. Click on Open
d. Select Receiving Alternative Region

3. Line Types
 
a. Navigate to: Setup > Purchasing > Line Types
b. In the Receipt Required field: Yes = 3-way, No = 2-way

4. Items
a. Navigate to: Items > Master Items
b. Query on specific item
c. Select Purchasing Alternative Region
d. In the Invoice Matching section: Yes = 3-way, No = 2-way

5. Purchase Order Shipments
a. Navigate to: Purchase Orders > Purchase Orders
b. Enter (header and) line information
c. Click on Shipments button
d. Select More Alternative Region
 FAQ Details
Q1. What is Pay On Receipt?

A: Pay on Receipt (also known as ERS (Evaluated Receipt Settlement) or Self-Billing) is an Oracle Purchasing's concurrent program, which automatically creates invoices in Oracle Payables and matches them with PO's automatically for the received amount. The short name for the program is POXPOIV.

  
Q2. What is the minimum set-up required? 

A: 1. In Oracle Purchasing responsibility, navigate to Supply base ->Suppliers. Query the supplier to be used in the PO and Query the site to be used in PO. In the General Tab, check the checkboxes for PAY SITE and PURCHASING. In the Purchasing tab, the Pay on field should have a value of' Receipt'. The invoice summary level should also have the value of 'Receipt'. 
2. Apart from the above set-up in R11i, we need to enter the value of ?Receipt? against the Pay on field in the Terms window of the PO.
 

  
Q3. What is the impact of payables options on ERS? 

A: From Payables options, under GL date basis there are four options. The accounting date will be based on the option selected here. Make sure that the date is in the open period.

  
Q4. How can we identify the invoices created by Pay on receipt? 

A: The invoices created by ERS will have ERS prefix generally. To identify the invoice created for a particular receipt we can query with the combination of ERS and receipt number in the invoice number field. In R11i, the profile option PO: ERS invoice number prefix can be set as needed which can be used to identify the invoices. 

  
Q5. What are the parameters passed? 

A: For R107 and R11, the parameters passed are Parameter name value:
1. Transaction Source - ERS
 
2. Commit interval- default 1
 
3. Organization- Receiving org
 
4. Receipt Number- optional
 
If a receipt number is not specified all the receipts for that organization, which are eligible for Pay on Receipt, are picked. For R11i, the organization parameter does not exist instead a new parameter called Aging period exists.
 

  
Q6. What is the significance of Ageing Period (R11i)? 

A: The parameter Aging period determines the transactions on the receipt that can be considered for the invoice creation. For ex if aging period is given as 1, then all the transactions that have a transaction date less than or equal to the (sysdate-1) are considered for invoice creation. The aging period can be set thru the profile option PO: ERS Aging period. 

  
Q7. How can we debug what went wrong? 

A: We can refer to the log file and check for error messages in po_interface_errors. 
There could be many errors. Listed below are some common errors and possible resolutions.
1) Error Occurred in routine: create_invoice_header - Location: 110. Please refer note 1071391.6.
2) Pay on receipt Autoinvoice does not create any invoice. Please ensure the setup is complete in payables and Purchasing modules.
3) You have a supplier who has a separate site for purchasing and Payables. When running the ERS (Evaluated Receipt Settlement) it is selecting the purchasing site and therefore does not create the invoice and gets a message that the POXPOIV: 'pay site is invalid'.
 
4) Purchasing Pay on Receipt Autoinvoice shows multiple occurrences of same receipt number in multiorg environment. See Note 95384.1 for the solution.
5) Pay On Receipt AutoInvoice errors: po_inv_cr_invalid_gl_period.

Q8. Does ERS work for unordered receipts? 
A: No. ERS does not work for unordered receipts. This means invoice needs to be created manually for those PO?s that are created from unordered receipts

No comments: