Search Results hr_dm_application_groups




Overview
Explore in AI Chat

Overview

HR_DM_APPLICATION_GROUPS is a table owned by the HR schema in Oracle E-Business Suite, registered under the PER (Human Resources) product family. ETRM describes its purpose as "Data Migrator locking ladder groups for applications." In practice, the table functions as a configuration and control structure for the Data Migrator utility, which supports bulk migration of HR and Oracle HRMS-related data across environments. The "locking ladder" concept refers to an ordered, sequence-driven contention control mechanism: records in this table associate an application with a group and assign that pairing a position in an ordered migration ladder, so that concurrent migration processes can be serialized and coordinated rather than executing against overlapping application groups simultaneously.

ETRM records the object as VALID in both 12.1.1 and 12.2.2, with the documented physical schema exposing eleven columns in 12.2.2. The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This should be read as a modeling suggestion rather than a statement of design intent: the table carries a surrogate primary key plus descriptive and ordering attributes, and it depends on parent entities through foreign keys. A Data Vault treatment would therefore place the ordering and migration-type attributes in a satellite attached to a hub or link formed from the group and application references.

Key Information Stored

Only eleven columns are documented, and they fall into three functional bands: identity, relationship, and audit.

Notably absent from the documented column list are any descriptive free-text name or description fields, which reinforces the interpretation of this table as a lean control construct rather than a reference or descriptive master.

Common Use Cases and Queries

The principal use case is diagnosing and tuning Data Migrator lock contention. When a migration stalls or deadlocks, the ladder sequencing defined here is the first place to inspect. A representative query orders the configured ladder for a given group and migration type:

  • SELECT a.app_group_id, a.group_id, a.application_id, a.migration_type, a.group_order FROM hr.hr_dm_application_groups a WHERE a.group_id = :group_id ORDER BY a.migration_type, a.group_order;

Resolving application identity is a second common pattern, joining to FND_APPLICATION to translate APPLICATION_ID into a readable application short name:

  • SELECT ag.group_order, fa.application_short_name, ag.migration_type FROM hr.hr_dm_application_groups ag, fnd_application fa WHERE ag.application_id = fa.application_id ORDER BY ag.group_order;

A third scenario is security-group-scoped reporting, filtering on SECURITY_GROUP_ID to confirm which ladder definitions are visible or applicable to a given security context. Because the table is small and configuration-oriented, reporting volumes are low and full scans are typically acceptable; the access path of interest is the primary-key lookup and the GROUP_ID foreign-key join.

Related Objects

The following objects are the most significant in relation to this table, based on the documented key structure:

  • HR_DM_GROUPS — parent table joined on HR_DM_APPLICATION_GROUPS.GROUP_ID = HR_DM_GROUPS.GROUP_ID. Defines the locking ladder group itself.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; supplies the security-group partitioning referenced by this table.
  • FND_APPLICATION — the natural source for resolving APPLICATION_ID into an application name; the reference is intrinsic even though it is not listed among the documented foreign keys.
  • HR_DM_APPLICATION_GROUPS_PK — the unique index enforcing surrogate uniqueness on APP_GROUP_ID.
  • Other HR_DM_% Data Migrator tables — sibling constructs in the Data Migrator subsystem that share the GROUP_ID and SECURITY_GROUP_ID reference conventions.

Administrators should treat modifications to this table as configuration changes, since altering GROUP_ORDER directly affects lock acquisition sequencing during migration runs.