Results for “cln_xmlg_txn_types_v”

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

Overview

CLN_XMLG_TXN_TYPES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite. It is delivered as part of the CLN product family — Supply Chain Trading Connector for RosettaNet — and is documented as VALID in both EBS 12.1.1 and 12.2.2. The view presents the distinct combinations of XML Gateway transaction setup entries, exposing the transaction type, sub-type, and direction values that have been configured in the XML Gateway infrastructure.

Rather than storing data of its own, the view projects a deduplicated projection of the XML Gateway external process configuration. Its functional purpose is to give integrators, RosettaNet trading partner administrators, and reporting developers a compact list of the transaction signatures (type/sub-type/direction) that the connector is prepared to handle. Because the view is a thin, read-only layer, it is safe to query from custom reports, concurrent programs, and analytical SQL without affecting transactional behavior. The user search term \"ext_type\" corresponds directly to the view's driving column, which is inherited from the ECX_EXT_PROCESSES base object.

Underlying Base Objects

The view is defined over a single referenced base object: ECX_EXT_PROCESSES, accessed through a SYNONYM in the APPS schema. ECX_EXT_PROCESSES is the XML Gateway repository of external process definitions, where each row describes a transaction that the gateway can process (for example, an outbound or inbound business document along with its processing rules).

The view's definition applies a SELECT DISTINCT over three columns of that table — EXT_TYPE, EXT_SUBTYPE, and DIRECTION — so that only one row per unique transaction signature is returned. No joins, filters, or DML are present; the view is non-updatable and does not inherit the full column set of the base table. Because it depends solely on a synonym to an XML Gateway object, its contents reflect the currently configured transactions in the instance and change immediately as XML Gateway setup is maintained.

Key Columns

• TRANSACTION_TYPE — The exposed label corresponding to EXT_TYPE on ECX_EXT_PROCESSES. It identifies the transaction family being configured in XML Gateway. This is the column most directly associated with the user search term \"ext_type\".
• TRANSACTION_SUBTYPE — The exposed label corresponding to EXT_SUBTYPE. It narrows the transaction family to a specific document or message variant, allowing multiple related transactions to share a type while remaining distinguishable.
• DIRECTION — Identifies the flow of the transaction, distinguishing inbound from outbound processing, matching the DIRECTION column of the base table.

Note that although the documented column list is TRANSACTION_TYPE, TRANSACTION_SUBTYPE, and DIRECTION, the underlying view text selects the physical column names EXT_TYPE, EXT_SUBTYPE, and DIRECTION. Where a column alias is not explicitly assigned, consumers should verify the exact projected names against the deployed view definition in their instance, since the aliases are the interface that reporting code should rely on.

Common Use Cases and Queries

Typical uses include validating that the required RosettaNet transactions are enabled before onboarding a trading partner, feeding lookups in custom concurrent programs, and supporting troubleshooting of XML Gateway routing. A representative query listing all configured transaction signatures is:

SELECT transaction_type, transaction_subtype, direction FROM apps.cln_xmlg_txn_types_v ORDER BY transaction_type, transaction_subtype, direction;

To isolate outbound document types the caller can filter on direction, for example WHERE direction = 'OUT'. Because the DISTINCT is applied in the view, the result set is naturally deduplicated and suitable for direct use in value sets or reporting extracts. As the view is read-only and security is governed by the APPS schema grants, access should be granted through standard EBS responsibilities rather than direct table privileges.