Search Results ecx_output_runs_s

Overview

The APPS.ECX_OUTBOUND package body is the outbound processing engine of Oracle E-Business Suite's E-Commerce eXchange (ECX) module, also referred to as the EDI Gateway. It is responsible for assembling, formatting, and dispatching outbound business documents — purchase orders, invoices, advance ship notices, and similar transaction sets — from the Oracle EBS application tables to external trading partners. In release 12.1.1 and 12.2.2 the package operates against the same APPS synonym layer, consolidating mapping lookups, XML generation, print/transmission handling, and error logging into a single server-side unit. The package body carries a VALID status in the data dictionary and is documented by ETRM as an OTHER-classified API, meaning it is not a supported open interface but a component invoked primarily by the EDI concurrent programs and the outbound workflow queue handler. Its dependency chain shows tight coupling to workflow (WF_CORE, WF_EVENT), the ECX conversion and mapping utilities, and Oracle XML and LOB built-ins.

Key Procedures and Functions

ETRM documents three procedures and functions within this package body:

• PROCESS_OUTBOUND_DOCUMENTS — the principal driver routine. It iterates the set of outbound document runs selected for a given transaction type, applies the configured mapping rules, and coordinates generation and dispatch of each document.
• GETXML — retrieves or constructs the XML representation of the outbound document. This routine relies on the XMLDOM and XMLPARSER built-ins listed in the dependency tree.
• PUTMSG — places a message onto the outbound workflow queue, interacting with WF_EVENT, WF_AGENT_T, and the WF_PARAMETER_LIST_T / WF_PARAMETER_T types to build the event payload.

Additional private routines are implied by the dependency references to ECX_ACTIONS, ECX_UTILS, and ECX_UTIL_API, but only the three above are formally documented. No parameter signatures are published in the metadata.

Tables Accessed

The package references the following documented tables and synonyms:

• ECX_OUTPUT_RUNS_S — the outbound run sequence and control table. This is the table behind the user's search term ecx_output_runs_s; it supplies the run identifiers that PROCESS_OUTBOUND_DOCUMENTS consumes and updates as documents are marked processed.
• ECX_MAPPINGS — holds the mapping rules used to translate Oracle EBS document values to trading-partner expectations.
• ECX_OBJECTS — defines the document objects handled by the mapping and generation logic.
• ECX_STANDARDS — the EDI standard definitions (for example, X12 or EDIFACT) that govern document layout.
• ECX_TP_HEADERS — trading partner header information, including communication and control details used at dispatch.
• WF_AGENT_T, WF_EVENT_T, WF_PARAMETER_LIST_T, WF_PARAMETER_T, WF_SYSTEMS — workflow event and agent tables employed by PUTMSG to enqueue outbound messages.

Utility built-ins (DBMS_LOB, DBMS_SQL, DUAL, PLITBLM, XMLDOM) are also referenced, the first two for large-object manipulation and dynamic SQL, the latter two for XML and PL/SQL table handling.

Usage Notes

ECX_OUTBOUND is normally invoked indirectly: the EDI Gateway outbound concurrent programs and the ECX outbound workflow queue handler call PROCESS_OUTBOUND_DOCUMENTS after run records are created in ECX_OUTPUT_RUNS_S. GETXML and PUTMSG are called within that flow rather than directly by end users. Because the package is classified as OTHER and is not referenced by any database object (though it is referenced by eight other packages), it should be treated as internal infrastructure. Custom developers are advised to invoke it only through the standard concurrent program or workflow entry points and not to call individual routines directly, as argument contracts and error handling are not published and may vary between 12.1.1 and 12.2.2. Diagnostic output is routed through ECX_DEBUG, ECX_ERRORLOG, FND_LOG, and FND_MESSAGE, so failures are visible in the standard EBS logging framework.