Results for “hxc_mapping_components”

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

Overview

HXC_MAPPING_COMPONENTS is a configuration table in the Oracle E-Business Suite Time and Labor Engine module (HXC schema). It stores the individual mapping components that define how Time and Labor data elements are translated, sourced, or projected between the various structures used in time collection, rules processing, and payroll aggregation. Each mapping component describes a discrete field or segment that participates in a broader mapping definition, and is tied to a build block information type. In effect, the table provides the atomic, reusable building blocks from which higher-level alias and usage mappings are assembled.

The objects it depends on and the objects that depend on it indicate the table functions as a reference data source rather than a high-volume transactional table. From a Data Vault perspective, the mined relationship structure is hub-leaning, which suggests modeling this object as a hub entity keyed on the surrogate identifier, with its descriptive attributes carried in a companion satellite and its dependencies represented as links to the referenced dimension tables.

Key Information Stored

The documented physical schema contains twelve columns, of which the following are the most significant:

• MAPPING_COMPONENT_ID — the surrogate primary key defined by HXC_MAPPING_COMPONENTS_PK. It uniquely identifies each mapping component row and is the column referenced by all dependent foreign keys.
• NAME — the business identifier for the component. Together with the edition column it forms the unique business key under HXC_MAPPING_COMPONENTS_UK1 (NAME, ZD_EDITION_NAME), making it the natural candidate for user-facing lookups.
• FIELD_NAME — the underlying field or column name that the mapping component represents, indicating the source or target data element.
• BLD_BLK_INFO_TYPE_ID — foreign key to HXC_BLD_BLK_INFO_TYPES, linking the component to its build block information type classification.
• SEGMENT — identifies the segment or logical partition within the mapping structure to which the component belongs.
• OBJECT_VERSION_NUMBER — the concurrency control column used by the EBS framework to detect stale updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on EBS tables.
• ZD_EDITION_NAME — the editioning column that supports multiple editions of the same logical row and is included in both unique indexes.

Common Use Cases and Queries

The primary practical use of HXC_MAPPING_COMPONENTS is diagnostic and configuration reporting. Administrators and support analysts query it to determine which mapping components exist, how they are named, and which build block information type they belong to. A typical lookup joins the table to its parent information type:

SELECT mc.mapping_component_id, mc.name, mc.field_name, mc.segment, bt.name
FROM hxc_mapping_components mc, hxc_bld_blk_info_types bt
WHERE mc.bld_blk_info_type_id = bt.bld_blk_info_type_id;

Because the table is widely referenced by alias type components and mapping component usages, it is frequently the driving table when resolving how a given alias or time category ultimately maps to its underlying field. Reverse lookups — finding every usage or alias that consumes a particular mapping component — rely on the foreign keys held in HXC_MAPPING_COMP_USAGES and HXC_ALIAS_TYPE_COMPONENTS. Reports commonly filter by NAME for a specific component or by BLD_BLK_INFO_TYPE_ID to enumerate all components of a given information type. When querying, remember that ZD_EDITION_NAME participates in the unique keys, so joins and lookups should account for editioning where multiple editions are active.

Related Objects

The following objects are the most significant with respect to HXC_MAPPING_COMPONENTS, based on the documented foreign key relationships:

• HXC_BLD_BLK_INFO_TYPES — referenced by HXC_MAPPING_COMPONENTS.BLD_BLK_INFO_TYPE_ID; the parent classification of the component.
• HXC_ALIAS_TYPE_COMPONENTS — references this table through MAPPING_COMPONENT_ID; associates mapping components with alias types.
• HXC_MAPPING_COMP_USAGES — references this table through MAPPING_COMPONENT_ID; records where and how each component is used.
• HXC_TIME_CATEGORY_COMPS — references this table through MAPPING_COMPONENT_ID; links components to time categories.
• HXC_MAPPING_COMPONENTS_PK and HXC_MAPPING_COMPONENTS_UK1 — the primary and unique indexes that enforce identity and business-key uniqueness. The Time and Labor Engine APIs that administer mappings operate against these relationships when creating, updating, or validating mapping definitions.