Results for “po_reqimp_s”

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

Overview

PO_REQIMP_S is a server-side PL/SQL package body owned by the APPS schema that supports the Oracle Purchasing requisition import process. Requisition import in Oracle E-Business Suite enables organizations to load requisition data from external systems, legacy applications, spreadsheets, or feeder programs into the purchasing interface tables and then validate and convert that data into live requisition documents. The PO_REQIMP_S package provides the low-level helper and validation logic invoked during this import cycle. It is classified as an "OTHER" API rather than a public, fully documented interface, meaning it is intended primarily for internal consumption by the requisition import concurrent program and closely coupled packages such as PO_REQIMPORT and PO_JL_INTERFACE_PVT, rather than for direct customer callouts. Its role centers on defaulting, conversion, and validation utilities that ensure imported requisition lines carry accurate pricing, unit of measure, and transaction reason information before the import engine processes them.

In the documented ETRM metadata for 12.2.2, the package is VALID and exposes four procedures or functions. PO_REQIMP_S is not referenced by any other database object, confirming it sits at the leaf of the dependency chain and is called dynamically or from top-level import drivers rather than being a shared dependency of many packages.

Key Procedures and Functions

• GET_LIST_PRICE_CONVERSION — Derives or converts a list price value for an imported requisition line, accounting for currency and pricing factors so that the interface record reflects the correct catalog or list price before validation.
• GET_UOM_CONVERSION — Resolves the unit of measure conversion between the transaction UOM and the primary or inventory UOM, supplying the conversion rate and factor needed for quantity and price normalization.
• DEFAULT_TRX_REASON_CODES — Populates default transaction reason codes on requisition interface records where the source system has not supplied them, ensuring downstream validation and approval logic has complete data.
• REQIMPORT_DEF_VALIDATE_SEC_QTY — Applies defaulting and validation to the secondary quantity on requisition lines, checking consistency between primary and secondary quantities and their associated UOM relationships.

No parameter signatures are documented in the ETRM metadata, so callers should treat these as internal routines used by the import driver.

Tables Accessed

The package reads and writes a focused set of interface and setup tables through APPS synonyms:

• PO_REQUISITIONS_INTERFACE — the primary staging table for imported requisition headers and lines; defaulting and validation updates are applied here.
• PO_INTERFACE_ERRORS — records validation failures surfaced during import processing.
• MTL_SYSTEM_ITEMS and MTL_UNITS_OF_MEASURE — supply item and UOM attributes required for conversion and validation logic.
• PO_LINE_TYPES, PO_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMETERS, and FINANCIALS_SYSTEM_PARAMS_ALL — provide defaulting sources for line types and system-level purchasing and financials configuration.
• PLITBLM — an APPS PL/SQL table type used for in-memory collections during processing.

Usage Notes

PO_REQIMP_S is normally invoked indirectly. The Requisition Import concurrent program (PO_REQIMPORT) and the purchasing interface private APIs call these routines as part of the validate-then-convert sequence. Because the package is not referenced by any other database object and is classified as OTHER, custom developers should not call it directly; instead, load data into PO_REQUISITIONS_INTERFACE and run the standard Requisition Import program. If custom SQL must invoke these procedures, the caller should first confirm the signature in the target release (12.1.1 or 12.2.2), since the package is internal and Oracle does not guarantee its interface across patches.