Results for “hr_tab_page_properties_b”

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

Overview

The HR_TAB_PAGE_PROPERTIES_B table resides in the HR schema and belongs to the PER (Human Resources) product family within Oracle EBS 12.1.1 and 12.2.2. It stores the base-table (language-independent) properties of tab pages used in configurable forms, which are the forms rendered by the Personalization and extensibility framework that lets administrators tailor the layout and content of Oracle Forms-based pages without modifying the underlying form definition. Each row defines the property set that governs a given tab page: whether it is visible and which information segments and navigation behavior should be presented to the user.

Because the table holds descriptive attributes that hang off parent tab-page entities rather than acting as a standalone business entity or a pure association, the mined Data Vault classification is satellite-leaning. In a Data Vault model this would typically be treated as a satellite attached to the parent tab-page hubs, carrying the configurable property attributes.

Key Information Stored

The primary surrogate key is TAB_PAGE_PROPERTY_ID, enforced by the unique index HR_TAB_PAGE_PROPERTIES_B_PK. The business-key candidate is defined by HR_TAB_PAGE_PROPERTIES_B_UK over FORM_TAB_PAGE_ID, TEMPLATE_TAB_PAGE_ID, and TAB_PAGE_PROPERTY_ID (with ZD_EDITION_NAME in 12.2.2). The most significant columns include:

• FORM_TAB_PAGE_ID — foreign key to HR_FORM_TAB_PAGES_B, identifying the owning form tab page.
• TEMPLATE_TAB_PAGE_ID — foreign key to HR_TEMPLATE_TAB_PAGES_B, tying the property to a template tab page.
• VISIBLE — controls whether the tab page is displayed to the end user.
• NAVIGATION_DIRECTION — governs the direction of navigation sequence across tab pages.
• INFORMATION_CATEGORY — classifies the information segment shown on the page.
• INFORMATION1 through INFORMATION30 — numbered slots holding the page's configurable informational content.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ADF/BC4J layer.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard WHO columns.
• ZD_EDITION_NAME — Editioning column that supports the 12.2 Online Patching (ADOP) model.

Common Use Cases and Queries

Typical usage centers on diagnosing why a configurable form tab page renders (or fails to render) for a given set of users, and on auditing customization of form properties. A common pattern joins the base table to the translation table to resolve meaningful names:

• Reporting visible tab pages for a form: SELECT b.form_tab_page_id, b.visible, b.navigation_direction FROM hr.hr_tab_page_properties_b b WHERE b.visible = 'Y';
• Resolving descriptive text: join HR_TAB_PAGE_PROPERTIES_TL tl ON tl.tab_page_property_id = b.tab_page_property_id AND tl.language = USERENV('LANG').
• Auditing recent configuration changes via LAST_UPDATE_DATE and LAST_UPDATED_BY to trace which administrator altered tab-page behavior.
• Extracting tab-page content for integration or migration by pivoting the INFORMATION1..30 columns into a normalized report.

Related Objects

• HR_FORM_TAB_PAGES_B — parent table joined on FORM_TAB_PAGE_ID, defining the tab page within a specific form.
• HR_TEMPLATE_TAB_PAGES_B — parent table joined on TEMPLATE_TAB_PAGE_ID, defining the reusable template tab page.
• HR_TAB_PAGE_PROPERTIES_TL — translation (MLS) table joined on TAB_PAGE_PROPERTY_ID, supplying language-specific property text.
• HR_TAB_PAGE_PROPERTIES_B_PK / _UK — primary and unique indexes enforcing surrogate and business keys.
• PER Personalization / Forms Configurator — the runtime API layer that reads these property rows to drive configurable form rendering.