Results for “wrap_validate_message”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ECX_INBOUND_TRIG package is a core component of the Oracle E-Business Suite E-Commerce eXtension (ECX) / XML Gateway messaging framework. Its primary business function is to serve as the inbound message trigger handler that bridges the Oracle Workflow Business Event System with the XML Gateway processing engine. When a business event is raised (for example, an inbound XML document arriving from a trading partner), this package is responsible for triggering the appropriate processing routine, validating the message, and either placing it on an outbound queue or routing it through the internal processing pipeline. In ETRM 12.2.2 it is classified as an OTHER API owned by APPS and is documented with twelve procedures and functions. The package depends on SYS.STANDARD and is referenced by several other EBS packages, including ECX_RULE, ECX_STANDARD, EDR_PSIG_RULE, EDR_UTILITIES, MSC_RULE, and WF_DIAGNOSTICS_APPS, confirming its role as a shared, low-level trigger utility rather than a user-facing API.

Key Procedures and Functions

The documented callable units reflect the package's trigger and dispatch responsibilities:

  • GETMSG_FROM_QUEUE — retrieves an inbound message from the ECX queue for subsequent processing.
  • PROCESSMSG_FROM_QUEUE — processes a message that was obtained from the inbound queue.
  • PROCESSMSG_FROM_TABLE — processes an inbound message sourced from a database table rather than the queue.
  • PUT_ON_OUTBOUND — places a message onto the outbound queue.
  • WRAP_VALIDATE_MESSAGE — wrapper routine that invokes message validation logic.
  • VALIDATE_MESSAGE — performs validation of an inbound XML message against its defined standard.
  • PROCESSXML — executes the core XML processing logic for a message.
  • REPROCESS — re-submits a previously failed or held message for processing.
  • RAISEEVENT — raises an Oracle Workflow business event as part of the trigger lifecycle.
  • SETWFFUNCTIONERRORSTATUS — sets the Workflow function error status when processing fails.

Tables Accessed

The package operates against a set of ECX configuration and runtime tables accessed via APPS synonyms. The transaction and logging tables — ECX_TRANSACTIONS, ECX_INBOUND_LOGS, and ECX_DOCLOGS — record inbound messages and their processing history. ECX_EXT_PROCESSES, ECX_MAPPINGS, and ECX_STANDARDS (with ECX_STANDARD_ATTRIBUTES) supply the processing definitions and mapping rules used during validation and XML handling. Trading partner context is drawn from ECX_TP_HEADERS, ECX_TP_DETAILS, ECX_HUBS, and ECX_HUB_USERS. The tables ECX_OBJECTS, ECX_OUTPUT_RUNS_S, and ECX_TRIGGER_ID_S support object resolution and sequence-based identifier generation. Finally, WF_AGENT_T is referenced to resolve the Workflow agent associated with event raising.

Usage Notes

This package is not typically invoked directly from a form or a standard concurrent program. It is invoked internally by the Oracle Workflow Business Event System as the PL/SQL function associated with subscribed inbound events, and by sibling ECX packages such as ECX_RULE and ECX_STANDARD during message dispatch. Because it is classified as an OTHER API, it should be treated as an internal implementation utility; customizations should prefer the higher-level documented ECX APIs. Direct calls are appropriate only within extensions that replicate the inbound trigger lifecycle or diagnostics performed by WF_DIAGNOSTICS_APPS. Implementers should be aware that changes to this package can affect every inbound XML Gateway transaction and the dependent packages that reference it.