Search Results audit_enabled




Overview
Explore in AI Chat

Overview

HXC_TK_GROUP_QUERY_CRITERIA_V is a reporting and integration view owned by the APPS schema within the HXC – Time and Labor Engine product. It is described in the Oracle E-Business Suite Electronic Technical Reference Manual (ETRM) as the "Timekeeper Group Query Criteria" view. Its purpose is to flatten the relationship between a timekeeper group query definition and the individual persons who are selected by that query, exposing one row per qualifying person criterion.

In EBS 12.1.1 and 12.2.2, the Time and Labor Engine uses timekeeper group queries to dynamically determine which employees a timekeeper is responsible for. Rather than storing a static list of people, a query is stored in HXC_TK_GROUP_QUERIES, and the set of matching persons is persisted as criteria rows in HXC_TK_GROUP_QUERY_CRITERIA. This view joins those two structures and enriches the result with person, person type, and assignment attributes, so reports, forms, and integrations can present the resolved member list without duplicating the underlying join logic. It is a view of primary value to developers and administrators building extracts, debugging membership rules, or validating include/exclude behavior.

Underlying Base Objects

The view is defined over the following documented base objects:

The view additionally calls the packages HR_PERSON_TYPE_USAGE_INFO (to derive CRITERIA_DISPLAY_TYPE) and HXC_TK_GRP_QUERY_CRITERIA_API (for TC_PERIOD_NAME and AUDIT_ENABLED). Other referenced objects such as FND_PROFILE, FND_SESSIONS, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PER_PERIODS_OF_PLACEMENT are transitive dependencies inherited through these packages and views.

Key Columns

  • TK_GROUP_QUERY_CRITERIA_ID / TK_GROUP_QUERY_ID / TK_GROUP_ID – identity and grouping keys linking the criterion to its query and parent timekeeper group.
  • CRITERIA_TYPE / CRITERIA_ID – the criterion driver; the view filters to CRITERIA_TYPE = 'PERSON', so CRITERIA_ID carries the PERSON_ID.
  • GROUP_QUERY_NAME – the user-facing name of the query definition.
  • INCLUDE_EXCLUDE – indicates whether the criteria act as an inclusion or exclusion list within the group query.
  • SYSTEM_USER – flag denoting whether the query is seeded by the system rather than user-defined.
  • CRITERIA_DISPLAY1 / CRITERIA_DISPLAY2 / CRITERIA_DISPLAY_TYPE – presentation values: person full name, employee or NPW number, and derived person type.
  • TC_PERIOD_NAME / AUDIT_ENABLED – timecard period name and audit-enabled indicator, both computed through the criteria API.
  • OBJECT_VERSION_NUMBER, CREATED_BY/DATE, LAST_UPDATED_BY/DATE, LAST_UPDATE_LOGIN, BUSINESS_GROUP_ID – standard WHO and multi-tenant columns.

Common Use Cases and Queries

Typical scenarios include resolving which employees a timekeeper group query selects, reporting on include versus exclude rules, and reconciling group membership against assignments. Because the view pre-joins person and assignment data, a simple SELECT is usually sufficient:

  • List all people per query: SELECT tk_group_id, group_query_name, include_exclude, criteria_display1, criteria_display2 FROM hxc_tk_group_query_criteria_v ORDER BY tk_group_id, group_query_name;
  • Filter by include/exclude: SELECT group_query_name, include_exclude, criteria_display1 FROM hxc_tk_group_query_criteria_v WHERE include_exclude = 'I';
  • Restrict to a group: SELECT criteria_display1, criteria_display2, criteria_display_type FROM hxc_tk_group_query_criteria_v WHERE tk_group_id = :p_group_id;
  • Exclude system-seeded queries: SELECT group_query_name, criteria_display1 FROM hxc_tk_group_query_criteria_v WHERE system_user = 'N';

All queries should bind BUSINESS_GROUP_ID or rely on HR security where multi-organization or secure access restrictions apply, since the view exposes person and assignment data subject to HR_SECURITY.