Search Results process_for_document_id

Overview

APPS.ECE_INBOUND is an internal PL/SQL package within the Oracle E-Business Suite E-Commerce Gateway (EC) product. Its documented display name, "Process Data from Staging Tables to Open Interface Tables," describes its central role: it transforms inbound XML or flat-file data that has already been loaded into the ECE staging tables and moves it into the open interface tables of the target application modules for further validation and import. The package is classified as OTHER in the ETRM repository and is scoped as internal, with an active lifecycle status. Its category is registered as BUSINESS_ENTITY EC_INBOUND, and compatibility is marked as S. The header source identifies a versioned file (ECEINBS.pls) last revised in 2005, indicating a mature, stable code line carried forward through EBS 12.1.1 and 12.2.2. The user search term "process_documents" corresponds to the PROCESS_DOCUMENTS procedure exposed by this package.

Key Procedures and Functions

The package exposes nineteen documented procedures. Collectively they drive the staging-to-interface pipeline:

• PROCESS_INBOUND_DOCUMENTS — Overloaded entry point for processing inbound documents by transaction type, with variants accepting a document ID, a run ID, a status, or no additional selector.
• PROCESS_RUN_INBOUND — Processes all staged data associated with a specific run ID, using the seeded map for the transaction.
• RUN_INBOUND — Top-level driver that coordinates an inbound processing pass.
• PROCESS_DOCUMENTS — The procedure matching the search term; iterates staged documents eligible for interface population.
• PROCESS_FOR_REQID / PROCESS_FOR_DOCUMENT_ID / PROCESS_FOR_STATUS / PROCESS_FOR_TRANSACTION / PROCESS_FOR_TPSTATUS — Focused processing routines that filter staged records by request ID, document ID, status, transaction type, or trading partner status respectively.
• SELECT_STAGE — Retrieves rows from the staging tables according to the applicable mapping.
• INSERT_INTO_PROD_INTERFACE — Inserts transformed staging records into the destination open interface tables.
• INSERT_INTO_VIOLATIONS — Records mapping or validation rule violations encountered during processing.
• UPDATE_DOCUMENT_STATUS — Advances the status of inbound documents as processing proceeds.
• INITIALIZE_INBOUND — Sets up package state before a processing cycle.
• CLOSE_INBOUND — Finalizes the inbound run, releasing resources and settling document states.

Tables Accessed

Documented table references include ECE_RULE_VIOLATIONS and ECE_STAGE. ECE_STAGE is the staging table that holds inbound data loaded by the ECE_INBOUND_STAGE load process; ECE_INBOUND reads it as the source for mapping-driven transformations. ECE_RULE_VIOLATIONS stores rule breaches detected during processing, populated through INSERT_INTO_VIOLATIONS. The package also relies on the PLITBLM PL/SQL table-management utility and, per the header, DBMS_SQL for dynamic SQL when constructing interface inserts. The global collection g_col_rule_viol_tbl is declared over ECE_RULE_VIOLATIONS columns, and g_previous_map_id tracks mapping continuity across staged rows. Additional destination tables are reached through open interface synonyms maintained in the APPS schema.

Usage Notes

ECE_INBOUND is typically invoked by the E-Commerce Gateway inbound concurrent programs after the staging load completes. The run ID returned by ECE_INBOUND_STAGE.load_data is passed to PROCESS_RUN_INBOUND or PROCESS_INBOUND_DOCUMENTS to drive transformation according to the seeded transaction map. Because the package is marked internal and scoped for EC use, direct custom calls should be limited and accompanied by thorough regression testing. The package is referenced by eight other packages within the EBS codebase, so modifications require impact analysis. Common invocation paths include the ECE inbound interface concurrent requests, workflow-driven document processing, and controlled extensions that call PROCESS_DOCUMENTS for specific transaction types. Errors surface through ECE_RULE_VIOLATIONS and document status updates, which should be monitored in inbound troubleshooting.