Search Results oe_order_import_util_pvt




Overview

OE_ORDER_IMPORT_UTIL_PVT is a private PL/SQL utility package in the Oracle E-Business Suite Order Management (OE) module. It belongs to the Order Import subsystem and provides low-level helper logic used by the Order Import concurrent program and its public APIs to manage staged interface data. The package is classified as Private (API classification PVT) and is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than as the defining APPS user.

Its business purpose is to support the housekeeping and reconciliation tasks that surround the Order Import process: removing orders previously loaded through the interface, clearing associated error and processing messages, and resolving line identifiers from external system references. These operations are essential to keep the interface tables clean, enable re-processing of failed records, and maintain referential consistency between the interface staging area and the base order tables in a multi-org environment.

The package header indicates a current version of 1.0 (initial version 1.0), and the source control header references a 2005 file revision, confirming it is a long-standing component of the Order Import infrastructure. The document applies to both Oracle EBS 12.1.1 and 12.2.2, where the Order Import architecture remains substantially consistent.

Key Procedures and Functions

The package exposes three documented program units:

  • DELETE_ORDER — A procedure that deletes an order previously processed through Order Import. It accepts the concurrent request identifier, the order source, the original system document reference, and optional buyer and change-sequence qualifiers, then returns a status indicator. It is used to back out a previously imported order so that it can be corrected and re-imported.
  • DELETE_MESSAGES — A procedure that removes the error and processing messages associated with an imported order, using the request ID, order source, document reference, and optional org-ID and buyer qualifiers. Clearing messages is a prerequisite for clean re-processing and prevents stale errors from obstructing subsequent import attempts.
  • GET_LINE_INDEX — A function that returns the index of a line within a line table collection, based on the original system line reference and the original system shipment reference. It enables callers to locate a specific imported line within the in-memory line table structure during processing.

Tables Accessed

The package operates across the Order Import interface staging tables, accessed through APPS synonyms. These include OE_HEADERS_INTERFACE, OE_LINES_INTERFACE, OE_ACTIONS_INTERFACE, OE_CREDITS_INTERFACE, OE_LOTSERIALS_INTERFACE, OE_PAYMENTS_INTERFACE, OE_PRICE_ADJS_INTERFACE, OE_PRICE_ATTS_INTERFACE, and OE_RESERVTNS_INTERFACE. These tables hold header-, line-, price adjustment-, payment-, credit-, lot/serial-, reservation-, and action-level data staged for import. The Delete_Order and Delete_Messages procedures target these interface tables to purge rows tied to a given request or document reference, while PLITBLM, a PL/SQL index-by table type used in the package, supports collection handling such as the line table input to GET_LINE_INDEX.

Usage Notes

OE_ORDER_IMPORT_UTIL_PVT is a private package and is not intended for direct invocation by external customizations. It is referenced by two other packages and is invoked internally by the Order Import concurrent program and by the public Order Import APIs during order creation, rollback, and message management. Administrators and developers interact with its behavior indirectly through the Order Import concurrent request, which calls these utilities to delete prior orders, clear messages, and reconcile line references. Because the package uses AUTHID CURRENT_USER, effective privileges depend on the calling schema, and callers must ensure appropriate grants on the underlying interface tables. When custom code must re-drive failed imports or clean up stale interface data, the supported approach is to use the documented Order Import public APIs rather than this private utility package.