Results for “hr_template_data_groups_uk”

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

Overview

The HR.HR_TEMPLATE_DATA_GROUPS table resides in the HR schema within Oracle E-Business Suite and operates in both 12.1.1 and 12.2.2 release lines. It serves as the definition table for data groups assigned to templates used by configurable forms in Oracle Human Resources and related self-service modules. Configurable forms allow implementers to control which fields, regions, and data groups appear on a given form template; this table records the association between a form template and the data groups it exposes.

From a Data Vault modeling perspective, the heuristic classification of this object is a link. The table does not hold descriptive attributes of its own beyond housekeeping columns; instead it resolves a many-to-many relationship between two business entities — form templates and form data groups — through two foreign keys. Under a Data Vault treatment, HR_TEMPLATE_DATA_GROUPS would be modelled as a link table connecting the HR_FORM_TEMPLATES_B and HR_FORM_DATA_GROUPS_B hubs.

Key Information Stored

The table is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes reside in APPS_TS_TX_IDX. It contains ten documented columns. The most significant are:

• TEMPLATE_DATA_GROUP_ID (NUMBER 15) — the system-generated surrogate primary key, populated from the sequence HR_TEMPLATE_DATA_GROUPS_S. It is enforced by the HR_TEMPLATE_DATA_GROUPS_PK unique index.
• FORM_TEMPLATE_ID (NUMBER 15) — foreign key to HR_FORM_TEMPLATES_B, identifying the configurable form template to which a data group is attached.
• FORM_DATA_GROUP_ID (NUMBER 15) — foreign key to HR_FORM_DATA_GROUPS_B, identifying the data group being exposed on the template.
• OBJECT_VERSION_NUMBER — the standard row versioning column, incremented on every update to support optimistic locking in the Oracle Applications framework.
• ZD_EDITION_NAME — the editioning column introduced for Oracle EBS 12.2 online patching, which partitions rows by edition. It forms part of both the primary key and the unique key in the 12.2.2 physical schema.
• Standard Who audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

The business key candidate is the unique index HR_TEMPLATE_DATA_GROUPS_UK, declared on the column pair FORM_DATA_GROUP_ID and FORM_TEMPLATE_ID (extended with ZD_EDITION_NAME). This confirms that a given data group may be attached to a given template only once, preventing duplicate assignments.

Common Use Cases and Queries

Typical usage is diagnostic and reporting-oriented. Implementers troubleshooting configurable form behavior query this table to determine which data groups are currently mapped to a template, and to confirm whether a mapping exists at all. A common pattern joins through to the base tables to resolve identifiers into human-readable names:

• Listing data groups for a specific template: SELECT FORM_DATA_GROUP_ID FROM HR.HR_TEMPLATE_DATA_GROUPS WHERE FORM_TEMPLATE_ID = :template_id;
• Detecting duplicate mapping attempts prior to insertion, using the unique key columns as the search predicate.
• Auditing configuration changes over time via the Who columns, for example filtering on LAST_UPDATE_DATE to identify recently modified template mappings.
• Reconciling templates and data groups that share no parent record, which surfaces orphaned or obsolete configuration during upgrade or consolidation projects.

Because the table carries no descriptive attributes, reporting typically joins outward to the template and data group base tables rather than reading this object in isolation.

Related Objects

• HR.HR_FORM_DATA_GROUPS_B — referenced by FORM_DATA_GROUP_ID; the base table holding data group definitions.
• HR.HR_FORM_TEMPLATES_B — referenced by FORM_TEMPLATE_ID; the base table holding form template definitions.
• HR.HR_FORM_DATA_GROUPS_TL — translation table supplying the display name for each data group.
• HR.HR_FORM_TEMPLATES_TL — translation table supplying the display name for each form template.
• HR.HR_TEMPLATE_DATA_GROUPS_FK1 — non-unique index on FORM_TEMPLATE_ID supporting the template-side foreign key lookup and typical query predicates.

Together these objects form the metadata layer that drives configurable form rendering, with HR_TEMPLATE_DATA_GROUPS acting strictly as the junction between templates and data groups.