Search Results hxc_entity_groups_pk

Overview

HXC_ENTITY_GROUPS is a foundational configuration table in the Oracle E-Business Suite Time and Labor Engine (HXC) module. It stores the definition of entity groups, which are logical groupings used by the Time and Labor rules engine and related HXC processing to bundle entities of a common type for evaluation during time entry validation, rule execution, and timecard processing. The table is owned by the HXC schema and holds a status of VALID across both EBS 12.1.1 and 12.2.2 releases.

From a heuristic Data Vault modeling perspective, the mined foreign-key and primary-key structure suggests HXC_ENTITY_GROUPS is hub-leaning. The table functions as a parent definition object referenced by dependent component tables, with its surrogate primary key acting as the stable identifier carried into child relationships. This classification should be treated as a modeling suggestion rather than a documented architectural mandate.

Key Information Stored

The table comprises 13 documented columns. The most significant are:

• ENTITY_GROUP_ID — the surrogate primary key, enforced by the HXC_ENTITY_GROUPS_PK index. This is the value propagated to child tables.
• NAME — the user-visible name of the entity group; together with ENTITY_TYPE and BUSINESS_GROUP_ID it forms a business-key candidate via the HXC_ENTITY_GROUPS_UK1 unique index.
• ENTITY_TYPE — classifies the type of entities the group contains, and is a distinguishing component of the business key.
• BUSINESS_GROUP_ID — the owning business group (HR operating unit), enforcing multi-tenant partitioning of group definitions.
• LEGISLATION_CODE — the legislation (country) context under which the group is valid.
• DESCRIPTION — free-text descriptive information for the group.
• ZD_EDITION_NAME — the edition identifier supporting Oracle's edition-based redefinition model; it participates in both the primary key and the unique business key.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record provenance.

The primary key is composed of ENTITY_GROUP_ID and ZD_EDITION_NAME, while the business-key candidate combines ENTITY_TYPE, NAME, BUSINESS_GROUP_ID, and ZD_EDITION_NAME.

Common Use Cases and Queries

Typical uses include resolving the members of an entity group, reporting on group definitions by business group, and joining group headers to their component detail rows for downstream rule evaluation.

• Listing all groups for a business group:
  SELECT entity_group_id, name, entity_type, legislation_code FROM hxc_entity_groups WHERE business_group_id = :p_bg_id;
• Resolving the business key for a known group:
  SELECT * FROM hxc_entity_groups WHERE entity_type = :p_type AND name = :p_name AND business_group_id = :p_bg_id;
• Joining header to components to enumerate membership:
  SELECT g.name, c.* FROM hxc_entity_groups g JOIN hxc_entity_group_comps c ON c.entity_group_id = g.entity_group_id;
• Reporting by legislation for compliance or localization analysis, filtering on legislation_code.

Because ZD_EDITION_NAME is part of the key, queries should generally filter on the current edition when running against an edition-enabled 12.2.2 instance to avoid returning historical editions.

Related Objects

• HXC_ENTITY_GROUP_COMPS — the primary dependent child table; its ENTITY_GROUP_ID column carries a foreign key to HXC_ENTITY_GROUPS.ENTITY_GROUP_ID, linking each group to its member components.
• HXC_ENTITY_GROUPS_PK — the primary-key unique index on ENTITY_GROUP_ID and ZD_EDITION_NAME.
• HXC_ENTITY_GROUPS_UK1 — the unique business-key index on ENTITY_TYPE, NAME, BUSINESS_GROUP_ID, and ZD_EDITION_NAME.
• HR_ALL_ORGANIZATION_UNITS — the business-group reference for BUSINESS_GROUP_ID, used to resolve operating-unit context.
• FND_LOOKUPS / FND_LOOKUP_VALUES — commonly consulted to decode ENTITY_TYPE and LEGISLATION_CODE values.
• Time and Labor rules engine tables (HXC rule and processing tables) that consume entity group definitions during timecard validation and rule execution.