Search Results oco_18586913

Overview

ECE_MAPPINGS_UPG is an upgrade staging table owned by the EC schema within the Oracle E-Business Suite e-Commerce Gateway module. In Oracle EBS 12.1.1 and 12.2.2, its documented purpose is to serve as the upgrade table for ECE_MAPPINGS, the base configuration table that defines mapping rules between Oracle EBS data elements and the flat-file or XML structures exchanged with external trading partners. During an upgrade cycle, ECE_MAPPINGS_UPG holds intermediate rows that are validated and reconciled before being merged into the permanent ECE_MAPPINGS definition set. The table exposes seven documented columns and carries a single primary key constraint, OCO_18586913, defined on MAP_ID.

From a Data Vault modeling perspective, the supplied metadata classifies this object as standalone. Following that heuristic, the table is best treated as a staging or load buffer rather than a fully modeled hub, link, or satellite. MAP_ID functions as the surrogate primary key, and because the FK relationship mined from the schema shows no outbound dependencies, the object can be modeled as an isolated hub candidate whose descriptive attributes (MAP_CODE, DESCRIPTION, MAP_TYPE, TRANSACTION_TYPE, ROOT_ELEMENT, ENABLED) behave as a satellite payload attached to that key.

Key Information Stored

• MAP_ID — The single-column primary key (constraint OCO_18586913) and surrogate identifier for each mapping row staged for upgrade.
• MAP_CODE — The business-facing code that identifies the mapping definition; this is the natural business-key candidate that corresponds to the same column in ECE_MAPPINGS.
• MAP_TYPE — Classifies the nature of the mapping, distinguishing the category of transformation or translation the gateway applies.
• TRANSACTION_TYPE — Identifies the e-Commerce Gateway transaction (for example, purchase order, invoice, or ship notice) to which the mapping applies.
• ROOT_ELEMENT — Names the root XML or hierarchical document element against which the mapping is evaluated during message construction.
• ENABLED — The activation flag indicating whether the staged mapping is active for processing.
• DESCRIPTION — Free-text description providing the user-visible meaning of the mapping entry.

The documented KEY/PK relationship label “standalone” confirms that no foreign keys emanate from this table; integrity is enforced solely through the MAP_ID primary key.

Common Use Cases and Queries

Typical usage is upgrade validation and reconciliation. Administrators and technical consultants compare rows in the upgrade table against the live mapping table to confirm that every staged definition was promoted correctly, and query for disabled or orphaned entries before completing the upgrade.

Representative SQL patterns include:

• Row-count reconciliation between ECE_MAPPINGS_UPG and ECE_MAPPINGS to detect dropped or duplicate mappings.
• Filtering by TRANSACTION_TYPE and MAP_TYPE to review mappings for a specific document interface prior to cutover.
• Identifying rows where ENABLED is not set as expected for the target transaction flow.
• Joining ECE_MAPPINGS_UPG to ECE_MAPPINGS on MAP_ID to isolate staged rows with no corresponding live record.

Because the object is an upgrade artifact, it should not be used for steady-state operational reporting; post-upgrade reporting should target ECE_MAPPINGS itself.

Related Objects

• ECE_MAPPINGS — The permanent mapping definition table that ECE_MAPPINGS_UPG stages data for; join on MAP_ID.
• ECE_MAPPINGS_UPG primary key constraint OCO_18586913 — Enforces uniqueness of MAP_ID and anchors any modeled hub candidate.
• EC schema upgrade scripts — Concurrent programs and SQL upgrade drivers that populate ECE_MAPPINGS_UPG and merge validated rows into ECE_MAPPINGS.
• e-Commerce Gateway transaction configuration objects — Transaction-type and root-element definitions referenced logically through TRANSACTION_TYPE and ROOT_ELEMENT values.

No additional FK-dependent objects are documented, consistent with the standalone classification.