Results for “ecx_level_mappings_pk”

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

Overview

ECX_LEVEL_MAPPINGS is a table owned by the ECX schema within the XML Gateway module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. The table's documented purpose is to store the relationship between source and target mappings. In the XML Gateway architecture, this means it records how a hierarchical level in an inbound or outbound XML message corresponds to a level in the associated Oracle EBS business object or interface table, together with the individual elements that participate in each level-level pairing.

The ETRM metadata classifies this object heuristically as satellite-leaning under a Data Vault modeling interpretation. That classification should be treated as a modeling suggestion rather than a normative fact: the table carries descriptive mapping attributes that extend a parent mapping definition rather than acting as an independent hub of business entities. Its grain is defined by the combination of MAP_ID and LEVEL_MAPPING_ID, making it subordinate to the parent mapping record it enriches.

Key Information Stored

The table contains seven documented columns. The most significant are:

• MAP_ID — Identifies the parent mapping definition. This is a foreign key to ECX_MAPPINGS and forms the leading column of both the primary key and the unique index.
• LEVEL_MAPPING_ID — The surrogate identifier for each level-to-level mapping row within a given MAP_ID. Together with MAP_ID it constitutes the primary key ECX_LEVEL_MAPPINGS_PK.
• SOURCE_LEVEL_ID — Identifies the source (XML message) hierarchical level being mapped.
• TARGET_LEVEL_ID — Identifies the corresponding target (EBS object or interface) level that receives the mapped data.
• SOURCE_ELEMENT_ID — References the specific element within the source level that is being translated.
• TARGET_ELEMENT_ID — References the specific element within the target level into which the source element is translated.
• ZD_EDITION_NAME — The editioning column introduced in the 12.2 online patching architecture. It is part of the unique index ECX_LEVEL_MAPPINGS_U1 (MAP_ID, LEVEL_MAPPING_ID, ZD_EDITION_NAME) and is a key differentiator between 12.1.1 and 12.2.2 deployments.

The unique index ECX_LEVEL_MAPPINGS_U1, spanning MAP_ID, LEVEL_MAPPING_ID, and ZD_EDITION_NAME, is the documented business-key candidate. The surrogate primary key remains MAP_ID plus LEVEL_MAPPING_ID; the edition name serves only to isolate mapping definitions across editioned environments in 12.2.x.

Common Use Cases and Queries

The primary use case is diagnostics and validation of XML Gateway transaction flows. When a message fails to populate the expected interface columns, the mapping chain spanning ECX_MAPPINGS, ECX_LEVEL_MAPPINGS, and the associated level and element definitions is examined to confirm that a valid source-to-target path exists. Typical queries join back to the parent mapping to obtain the transaction type and direction:

• List all level mappings for a given transaction type: join ECX_LEVEL_MAPPINGS to ECX_MAPPINGS on MAP_ID and filter by the parent mapping's transaction identifier.
• Verify element coverage: select SOURCE_ELEMENT_ID and TARGET_ELEMENT_ID for a MAP_ID and compare the result set against the expected message schema.
• Edition-scoped reporting: in 12.2.2, constrain queries by ZD_EDITION_NAME to avoid returning duplicate rows from prior editions during an online patching cycle.

Reporting use cases include generating mapping inventories for integration audits, documenting which source elements feed each target column, and assessing the impact of a schema change before a message interface is modified.

Related Objects

• ECX_MAPPINGS — Parent table referenced by ECX_LEVEL_MAPPINGS.MAP_ID; supplies the mapping definition header.
• ECX_LEVEL_MAPPINGS_PK — Composite primary key on MAP_ID and LEVEL_MAPPING_ID.
• ECX_LEVEL_MAPPINGS_U1 — Unique index on MAP_ID, LEVEL_MAPPING_ID, and ZD_EDITION_NAME.
• ECX_LEVELS / ECX_ELEMENTS — Reference tables supplying the definitions behind SOURCE_LEVEL_ID, TARGET_LEVEL_ID, SOURCE_ELEMENT_ID, and TARGET_ELEMENT_ID.

Together these objects form the metadata backbone that the XML Gateway runtime consults to transform messages between external representations and internal EBS structures.