Requisition Import FAQ’s

Basic Purchasing Setup for Requisition Import

1. 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.
2. 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.
3. Setup/Organizations/Purchasing Options - 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.
4. If you expect releases to be created from the requisitions which
you import,make sure the profile option PO: Release During
ReqImport 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 AutoCreate.

Contents:

1. How does Requisition Import determine the grouping method

for incoming pieces of data?
2. How is the PO_INTERFACE_ERRORS table purged and does
this data have any dependencies?

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

4. What methods are available in the application to resolve errored

records in the PO_INTERFACE_ERRORS table?

5. Can Requisition Import handle multiple currencies?

6. Can Requisition Import handle multiple distributions?

7. Is it possible to have all requisitions created from MRP to be

imported with a status of INCOMPLETE?

8. Is it possible to have all requisitions created from Inventory -

Min-Max Planning to be imported with a status of
INCOMPLETE?

9. The PO_REQUISITIONS_INTERFACE_ALL table has been

loaded with 10 records.Upon running Requisition Import, 1
Requisition is created with 10 lines,whereas the preferred
outcome is 10 Requisitions with 1 line on each Requisition.
How can this preferred outcome be made possible?

10.Is Requisition Import organization-specific?

11.When using encumbrance, is there any validation on the GL

Date, ensuring the appropriate periods are open?

12.When running the Requisition Import process it completes

normally, but does not group by vendor.You end up generating
number of requisitions that do Not match the number of vendors
represented by the imported records,Why?

13.Why some times Requisition Import Process fails to create

Requisitions when the Data is Imported from MRP?
 14. In Requisition Import Process how does the Accounts are
generated?

Questions && Answers:

Q1: How does Requisition Import determine the grouping method for
incoming pieces of data?
A1: 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.

Q2: How is the PO_INTERFACE_ERRORS table purged and does

this data have any dependencies?
A2:Currently, there are no reports or concurrent programs available
that will remove data from the PO_INTERFACE_ERRORS table.It is
recommended that,after full implementation and testing of Oracle
Purchasing and dependent products (such as MRP, INV, OE, etc.) is
complete, a purge of old unnecessary data be performed on this table.
It should be noted that upon removing data from the
PO_INTERFACE_ERRORS table, you are removing the source for
any error Messages which correlate to records stuck in the
PO_REQUISITIONS_INTERFACE_ALL table (as well as records
stuck in the RCV_TRANSACTIONS_INTERFACE table). There are
no primary or foreign key references to the
PO_INTERFACE_ERRORS table, and all data seen in this table is for
informational purposes only.
Q3: How is the list of values derived for the Import Source column
within the Requisition Import report parameters window?
A3: 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.

Q4: What methods are available in the application to resolve errored

records in the PO_INTERFACE_ERRORS table?
A4: 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.

Q5:Can Requisition Import handle multiple currencies?

A5: Requisition Import is capable of handling multiple currencies,
provided that all rate types and currency conversions have been
defined.
Q6:Can Requisition Import handle multiple distributions?
A6: Requisition Import can handle multiple distributions.

Q7:Is it possible to have all requisitions created from MRP to be

imported with a status of INCOMPLETE?
A7: 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.

Q8: Is it possible to have all requisitions created from Inventory -

Min-Max Planning to be imported with a status of INCOMPLETE?
A8: 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.

Q9: The PO_REQUISITIONS_INTERFACE_ALL table has been

loaded with 10 records.Upon running Requisition Import, 1
Requisition is created with 10 lines,whereas the preferred outcome is
10 Requisitions with 1 line on each Requisition. How can this
preferred outcome be made possible?
A9: 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.

Q10: Is Requisition Import organization-specific?

A10: 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.

Q11:When using encumbrance, is there any validation on the GL Date,

ensuring the appropriate periods are open?
A11: 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.

Q12:When running the Requisition Import process it completes

normally, but does not group by vendor.You end up generating
number of requisitions that do Not match the number of vendors
represented by the imported records,Why?
A12: 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.

Q13:Why some times Requisition Import Process fails to create

Requisitions when the Data is Imported from MRP?
A13: 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.

Q14. In Requisition Import Process how does the Accounts are

generated?
A14. In Requisition Import Process we do not generate the accounts
using the Accountgeneration process.We only validate the
charge_account_id which is populated in the interface table. This is the
existing functionality.