Search Results hxc_tk_groups




Overview
Explore in AI Chat

Overview

HXC_TK_GROUPS is the master table for Timekeeper Groups within the Oracle EBS Time and Labor Engine (HXC) product family. In Time and Labor, a timekeeper is the administrative user or role responsible for entering, reviewing, approving, and transferring timecard data on behalf of a defined population of workers. The HXC_TK_GROUPS table persists those group definitions, providing the container that binds a named timekeeper group to the resource (person or application entity) that owns or operates it. Each row represents a single timekeeper group, and the table functions as the authoritative definition point referenced by downstream query and retrieval logic within the Time and Labor Engine.

From a heuristic Data Vault modeling perspective, the mined FK structure (HXC_TK_GROUP_QUERIES references this table, and no upstream parent table is documented) classifies HXC_TK_GROUPS as hub-leaning. In practical terms, this suggests treating TK_GROUP_ID as a durable business key whose descriptive attributes (name, resource association) behave like a lightweight satellite. The table is owned by the HXC schema and is marked VALID in the ETRM 12.2.2 physical schema documentation, with 10 documented columns.

Key Information Stored

The table's surrogate primary key, enforced by unique index HXC_TK_GROUPS_PK, is TK_GROUP_ID. This is the only documented unique index, so no separate alternate business-key unique constraint is defined in the metadata; however, TK_GROUP_NAME carries the human-readable identifier for the group and is the primary business-key candidate in practice.

  • TK_GROUP_ID — Surrogate primary key; the value propagated to dependent tables as a foreign key.
  • TK_GROUP_NAME — Descriptive name of the timekeeper group, used in user interface selection lists and reports.
  • TK_RESOURCE_ID — Identifier of the resource (typically the timekeeper or associated person/application resource) bound to the group.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework to control concurrent updates.
  • BUSINESS_GROUP_ID — Multi-tenancy discriminator segregating data by Business Group (HR security organization), essential for any query scoped to a specific operating unit or legislative environment.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the row and when.

Common Use Cases and Queries

Typical use cases include reporting the roster of timekeeper groups, resolving a group name to its internal ID for integration, and auditing which resource owns each group. Queries should almost always be filtered by BUSINESS_GROUP_ID to respect HR security.

SELECT tk_group_id, tk_group_name, tk_resource_id
FROM   hxc.hxc_tk_groups
WHERE  business_group_id = :p_business_group_id
ORDER BY tk_group_name;

To locate groups for a specific resource:

SELECT tk_group_name
FROM   hxc.hxc_tk_groups
WHERE  tk_resource_id = :p_resource_id;

Reporting and reconciliation scripts join this table to its dependent query definitions (see below) to enumerate the retrieval criteria that determine which workers fall into each group. Change-audit reports can use LAST_UPDATE_DATE and LAST_UPDATED_BY to trace recent maintenance.

Related Objects

The principal documented relationship is a one-to-many link from group to query definition:

  • HXC_TK_GROUP_QUERIES — References HXC_TK_GROUPS via HXC_TK_GROUP_QUERIES.TK_GROUP_ID → HXC_TK_GROUPS.TK_GROUP_ID. This child table stores the query criteria that define group membership.

Additional objects that logically participate in the same functional area include the timecard and time repository tables within the HXC schema, and the Time and Labor Engine public APIs (for example the timecard and timekeeper management APIs) that read and validate group definitions during timecard submission and approval. Human Resources resource and person tables supply the value held in TK_RESOURCE_ID, and FND/HR security views supply the BUSINESS_GROUP_ID context used to scope access.