Search Results ece_stage_id_s

Overview

APPS.EC_OUTBOUND is a core PL/SQL package body within the Oracle E-Business Suite E-Commerce Gateway (EC) module. Its principal business function is to assemble, stage, and emit outbound electronic commerce documents — such as EDI purchase orders, invoices, and shipment notices — by extracting transactional data from Oracle EBS application tables and writing it to the ECE_STAGE staging and interface tables in a structure suitable for downstream flat-file generation and transmission to trading partners. The package operates as an outbound processing engine, parsing dynamic SQL statements against configured interface file/column definitions in order to populate the ECE_STAGE populator tables.

The "load_objects" term that guided this search corresponds to the package's internal dynamism: EC_OUTBOUND constructs, parses, and executes INSERT statements at runtime via DBMS_SQL, orchestrated through cursors whose handles are held in ec_utils.g_int_levels(i).cursor_handle (as documented in the header comments). This design allows the package to accommodate the flexible column mappings defined for each E-Commerce Gateway interface.

Key Procedures and Functions

• PROCESS_OUTBOUND_DOCUMENTS — The main driver for outbound document generation. It is responsible for creating the outbound run context, iterating over the configured interface levels and record structures, invoking the dynamic insert-statement builder (parse_insert_statement), and populating ECE_STAGE with the extracted outbound data. It is the entry point through which the E-Commerce Gateway constructs outbound interface files. Parameter lists are not provided in the documented metadata; the procedure is invoked as the primary processing call.
• DELETE_STAGE_DATA — Cleanses previously staged records from ECE_STAGE. This routine supports run cleanup and re-processing scenarios by removing stale or completed staged rows so that subsequent outbound runs operate on a clean set of data. As with the above, no documented parameter list is asserted.

The package body additionally declares cursors over sequences (seq_stage_id on ECE_STAGE_ID_S and seq_document_id on ECE_DOCUMENT_ID_S) used to generate unique identifiers for each staged record and document.

Tables Accessed

• ECE_STAGE — The primary staging table populated by PROCESS_OUTBOUND_DOCUMENTS and cleansed by DELETE_STAGE_DATA. Stores the flattened outbound document records prior to file generation.
• ECE_STAGE_ID_S — Sequence supplying Stage_id values for each staged record.
• ECE_DOCUMENT_ID_S — Sequence supplying Document_Id values for each outbound document.
• ECE_OUTPUT_RUNS_S — Sequence associated with outbound run identifiers, used to tag staged records with a Run_Id.
• DBMS_SQL — Oracle-supplied package used to dynamically parse, bind, and execute the generated INSERT statements that load ECE_STAGE.
• DUAL — Used exclusively to fetch next values from the ECE_STAGE_ID_S and ECE_DOCUMENT_ID_S sequences.
• PLITBLM — Referenced in the documented metadata, this is the Oracle-supplied PL/SQL table memory access package used in conjunction with index-by tables.

Usage Notes

EC_OUTBOUND is invoked as part of the standard Oracle E-Commerce Gateway outbound processing flow. In Oracle EBS 12.1.1 and 12.2.2 it is typically called by the E-Commerce Gateway concurrent programs that generate outbound transactions (for example, the EDI outbound extract programs). The calling convention passes a run context; the package reads the configured interface definitions, builds the dynamic INSERT through parse_insert_statement, and populates ECE_STAGE.

The package is referenced by two other packages within the E-Commerce Gateway module, indicating it sits within a layered call hierarchy rather than being invoked directly by forms. Customisations or extensions should preserve the documented behaviour around sequence consumption (ECE_STAGE_ID_S, ECE_DOCUMENT_ID_S, ECE_OUTPUT_RUNS_S) and the ECE_STAGE column mapping, since these identifiers and structure are relied upon by downstream file-generation routines. Because the package depends on DBMS_SQL and dynamic SQL, any change to the underlying gateway interface definitions must be validated against the dynamic statement builder before recycling the concurrent program.