Search Results value_set_datatype




Overview

EDW_FLEX_SEG_MAPPINGS_V is an Oracle Applications (APPS) view owned by the APPS schema and registered under the BIS (Business Intelligence System) product family. It is part of the Enterprise Data Warehouse (EDW) integration layer that exposes Oracle E-Business Suite Key Flexfield metadata in a flattened, warehouse-friendly form. In Oracle EBS 12.1.1 and 12.2.2, this view presents the mapping between key flexfield structures, their constituent segments, and the underlying value sets that govern allowed values. Its primary role is to support EDW and BIS-based reporting, ETL extraction, and analytical modeling where downstream consumers must understand how flexfield segments map to value sets and to application columns without querying the highly normalized flexfield definition tables directly.

The view exposes a curated set of attributes — including STRUCTURE_NAME, STRUCTURE_NUM, SEGMENT_NAME, VALUE_SET_NAME, and ID_FLEX_CODE — that describe the accounting and other key flexfield configurations in a single, denormalized result set. This makes it suitable for building EDW dimensions and for reconciling warehouse content with the source EBS configuration.

Underlying Base Objects

The view text reveals that EDW_FLEX_SEG_MAPPINGS_V is defined as a simple projection over the base table EDW_FLEX_SEG_MAPPINGS, selecting all of its documented columns without joins, filters, or aggregation. Consequently, the view shares the column list and data characteristics of its base table and inherits any population logic applied to that table by the BIS/EDW collection programs.

The ETRM metadata does not document any additional referenced base objects, so the view's dependency footprint is limited to APPS.EDW_FLEX_SEG_MAPPINGS. The upstream flexfield definition data — such as the key flexfield structure and segment definitions and their associated value sets — is materialized into that base table before the view is queried. Administrators should therefore treat the view as a read-only presentation layer and direct any data refresh or troubleshooting activity to the underlying collection and staging processes that populate the base table.

Key Columns

Common Use Cases and Queries

The view is typically used to inventory flexfield structures and their segment-to-value-set mappings, to validate warehouse dimension definitions, and to drive ETL logic that resolves segment values.

  • List segments for a specific structure: SELECT structure_name, segment_name, value_set_name FROM apps.edw_flex_seg_mappings_v WHERE structure_name = :p_structure;
  • Find value sets by type across a flexfield: SELECT id_flex_code, structure_name, segment_name, value_set_type FROM apps.edw_flex_seg_mappings_v WHERE id_flex_code = 'GL#';
  • Review dimension mapping and datatypes: SELECT dimension_short_name, segment_datatype, value_set_datatype FROM apps.edw_flex_seg_mappings_v ORDER BY structure_name, segment_name;
  • Check recently changed mappings: SELECT structure_name, segment_name, last_update_date FROM apps.edw_flex_seg_mappings_v WHERE last_update_date > SYSDATE - 30;