Search Results ecx_trigger_id_s




Overview
Explore in AI Chat

Overview

ECX_INBOUND_LISTENER_QH is an internal Oracle E-Business Suite package body owned by APPS that implements the inbound listener queue handler for the E-Business Suite Integrated SOA Gateway / EDI messaging infrastructure (ECX schema). Its principal role is to service the Advanced Queue (AQ) that holds inbound business events destined for the Workflow Business Event System. When an inbound message arrives on the ECX queue, this package dequeues the raw payload, resolves it into a WF_EVENT_T structure, determines the correct event name through the get_event_name helper, and hands the event to Workflow for subscription-based processing. The package also provides the corresponding enqueue path used to place inbound messages back onto the queue when required.

Because the user search term was get_event_name, it is worth noting that this private procedure is the piece of logic that normalizes an inbound message's attribute4 value into a fully qualified Oracle event name. If the value already begins with the oracle.apps. prefix it is lower-cased and returned unchanged; otherwise the substring preceding the first underscore is extracted, and a prefix length of three characters or fewer produces an oracle.apps.<prefix>.inbound.message.receive event, while anything longer falls back to the generic oracle.apps.ecx.inbound.message.receive event. A null input likewise yields the generic ECX event. This routine, though not part of the formally documented API classification (the package is classified OTHER, not as a public API), governs which Workflow subscriptions fire for each inbound message.

Key Procedures and Functions

  • DEQUEUE — Dequeues a single inbound message from the ECX Advanced Queue using DBMS_AQ, given an agent GUID. It reads the message properties and payload, maps the sender and recipient agents, populates the WF_EVENT_T structure (including event name derived via get_event_name logic), and returns the constructed event for Workflow processing. It also manages queue exceptions such as the no-messages condition (-25228).
  • ENQUEUE — The complementary operation that places an inbound message onto the ECX AQ, associating it with the appropriate agent and message attributes so it can be subsequently dequeued and raised as a Workflow event.

The private get_event_name procedure, although not listed among the documented callable procedures, is the internal naming authority used by the dequeue path to map message attribute4 values onto standard event names.

Tables Accessed

  • ECX_INLSTN_S — The inbound listener sequence/setup object used to obtain or register inbound listener configuration during dequeue processing.
  • ECX_TP_DETAILS — Trading partner detail records, used to resolve inbound agent/trading partner context (including encrypted password handling).
  • ECX_TRIGGER_ID_S — Sequence supplying trigger identifiers for the inbound processing cycle.
  • WF_AGENTS and WF_SYSTEMS — Workflow agent and system registries, used to translate agent GUIDs into the WF_AGENT_T sender and recipient roles attached to the event.
  • DBMS_AQ and DUAL — Oracle AQ package calls for enqueue/dequeue operations and dual for sequence selection.

The package additionally references the WF_AGENT_T and WF_EVENT_T Workflow datatypes when constructing event payloads.

Usage Notes

ECX_INBOUND_LISTENER_QH is invoked indirectly by the ECX inbound messaging infrastructure rather than from Oracle Forms or standard concurrent programs. It is not referenced by any other documented package (0 dependents), confirming its role as a leaf-level implementation detail of the inbound listener. Customizations that need to influence event naming or inbound routing should not call this package directly; instead, administrators should be aware that the get_event_name logic determines whether a message raises a partner-specific event (oracle.apps.<prefix>.inbound.message.receive) or the generic oracle.apps.ecx.inbound.message.receive event, and should configure Workflow subscriptions accordingly. This behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, though the source header indicates the shipped version dates to the 2007 maintenance baseline.