Search Results hr_dm_groups_pk

Overview

HR.HR_DM_GROUPS is a core Oracle E-Business Suite table residing in the HR (Human Resources) schema that stores information about the groupings used during the data migration process. It is a foundational configuration object for Oracle's Data Migration (DM) framework, which supports the bulk loading, cleansing, and validation of legacy or external data into EBS. Each row defines a logical grouping that determines how a particular subset of data is processed, which loader is invoked, and whether the grouping participates in the cleanup phase.

The table is stored in the APPS_TS_INTERFACE tablespace with PCT Free 10, reflecting its role as an interface-oriented object rather than a transactional core table. Its FND Design Data registration is PER.HR_DM_GROUPS. From a heuristic Data Vault modeling perspective, the metadata classifies HR_DM_GROUPS as hub-leaning: it presents a stable, uniquely identified business concept (via GROUP_ID) referenced by multiple dependent tables, which aligns with hub semantics. This classification is a modeling suggestion only and should not be treated as a formal Data Vault designation.

Key Information Stored

The primary key is enforced by the HR_DM_GROUPS_PK unique index on GROUP_ID (NUMBER(15)), a system-generated surrogate identifier for each grouping. Beyond this surrogate key, the most significant columns are:

• GROUP_ID — System-generated primary key; the sole unique index column and the join key for all dependent tables.
• DESCRIPTION — Free-text description (VARCHAR2(240)) identifying the grouping's business purpose for administrators.
• GROUP_TYPE — Defines the type of data within the grouping; explicitly indicates which loader is required or whether the grouping applies to the cleanup phase.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant and security-group partitioning.
• CREATED_BY, CREATION_DATE — Standard Who audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns recording the last modification and session context.

The table carries nine documented columns in total. Note that GROUP_ID functions as the surrogate primary key, while DESCRIPTION and GROUP_TYPE serve as the practical business descriptors; no additional unique business-key index is documented beyond the primary key itself.

Common Use Cases and Queries

The primary use case is configuration and administration of the data migration process. Because GROUP_TYPE drives loader selection, administrators query the table to audit which groupings exist and how they are processed. A typical pattern joins groups to their dependent mappings:

• Listing all migration groups and their descriptions: SELECT GROUP_ID, DESCRIPTION, GROUP_TYPE FROM HR.HR_DM_GROUPS ORDER BY GROUP_ID;
• Identifying loaders versus cleanup groupings: SELECT * FROM HR.HR_DM_GROUPS WHERE GROUP_TYPE = :p_type;
• Auditing recently modified groupings: SELECT GROUP_ID, DESCRIPTION, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM HR.HR_DM_GROUPS WHERE LAST_UPDATE_DATE > SYSDATE - 30;
• Joining to dependent tables to enumerate applications or tables assigned to a group using GROUP_ID.
• Security-group filtered reporting by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Reporting use cases include migration readiness dashboards, loader-configuration audits, and impact analysis before modifying a grouping.

Related Objects

The FK relationships documented in the ETRM metadata define the most significant related objects:

• HR_DM_APPLICATION_GROUPS — References HR_DM_GROUPS via GROUP_ID, associating application-level data with a migration group.
• HR_DM_TABLE_GROUPINGS — References HR_DM_GROUPS via GROUP_ID, mapping individual tables to their migration grouping.
• FND_SECURITY_GROUPS — Referenced by HR_DM_GROUPS.SECURITY_GROUP_ID, providing the security-group context.
• HR_DM_GROUPS_WHO — A Who-column dependent object built on HR_DM_GROUPS in the APPS schema for audit tracking.
• APPS.HR_DM_GROUPS and PUBLIC.HR_DM_GROUPS — Synonym or view exposures that make the table accessible to the APPS and PUBLIC schemas for reporting and API consumption.

HR_DM_GROUPS itself does not reference other database objects beyond FND_SECURITY_GROUPS, confirming its position as a hub-leaning reference table within the data migration framework.