Search Results hr_tcp_uk

Overview

The HR.HR_TEMPLATE_ITEM_CONTEXT_PAGES table is a component of the PER (Human Resources) product family in Oracle E-Business Suite, documented as VALID across both 12.1.1 and 12.2.2. It stores information about which tab pages an item belongs to for a specific context, on a template used for a configurable form. In practical terms, this table is the mapping layer that resolves the relationship between a contextual template item and the tab page on which that item is rendered within a configurable form layout.

The table participates in the configurable form framework, where administrators define templates, contexts, items, and tab pages, and the system assembles them into a runtime presentation. This table supplies the placement metadata that determines how items are organized across tabbed regions for a given context.

Based on the foreign key structure mined from the ETRM metadata, the heuristic Data Vault classification for this object is link. This is a modeling suggestion: the table does not hold descriptive attributes of an entity in its own right, but rather resolves many-to-many style associations between two parent entities — template item contexts and template tab pages — through its foreign keys. Note that the same physical table also carries audit and edition columns, so a formal Data Vault model might treat those as satellite concerns.

Key Information Stored

The documented schema exposes 10 columns in release 12.2.2, under the HR owner. The most significant columns are the following.

• TEMPLATE_ITEM_CONTEXT_PAGE_ID — the surrogate primary key of the row, enforced by the HR_TCP_PK index. It uniquely identifies each item-to-tab-page placement record.
• TEMPLATE_ITEM_CONTEXT_ID — foreign key to HR_TEMPLATE_ITEM_CONTEXTS_B. It identifies the contextual instance of a template item whose page placement is being defined.
• TEMPLATE_TAB_PAGE_ID — foreign key to HR_TEMPLATE_TAB_PAGES_B. It identifies the tab page to which the item is assigned for that context.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• ZD_EDITION_NAME — the editioning column. In 12.2.2 this participates in the unique indexes HR_TCP_PK and HR_TCP_UK, reflecting the edition-based redefinition architecture used by EBS 12.2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns recording who created and last modified the row and when.

The business-key candidate is defined by HR_TCP_UK, a unique index over TEMPLATE_TAB_PAGE_ID, TEMPLATE_ITEM_CONTEXT_ID, and ZD_EDITION_NAME. This uniqueness constraint enforces that a given template item context may be associated with a given tab page only once per edition, which is the core business rule of the table. The surrogate key is TEMPLATE_ITEM_CONTEXT_PAGE_ID; the business key is the combination of the two foreign keys plus the edition.

Common Use Cases and Queries

Typical usage centers on reconstructing the layout of configurable forms. A common reporting pattern joins the two parent tables to present each item alongside the tab page it appears on for a given context.

• Determining which items appear on a specific tab page: filter by TEMPLATE_TAB_PAGE_ID and join to HR_TEMPLATE_ITEM_CONTEXTS_B to retrieve item details.
• Determining the page placement of a specific item context: filter by TEMPLATE_ITEM_CONTEXT_ID and join to HR_TEMPLATE_TAB_PAGES_B for the tab page name and ordering.
• Validating configuration integrity: detecting item contexts that have no page assignment, or detecting duplicate assignments, using the business-key columns.
• Diagnosing rendering failures where an item does not appear on the expected tab, by comparing the stored association against the intended template design.

A representative query pattern is: SELECT tcp.TEMPLATE_ITEM_CONTEXT_PAGE_ID, tic.TEMPLATE_ITEM_CONTEXT_ID, ttp.TEMPLATE_TAB_PAGE_ID FROM hr.hr_template_item_context_pages tcp JOIN hr.hr_template_item_contexts_b tic ON tcp.template_item_context_id = tic.template_item_context_id JOIN hr.hr_template_tab_pages_b ttp ON tcp.template_tab_page_id = ttp.template_tab_page_id WHERE tcp.zd_edition_name = :edition;. Because the table is edition-enabled in 12.2.2, queries should always constrain or be aware of ZD_EDITION_NAME when run against that release.

Related Objects

The table depends on and is referenced by the following significant objects, per the documented relationships:

• HR_TEMPLATE_ITEM_CONTEXTS_B — referenced through TEMPLATE_ITEM_CONTEXT_ID; the parent table of the item context being placed.
• HR_TEMPLATE_TAB_PAGES_B — referenced through TEMPLATE_TAB_PAGE_ID; the parent table of the tab page receiving the item.
• HR_TEMPLATE_ITEM_CONTEXT_PAGES (synonym and editioned variants) — the underlying object exposed for querying across editions in 12.2.2.
• The wider configurable form template tables in the PER schema — including the template, template item, and context definition tables that feed HR_TEMPLATE_ITEM_CONTEXTS_B — form the surrounding data model and are required to interpret this table fully.
• Oracle HRMS configurable form setup and self-service configuration flows that read this table to render tabbed layouts at runtime.

Because the table carries WHO audit columns and an object version number, it is maintained through the standard Applications DML conventions rather than direct manipulation, and joins should routinely respect the editioning column in 12.2.2 environments.