Results for “hxc_mappings”

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

Overview

HXC_MAPPINGS is a core configuration table within the Oracle E-Business Suite Time and Labor Engine (HXC) product family. It resides in the HXC schema and stores the definitions of mapping records that govern how time and labor data is transformed, deposited, or retrieved between the Time and Labor Engine and downstream or upstream systems and processes. In Oracle EBS 12.1.1 and 12.2.2, HXC_MAPPINGS serves as a central reference point referenced by multiple process-definition tables, making it a foundational object for the configuration of deposit processes, retrieval processes, mapping component usages, and time entry rules.

The heuristic Data Vault classification for this table is hub-leaning, indicating that MAPPING_ID behaves as a durable business key and that HXC_MAPPINGS is most naturally modeled as a hub, with dependent process and usage tables acting as satellites or links. This classification is a modeling suggestion mined from the foreign-key structure and should be validated against the actual integration architecture before being adopted.

Key Information Stored

HXC_MAPPINGS contains nine documented columns. The surrogate primary key is MAPPING_ID, enforced by the HXC_MAPPINGS_PK unique index. The business-key candidate is NAME, enforced by the HXC_MAPPINGS_UK1 unique index. Both unique indexes include ZD_EDITION_NAME, reflecting the editioning support present in 12.2.2.

• MAPPING_ID — Surrogate primary key uniquely identifying each mapping definition.
• NAME — Business-key name of the mapping; the primary user-facing identifier.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (12.2.2), included in both unique indexes.
• OBJECT_VERSION_NUMBER — Optimistic locking column used for row-level concurrency control.
• CREATED_BY, CREATION_DATE — Standard Who columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Who columns recording the last modifying user and timestamp.
• LAST_UPDATE_LOGIN — Login identifier associated with the most recent update.

The distinction between MAPPING_ID and NAME is important: MAPPING_ID is the technical key propagated to child tables, while NAME is the human-readable unique label used in configuration and troubleshooting.

Common Use Cases and Queries

Because HXC_MAPPINGS is referenced by deposit processes, retrieval processes, mapping component usages, and time entry rules, the most frequent query pattern is a join from a consuming table back to the mapping definition to resolve a NAME. For example:

• Resolving mapping names for deposit processes: SELECT d.*, m.NAME FROM HXC_DEPOSIT_PROCESSES d JOIN HXC_MAPPINGS m ON d.MAPPING_ID = m.MAPPING_ID;
• Identifying all process definitions that depend on a given mapping: query HXC_DEPOSIT_PROCESSES, HXC_RETRIEVAL_PROCESSES, and HXC_TIME_ENTRY_RULES filtered by MAPPING_ID.
• Impact analysis before modifying or retiring a mapping: enumerate dependent rows across all four referenced tables.
• Audit reporting: use CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace configuration changes over time.

Related Objects

The following tables reference HXC_MAPPINGS through MAPPING_ID and are the most significant related objects:

• HXC_DEPOSIT_PROCESSES — join column MAPPING_ID; deposit process definitions tied to a mapping.
• HXC_RETRIEVAL_PROCESSES — join column MAPPING_ID; retrieval process definitions tied to a mapping.
• HXC_MAPPING_COMP_USAGES — join column MAPPING_ID; records component-level usage of a mapping.
• HXC_TIME_ENTRY_RULES — join column MAPPING_ID; time entry rules that reference the mapping.

These dependencies confirm that HXC_MAPPINGS is a hub object whose MAPPING_ID is propagated as a foreign key across the HXC process and rule model.