Results for “child_flex_value_low”

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

Overview

FII_DIM_NORM_HIERARCHY is a Financial Intelligence (FII) table in Oracle E-Business Suite that stores multi-level value hierarchies for financial dimension value sets. Each record captures a normalized parent-child relationship between financial dimension values, allowing FII to flatten or traverse hierarchical rollups used in financial reporting and analytics. The table belongs to the FII product, which carries an Obsolete status in the reference environment, and it is documented as "Not implemented in this database" under the ETRM metadata — meaning the object may not exist in all installations or may have been superseded by later architecture.

From a Data Vault modeling perspective (heuristic, mined from FK structure), this table is classified as standalone — it does not function as a hub, link, or satellite in the classic Data Vault sense, and no foreign-key-driven relationships to other vault entities were detected. The table is best understood as a self-contained hierarchy bridge: it encodes parent-to-child (or parent-to-range) relationships entirely within its own column set, using the flex value set identifiers and value ranges as the connective tissue.

Key Information Stored

The physical schema (ETRM 12.1.1) documents 11 columns owned by FII. The most important are:

• PARENT_FLEX_VALUE_SET_ID — identifies the value set that owns the parent value. Part of the primary key.
• PARENT_FLEX_VALUE — the parent value in the hierarchy. Part of the primary key.
• CHILD_FLEX_VALUE_SET_ID — the value set for the child side of the relationship; may differ from the parent value set where cross-value-set hierarchies are modeled.
• CHILD_FLEX_VALUE_LOW — the low end of the child value or child range.
• CHILD_FLEX_VALUE_HIGH — the high end of the child range. Where a single child value is used, LOW and HIGH typically coincide.
• RANGE_ATTRIBUTE — the flag that distinguishes a child value from a parent value, and indicates whether the child entry represents a discrete value or a range. This is the attribute users most often query directly.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each hierarchy row.

The surrogate primary key is composite: FII_DIM_NORM_HIERARCHY_PK spans (PARENT_FLEX_VALUE_SET_ID, PARENT_FLEX_VALUE, CHILD_FLEX_VALUE_SET_ID, CHILD_FLEX_VALUE_LOW, CHILD_FLEX_VALUE_HIGH, RANGE_ATTRIBUTE). The unique index FII_DIM_NORM_HIERARCHY_U1 uses the identical column list, meaning the business key and the physical PK are effectively the same — there is no separate surrogate identifier. Any hierarchy relationship is therefore uniquely identified by the parent/child value combination plus the RANGE_ATTRIBUTE flag.

Common Use Cases and Queries

The principal use case is reconstructing financial dimension rollups for reporting. Typical query patterns include:

• Find all children of a parent: SELECT child_flex_value_low, child_flex_value_high, range_attribute FROM fii_dim_norm_hierarchy WHERE parent_flex_value_set_id = :pvs AND parent_flex_value = :pv;
• Filter by RANGE_ATTRIBUTE to isolate discrete child values versus range entries, which is the most common user search intent associated with this table.
• Resolve a specific value to its parent for drill-down or drill-up reporting: match the value against the CHILD_FLEX_VALUE_LOW/HIGH boundaries for the relevant child value set.
• Validate hierarchy completeness prior to financial consolidation or FSG-style reporting, ensuring every child value has a defined parent path.

Because the table is FII-owned and marked Obsolete/Not Implemented in the reference environment, production queries should first confirm the object exists; in later releases, equivalent hierarchy information may be sourced from GL or FND flex value hierarchy objects.

Related Objects

The metadata documents no foreign-key relationships to other EBS objects (standalone classification). Conceptually, the identifiers used in this table align with standard flexfield objects that FII consumes:

• FND_FLEX_VALUE_SETS — joined on FLEX_VALUE_SET_ID = PARENT_FLEX_VALUE_SET_ID or CHILD_FLEX_VALUE_SET_ID.
• FND_FLEX_VALUES — joined on FLEX_VALUE = PARENT_FLEX_VALUE or against CHILD_FLEX_VALUE_LOW/HIGH.
• FND_FLEX_VALUE_NORM_HIERARCHY — the corresponding standard flexfield normalization hierarchy object, populated by the same range-attribute concept.
• FND_FLEX_VALUES_TL — for descriptive translations of parent and child values in reporting.
• FII dimension staging and fact tables — which consume normalized hierarchies during FII data loading and rollup processing.