Results for “map_code”

2 results




Overview
Explore in AI Chat

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

Overview

ECX_MAPPINGS is the definitional master table for the XML Gateway mapping framework in Oracle E-Business Suite, owned by the ECX schema. XML Gateway is the integration infrastructure that allows external systems to exchange business documents with EBS through standardized XML messages, and every message processed by the gateway is governed by a map definition. ECX_MAPPINGS holds those map headers; each row represents a logical mapping (for example, an inbound or outbound transaction definition) that binds an XML message structure to an EBS business object and its processing rules.

The table is the central hub of the XML Gateway metadata model. Downstream definition tables—attribute mappings, level mappings, procedure mappings, object definitions, level definitions, and attribute definitions—all carry a MAP_ID column that points back to ECX_MAPPINGS, so a single map row fans out into a complete mapping specification. From a Data Vault modeling perspective, the mined foreign-key structure classifies ECX_MAPPINGS as a hub: it holds the durable identity of each map, with satellites and links attaching descriptive and structural detail around it.

ECX_MAPPINGS is present and valid in both EBS 12.1.1 and 12.2.2. The 12.2.2 documented schema exposes 14 columns, and the table participates in online patching through its ZD_EDITION_NAME column and edition-aware unique indexes.

Key Information Stored

The most significant columns documented for ECX_MAPPINGS are:

  • MAP_ID — the surrogate primary key (ECX_MAPPINGS_PK) that uniquely identifies each map and is the join key for every child definition table.
  • MAP_CODE — the user-facing business identifier for the map; together with ZD_EDITION_NAME it forms the unique index ECX_MAPPINGS_U1.
  • DESCRIPTION — free-text explanation of the map's purpose, typically the transaction type and direction.
  • OBJECT_ID_SOURCE and OBJECT_ID_TARGET — references that identify the source and target business objects involved in the mapping.
  • ENABLED — flag controlling whether the map is active and available to the gateway at runtime.
  • ECX_MAJOR_VERSION and ECX_MINOR_VERSION — version attributes used to distinguish releases of the XML Gateway mapping metadata.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created or last changed the definition and when.
  • ZD_EDITION_NAME — the editioning column supporting Online Patching in 12.2.x; the second unique index, ECX_MAPPINGS_U2 (MAP_ID, ZD_EDITION_NAME), enforces edition-aware uniqueness.

Common Use Cases and Queries

The table is queried most often to inventory the maps available in a system, to confirm which maps are active, and to trace a transaction failure back to its map definition. A typical inventory query is:

  • SELECT map_id, map_code, description, enabled FROM ecx.ecx_mappings ORDER BY map_code;
  • Joining to the dependent tables to inspect a complete mapping definition, for example linking ECX_MAPPINGS to ECX_OBJECTS, ECX_LEVEL_MAPPINGS, or ECX_PROC_MAPPINGS on MAP_ID.
  • Filtering on ENABLED = 'Y' to list only maps that the gateway will invoke.
  • Auditing recently modified definitions using LAST_UPDATED_BY and LAST_UPDATE_DATE, useful when troubleshooting post-patch integration failures.

In 12.2.x, queries should be aware of editioning; existing data typically carries a null or default ZD_EDITION_NAME, and the unique index ensures that patched copies of a map are distinguished from the run edition.

Related Objects

ECX_MAPPINGS is referenced by MAP_ID from seven documented child tables, each supplying a distinct facet of the mapping specification:

  • ECX_ATTRIBUTE_MAPPINGS (MAP_ID) — column-to-XML element and attribute level mapping rules.
  • ECX_LEVEL_MAPPINGS (MAP_ID) — hierarchical level definitions within the message.
  • ECX_PROC_MAPPINGS (MAP_ID) — processing rules or stored procedures invoked during mapping.
  • ECX_TP_DETAILS (MAP_ID) — trading partner details associated with the map.
  • ECX_OBJECTS (MAP_ID) — business object definitions bound to the map.
  • ECX_OBJECT_LEVELS (MAP_ID) — level structures for the associated objects.
  • ECX_OBJECT_ATTRIBUTES (MAP_ID) — attribute definitions for those objects.

Collectively, these tables constitute the XML Gateway repository, and ECX_MAPPINGS is the parent record that must be resolved first when diagnosing or extending any gateway transaction.