Search Results oe_batch_id_s

Overview

APPS.OE_BULK_ORDER_IMPORT_PVT is a private (PVT) PL/SQL package body in the Oracle Order Management module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It provides the internal processing engine behind the Bulk Order Import feature, which allows large volumes of sales orders to be loaded from external sources through the Order Management interface tables rather than through the interactive Order Entry form. The package reads staged header, line, action, credit, price adjustment, and price attribute records, validates them against Order Management setup, and converts them into actual order headers and lines with associated processing messages. As a PVT package it is not a published public API; the supported entry point for external callers is the public OE_BULK_ORDER_PVT wrapper.

Key Procedures and Functions

The ETRM metadata documents a single entry point for this package body:

• ORDER_IMPORT_CONC_PGM — The concurrent program driver for bulk order import. It is the procedure registered against the Bulk Order Import concurrent program and orchestrates the full import run: initialising the API environment, determining the operating unit context, iterating over the pending batch of interface records, invoking the bulk import and hold-processing logic, writing output and log messages, and recording the completion status of the batch.

The broader dependency list shows the package body also calls OE_BULK_ORDER_PVT, OE_BULK_HOLDS_PVT, OE_BULK_MSG_PUB, OE_MSG_PUB, OE_DEBUG_PUB, and OE_STANDARD_WF, indicating that import processing is layered, with hold application, message publishing, debugging, and workflow notification handled by supporting packages rather than by the driver itself.

Tables Accessed

The package body works primarily against the Order Management interface tables and their base-table counterparts, all accessed through APPS synonyms:

• OE_HEADERS_IFACE_ALL / OE_HEADERS_INTERFACE and OE_LINES_IFACE_ALL / OE_LINES_INTERFACE — The staging tables holding inbound order header and line data awaiting validation and import.
• OE_ACTIONS_IFACE_ALL / OE_ACTIONS_INTERFACE — Interface records for order actions such as cancellations and holds applied during import.
• OE_CREDITS_IFACE_ALL — Credit check information staged for imported orders.
• OE_PRICE_ADJS_IFACE_ALL and OE_PRICE_ATTS_IFACE_ALL — Staged price adjustment and pricing attribute detail for imported lines.
• OE_ORDER_HEADERS_S and OE_ORDER_LINES_S — The base sequence generators used when creating the resulting order headers and lines.
• OE_BATCH_ID_S — The sequence that assigns batch identifiers to import groups. This is the object most commonly searched for alongside this package, since it provides the batch grouping key used to process and reconcile bulk import runs.
• OE_ORDER_SOURCES — Order source validation against defined sales channels.
• OE_PROCESSING_MSGS / OE_PROCESSING_MSGS_TL — Storage of error and information messages returned to the user after import.

Usage Notes

OE_BULK_ORDER_IMPORT_PVT is invoked indirectly, not from custom code. The normal route is the Bulk Order Import concurrent program, whose executable calls ORDER_IMPORT_CONC_PGM. External systems first populate the OE_*_IFACE_ALL tables (frequently through the public OE_BULK_ORDER_PVT or the Order Import open interface), then submit the concurrent program for a specific batch. Batch grouping is driven by OE_BATCH_ID_S, so queries used to diagnose failed runs typically join the interface tables on the batch identifier. The package is not referenced by any database object and, being a PVT body, should not be called directly; customisations should target the public OE_BULK_ORDER_PVT API or the concurrent program parameters instead. Diagnostic output is written through FND_FILE to the concurrent request log and output files.