Results for “hr_template_data_groups”

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

Overview

HR_TEMPLATE_DATA_GROUPS is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas. It stores the definition of data groups that are associated with templates used for configurable forms. In the Oracle EBS self-service and configurable form architecture, a form template defines a reusable presentation layout, while a data group defines the set of data elements to be rendered within that layout. This intersection table records exactly which data groups are attached to a given form template, thereby controlling which fields, regions, or blocks appear when a configurable form is instantiated for an end user.

From a dimensional modeling perspective, the mined foreign key structure suggests classifying this object as a link table. It resolves a many-to-many association between form templates and form data groups, carrying no descriptive business attributes of its own beyond the association and its audit columns. Modelers building a Data Vault layer should treat HR_TEMPLATE_DATA_GROUPS as a link connecting the HR_FORM_TEMPLATES_B and HR_FORM_DATA_GROUPS_B hubs.

Key Information Stored

The table contains ten documented columns in the 12.2.2 physical schema. The most significant are listed below.

• TEMPLATE_DATA_GROUP_ID — the surrogate primary key, defined by the unique index HR_TEMPLATE_DATA_GROUPS_PK. It uniquely identifies each template-to-data-group association.
• FORM_TEMPLATE_ID — foreign key to HR_FORM_TEMPLATES_B, identifying the configurable form template to which the data group belongs.
• FORM_DATA_GROUP_ID — foreign key to HR_FORM_DATA_GROUPS_B, identifying the data group being associated.
• ZD_EDITION_NAME — the editioning column used in the EBS 12.2 online patching architecture. It is part of both the primary key and the unique key, enabling edition-aware querying across patched and unpatched states.
• OBJECT_VERSION_NUMBER — the optimistic locking column used to detect concurrent updates to the same association row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording when and by whom the row was last modified, and the login session used.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording row creation.

The business-key candidate is captured by HR_TEMPLATE_DATA_GROUPS_UK, a unique index over (FORM_DATA_GROUP_ID, FORM_TEMPLATE_ID, ZD_EDITION_NAME). This enforces that any given data group may be linked to a specific form template only once per edition. The surrogate TEMPLATE_DATA_GROUP_ID should not be confused with this business key; applications should validate uniqueness on the natural column pair rather than on the numeric identifier.

Common Use Cases and Queries

Typical uses involve reporting on form configuration, auditing which data groups are wired into a template, and troubleshooting missing fields on a configurable form. A standard join to resolve the association is:

• SELECT tdg.template_data_group_id, ft.form_template_id, ft.name template_name, dg.form_data_group_id, dg.name data_group_name FROM hr.hr_template_data_groups tdg, hr.hr_form_templates_b ft, hr.hr_form_data_groups_b dg WHERE tdg.form_template_id = ft.form_template_id AND tdg.form_data_group_id = dg.form_data_group_id AND tdg.zd_edition_name = 'SET1';
• To find all templates that reference a specific data group: filter by FORM_DATA_GROUP_ID and join upward to HR_FORM_TEMPLATES_B.
• To detect duplicate or orphaned associations, compare counts against the unique index columns FORM_DATA_GROUP_ID and FORM_TEMPLATE_ID.
• For audit reporting, select LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration changes made through the form template setup UI.

Reports generated against this table should always constrain ZD_EDITION_NAME to the active edition, since rows may exist simultaneously for online-patching editions in 12.2.x environments.

Related Objects

The following objects are most directly involved through the documented foreign keys and dependencies.

• HR_FORM_TEMPLATES_B — parent of FORM_TEMPLATE_ID; holds the base template definition.
• HR_FORM_DATA_GROUPS_B — parent of FORM_DATA_GROUP_ID; holds the base data group definition.
• HR_TEMPLATE_DATA_GROUPS_PK — primary key index on TEMPLATE_DATA_GROUP_ID and ZD_EDITION_NAME.
• HR_TEMPLATE_DATA_GROUPS_UK — unique index enforcing the business key on FORM_DATA_GROUP_ID, FORM_TEMPLATE_ID, and ZD_EDITION_NAME.
• HR_FORM_TEMPLATES_TL and HR_FORM_DATA_GROUPS_TL — translation tables for the parent entities, joined when display names are required.
• Configurable form runtime and template setup APIs in the PER module, which read these associations when rendering self-service forms.