Search Results hr_item_contexts




Overview
Explore in AI Chat

Overview

HR_ITEM_CONTEXTS is the combinations table for the Item Context Key Flexfield (ICX) in the Oracle Human Resources (PER) module. It stores the valid, enabled code combinations that make up item contexts — the structured, flexfield-based descriptors used by Oracle EBS to classify template items within HR templates, checklists, and related configuration objects. Each row represents one context combination, with its descriptive segments resolved into SEGMENT1 through SEGMENT30 alongside the flexfield structure identifier (ID_FLEX_NUM) and standard date-effective and audit controls.

In Oracle EBS 12.1.1 and 12.2.2, Key Flexfield combinations tables follow the standard Oracle Application Object Library pattern: a surrogate primary key, a foreign key to the flexfield definition, a "Summary" flag for parent/rollup combinations, an enabled flag, active date ranges, and discrete segment columns. HR_ITEM_CONTEXTS conforms to this pattern and is owned by the HR schema with 43 documented columns.

Regarding Data Vault modeling, the metadata's heuristic classification is hub-leaning. This reflects that the table carries a stable, surrogate-keyed identity (ITEM_CONTEXT_ID) that is referenced by dependent tables, but it also holds substantial descriptive attributes — a mixture of hub and satellite characteristics. A rigorous Data Vault design would typically split the identity into a hub and the descriptive segments into one or more satellites keyed by the hub and load date.

Key Information Stored

The table's central identifier is ITEM_CONTEXT_ID, the surrogate primary key defined by HR_ITEM_CONTEXTS_PK. Note that the documented unique index HR_ITEM_CONTEXTS_PK is defined over ITEM_CONTEXT_ID and ZD_EDITION_NAME, reflecting Oracle's edition-based redefinition (EBR) support in 12.2.x. The edition column, ZD_EDITION_NAME, is therefore part of the business-key candidate set.

  • ITEM_CONTEXT_ID — Surrogate primary key; the unique identity of each item context combination.
  • ID_FLEX_NUM — Identifies the specific key flexfield definition this combination belongs to.
  • SUMMARY_FLAG — Indicates whether the row is a summary (parent/rollup) combination rather than a detail combination.
  • ENABLED_FLAG — Controls whether the combination is usable for new transactions or assignments.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Date-effective range during which the combination is valid.
  • SEGMENT1 … SEGMENT30 — The resolved segment values that make up the context combination; these are the flexfield's discrete, queryable attributes.
  • ZD_EDITION_NAME — EBR edition identifier; part of the composite unique key in 12.2.x.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard audit columns.
  • OBJECT_VERSION_NUMBER — Optimistic locking token used by the OAF/ADF framework.

Common Use Cases and Queries

Typical uses include validating context combinations before template item assignment, reporting on active versus disabled contexts, and resolving segments into human-readable context descriptions. A common pattern joins the combinations table to its flexfield definition and filters for enabled, currently active rows:

  • List active item contexts for a given flexfield: SELECT ITEM_CONTEXT_ID, SEGMENT1, SEGMENT2 FROM HR_ITEM_CONTEXTS WHERE ID_FLEX_NUM = :flex_num AND ENABLED_FLAG = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE);
  • Identify disabled or expired contexts for cleanup and impact analysis before decommissioning a template item.
  • Reporting on which templates reference which item contexts by joining through HR_TEMPLATE_ITEM_CONTEXTS_B.
  • Edition-aware queries in 12.2.x should account for ZD_EDITION_NAME when comparing combinations across editions.

Related Objects

The principal documented relationship is the foreign key from HR_TEMPLATE_ITEM_CONTEXTS_B to HR_ITEM_CONTEXTS on ITEM_CONTEXT_ID. That dependent table links templates to the item contexts they use, making it the most significant downstream consumer of this combinations table. In practice, the surrounding object family includes the following:

  • HR_TEMPLATE_ITEM_CONTEXTS_B — Joins on ITEM_CONTEXT_ID; associates template items with item contexts.
  • FND_ID_FLEX_STRUCTURES — Matched on ID_FLEX_NUM; defines the flexfield structure for the ICX context.
  • FND_ID_FLEX_SEGMENTS — Supplies segment definitions that map to SEGMENT1 … SEGMENT30.
  • HR_TEMPLATE_ITEM_CONTEXTS_TL — The translatable (TL) companion that stores language-specific text for template item contexts.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — Provide the valid values referenced by individual segment columns.

Because the table is HR-owned and flexfield-driven, customization should respect the standard combinations-table integrity rules and the EBR edition semantics present in Release 12.2.2.