Results for “ecx_transaction_subtype”

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

Overview

ISG_XMLG_UTIL is a utility package body owned by APPS in the Oracle E-Business Suite, classified in the ETRM repository as a UTIL object. Its primary responsibility is to place outbound XML Gateway messages onto the Oracle Advanced Queuing (AQ) infrastructure so that they can be processed by the XML Gateway transport and delivery agents. In business terms, this package provides the programmatic bridge between an application or integration component that has assembled an outbound business document and the XML Gateway messaging layer that routes that document to a trading partner.

The package header deliberately exposes a narrow surface: a single documented procedure, ENQUEUE_MESSAGE. This narrowness reflects its role as a reusable plumbing routine rather than a business API. The source header identifier (“ISGECXUTILB.pls 120.3 2011/07/18”) confirms the package is part of the ISG (Integrated Supply Chain / XML Gateway) family of ECX-prefixed utilities that predate and support the broader ECX and EDI Gateway stack.

Key Procedures and Functions

• ENQUEUE_MESSAGE — Enqueues an outbound XML Gateway message into the AQ queue. The procedure accepts the standard XML Gateway routing attributes (message type, message standard, transaction type, transaction subtype, document number, party and party site identifiers, and username) together with the message payload, which is passed as a CLOB, and returns the generated message identifier through an OUT parameter. Internally, the procedure first validates the trading partner and user context by calling ECX_Trading_Partner_PVT.validateTPUser, using the message type, standard, transaction type and subtype, and party site ID as inputs. If validation succeeds, it constructs the AQ header and text message objects and performs the enqueue using DBMS_AQ enqueue options. Validation failures raise the package’s internal exceptions (INVALID_TP_SETUP or TP_SETUP_ERROR) rather than silently discarding the message.

Tables Accessed

• WF_AGENTS — The Workflow agent view is used to resolve the agent name and associated AQ agent required for the enqueue operation. The procedure derives the agent name from the trading partner and message routing attributes before building the message properties.
• DBMS_AQ — Although a PL/SQL package rather than a table, DBMS_AQ appears in the dependency list because the enqueue is executed through its enqueue_options_t and message_properties_t types and its enqueue entry point.
• DUAL — Referenced for lightweight scalar evaluation, typically when the procedure needs to normalize or default a value without touching application data.

The ETRM metadata records no other base tables accessed directly. Trading partner validation is delegated to ECX_Trading_Partner_PVT, so the underlying ECX trading partner and location tables are read through that package rather than directly by ISG_XMLG_UTIL.

Usage Notes

ISG_XMLG_UTIL is a low-level utility and is not normally invoked interactively. It is called from custom PL/SQL integration code, from concurrent programs that generate outbound XML documents, and from other XML Gateway procedures that need to publish a message to the outbound queue. Because the procedure performs trading partner validation before enqueue, callers should expect an exception when the trading partner, party site, or user combination is not correctly configured for the specified message type, standard, transaction type, and transaction subtype.

The parameter named ecx_transaction_subtype is the XML Gateway transaction subtype used to qualify the business document during routing and partner validation. When troubleshooting enqueue failures, the transaction type and subtype pair is the first attribute to verify, since validateTPUser uses it to determine whether an active trading partner agreement exists.

In EBS 12.1.1 and 12.2.2 environments, the package resides in the APPS schema and should be referenced as APPS.ISG_XMLG_UTIL or through the APPS synonym resolution. The ETRM metadata indicates no other packages depend on it, so its footprint is limited to direct callers; customizations extending XML Gateway output should call it rather than replicating the AQ enqueue logic, to preserve the validation behavior and the standard message header construction.