Results for “parent_flex_value_id”

5 results




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

Overview

The FII_FIN_ITEM_HIERARCHIES table belongs to the Financial Intelligence (FII) product family within Oracle EBS, a module that has since been classified as obsolete. Its stated purpose is to store the child-parent relationship between financial items, effectively materializing a navigable hierarchy of financial categories and their associated flex values. In the Oracle EBS 12.1.1 schema, the object is owned by the FII schema and is documented with 25 columns. Within the 12.2.2 environment, the object is not implemented in the database, and no runtime or DBA artifact exists for it.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a standalone classification. This is a heuristic suggestion only: because the table's relationships are self-contained and its only documented outgoing reference is to MSD_LEVELS via LEVEL_ID, the table behaves less like a conventional hub or link and more like a denormalized structural artifact. Practitioners modeling this data in a modern warehouse may treat it as a standalone reference structure rather than attempting to decompose it into canonical Data Vault entities.

Key Information Stored

The table captures the adjacency of financial items across multiple hierarchy levels. The most significant columns are:

The unique index FII_FIN_ITEM_HIERARCHIES_U1 on (PARENT_FIN_CAT_ID, CHILD_FIN_CAT_ID) establishes the composite business key, while LEVEL_ID serves as the documented foreign key to MSD_LEVELS, distinguishing the surrogate relationship from the business identity of the hierarchy edge.

Common Use Cases and Queries

Because this object is obsolete and not implemented in 12.2.2, its primary value is in historical reporting, migration analysis, and legacy data reconciliation. Typical patterns include extracting the full parent-child mapping for financial category roll-ups, and identifying leaf nodes for aggregation endpoints.

  • Traversing a single level: SELECT PARENT_FLEX_VALUE, CHILD_FLEX_VALUE FROM FII_FIN_ITEM_HIERARCHIES WHERE LEVEL_ID = :level_id;
  • Finding terminal items: SELECT CHILD_FIN_CAT_ID FROM FII_FIN_ITEM_HIERARCHIES WHERE IS_LEAF_FLAG = 'Y';
  • Joining to level metadata: SELECT h.PARENT_FLEX_VALUE, l.LEVEL_NAME FROM FII_FIN_ITEM_HIERARCHIES h, MSD_LEVELS l WHERE h.LEVEL_ID = l.LEVEL_ID;
  • Building two-level roll-ups without recursion using NEXT_LEVEL_FIN_CAT_ID and NEXT2_LEVEL_FLEX_VALUE.

Reporting use cases center on financial statement generation, category roll-up validation, and pre-migration audits comparing legacy hierarchy edges against the replacement structures in 12.2.2.

Related Objects

The most significant related objects are:

  • MSD_LEVELS — referenced via LEVEL_ID; supplies level definitions and hierarchy context.
  • FII_FIN_ITEM_HIERARCHIES_U1 — the unique index enforcing the parent/child business key.
  • FII financial category and flex value tables — resolved through PARENT_FIN_CAT_ID, CHILD_FIN_CAT_ID, and the FLEX_VALUE_ID columns.
  • FND_FLEX_VALUE_SETS — implied by PARENT_FLEX_VALUE_SET_ID and CHILD_FLEX_VALUE_SET_ID.
  • FND_FLEX_VALUES — implied by the parent, child, and next-level flex value identifiers.
  • FII financial item and reporting objects — consume the hierarchy for aggregation and presentation.

These relationships should be confirmed against the target environment, as the object is documented as obsolete and not implemented in the current database.