Search Results hxc_entity_group_comps_pk




Overview
Explore in AI Chat

Overview

HXC_ENTITY_GROUP_COMPS is a table in the HXC schema (Oracle Time and Labor Engine) that stores the individual components, or members, that make up an entity group defined in HXC_ENTITY_GROUPS. In Oracle EBS 12.1.1 and 12.2.2, Time and Labor uses entity groups to bundle collections of people, assignment sets, or other entities so that rules, preferences, and time entry validations can be applied consistently across a defined population. Each row in HXC_ENTITY_GROUP_COMPS represents one member of such a group, linking the parent group to a specific entity via the ENTITY_ID and ENTITY_TYPE columns.

From a Data Vault modeling perspective, the mined relationship structure suggests this object leans toward a satellite classification. It carries descriptive detail about the membership relationships and includes the standard EBS audit and ZD_EDITION_NAME columns rather than behaving as a pure hub or link. This heuristic is offered as a modeling suggestion; the authoritative physical PK is HXC_ENTITY_GROUP_COMPS_PK on ENTITY_GROUP_COMP_ID (plus ZD_EDITION_NAME).

Key Information Stored

The most significant columns are:

  • ENTITY_GROUP_COMP_ID — surrogate primary key, uniquely identifying each component row.
  • ENTITY_GROUP_ID — foreign key to HXC_ENTITY_GROUPS; identifies the parent group.
  • ENTITY_ID — the identifier of the specific member entity associated with the group.
  • ENTITY_TYPE — classifies what kind of entity the row references (for example, person or assignment).
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) columns for capturing client-specific member attributes.
  • OBJECT_VERSION_NUMBER — optimistic locking counter used by the OAF/BC4J framework.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns for auditing and concurrency.
  • ZD_EDITION_NAME — the editioning column that supports Oracle EBS online patching (edition-based redefinition) in Release 12.2.

The unique business-key candidate is defined by HXC_ENTITY_GROUP_COMPS_PK over ENTITY_GROUP_COMP_ID and ZD_EDITION_NAME. The 30 DFF attribute columns plus ATTRIBUTE_CATEGORY make up the bulk of the documented 42 columns, indicating the table is highly extensible.

Common Use Cases and Queries

Typical usage involves reporting on group membership, troubleshooting rule application, and validating time entry populations. The most common join pattern links components back to their parent group:

  • List all members of a named group: SELECT c.ENTITY_ID, c.ENTITY_TYPE FROM HXC_ENTITY_GROUP_COMPS c, HXC_ENTITY_GROUPS g WHERE c.ENTITY_GROUP_ID = g.ENTITY_GROUP_ID AND g.NAME = :group_name.
  • Identify which groups a given entity belongs to: SELECT ENTITY_GROUP_ID FROM HXC_ENTITY_GROUP_COMPS WHERE ENTITY_ID = :person_id.
  • Audit membership changes over time using CREATION_DATE and LAST_UPDATE_DATE.
  • Extract flexfield attributes via the DFF tables for group-specific reporting.

Related Objects

  • HXC_ENTITY_GROUPS — parent group header, joined on ENTITY_GROUP_ID (the documented foreign key relationship).
  • HXC_ENTITY_GROUP_COMPS_PK — the primary key constraint enforcing row uniqueness.
  • HXC_TIME_ATTRIBUTES and Time and Labor rule/building-block tables — consume group membership for rule scoping.
  • HXC_PER_TIME_ENTRY — time entry records whose validation and preferences frequently reference entity groups.
  • PER_ALL_PEOPLE_F / PER_ALL_ASSIGNMENTS_F — resolve PERSON and assignment entity types referenced by ENTITY_ID.
  • Standard HXC audit and DFF views, including the descriptive flexfield tables surfaced through ATTRIBUTE_CATEGORY.