Results for “po_reqimport”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The Concurrent Program REQIMPORT, presented to users as Requisition Import, is a Purchasing (PO) module utility in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to load requisition data from the open interface tables into the live Purchasing tables, creating requisitions and requisition lines that can subsequently be processed through the standard procurement cycle. The program is the standard mechanism by which requisitions originating outside of the core Purchasing forms — for example, those generated by external systems, feeder programs, or custom integrations — are validated and converted into functional purchasing documents.

Requisition Import is part of the broader family of Purchasing import programs and operates directly against the requisition interface tables. It is enabled by default and is a core component of the requisition-to-purchase-order lifecycle. Because it writes to the base requisition tables, it must be run only after the input data has been fully populated and validated in the interface tables.

Execution Details

The documented ETRM metadata for this program specifies the following technical attributes:

• User-facing name: Requisition Import
• Product: PO — Purchasing
• Enabled: Yes
• Execution Method: Spawned
• Argument Method: Database fetch
• Executable: POCIRM
• Execution Filename: POCIRM
• Subroutine Name: po_reqimport

The "Spawned" execution method indicates that the program runs as a spawned process rather than a direct PL/SQL invocation, and the "Database fetch" argument method means the program retrieves its runtime parameters from the database rather than from a submitted parameter form. The underlying executable, POCIRM, invokes the po_reqimport routine to perform the actual import logic.

How to Run

Users typically submit Requisition Import through the Standard Request Submission (SRS) window by navigating to Responsibility: Purchasing > Reports > Run (or the equivalent Submit Requests form) and selecting Requisition Import. Because the program is defined with the "Database fetch" argument method, its parameters are not entered interactively on the submission form; instead, the program derives its selection criteria from records already staged in the interface tables.

General guidance for a successful run includes:

• Populate and verify the requisition interface tables before submission.
• Ensure the interface rows reference valid items, suppliers, units of measure, and accounting information to avoid validation errors.
• Run the program and then review the import output and the associated error tables for rejected records.
• Correct rejected rows and resubmit, since the program only processes rows still pending in the interface.

Related Objects

Requisition Import is closely associated with several Purchasing interface components and related programs:

• PO_REQUISITIONS_INTERFACE — the primary requisition interface table that feeds the import.
• PO_REQ_DISTRIBUTIONS_INTERFACE — holds distribution lines for interface requisitions.
• PO_INTERFACE_ERRORS — stores validation and processing errors generated during import.
• PO_REQUISITIONS_HEADERS_ALL / PO_REQUISITIONS_LINES_ALL — the destination base tables populated by the program.
• Requisition Import Corrections and the requisition open interface concurrent programs, which are frequently run alongside REQIMPORT.

Together these objects form the standard inbound path for external requisition data in Oracle Purchasing.