Results for “next_level_flex_value”
9 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The FII_LOB_HIERARCHIES table is a core reference object within the Oracle EBS Financial Intelligence (FII) product family. It stores the child-parent relationships that define line of business (LOB) hierarchies, providing the structural backbone used by financial intelligence reporting, consolidation, and analytical processes. Each row represents a relationship edge between a parent LOB and a child LOB, together with the flex value identifiers and flex value set identifiers that map those LOB nodes to their underlying accounting flexfield definitions. The table is owned by the FII schema and is marked VALID in the documented ETRM repository for EBS 12.1.1 and 12.2.2.
The heuristic Data Vault classification mined from the foreign key structure is standalone. This should be treated as a modeling suggestion rather than a normative declaration: the table contains both descriptive hierarchy attributes and edge-relationship semantics, so depending on warehouse design it may be modeled as a link (parent-child relationship) or as a satellite when flattened against a LOB hub. The presence of a single documented foreign key, LEVEL_ID to MSD_LEVELS, is what drives the standalone classification.
Key Information Stored
The table exposes 26 columns. The most significant fall into three groups: hierarchy identifiers, flexfield mappings, and audit columns.
- PARENT_LOB_ID and CHILD_LOB_ID — the parent and child line-of-business identifiers. Together these form the documented unique index FII_LOB_HIERARCHIES_U1, making them the primary business-key candidates for the hierarchy edge.
- NEXT_LEVEL_LOB_ID — the immediate next-level LOB in the traversed path, supporting leveled expansions alongside PARENT_LOB_ID and CHILD_LOB_ID.
- LEVEL_ID — foreign key to MSD_LEVELS, defining the hierarchy level at which the relationship resides.
- PARENT_LEVEL, NEXT_LEVEL, and CHILD_LEVEL — numeric level indicators for each node in the relationship, used for depth-based filtering and roll-ups.
- PARENT_FLEX_VALUE_ID, NEXT_LEVEL_FLEX_VALUE_ID, and CHILD_FLEX_VALUE_ID — surrogate flex value identifiers for each LOB node.
- PARENT_FLEX_VALUE, NEXT_LEVEL_FLEX_VALUE, and CHILD_FLEX_VALUE — the human-readable flex value strings.
- PARENT_FLEX_VALUE_SET_ID and CHILD_FLEX_VALUE_SET_ID — identify which flex value set the values belong to, enabling multi-structure support.
- NEXT2_LEVEL_FLEX_VALUE_ID and NEXT2_LEVEL_FLEX_VALUE — a second-ahead hop used when traversing more than one level down.
- NEXT_LEVEL_IS_LEAF and IS_LEAF_FLAG — boolean indicators marking terminal nodes, useful for pruning traversal queries.
- NEXT_LEVEL_LOB_SORT_ORDER — controls presentation ordering within a level.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit columns.
Common Use Cases and Queries
Typical usage centers on hierarchical reporting and roll-up of financial results across lines of business. Analysts join this table to fact data keyed by LOB to aggregate amounts at each ancestor level, and to flatten multi-level hierarchies into denormalized reporting structures.
- Retrieving direct children of a given LOB:
SELECT CHILD_LOB_ID, CHILD_FLEX_VALUE, CHILD_LEVEL FROM FII_LOB_HIERARCHIES WHERE PARENT_LOB_ID = :p_lob_id. - Identifying leaf LOBs for granular reporting:
SELECT CHILD_LOB_ID FROM FII_LOB_HIERARCHIES WHERE IS_LEAF_FLAG = 'Y'. - Level-scoped expansion: filtering by
PARENT_LEVELorCHILD_LEVELto constrain a hierarchy walk to a specified depth. - Cross-referencing flex values with GL code combinations via
PARENT_FLEX_VALUE_IDandCHILD_FLEX_VALUE_IDfor reconciliation against the chart of accounts. - Sort-ordered sibling presentation using
NEXT_LEVEL_LOB_SORT_ORDER.
Related Objects
- MSD_LEVELS — referenced through
FII_LOB_HIERARCHIES.LEVEL_ID = MSD_LEVELS.LEVEL_ID; defines the hierarchy level for each relationship row. - FII_LOB_HIERARCHIES_U1 — the unique index on (PARENT_LOB_ID, CHILD_LOB_ID), enforcing uniqueness of hierarchy edges.
- FND_FLEX_VALUES and FND_FLEX_VALUE_SETS — the underlying flex value and value set definitions that
PARENT_FLEX_VALUE_ID,CHILD_FLEX_VALUE_ID, and the associated value set identifiers resolve against. - Other FII-lineage tables in the FII schema that consume LOB membership for financial consolidation and dimensional analysis.
- GL code combination objects — joined via flex value identifiers when mapping LOB nodes to accounting combinations for GL-level reporting.
-
This table stores the child-parent relatioship for line of business.
-
This table stores the child-parent relationship between financial items.
-
View: FII_LOB_HIER_V 12.2.2
Internal view used to support Line of Business Hierarchy in DBI.
Not implemented in this database·Explore FII module →
-
View: FII_FIN_ITEM_HIER_V 12.2.2
Internal view used to support Financial Item Hierarchy in DBI.
Not implemented in this database·Explore FII module →
-
View: FII_LOB_HIER_V 12.1.1
Internal view used to support Line of Business Hierarchy in DBI.
Not implemented in this database·Explore FII module →
-
View: FII_FIN_ITEM_HIER_V 12.1.1
Internal view used to support Financial Item Hierarchy in DBI.
Not implemented in this database·Explore FII module →
-
eTRM - FII Tables and Views 12.1.1
This table stores the mapping of leaf nodes from pruned dimension to nodes in the child value sets