Search Results hxc_tk_group_query_pk




Overview
Explore in AI Chat

Overview

HXC_TK_GROUP_QUERIES is a table in the HXC schema, owned by the Time and Labor Engine product within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its documented description is "Timekeeper Group Queries." In practical terms, the table stores the query definitions that a timekeeper uses to define the population of a timekeeper group. Each row represents one named query associated with a specific timekeeper group, allowing administrators to build dynamic or rule-based group membership rather than static assignment.

Under the heuristic Data Vault classification provided in the metadata, this table is identified as satellite-leaning. In modeling terms, this suggests the table behaves primarily as a descriptive satellite attached to the HXC_TK_GROUPS hub, holding attribute context about the query object rather than serving as a pure link or independent hub. The classification is a suggestion derived from the foreign key structure, not a formal Oracle designation.

Key Information Stored

The table is documented with 11 physical columns. The surrogate primary key is TK_GROUP_QUERY_ID, enforced by the unique index HXC_TK_GROUP_QUERY_PK. This column is the single documented business-key candidate and uniquely identifies each group query record.

  • TK_GROUP_QUERY_ID — Surrogate primary key and the only unique-index candidate, identifying each query definition row.
  • GROUP_QUERY_NAME — The user-facing name of the query, used to identify the query definition within a timekeeper group.
  • TK_GROUP_ID — Foreign key to HXC_TK_GROUPS, tying the query to its parent timekeeper group.
  • INCLUDE_EXCLUDE — Governs whether matching members are included in or excluded from the group population.
  • SYSTEM_USER — Identifies the system user context associated with the query row.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control, standard in EBS 12.2.2 (OAF-based) tables.
  • 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, when, and under which login session.

The combination of TK_GROUP_QUERY_ID and TK_GROUP_ID is central to how the table integrates with the surrounding Time and Labor model. Note that the detailed membership rules themselves are not stored here; they reside in the dependent criteria table.

Common Use Cases and Queries

Typical scenarios include listing all queries for a timekeeper group, determining include/exclude behavior, and joining to criteria to reconstruct full population rules. A common reporting pattern joins this table to its parent group:

  • Listing queries for one timekeeper group: SELECT GROUP_QUERY_NAME, INCLUDE_EXCLUDE FROM HXC_TK_GROUP_QUERIES WHERE TK_GROUP_ID = :p_group_id;
  • Reconstructing criteria per query: joining HXC_TK_GROUP_QUERIES to HXC_TK_GROUP_QUERY_CRITERIA on TK_GROUP_QUERY_ID.
  • Audit reporting: filtering by LAST_UPDATE_DATE or LAST_UPDATED_BY to track query definition changes.
  • Include/exclude analysis: aggregating counts by INCLUDE_EXCLUDE across a group.

Because the table is satellite-leaning, reporting queries frequently start from HXC_TK_GROUPS and traverse to this table via TK_GROUP_ID.

Related Objects

  • HXC_TK_GROUPS — Parent table referenced by HXC_TK_GROUP_QUERIES.TK_GROUP_ID; holds the timekeeper group definitions.
  • HXC_TK_GROUP_QUERY_CRITERIA — Child table referencing HXC_TK_GROUP_QUERIES via TK_GROUP_QUERY_ID; stores the individual filter criteria for each query.

These two objects form the core documented FK relationships. Broader Time and Labor integrations involving timekeeper group membership should be validated against application data, as only the relationships above are confirmed in the supplied ETRM metadata.