Search Results p_order_source

Overview

APPS.OE_ORDER_IMPORT_MAIN_PVT is the private driver package behind Oracle Order Management's Order Import concurrent program and the Order Import form. Order Import is the high-volume mechanism by which sales orders are created in Oracle E-Business Suite from external sources—interfaced data loaded into the OE_*_IFACE_ALL tables, 3PL/EDI feeds, web storefront drops, or legacy extracts. The package is not a standalone public API; it is the internal orchestrator that a) validates and prepares import data, and b) submits the actual Order Import worker processes that transform interface rows into real order headers, lines, and related entities.

As classified "PVT" in the ETRM registry, OE_ORDER_IMPORT_MAIN_PVT is intended for internal use by Oracle's Order Management application code and by the concurrent manager. It exposes three documented entry points—two concurrent-program wrappers and one form wrapper—that accept filtering parameters such as order source, originating system document reference, sold-to organization, and operating unit, then hand control to the underlying import engine (typically OE_ORDER_PUB / the import processor). Because it is a private package, Oracle does not guarantee its signature across releases; custom development should prefer the documented public APIs or the standard concurrent program submission path.

Key Procedures and Functions

• ORDER_IMPORT_STATS_CONC_PGM — A concurrent-program entry point added to gather and report Order Import statistics (for example, counts of records processed, succeeded, or failed). It uses the standard concurrent program OUT signature (errbuf, retcode) and is invoked by a dedicated FND_STAT concurrent program registered in Oracle EBS.
• ORDER_IMPORT_CONC_PGM — The primary concurrent-program entry point for Order Import. It is the procedure invoked when the "Order Import" concurrent program is run, and it accepts parameters for filtering the import set. Relevant to the user's search, it receives p_order_source (VARCHAR2) alongside p_operating_unit, p_orig_sys_document_ref, p_operation_code, and validation/processing flags such as p_validate_only, p_debug_level, p_num_instances, p_perf_param, p_rtrim_data, p_process_orders_with_null_org, and p_validate_desc_flex. Its purpose is to select the appropriate interface records and submit the Order Import processing logic.
• ORDER_IMPORT_FORM — The form-layer entry point used by the Order Import concurrent form. It accepts p_order_source_id (the internal ID corresponding to the order source), p_orig_sys_document_ref, sold-to identifiers, change sequence, org context, and validation flags, returning standard FND_API message list, message count, message data, and return status OUT parameters. Whereas the concurrent program passes an order source name, the form passes the numeric p_order_source_id resolved from the form's list of values.

No additional public functions are documented for this package; it relies on collaborating private packages (referenced by two other packages per the ETRM registry) to perform the row-level import work.

Tables Accessed

The package reads and writes the core Order Import interface tables via APPS synonyms:

• OE_HEADERS_IFACE_ALL and OE_HEADERS_INTERFACE — staging of order header interface records.
• OE_LINES_IFACE_ALL — staging of order line interface records.
• OE_ORDER_SOURCES — lookup of order source definitions, which is how the p_order_source / p_order_source_id parameters are resolved to the source context that governs the import.
• OE_ACTIONS_IFACE_ALL, OE_LOTSERIALS_IFACE_ALL, OE_RESERVTNS_IFACE_ALL, OE_PRICE_ADJS_IFACE_ALL, OE_PRICE_ATTS_IFACE_ALL, OE_CREDITS_IFACE_ALL, and OE_PAYMENTS_IFACE_ALL — the associated interface tables for actions, lots/serials, reservations, price adjustments and attributes, credits, and payments that accompany header/line import.
• OE_PROCESSING_MSGS and OE_PROCESSING_MSGS_TL — storage and translation of processing messages generated during import, used to report errors back to the user.
• FND_CONCURRENT_REQUESTS — read to correlate the run with concurrent request context and status, supporting the concurrent-program entry points.

Usage Notes

In practice, OE_ORDER_IMPORT_MAIN_PVT is invoked indirectly. From the EBS UI, users run Order Import via the standard concurrent program ("Order Import") or the Order Import form; both resolve to this package's ORDER_IMPORT_CONC_PGM or ORDER_IMPORT_FORM procedure. Administrators schedule the concurrent program, supply an order source and optionally an originating document reference so only a subset of interface rows is processed, and review the resulting messages written to OE_PROCESSING_MSGS.

Because the package is classified private, custom integrations should not call it directly; the supported approach is to load data into the OE_*_IFACE_ALL staging tables and then submit the Order Import concurrent program (or call the documented public Order Import APIs). Direct invocation risks breakage on patching, since Oracle may alter the private signature. When troubleshooting, note that the p_order_source parameter is the common filter users search for—its value must match an active order source defined in OE_ORDER_SOURCES, or no interface records will qualify for import.