ReqImport

Overview
This interface lets you integrate Oracle Purchasing quickly with new or existing applications such as
material requirements planning, inventory management, and production control systems. Purchasing
automatically validates your data and imports your requisitions. You can import requisitions as often
as you want. Then, you can review these requisitions, approve or reserve for them if necessary, and
place them on purchase orders or internal sales orders.
Flow
You must write the program that inserts a single row into the
PO_REQUISITIONS_INTERFACE_ALL and/or the PO_REQ_DIST_INTERFACE_ALL table for
each requisition line that you want to import. Then you use the Submit Request window to launch the
Requisition Import program for any set of rows.
You identify the set of rows you want to import by setting the INTERFACE_SOURCE_CODE and
BATCH_ID columns appropriately in the PO_REQUISITIONS_INTERFACE_ALL table. You then
pass these values as parameters to the Requisition Import program. If you do not specify any values
for these parameters, the program imports all therequisition lines in the
PO_REQUISITIONS_INTERFACE_ALL table. You also specify the requisition grouping and
numbering criteria as parameters to the Requisition Import program.
Each run of the Requisition Import program picks up distribution information from either the
PO_REQUISITIONS_INTERFACE_ALL or the PO_REQ_DIST_INTERFACE_ALL table. The
PO_REQ_DIST_INTERFACE_ALL table was used in Release 11, for Self-Service Purchasing
(known then as Web Requisitions). In Release 11i, you should use the
PO_REQ_DIST_INTERFACE_ALL table to create multiple distributions only for requisitions
created in non-Oracle systems that use multiple distributions. As long as the Multiple Distributions
field in the Requisition Import program is No (or blank), Requisition Import looks for distribution
information in the PO_REQUISITIONS_INTERFACE_ALL table.
The Requisition Import program operates in three phases. In the first phase, the program validates
your data and derives or defaults additional information. The program generates an error message for
every validation that fails and creates a row in the PO_INTERFACE_ERRORS table with detailed
information about each error.
In the second phase, the program groups and numbers the validated requisition lines according to the
following criteria. If you specify a value in the REQ_NUMBER_SEGMENT1 column of the
PO_REQUISITIONS_INTERFACE_ALL table, all lines with the same value for this column are
grouped together under a requisition header. If you provide a value in the GROUP_CODE column,
all lines with the same value in this column are grouped together under a requisition header.
If you do not provide values in either of these columns, the Requisition Import program uses the
Group By parameter to group lines together. If you do not provide a value for this parameter, the
program uses the default Group By that you set up to group requisition lines. You can group
requisition lines in one of the following ways that the Requisition Import program supports by:
BUYER
CATEGORY
LOCATION
VENDOR
ITEM
ALL (all requisition lines grouped under one header)
If you provide a value in the REQ_NUMBER_SEGMENT1 column of the
PO_REQUISITIONS_INTERFACE_ALL table, this value becomes the requisition number. If not,
the Requisition Import program uses either the Last Requisition Number parameter if specified or the
next unique number stored in the PO_UNIQUE_IDENTIFIER_CONTROL table, adds 1 to this
number, and starts numbering requisitions. If any of the requisition numbers generated already exists,
the program loops until it finds a unique number. For every line that is successfully imported, a
default distribution is created with the account information that you specify. (You specify account
information in any of the following columns in either the PO_REQUISITIONS_INTERFACE_ALL
or the PO_REQ_DIST_INTERFACE_ALL table: CHARGE_ACCOUNT_ID,
ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID, BUDGET_ACCOUNT_ID, or any of
the CHARGE_ACCOUNT_SEGMENT columns.) Requisition supply is also created for every
approved requisition that is successfully imported.
In the third phase, the program deletes all the successfully processed rows in the interface tables, and
creates a report which lists the number of interface records that were successfully imported and the
number that were not imported. This report can be viewed by choosing View Output for the
Requisition Import concurrent
Request ID in the Requests window. You can launch the Requisition Import Exceptions Report to
view the rows that were not imported by the Requisition Import program along with the failure
reason(s) for each row.