Results for “hr_form_data_groups_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_FORM_DATA_GROUPS_B is the base (non-translated) definition table for form data groups used by Oracle Human Resources configurable forms. A form data group is a logical container that controls which groups of fields, blocks, or data items are made available when a configurable form template is executed. The table belongs to the PER (Human Resources) product family and resides in the HR schema. It holds the metadata that links an Oracle Forms form definition (identified by APPLICATION_ID and FORM_ID) to a named data group, and each row is subsequently consumed by translation rows, data group item definitions, and template bindings. The table is a core configuration object rather than a transactional fact table; it changes infrequently and is typically populated during implementation of configurable forms rather than during day-to-day HR processing.

From a Data Vault modeling perspective, the ETRM relationship data classifies this object as hub-leaning. That heuristic reflects the fact that FORM_DATA_GROUP_ID acts as a stable, non-volatile business key that is referenced by three downstream tables (HR_FORM_DATA_GROUPS_TL, HR_FORM_DATA_GROUP_ITEMS, and HR_TEMPLATE_DATA_GROUPS), matching the characteristic pattern of a hub entity surrounded by satellites and links.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• FORM_DATA_GROUP_ID — The surrogate primary key, defined by the constraint HR_FORM_DATA_GROUPS_B_PK (which also includes ZD_EDITION_NAME in 12.2.x). This is the value propagated to all foreign-key child tables.
• APPLICATION_ID — Identifies the Oracle EBS application owning the form (typically the HR application ID).
• FORM_ID — Identifies the specific Oracle Forms form definition to which the data group belongs.
• DATA_GROUP_NAME — The user-facing name of the data group, used for identification in form configuration and template setup.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column used to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard auditing triad capturing who changed the row, when, and from which login session.
• CREATED_BY, CREATION_DATE — Creation audit columns recording the initial insert.
• ZD_EDITION_NAME — The editioning column introduced in EBS 12.2.x to support online patching (Edition-Based Redefinition); it is NULL for the runtime edition and set for patch editions.

Business-key candidates are captured by the unique index HR_FORM_DATA_GROUPS_B_UK over APPLICATION_ID, FORM_ID, DATA_GROUP_NAME, and ZD_EDITION_NAME, meaning a data group name must be unique within a given application, form, and edition. This distinguishes the surrogate key (FORM_DATA_GROUP_ID) from the natural composite key used for logical identification.

Common Use Cases and Queries

Typical use cases center on form configuration audits, template troubleshooting, and implementation validation. A common query lists all data groups defined for the HR forms:

• Joining HR_FORM_DATA_GROUPS_B to HR_FORM_DATA_GROUPS_TL on FORM_DATA_GROUP_ID to retrieve translated (language-specific) descriptions of each group.
• Joining to HR_FORM_DATA_GROUP_ITEMS to inspect which individual data items are members of a specific group, useful when verifying that all required fields are exposed in a configurable form.
• Joining to HR_TEMPLATE_DATA_GROUPS to determine which form templates reference a given data group, supporting impact analysis before changing or retiring a group.
• Filtering on APPLICATION_ID and FORM_ID to enumerate the data groups for a specific form, most often during implementation or upgrade reconciliation.
• Reporting on audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY) to identify recent configuration changes for change-control governance.

Because the table is configuration metadata, queries are usually read-only and run during implementation or support investigations rather than in high-volume batch processes.

Related Objects

Three foreign keys point to HR_FORM_DATA_GROUPS_B, all keyed on FORM_DATA_GROUP_ID, defining the surrounding relationship set:

• HR_FORM_DATA_GROUPS_TL — The translated (TL) companion table holding language-specific name and description columns, joined on FORM_DATA_GROUP_ID.
• HR_FORM_DATA_GROUP_ITEMS — Child table enumerating the individual data items assigned to each group, joined on FORM_DATA_GROUP_ID.
• HR_TEMPLATE_DATA_GROUPS — Associates form templates with the data groups they consume, joined on FORM_DATA_GROUP_ID.

In addition, the APPLICATION_ID and FORM_ID columns logically reference the standard EBS application and form definition registries (FND_APPLICATION and FND_FORM) even though those references are not enforced as database-level foreign keys on this table. Together these objects form the metadata graph that governs how configurable HR forms render and which fields they expose.