Results for “structure_num”

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

Overview

The BIS_FLEX_SEG_MAPPING_LINES table is a dictionary-style configuration object owned by the BIS schema in Oracle E-Business Suite (12.1.1 / 12.2.2). It records the line-level mapping between a Key Flexfield (KFF) segment and its corresponding target dimension, value set, instance, and level. Functionally, the table underpins the mapping definitions consumed by the BIS (Business Intelligence System) / ETRM integration layer, translating an EBS flexfield structure into the structures required for downstream reporting and data-warehouse loads. It is documented with 17 columns and a single unique index (BIS_FLEX_SEG_MAPPING_LINES_U1 on SEG_MAPPING_LINE_ID).

Per the ETRM metadata, the heuristic Data Vault classification is standalone, meaning it is not modeled as a child satellite of an established hub or link. As a modeling suggestion, this indicates the table behaves as a self-contained reference/definition entity rather than a transactional record or an associative link between two strong business entities.

Key Information Stored

The most significant columns represent the identity of each mapping line and the flexfield context it resolves. The surrogate primary key, enforced by the unique index, is SEG_MAPPING_LINE_ID. Business-key context is provided by the combination of flexfield and segment attributes rather than by a separate documented unique constraint.

• SEG_MAPPING_LINE_ID — surrogate primary key / unique business-key candidate for the mapping line.
• SEGMENT_NAME — the flexfield segment being mapped.
• APPLICATION_ID and ID_FLEX_CODE — identify the owning application and the Key Flexfield (KFF) code.
• STRUCTURE_NUM and STRUCTURE_NAME — the flexfield structure being mapped.
• APPLICATION_COLUMN_NAME — the underlying EBS column that stores the segment value.
• VALUE_SET_ID — reference to the value set (validated against FRM_PART_VALUE_SETS), defining the allowed values.
• INSTANCE_CODE, DIMENSION_ID and WH_DIMENSION_NAME — the target ETRM/warehouse dimension and instance context.
• LEVEL_ID — reference to MSD_LEVELS, indicating the hierarchy level applicable to the mapping.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical uses include reviewing how EBS flexfield segments map to warehouse dimensions, validating value-set alignment, and auditing configuration changes across releases. A representative query joining to the referenced value-set and level tables follows:

• List all mapping lines for a given KFF: SELECT segment_name, structure_name, application_column_name FROM bis.bis_flex_seg_mapping_lines WHERE id_flex_code = :p_code AND application_id = :p_app;
• Resolve dimension and level context: SELECT m.segment_name, m.wh_dimension_name, l.* FROM bis.bis_flex_seg_mapping_lines m, msd_levels l WHERE m.level_id = l.level_id;
• Validate value-set references: SELECT m.segment_name, v.* FROM bis.bis_flex_seg_mapping_lines m, frm_part_value_sets v WHERE m.value_set_id = v.value_set_id;
• Change/audit reporting filtered by LAST_UPDATE_DATE to track configuration drift.

Related Objects

The following objects are most significant to this table, per the documented foreign-key relationships and the surrounding BIS/ETRM model:

• FRM_PART_VALUE_SETS — joined via BIS_FLEX_SEG_MAPPING_LINES.VALUE_SET_ID = FRM_PART_VALUE_SETS.VALUE_SET_ID.
• MSD_LEVELS — joined via BIS_FLEX_SEG_MAPPING_LINES.LEVEL_ID = MSD_LEVELS.LEVEL_ID.
• FND_ID_FLEX_STRUCTURES — resolves the flexfield structure referenced by ID_FLEX_CODE/STRUCTURE_NUM.
• FND_ID_FLEX_SEGMENTS — resolves segment and column definitions matching SEGMENT_NAME.
• FND_FLEX_VALUE_SETS — correlates the value-set context used by the mapping.