Search Results hxc_time_category_comps_pk

Overview

HXC_TIME_CATEGORY_COMPS is a table within the HXC (Time and Labor Engine) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual components that compose a time category definition — the constituent rules, mapping references, and value-set bindings that together determine how a given time category behaves during time entry, validation, and processing. Time categories are the functional backbone of Oracle Time and Labor: they drive how reported hours are classified, validated, and eventually transferred to payroll or project costing. Each row in this table contributes one such component to a parent time category.

The ETRM metadata classifies this object as standalone under a heuristic Data Vault assessment, meaning it is largely self-contained rather than acting as a pure transaction hub or a descriptive satellite. In dimensional or Data Vault modeling terms, this table behaves more like a reference/detail structure attached to a time category than a central hub; the classification should be treated as a modeling suggestion rather than a definitive architectural constraint.

Key Information Stored

The table consists of 18 documented columns, of which the following are most significant:

• TIME_CATEGORY_COMP_ID — the surrogate primary key identifying each component record.
• OBJECT_VERSION_NUMBER — the optimistic locking / row versioning column, which also participates in the primary key (HXC_TIME_CATEGORY_COMPS_PK = TIME_CATEGORY_COMP_ID + OBJECT_VERSION_NUMBER).
• TIME_CATEGORY_ID — references the parent time category to which the component belongs.
• REF_TIME_CATEGORY_ID — supports referencing an alternate or related time category, typically used where a component points at another category's definition.
• MAPPING_COMPONENT_ID — foreign key to HXC_MAPPING_COMPONENTS, linking this component to the time-mapping framework that governs category transfer behavior.
• COMPONENT_TYPE_ID — foreign key to AMS_DLG_COMP_TYPES_B, identifying the type of component (the lookup that defines what kind of rule or binding this row represents).
• FLEX_VALUE_SET_ID and VALUE_ID — identify the key flexfield value set and the specific value used when the component compares or validates against a flexfield.
• SPECIFY_VALUE, IS_NULL, EQUAL_TO — control the comparison semantics of the component, allowing conditional logic such as equality tests or null checks.
• TYPE — categorizes the component row itself.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — the editioning column present in 12.2.x (and in 12.1.3+ with online patching), enabling edition-based redefinition.

The documented unique index HXC_TIME_CATEGORY_COMPS_PK includes TIME_CATEGORY_COMP_ID, OBJECT_VERSION_NUMBER, and ZD_EDITION_NAME, making this the principal business-key candidate alongside the raw surrogate.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying all components attached to a given time category, verifying component-type coverage, and auditing flexfield bindings. A representative query:

SELECT c.time_category_comp_id,
       c.time_category_id,
       c.component_type_id,
       c.mapping_component_id,
       c.flex_value_set_id,
       c.value_id,
       c.specify_value,
       c.is_null,
       c.equal_to
  FROM hxc.hxc_time_category_comps c
 WHERE c.time_category_id = :p_time_category_id;

Joining to the mapping framework helps validate that every referenced mapping component exists and is active. Querying by COMPONENT_TYPE_ID supports impact analysis before changing component-type definitions. Because the table participates in Oracle Time and Labor's core processing, it is also commonly queried during troubleshooting of time-validation failures.

Related Objects

• HXC_MAPPING_COMPONENTS — joined via MAPPING_COMPONENT_ID; supplies the mapping definition each component references.
• AMS_DLG_COMP_TYPES_B — joined via COMPONENT_TYPE_ID; defines the component type lookup.
• HXC_TIME_CATEGORIES — the parent category referenced by TIME_CATEGORY_ID.
• Flexfield base views / value-set tables associated with FLEX_VALUE_SET_ID and VALUE_ID.
• Time and Labor setup and API surfaces that consume category definitions during time-entry validation and transfer.

Because the table is classified as standalone, its principal dependencies are through the two declared foreign keys rather than through inbound references from other tables.