Results for “hxc_time_categories_v”

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

Overview

HXC_TIME_CATEGORIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the HXC product family, the Time and Labor Engine that underpins Oracle Time and Labor and related timecard-processing flows. The view presents configuration data describing time categories — the logical groupings used to classify time entries and drive timecard search and retrieval behavior. Each row represents a defined time category together with its associated SQL fragment and connector operator.

In practice the view serves reporting and integration consumers that need to inspect the definition of time categories without navigating the full base table. The most distinctive attribute it exposes is TIME_SQL, a stored SQL fragment associated with a category. This is why the object is frequently referenced during investigations of dynamic timecard queries, since TIME_SQL determines how a category resolves its underlying data. Because the view joins the base table to HR_LOOKUPS, it also delivers the lookup meaning of the operator rather than the raw lookup code.

Underlying Base Objects

The documented base objects for the view are HXC_TIME_CATEGORIES (the underlying synonym resolving to the time categories table), HR_LOOKUPS (a view over the lookups data), and HR_API (a package referenced in the dependency chain). The view text is defined as a join between HR_LOOKUPS and HXC_TIME_CATEGORIES on the operator column:

• HXC_TIME_CATEGORIES supplies the category definition, including TIME_CATEGORY_ID, TIME_CATEGORY_NAME, DESCRIPTION, TIME_SQL, OPERATOR, and DISPLAY.
• HR_LOOKUPS is joined with LOOKUP_TYPE = 'HXC_TIMECARD_SEARCH_CONNECTORS' and APPLICATION_ID = 800, matching LOOKUP_CODE to the category OPERATOR to derive OPERATOR_MEANING.
• The ROWID of HXC_TIME_CATEGORIES is exposed as ROW_ID, and standard WHO audit columns are carried through.

The join restricts output to categories whose OPERATOR value is a valid connector lookup code, so categories lacking a matching lookup are not returned.

Key Columns

• TIME_CATEGORY_ID — Primary identifier for the time category.
• TIME_CATEGORY_NAME — User-facing name of the category.
• DESCRIPTION — Free-text description of the category's purpose.
• TIME_SQL — Stored SQL text associated with the category; the central column for timecard search logic diagnosis.
• OPERATOR — Lookup code of the connector operator applied to the category.
• OPERATOR_MEANING — Translated meaning of the operator from HR_LOOKUPS.
• DISPLAY — Flag indicating whether the category is displayed.
• ROW_ID — Row identifier of the base table row.
• OBJECT_VERSION_NUMBER — Optimistic locking version, consistent with OAF-based maintenance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include auditing which time categories carry embedded SQL, reviewing connector operators in readable form, and verifying the definition behind a misbehaving timecard search.

List all categories with their operator meaning:

• SELECT time_category_id, time_category_name, operator, operator_meaning FROM apps.hxc_time_categories_v;

Find categories that define an SQL fragment:

• SELECT time_category_name, time_sql FROM apps.hxc_time_categories_v WHERE time_sql IS NOT NULL;

Search for a specific SQL token, matching the common "time_sql" lookup, for example:

• SELECT time_category_id, time_category_name, time_sql FROM apps.hxc_time_categories_v WHERE UPPER(time_sql) LIKE '%TIME_SQL%' OR time_category_name = 'TIME_SQL';

Review operator usage distribution across categories:

• SELECT operator_meaning, COUNT(*) FROM apps.hxc_time_categories_v GROUP BY operator_meaning;