Search Results hr_template_tab_pages_b_uk

Overview

HR_TEMPLATE_TAB_PAGES_B is a core configuration table in the Oracle E-Business Suite Human Resources (PER) module. It stores the definition of tab pages that belong to configurable form templates. In the context of Oracle EBS 12.1.1 and 12.2.2, this table supports the Configurable Forms framework, which allows implementers to tailor the layout, tabs, and page structure of HR forms without modifying the underlying form definitions directly. Each row in HR_TEMPLATE_TAB_PAGES_B represents a single tab page defined within a template canvas.

From a dimensional modeling perspective, the Data Vault classification of this table is hub-leaning. This heuristic derives from its FK structure: the table is the target of multiple foreign keys from dependent child tables, and its primary key consists of a surrogate identifier rather than a composite of foreign references. This suggests it functions as a central hub from which property and item-relationship satellites or links extend, rather than as a transactional link or pure descriptive satellite.

Key Information Stored

The table contains 10 documented columns. The most significant are the following:

• TEMPLATE_TAB_PAGE_ID — The surrogate primary key, uniquely identifying each tab page definition. This column is the target of foreign keys from several dependent tables.
• TEMPLATE_CANVAS_ID — Foreign key to HR_TEMPLATE_CANVASES_B, identifying the canvas (a higher-level layout container) to which this tab page belongs. This establishes the page-to-canvas hierarchy.
• FORM_TAB_PAGE_ID — Foreign key to HR_FORM_TAB_PAGES_B, linking the template-specific tab page back to the underlying form tab page definition. This is a documented unique-index component.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control, a standard column in EBS 12.2.2 tables.
• ZD_EDITION_NAME — The editioning column introduced in EBS 12.2.2 to support online patching. It is included in both unique indexes, ensuring edition-aware uniqueness.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO (Who Columns) audit fields capturing creation and last modification metadata for each row.

Two unique indexes are documented. HR_TEMPLATE_TAB_PAGES_B_PK covers TEMPLATE_TAB_PAGE_ID and ZD_EDITION_NAME, confirming the surrogate key. HR_TEMPLATE_TAB_PAGES_B_UK covers FORM_TAB_PAGE_ID, TEMPLATE_CANVAS_ID, and ZD_EDITION_NAME, representing the business-key uniqueness: a given form tab page maps to exactly one canvas within an edition.

Common Use Cases and Queries

Typical use cases include auditing which tab pages are defined for a template canvas, tracing inheritance from form definitions, and reporting on configurable form layouts.

• Retrieving all tab pages for a specific canvas:

SELECT template_tab_page_id, form_tab_page_id
FROM hr_template_tab_pages_b
WHERE template_canvas_id = :canvas_id
AND zd_edition_name = :edition;

• Joining to the parent canvas to obtain layout context:

SELECT p.template_tab_page_id, c.template_canvas_id, p.form_tab_page_id
FROM hr_template_tab_pages_b p, hr_template_canvases_b c
WHERE p.template_canvas_id = c.template_canvas_id;

Reporting scenarios include documenting configured page hierarchies per business group, verifying edition-migrated configurations after an online patch, and identifying tab pages that lack associated item relationships by checking for orphans against HR_TEMPLATE_ITEM_TAB_PAGES.

Related Objects

The table participates in a well-defined FK network:

• HR_TEMPLATE_CANVASES_B — Parent object; joined via HR_TEMPLATE_TAB_PAGES_B.TEMPLATE_CANVAS_ID.
• HR_FORM_TAB_PAGES_B — Source form tab page definition; joined via FORM_TAB_PAGE_ID.
• HR_TAB_PAGE_PROPERTIES_B — Child table storing property values per tab page; references TEMPLATE_TAB_PAGE_ID.
• HR_TEMPLATE_ITEM_CONTEXT_PAGES — Child table linking tab pages to item contexts; references TEMPLATE_TAB_PAGE_ID.
• HR_TEMPLATE_ITEM_TAB_PAGES — Child table associating items with tab pages; references TEMPLATE_TAB_PAGE_ID.

These relationships confirm the table's role as a hub in the Configurable Forms persistence model, with property and item-association data extending from it as dependent satellites or links.