Results for “hxc_mapping_comp_usages”

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

Overview

HXC_MAPPING_COMP_USAGES is a table in the HXC schema, owned by the Oracle Time and Labor Engine (HXC) product module. Its documented description is "Mapping Component Usages." In the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, it functions as an associative detail table that records which mapping components are used by a given mapping definition. It sits beneath the HXC_MAPPINGS parent and alongside HXC_MAPPING_COMPONENTS, allowing the Time and Labor Engine to resolve how incoming time attributes are transformed and routed.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This reflects the table's role as a many-to-many intersection between mappings and mapping components, rather than a descriptive hub or a satellite holding slowly changing attributes.

Key Information Stored

The documented physical schema for release 12.2.2 contains ten columns in the HXC schema. The most significant are summarized below.

• MAPPING_COMP_USAGE_ID — the surrogate primary key, defined by the unique index HXC_MAPPING_COMP_USAGES_PK.
• ZD_EDITION_NAME — the editioning column that, together with the surrogate key, forms the documented unique index HXC_MAPPING_COMP_USAGES_PK (MAPPING_COMP_USAGE_ID, ZD_EDITION_NAME), making it the business-key candidate for edition-aware lookups.
• MAPPING_ID — foreign key to HXC_MAPPINGS, identifying the parent mapping definition that owns this usage row.
• MAPPING_COMPONENT_ID — foreign key to HXC_MAPPING_COMPONENTS, identifying the specific component referenced by the mapping.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing the creating and last-updating user, timestamps, and login context.

Common Use Cases and Queries

The table is typically queried by administrators and technical consultants diagnosing Time and Labor mapping configuration, particularly to determine which components a mapping consumes and to trace the mapping path applied to a worker's time entries.

List the components used by a specific mapping:

• SELECT mcu.mapping_component_id, mc.* FROM hxc_mapping_comp_usages mcu JOIN hxc_mapping_components mc ON mc.mapping_component_id = mcu.mapping_component_id WHERE mcu.mapping_id = :mapping_id;

Identify all mappings that reference a given component:

• SELECT mcu.mapping_id FROM hxc_mapping_comp_usages mcu WHERE mcu.mapping_component_id = :component_id;

Because the table is edition-enabled in 12.2.x, reporting queries should constrain ZD_EDITION_NAME where the runtime edition must be respected. Typical reporting outputs include mapping coverage matrices, orphan-component detection, and impact analysis before changing a shared mapping component.

Related Objects

The following objects are the most significant references to or dependents of this table, based on the documented foreign keys and primary key structure.

• HXC_MAPPINGS — parent mapping definitions; joined via HXC_MAPPING_COMP_USAGES.MAPPING_ID.
• HXC_MAPPING_COMPONENTS — component definitions; joined via HXC_MAPPING_COMP_USAGES.MAPPING_COMPONENT_ID.
• HXC_MAPPING_COMP_USAGES_PK — the unique index enforcing the surrogate primary key and edition-aware business key.
• HXC Time and Labor mapping views and APIs — runtime consumers that read mapping definitions to transform time entry attributes.