Search Results fii_fa_cat_segments_pk

Overview

FII_FA_CAT_SEGMENTS is a configuration table in the FII (Financial Intelligence) product family of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the Asset Category flexfield structure information that drives how Oracle Assets asset categories are decomposed into analytical segments for Financial Intelligence reporting and data extraction. Each row describes one flexfield structure definition, identifying the major and minor segments that compose the category key and the underlying database objects and columns from which valid segment values are sourced.

The table functions as a metadata registry rather than a transactional ledger. Its records govern the runtime behavior of the FII asset category dimension, meaning changes here propagate directly into how asset category data is read, validated, and presented. The heuristic Data Vault classification mined from the foreign key structure is standalone; in modeling terms this suggests the table be treated as an independent reference or hub-style entity, since no inbound foreign keys to other tables are documented and the only external dependency is a child reference from FII_FA_CAT_DIMENSIONS.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• FLEX_STRUCTURE_ID — The primary key of the table (constraint FII_FA_CAT_SEGMENTS_PK) and also the sole business-key candidate, enforced by unique index FII_FA_CAT_SEGMENTS_U1. It identifies the flexfield structure being defined.
• MAJOR_SEG_NAME — Name of the major segment within the flexfield structure.
• MAJOR_VAL_TYPE_CODE — Validation type code controlling how major segment values are validated.
• MAJOR_TABLE_NAME — The table from which valid major segment values are drawn.
• MAJOR_VALUE_COLUMN_NAME — The value column read for major segment lookups.
• MAJOR_ID_COLUMN_NAME — The identifier column corresponding to the major segment value.
• MAJOR_ADD_WHERE_CLAUSE — An additional SQL predicate applied when resolving major segment values.
• MINOR_SEG_NAME — Name of the minor segment within the structure.
• MINOR_VAL_TYPE_CODE — Validation type code for minor segment values.
• MINOR_TABLE_NAME — Source table for valid minor segment values.
• MINOR_VALUE_COLUMN_NAME and MINOR_ID_COLUMN_NAME — The value and identifier columns for the minor segment.
• MINOR_ADD_WHERE_CLAUSE — Additional predicate for minor segment value resolution.
• DEPENDANT_VALUE_SET_FLAG — Indicates whether the minor value set depends on the major segment selection.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN track record provenance.

The distinction between the surrogate primary key and the business key is nominal here: FLEX_STRUCTURE_ID serves both roles, which is a common pattern for configuration tables seeded with a small, stable set of rows.

Common Use Cases and Queries

Because the table defines flexfield structure metadata, the most frequent access pattern is a direct lookup by structure identifier, typically during setup validation or when diagnosing why asset category values fail to resolve.

• Retrieve the full definition of a structure:
  SELECT * FROM fii.fii_fa_cat_segments WHERE flex_structure_id = :p_id;
• List all configured structures with their segment pairing:
  SELECT flex_structure_id, major_seg_name, minor_seg_name, dependant_value_set_flag FROM fii.fii_fa_cat_segments ORDER BY flex_structure_id;
• Identify structures that use dependent value sets, which affect how downstream extraction must sequence value resolution:
  SELECT flex_structure_id, major_seg_name, minor_seg_name FROM fii.fii_fa_cat_segments WHERE dependant_value_set_flag = 'Y';
• Reconcile the source tables referenced by a structure against the data dictionary, using MAJOR_TABLE_NAME and MINOR_TABLE_NAME, to confirm that the configured lookup objects exist after an upgrade.

Reporting use cases center on metadata audits before or after patching, and on troubleshooting FII asset category dimension loads where segment values are missing or rejected.

Related Objects

The documented relationship data identifies one dependent table:

• FII_FA_CAT_DIMENSIONS — references this table via FLEX_STRUCTURE_ID, forming the principal parent-child relationship. Any query joining asset category dimension rows to their flexfield structure definition uses this column pair.

Beyond the documented foreign key, the table is read in conjunction with the Oracle Assets asset category definition to which each structure corresponds, and with the standard FND flexfield definition tables that describe the underlying value sets referenced by the MAJOR and MINOR column families. The audit columns follow the standard EBS WHO column conventions shared across the FII schema.