Search Results hxc_time_categories




Overview
Explore in AI Chat

Overview

HXC_TIME_CATEGORIES is a table within the HXC schema (Time and Labor Engine product module) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of time categories, which are configurable classifications used by Oracle Time and Labor to group, validate, and process time entries. Time categories act as a central reference for how reported time is interpreted — for example, distinguishing billable from non-billable hours, regular from overtime, or hours eligible for a particular payroll or costing treatment. The table is classified as VALID in the ETRM metadata.

Based on the heuristic data vault classification mined from the foreign key structure, HXC_TIME_CATEGORIES is modeled as a standalone object. In data vault terms, this suggests the table behaves primarily as a reference or lookup set rather than participating in an explicit parent-child hub/link/satellite hierarchy with other tables in the documented relationship data. The absence of documented foreign keys reinforces its role as an independent reference table keyed by its own surrogate and business keys.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • TIME_CATEGORY_ID — Surrogate primary key column; part of HXC_TIME_CATEGORIES_PK. Uniquely identifies each category record.
  • OBJECT_VERSION_NUMBER — Concurrency control column and part of the composite primary key; used by the ORM (object-relational mapping) framework to detect stale updates.
  • TIME_CATEGORY_NAME — Business-key candidate; part of unique index HXC_TIME_CATEGORIES_UK1. The user-facing, human-readable name of the time category.
  • TIME_SQL — Holds SQL logic associated with the category, typically used to derive or validate time entries against rules.
  • OPERATOR — Comparison operator used in conjunction with TIME_SQL to evaluate category membership or eligibility.
  • DESCRIPTION — Free-text description of the category's purpose.
  • DISPLAY — Flag controlling whether the category is presented to users in the time entry UI.
  • ZD_EDITION_NAME — Editioning column enabling Oracle EBS online patching (12.2.2); included in both the primary key and unique key indexes.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard who-column tracking.

The surrogate primary key (TIME_CATEGORY_ID with OBJECT_VERSION_NUMBER) is distinct from the business-key candidate TIME_CATEGORY_NAME, which is enforced unique in combination with ZD_EDITION_NAME via HXC_TIME_CATEGORIES_UK1.

Common Use Cases and Queries

Time categories are referenced during time-entry submission to classify reported hours, drive validation rules, and feed downstream payroll and costing processes. Typical reporting scenarios include listing active, displayable categories and auditing recently changed definitions.

  • Retrieve all displayable categories:
    SELECT TIME_CATEGORY_ID, TIME_CATEGORY_NAME, DESCRIPTION FROM HXC.HXC_TIME_CATEGORIES WHERE DISPLAY = 'Y';
  • Find a category by business key:
    SELECT * FROM HXC.HXC_TIME_CATEGORIES WHERE TIME_CATEGORY_NAME = :name;
  • Audit recent changes using the audit columns:
    SELECT TIME_CATEGORY_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM HXC.HXC_TIME_CATEGORIES WHERE LAST_UPDATE_DATE > SYSDATE - 7;
  • Inspect rule logic via TIME_SQL and OPERATOR for troubleshooting validation behavior.

Related Objects

Although the ETRM metadata classifies this object as standalone with no documented foreign key relationships, time categories are logically referenced by transactional and setup tables in the Time and Labor module. The most significant related objects include:

  • HXC_TIME_ATTRIBUTES / HXC_TIME_ENTRY_* tables — transactional time entries that consume TIME_CATEGORY_ID for classification.
  • HXC_TIME_RECIPIENTS / HXC_TIME_GROUPS — setup objects that may reference categories to scope entry options.
  • HXC_TIME_CATEGORIES_TL — translation table keyed by TIME_CATEGORY_ID for multi-language names.
  • Payroll and Costing integration tables that receive categorized time for downstream processing.

Because no explicit foreign keys are documented, joins should be validated against the live schema for the specific EBS release.