Results for “party_site_code”

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

Overview

The ECX_OAG_CBOD_V view is a reporting and integration object in the Oracle E-Business Suite XML Gateway module (ECX). It is owned by the APPS schema and is defined as a view over the XML Gateway document log, exposing message-oriented metadata in a shape suitable for Open Applications Group (OAG) confirmation Business Object Document (BOD) processing. In both Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID, indicating that its definition compiles cleanly against the referenced base synonym.

The view is not a transaction-processing entry point; rather, it provides a denormalized, read-oriented projection of XML Gateway messages so that outbound and inbound confirmation BODs can be inspected, reconciled, or re-used by integration routines. Its principal utility is to surface the XML Gateway message identifier, message type, and transaction classification alongside the descriptive header and payload attributes extracted from logged documents. This makes it a convenient source for diagnostics, audit reporting, and the construction of confirmation responses that reference a previously transmitted document.

Underlying Base Objects

According to the documented view metadata, ECX_OAG_CBOD_V is defined over a single referenced base object: the ECX_DOCLOGS synonym in the APPS schema. ECX_DOCLOGS is the XML Gateway document log that records each message transacted through the gateway, including its identifier, type, party information, protocol details, and a numbered set of generic FIELD columns used to carry payload-specific values.

The view does not introduce joins to other tables; instead it renames and maps the generic columns of ECX_DOCLOGS into semantically meaningful aliases. Notably, the base column TRANSACTION_TYPE is exposed as EXT_TYPE, and TRANSACTION_SUBTYPE as EXT_SUBTYPE. This aliasing is the reason the view appears when searching for "ext_type": consumers looking for the transaction-type classification of a logged XML Gateway message will find it exposed under the EXT_TYPE column name here, even though the underlying stored column is TRANSACTION_TYPE. The view therefore acts as a naming and presentation layer rather than an aggregating or join-driven construct.

Key Columns

The columns exposed by the view fall into several functional groups:

• Message identity: MSGID and MESSAGE_TYPE identify the logged XML Gateway message and its category; DOCUMENT_ID (aliased from INTERNAL_CONTROL_NUMBER) provides the internal control number, while DOCUMENT_NUMBER carries the business document number.
• Transaction classification: EXT_TYPE (from TRANSACTION_TYPE) and EXT_SUBTYPE (from TRANSACTION_SUBTYPE) describe the transaction type and subtype of the logged message.
• Party and routing: PARTY_CODE (from PARTYID), PARTY_SITE_CODE (from PARTY_SITE_ID), PARTY_TYPE, ROUTING_PARTY_CODE (from ATTRIBUTE3), and EXCHANGE_NAME (from ATTRIBUTE1) describe who sent or received the document and how it was routed.
• Protocol: PROTOCOL_TYPE and PROTOCOL_ADDRESS describe the transport used for delivery.
• References: ORIG_REFERENCE_ID and REFERENCEID, together with LOGICALID, support correlation between a confirmation BOD and the originating document.
• OAG payload attributes: The generic FIELD columns are renamed to OAG-specific semantics, including VERB (FIELD1), NOUN (FIELD2), REVISION (FIELD3), COMPONENT (FIELD5), TASK (FIELD6), CONFIRMATION (FIELD8), LANGUAGE (FIELD9), CODEPAGE (FIELD10), and AUTHID (FIELD11). Date and time components are exposed individually through YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, SUBSECOND, and TIMEZONE.
• Diagnostics: LOGFILE records the associated log file reference.

Common Use Cases and Queries

Typical usage centers on inspecting logged confirmation messages and correlating them with the transaction types they represent. A straightforward query lists the transaction classification and party context for recent messages:

• SELECT MSGID, MESSAGE_TYPE, EXT_TYPE, EXT_SUBTYPE, DOCUMENT_NUMBER, PARTY_CODE, ROUTING_PARTY_CODE FROM ECX_OAG_CBOD_V WHERE EXT_TYPE = :p_type;
• SELECT MSGID, VERB, NOUN, REVISION, CONFIRMATION, ORIG_REFERENCE_ID FROM ECX_OAG_CBOD_V WHERE DOCUMENT_NUMBER = :p_doc;
• SELECT MSGID, LOGFILE, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND FROM ECX_OAG_CBOD_V WHERE MESSAGE_TYPE = :p_msg_type ORDER BY MSGID;

These patterns are useful for troubleshooting failed or delayed confirmations, for audit reporting on gateway traffic by transaction type, and for supplying the reference identifiers required when a downstream process must construct a confirmation BOD that points back to an original message. All queries should be run in a read-only context, since the view is intended for inquiry and reporting rather than data maintenance.