Search Results logical_id




Overview
Explore in AI Chat

Overview

ECX_OAG_CONTROLAREA_V is a public view owned by the APPS schema in Oracle E-Business Suite, defined in the ECX (XML Gateway) product. Its purpose is to construct the Control Area segment of an Open Applications Group (OAG) message, presenting the routing and control metadata that precedes the business document payload in an OAG Integration Specification (OAGIS) transaction. The view is not an operational data entry surface; it is a read-only, runtime projection used by the XML Gateway outbound processing engine to emit the standard OAG control block whenever an outbound message is generated from a transaction type and transaction subtype registered in the ECX repository.

Because the verb and noun identifiers in an OAG message are derived primarily from configured transaction type and transaction subtype values, the view is frequently the object of interest for implementers searching on "transaction_subtype." That column appears directly in the projection, sourced from ECX_TRANSACTIONS_B.TRANSACTION_SUBTYPE, making the view the canonical place to correlate an EBS transaction subtype with the verb/noun pair published in an outbound OAG envelope.

Underlying Base Objects

The view text joins four documented objects, all resolved through APPS synonyms or packages:

The view additionally calls the FND_PROFILE package, FND_PROFILE.VALUE('ECX_OAG_LOGICALID'), to retrieve the site-level logical identifier, and uses SQL built-ins USER, SYSDATE, and USERENV('LANG') to populate runtime attributes. The WHERE clause filters to EEP.DIRECTION = 'OUT', so only outbound definitions are represented.

Key Columns

  • VERB_VALUE / VERB_ATTVALUE — both mapped to EEP.EXT_SUBTYPE, carrying the OAG verb in value and attribute form.
  • NOUN_VALUE / NOUN_ATTVALUE / COMPONENT — all mapped to EEP.EXT_TYPE, providing the noun or component identifier.
  • TASK — also sourced from EXT_SUBTYPE, distinguishing the task element of the control area.
  • LOGICAL_ID — the profile-driven sender logical identifier ("from" logical ID) for the message.
  • DATETIME / DATE_ATTVALUE / REFERENCE_ID — fixed runtime values: SYSDATE, the literal 'CREATION', and the literal '1'.
  • LANGUAGE / CODEPAGE — session language from USERENV('LANG') and the NLS character set from V$NLS_PARAMETERS.
  • AUTHID, CONFIRMATION, REVISION_VALUE, REVISION_ATTVALUE — AUTHID and CONFIRMATION are seeded with USER and 0 respectively; the revision columns are returned as NULL.
  • TRANSACTION_TYPE / TRANSACTION_SUBTYPE — the EBS transaction classification from ECX_TRANSACTIONS_B; these are the columns most relevant when tracing how a given transaction subtype maps to an OAG verb and noun.

Common Use Cases and Queries

The view is used to validate OAG envelope configuration, to diagnose mismatches between expected verb/noun pairs and configured transaction subtypes, and to confirm the logical ID and codepage emitted at runtime. A representative query to list all outbound OAG control areas with their transaction classifications is:

  • SELECT transaction_type, transaction_subtype, verb_value, noun_value, task, logical_id, codepage FROM ecx_oag_controlarea_v ORDER BY transaction_type, transaction_subtype;

To isolate a specific subtype during troubleshooting of an outbound interface:

  • SELECT verb_value, noun_value, component, logical_id, language, codepage FROM ecx_oag_controlarea_v WHERE transaction_subtype = 'INVOICE';

Because the view joins V$NLS_PARAMETERS and calls a profile function, it should be queried as APPS or a user with EXECUTE on FND_PROFILE and SELECT on the base ECX and V$ objects. It returns no rows when the target transaction has no outbound ECX_EXT_PROCESSES definition or is not registered against the OAG standard.