Results for “flex_mapping_set_id”

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

Overview

PSB_FLEX_MAPPING_SEGMENTS_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and supplied by the Public Sector Budgeting (PSB) product. The view exposes the relationship between PSB flex mapping sets and the descriptive flexfield structures that back them, resolving the ambiguous identifiers of a mapping set into human-readable key flexfield segment information. In release 12.1.1 and 12.2.2, the object is shipped with a VALID status and is defined exclusively as a query over existing PSB and Application Object Library (FND) objects; it stores no data of its own. Its role in EBS reporting and integration is to provide a denormalized, ready-to-join source that describes which application column, key flexfield structure, segment, and value set are associated with each PSB flex mapping set, without requiring an implementer to reconstruct the join logic manually.

The view is relevant to users who search for the related dictionary object fnd_id_flex_segments_vl, because that view is the principal FND dependency used internally by PSB_FLEX_MAPPING_SEGMENTS_V to resolve segment names and value set identifiers.

Underlying Base Objects

The view text defines a three-table join with a DISTINCT restriction. The participating objects are:

• PSB_FLEX_MAPPING_SET_VALUES (aliased VAL) — supplies FLEX_MAPPING_SET_ID, APPLICATION_COLUMN_NAME, and FLEX_VALUE_SET_ID.
• FND_ID_FLEX_SEGMENTS_VL (aliased SEG) — supplies SEGMENT_NAME and ID_FLEX_NUM for the matching application column and flexfield structure.
• PSB_FLEX_MAPPING_SETS (aliased SETS) — supplies the mapping set header against which the set identifier is validated.

Join conditions are: VAL.FLEX_MAPPING_SET_ID = SETS.FLEX_MAPPING_SET_ID and SEG.APPLICATION_COLUMN_NAME = VAL.APPLICATION_COLUMN_NAME. The segment side is further restricted to SEG.APPLICATION_ID = 101 and SEG.ID_FLEX_CODE = 'GL#'. Application ID 101 is the General Ledger application, and GL# is the standard flexfield code for the GL Accounting Flexfield. Consequently, the view returns only those mappings whose application column resolves to a General Ledger key flexfield segment; PSB mappings linked to other applications or flexfield codes are excluded by design.

The ETRM 12.2.2 metadata documents no additional referenced base objects beyond those appearing in the view text. Note that FND_ID_FLEX_SEGMENTS_VL is itself a view over FND_ID_FLEX_SEGMENTS with translation handling, so row-level security and language settings on the FND tier can influence the segment names returned.

Key Columns

• FLEX_MAPPING_SET_ID — Identifier of the PSB flex mapping set. Serves as the primary join key back to PSB_FLEX_MAPPING_SETS and forward to PSB_FLEX_MAPPING_SET_VALUES.
• APPLICATION_COLUMN_NAME — Name of the application column used by the mapping, used to correlate the mapping value with its corresponding key flexfield segment.
• SEGMENT_NAME — Descriptive name of the GL key flexfield segment (for example, Company, Cost Center, Account), sourced from FND_ID_FLEX_SEGMENTS_VL.
• ID_FLEX_NUM — Internal identifier of the key flexfield structure to which the segment belongs, allowing separation of segments across multiple chart of accounts structures.
• FLEX_VALUE_SET_ID — Identifier of the value set that validates values for the mapped segment, supporting downstream validation and reporting of allowable values.

Because the view uses SELECT DISTINCT, duplicate combinations arising from overlapping mapping values are collapsed, yielding one row per distinct set, column, segment, structure, and value set combination.

Common Use Cases and Queries

Typical uses include diagnosing which segments a PSB mapping set touches, auditing the value sets feeding a budgeting configuration, and building extract queries that describe the chart of accounts context for a mapping.

• List all segments for a given mapping set:

SELECT flex_mapping_set_id, application_column_name, segment_name, id_flex_num, flex_value_set_id FROM apps.psb_flex_mapping_segments_v WHERE flex_mapping_set_id = :p_set_id ORDER BY application_column_name;

• Find mapping sets that reference a particular value set, useful when a value set is being changed or retired:

SELECT DISTINCT flex_mapping_set_id, segment_name FROM apps.psb_flex_mapping_segments_v WHERE flex_value_set_id = :p_value_set_id;

• Joining back to PSB_FLEX_MAPPING_SETS to present the mapping set name alongside segment detail:

SELECT s.mapping_set_name, v.segment_name, v.application_column_name, v.flex_value_set_id FROM apps.psb_flex_mapping_segments_v v, apps.psb_flex_mapping_sets s WHERE v.flex_mapping_set_id = s.flex_mapping_set_id;

Because the view filters on APPLICATION_ID = 101 and ID_FLEX_CODE = 'GL#', queries intended to describe non-GL flexfield mappings will return no rows; such cases must be sourced from the underlying PSB and FND tables directly.