Search Results hxc_mapping_components

Overview

The HXC_MAPPING_COMPONENTS table is a core metadata repository within the Oracle E-Business Suite (EBS) Time and Labor Engine (HXC). It serves as the master definition table for the fundamental building blocks used in the Timecard Mapping process. This process is critical for translating raw time entry data, often from external devices or simplified entry interfaces, into the structured building blocks that constitute a formal timecard in Oracle Time and Labor. The table's role is to define and store the individual components—such as specific hours types, cost codes, or project tasks—that can be mapped to predefined timecard attributes, enabling automated and rule-based timecard population.

Key Information Stored

The table's primary function is to uniquely identify and name each mappable component. The key columns, as indicated by the primary and unique keys, are MAPPING_COMPONENT_ID and NAME. The MAPPING_COMPONENT_ID is the system-generated primary key, ensuring each component has a unique identifier. The NAME column holds the unique, user-defined identifier for the mapping component, such as 'REGULAR_HOURS' or 'PROJECT_A_TASK_1'. A critical foreign key column is BLD_BLK_INFO_TYPE_ID, which links the component to a specific building block information type (e.g., Hours, Costing, Projects) defined in the HXC_BLD_BLK_INFO_TYPES table. This link categorizes the component and determines what kind of timecard data it can populate.

Common Use Cases and Queries

This table is primarily accessed for setup, maintenance, and troubleshooting of time entry mappings. Common scenarios include auditing the list of available mapping components or identifying components associated with a specific information type. A typical administrative query would join to the building block info types table for a readable report:

• SELECT hmc.name AS component_name, hbbit.name AS info_type_name
• FROM hxc_mapping_components hmc, hxc_bld_blk_info_types hbbit
• WHERE hmc.bld_blk_info_type_id = hbbit.bld_blk_info_type_id
• ORDER BY info_type_name, component_name;

Another critical use case is diagnosing mapping failures by verifying if a specific component is correctly defined in this master table before it can be used in a mapping rule (HXC_MAPPING_COMP_USAGES) or an alias definition (HXC_ALIAS_TYPE_COMPONENTS).

Related Objects

As per the provided metadata, HXC_MAPPING_COMPONENTS is central to several key relationships. It is a parent table to HXC_ALIAS_TYPE_COMPONENTS and HXC_MAPPING_COMP_USAGES, which reference its MAPPING_COMPONENT_ID. These child tables define how the component is used within alias definitions and specific mapping rules, respectively. It is also a child table to HXC_BLD_BLK_INFO_TYPES via the BLD_BLK_INFO_TYPE_ID foreign key, which provides the high-level classification for the component. This network of relationships positions HXC_MAPPING_COMPONENTS as the pivotal link between the abstract definition of timecard attributes (info types) and their concrete application in mapping and aliasing rules.