Results for “ecx_mappings_u2”

12 results




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

Overview

ECX.ECX_MAPPINGS is a seed data table owned by the ECX schema within Oracle E-Business Suite. It stores the definitions of the maps used by the XML Gateway, the integration layer responsible for exchanging business documents with external trading partners. Each row in ECX_MAPPINGS defines a map that associates a source object with a target object and provides the versioning envelope under which transformation and routing logic executes. The table resides in the APPS_TS_SEED tablespace, reflecting its role as setup and reference data populated at installation or patching time rather than transactional runtime data. Its status is documented as VALID in both 12.1.1 and 12.2.2 ETRM schemas.

The heuristic Data Vault classification for this object is hub. In that modeling view, MAP_ID serves as the hub key and the remaining descriptive and versioning columns behave as hub attributes. Consumers should treat this suggestion as a modeling observation rather than a strict architectural mandate, since the physical table also carries standard Oracle WHO columns and a multi-tenant editioning column.

Key Information Stored

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

Two unique indexes exist: ECX_MAPPINGS_U1 on (MAP_CODE, ZD_EDITION_NAME) and ECX_MAPPINGS_U2 on (MAP_ID, ZD_EDITION_NAME). The user's search for "ecx_mappings_u2" corresponds to the primary-key-supporting unique index that pairs the surrogate key with the edition name.

Common Use Cases and Queries

Typical scenarios include verifying map configuration before enabling an outbound XML Gateway transaction, auditing which maps are active for a given version, and joining map definitions to their attribute and level detail tables to reconstruct complete mapping behavior.

A basic lookup by business key:

SELECT MAP_ID, MAP_CODE, DESCRIPTION, ENABLED, ECX_MAJOR_VERSION, ECX_MINOR_VERSION FROM ECX.ECX_MAPPINGS WHERE MAP_CODE = :p_map_code;

A listing of enabled maps with their source and target objects:

SELECT MAP_ID, MAP_CODE, OBJECT_ID_SOURCE, OBJECT_ID_TARGET FROM ECX.ECX_MAPPINGS WHERE ENABLED = 'Y';

A join to detail mappings for diagnostics:

SELECT m.MAP_CODE, a.ATTRIBUTE_NAME, a.ATTRIBUTE_TYPE FROM ECX.ECX_MAPPINGS m, ECX.ECX_ATTRIBUTE_MAPPINGS a WHERE m.MAP_ID = a.MAP_ID AND m.MAP_CODE = :p_map_code;

Related Objects

ECX_MAPPINGS is referenced by foreign keys from seven dependent tables, all keyed on MAP_ID:

  • ECX_ATTRIBUTE_MAPPINGS — attribute-level transformation definitions (ECX_ATTRIBUTE_MAPPINGS.MAP_ID → ECX_MAPPINGS.MAP_ID).
  • ECX_LEVEL_MAPPINGS — level-based mappings within a transaction structure.
  • ECX_PROC_MAPPINGS — procedural mapping logic invoked during transformation.
  • ECX_TP_DETAILS — trading partner details associated with a map.
  • ECX_OBJECTS — object definitions linked to maps.
  • ECX_OBJECT_LEVELS — object-level hierarchy used by map processing.
  • ECX_OBJECT_ATTRIBUTES — object attribute definitions tied to map behavior.

The table also exposes an editioning view ECX.ECX_MAPPINGS# used for Online Patching support in 12.2.x. No database objects are directly referenced by ECX_MAPPINGS beyond the WHO column foreign keys to FND_USER.