Search Results hxc_entity_groups_uk1

Overview

HXC.HXC_ENTITY_GROUPS is a transactional configuration table in the Oracle E-Business Suite HR/HXC schema that stores named groupings of entities used by time and labor, deposit, and retrieval processing. Each row defines an entity group header identified by a surrogate primary key and qualified by a business key composed of entity type, name, and business group. The table serves as the parent of HXC_ENTITY_GROUP_COMPS, which holds the individual constituent members that make up each group.

The object resides in the APPS_TS_TX_DATA tablespace and is owned by the HXC schema, with its unique indexes in APPS_TS_TX_IDX. In the 12.2.2 edition-aware data model, both the primary key and the unique business index include a ZD_EDITION_NAME column, reflecting the editioning infrastructure introduced in that release. Under the heuristic Data Vault classification mined from the foreign key structure, HXC_ENTITY_GROUPS is hub-leaning: it is the referenced parent in a parent-child relationship, so it is best modeled as a hub with its descriptive attributes carried in a satellite, while HXC_ENTITY_GROUP_COMPS acts as the link or child component.

Key Information Stored

• ENTITY_GROUP_ID — the surrogate primary key (NUMBER(15)), populated from a sequence. This is the column referenced by dependent tables.
• NAME — VARCHAR2(80), the descriptive name of the entity group. Together with ENTITY_TYPE and BUSINESS_GROUP_ID it forms the documented unique business key.
• ENTITY_TYPE — VARCHAR2(30), validated against HR lookups and constrained to values such as DATA_APPROVAL, DEPOSIT_PROCESS, and RETRIEVAL_PROCESS. This column determines the functional purpose of the group.
• BUSINESS_GROUP_ID — NUMBER(15), the operating unit or business group context that scopes the group and participates in the unique index.
• DESCRIPTION — VARCHAR2(150), free-text description of the group.
• LEGISLATION_CODE — VARCHAR2(30), the legislation under which the group applies.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework during concurrent updates.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard audit and traceability.
• ZD_EDITION_NAME — editioning discriminator present in both unique indexes in the 12.2.2 physical model.

The documented unique indexes are HXC_ENTITY_GROUPS_PK on ENTITY_GROUP_ID (plus ZD_EDITION_NAME) and HXC_ENTITY_GROUPS_UK1 on ENTITY_TYPE, NAME, BUSINESS_GROUP_ID (plus ZD_EDITION_NAME).

Common Use Cases and Queries

Typical reporting and support scenarios include locating a group by its business key, listing all groups of a given entity type, and joining to the component table to enumerate members.

• Resolve a group identifier from name and type: SELECT entity_group_id, name FROM hxc.hxc_entity_groups WHERE entity_type = :type AND name = :name AND business_group_id = :bg_id;
• List retrieval process groups: SELECT entity_group_id, name, description FROM hxc.hxc_entity_groups WHERE entity_type = 'RETRIEVAL_PROCESS' ORDER BY name;
• Trace membership by joining to the component table on ENTITY_GROUP_ID, filtering by business group and legislation code for region-specific reporting.

Because ENTITY_TYPE is validated against HR lookups, lookup values control which group classifications appear at runtime.

Related Objects

• HXC_ENTITY_GROUP_COMPS — the primary dependent child, joined on ENTITY_GROUP_ID; holds the constituent entities of each group.
• FND_USER — referenced indirectly through CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced through LAST_UPDATE_LOGIN.
• HR_LOOKUPS — supplies the validated ENTITY_TYPE values (DATA_APPROVAL, DEPOSIT_PROCESS, RETRIEVAL_PROCESS).