Search Results bis_flex_seg_mapping_lines_u1

Overview

BIS.BIS_FLEX_SEG_MAPPING_LINES is a key flexfield segment mapping table owned by the BIS (Business Intelligence System / Oracle Daily Business Intelligence) schema. It stores the relationship between Oracle EBS key flexfield segments and the dimensional structures used by the BIS/ETRM data warehouse and analytical reporting layer. In practice, the table serves as a bridge between the operational accounting flexfield (or other registered key flexfields) and the warehouse dimensions against which segment-level data is aggregated and reported. Each row identifies a single segment line within a mapping definition, recording the flexfield segment, its structure, its associated value set, and the corresponding warehouse dimension or level.

The ETRM metadata classifies this object heuristically as a standalone entity, meaning it does not participate in a strong hub/link/satellite pattern in the Data Vault sense. It behaves more like a reference or configuration satellite that anchors descriptive attributes to a mapping line identifier and carries standard WHO audit columns. The presence of foreign keys to FRM_PART_VALUE_SETS and MSD_LEVELS indicates it is nonetheless embedded within the dimensional metadata model used by the analytical applications.

Key Information Stored

The surrogate primary key of the table is SEG_MAPPING_LINE_ID, a NUMBER(10) column that is also the sole column of the unique index BIS_FLEX_SEG_MAPPING_LINES_U1. This index is the documented business-key candidate and provides the row-level uniqueness guarantee. The table contains seventeen columns in total.

• SEG_MAPPING_LINE_ID — surrogate identifier, enforced unique by BIS_FLEX_SEG_MAPPING_LINES_U1.
• SEGMENT_NAME and APPLICATION_COLUMN_NAME — identify the specific flexfield segment and the underlying application column to which the mapping applies.
• APPLICATION_ID, ID_FLEX_CODE, STRUCTURE_NUM, and STRUCTURE_NAME — together describe the owning application and the key flexfield structure context for the mapping.
• VALUE_SET_ID — foreign key to FRM_PART_VALUE_SETS, identifying the value set that constrains the segment.
• INSTANCE_CODE — identifies the flexfield instance or context.
• DIMENSION_ID, LEVEL_ID, and WH_DIMENSION_NAME — link the segment to the warehouse dimension and level; LEVEL_ID carries a foreign key to MSD_LEVELS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — standard Oracle WHO audit columns.

Common Use Cases and Queries

Typical use cases include validating flexfield-to-dimension mappings, tracing which value set governs a mapped segment, and reporting dimension-to-segment alignment for DBI/ETRM dashboards. A representative query joining to the value set and level dimensions is:

SELECT m.SEG_MAPPING_LINE_ID
     , m.SEGMENT_NAME
     , m.ID_FLEX_CODE
     , m.STRUCTURE_NAME
     , m.WH_DIMENSION_NAME
     , l.LEVEL_ID
  FROM BIS.BIS_FLEX_SEG_MAPPING_LINES m
     , BIS.MSD_LEVELS l
 WHERE m.LEVEL_ID = l.LEVEL_ID
   AND m.APPLICATION_ID = :app_id;

Because the table carries full WHO audit columns, it can also be queried for change audit and configuration lineage reporting across 12.1.1 and 12.2.2 environments.

Related Objects

The following objects are the most significant references and dependencies:

• FRM_PART_VALUE_SETS — referenced via VALUE_SET_ID.
• MSD_LEVELS — referenced via LEVEL_ID.
• FND_USER — implicit reference from LAST_UPDATED_BY and CREATED_BY.
• FND_LOGINS — implicit reference from LAST_UPDATE_LOGIN.
• BIS.BIS_FLEX_SEG_MAPPING_LINES_U1 — the unique index enforcing SEG_MAPPING_LINE_ID.

Note that Oracle designates this object as Internal Use Only; access should occur only through supported Oracle Applications programs rather than direct SQL.