Search Results hr_tic_b_pk




Overview
Explore in AI Chat

Overview

The HR.HR_TEMPLATE_ITEM_CONTEXTS_B table stores the definition of items placed on a template for a given context within Oracle E-Business Suite, specifically for configurable forms. It is a transactional data table belonging to the Human Resources (HR) schema, with FND design data registered under PER.HR_TEMPLATE_ITEM_CONTEXTS_B. The table resides in the APPS_TS_TX_DATA tablespace and is marked VALID in both 12.1.1 and 12.2.2. Its function is to associate a template item with a context — such as a Descriptive Flexfield or Key Flexfield — enabling configurable form behavior driven by template metadata.

From a Data Vault modeling perspective, the mined relationship structure classifies this table as satellite-leaning. It holds descriptive attributes tied to the template item context identifier rather than acting as a pure hub or link, which suggests it functions as a dependent attribute store anchored to a parent entity.

Key Information Stored

The table's primary key is HR_TIC_B_PK, defined on the TEMPLATE_ITEM_CONTEXT_ID column. This is a system-generated surrogate key populated from the sequence HR_TEMPLATE_ITEM_CONTEXTS_B_S. A second unique index, HR_TIC_B_UK, spans ITEM_CONTEXT_ID and TEMPLATE_ITEM_ID, forming the business-key candidate for this object. In the 12.2.2 documented schema, both unique indexes additionally include ZD_EDITION_NAME to support editioning.

  • TEMPLATE_ITEM_CONTEXT_ID — surrogate primary key; the anchor column referenced by dependent child tables.
  • TEMPLATE_ITEM_ID — foreign key to HR_TEMPLATE_ITEMS_B, identifying the template item to which this context applies.
  • ITEM_CONTEXT_ID — foreign key to HR_ITEM_CONTEXTS, identifying the specific context definition.
  • CONTEXT_TYPE — type of context, restricted initially to "Descriptive Flexfield" and "Key Flexfield".
  • OBJECT_VERSION_NUMBER — system-generated row version, incremented on each update, used for optimistic locking.
  • Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE capture audit and concurrency information for every row.

Common Use Cases and Queries

Typical usage involves resolving which contexts are attached to template items for configurable forms, and joining through to the child pages and properties that render those contexts. A common reporting pattern joins this table to HR_TEMPLATE_ITEMS_B and HR_ITEM_CONTEXTS to obtain descriptive labels for template configuration:

  • Retrieve all contexts for a given template item: SELECT * FROM hr_template_item_contexts_b WHERE template_item_id = :item_id;
  • Resolve context details: SELECT t.template_item_context_id, c.context_type, t.item_context_id FROM hr_template_item_contexts_b t, hr_item_contexts c WHERE t.item_context_id = c.item_context_id;
  • Retrieve dependent pages: SELECT * FROM hr_template_item_context_pages WHERE template_item_context_id = :tic_id;
  • Retrieve item properties: SELECT * FROM hr_item_properties_b WHERE template_item_context_id = :tic_id;

These queries support configuration diagnostics, template migration validation, and reporting on flexfield-to-template mappings.

Related Objects

The following objects are the most significant dependents and parents in the documented relationship structure:

These relationships confirm the table's role as the linking anchor between template items and their context and page definitions, making HR_TIC_B_PK the central reference point for the template configuration model.