Search Results edw_flex_seg_mappings




Overview
Explore in AI Chat

Overview

EDW_FLEX_SEG_MAPPINGS is a standalone table owned by the BIS schema within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It serves as a mapping repository that correlates Oracle EBS key flexfield structures and their constituent segments with the value sets and dimensions used by the Enterprise Data Warehouse (EDW) and Business Intelligence (BIS) integration layer. In this capacity the table acts as a bridge between the operational flexfield definition metadata stored in the Application Object Library and the analytical dimension model used for reporting and extract-transform-load processing.

The heuristic Data Vault classification derived from the foreign key structure is standalone. That classification indicates the table does not participate in a classic hub-and-satellite pattern with multiple parent references; instead it behaves as a self-contained reference or mapping table. The single documented foreign key, from EDW_FLEX_SEG_MAPPINGS.VALUE_SET_ID to FRM_PART_VALUE_SETS, suggests the mapping depends on Oracle Enterprise Performance Foundation (FRM) value set definitions rather than on the core FND flexfield tables.

Key Information Stored

The table contains 21 documented columns. The most significant are those that identify the flexfield being mapped and the segment-to-dimension correspondence:

No separate surrogate primary key is documented in the provided metadata; the identifying key is therefore composite, based on the flexfield/structure/segment combination together with INSTANCE_CODE.

Common Use Cases and Queries

The table is typically queried when building or validating the mapping between EBS accounting flexfield segments and EDW dimensions. A representative query retrieves the dimension assignment for a given flexfield structure:

  • SELECT STRUCTURE_NAME, SEGMENT_NAME, DIMENSION_SHORT_NAME, VALUE_SET_NAME FROM BIS.EDW_FLEX_SEG_MAPPINGS WHERE APPLICATION_ID = :app_id AND ID_FLEX_CODE = :code ORDER BY STRUCTURE_NUM;
  • Validating value set coverage: join to FRM_PART_VALUE_SETS on VALUE_SET_ID to confirm that every mapped segment references a defined value set.
  • Data lineage reporting: list INSTANCE_CODE alongside STRUCTURE_NAME to document which source instances contributed which segment mappings.
  • Impact analysis: identify all segments referencing a given VALUE_SET_ID before changing that value set.

Related Objects

  • FRM_PART_VALUE_SETS — referenced via EDW_FLEX_SEG_MAPPINGS.VALUE_SET_ID; the primary documented dependency.
  • FND_ID_FLEX_STRUCTURES — defines the flexfield structures identified by APPLICATION_ID, ID_FLEX_CODE, and STRUCTURE_NUM.
  • FND_ID_FLEX_SEGMENTS — defines the individual segments mapped by SEGMENT_NAME and APPLICATION_COLUMN_NAME.
  • FND_FLEX_VALUE_SETS — the core value set definition underlying VALUE_SET_NAME and VALUE_SET_TYPE.
  • FND_APPLICATION — resolves APPLICATION_ID to the owning application name.