Search Results flex_structure_name

Overview

The FND_FLEX_CROSS_VALIDATION_V view is a reporting and integration artifact owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the set of key flexfield structures that have cross-segment (cross-validation) rules enabled, joined to the application that owns them and the descriptive identity of each flexfield. Cross-validation controls permissible combinations of segment values when an end user enters a key flexfield combination; this view provides a single, denormalized read interface over the configuration metadata that governs that behavior.

Because cross-validation setup spans multiple base objects, administrators and developers frequently need a consolidated query surface to answer questions such as which structures enforce cross-validation, which application owns each flexfield, and what the structure names and descriptions are. The view serves that purpose and is exposed through the standard FND Application Object Library dictionary, making it available to concurrent programs, Forms personalizations, Web ADI, and custom SQL reports in both release families. The view metadata is documented as VALID in both 12.1.1 and 12.2.2, and its column list is stable across the two releases.

Underlying Base Objects

Per the ETRM metadata, the view is defined over three documented base objects:

• FND_ID_FLEXS (referenced through a synonym) — the flexfield definition table, supplying the flexfield code, name, description, and owning application.
• FND_APPLICATION_VL (VIEW) — the multi-language application view, supplying the application name and short name.
• FND_ID_FLEX_STRUCTURES_VL (VIEW) — the multi-language flexfield structure view, supplying the structure number, structure name, and structure description.

Internally, FND_ID_FLEX_STRUCTURES_VL is itself defined over FND_ID_FLEX_STRUCTURES and its translations, and it exposes the CROSS_SEGMENT_VALIDATION_FLAG column. The view's defining predicate filters on S.CROSS_SEGMENT_VALIDATION_FLAG = 'Y', so only structures with cross-validation enabled are returned. The joins are made on APPLICATION_ID and ID_FLEX_CODE, which is the natural composite key linking a flexfield definition to its structures.

Key Columns

• FLEX_CODE — the key flexfield code (for example, GL# for the Accounting Flexfield), the primary searchable identifier.
• FLEX_NAME and FLEX_DESCRIPTION — the display name and description of the flexfield definition.
• APPLICATION_ID — the numeric application identifier of the owning application.
• APPLICATION_NAME and APPLICATION_SHORT_NAME — the translated application name and its short name.
• FLEX_STRUCTURE_NUM — the structure number (ID_FLEX_NUM), unique within a flexfield code.
• FLEX_STRUCTURE_NAME and FLEX_STRUCTURE_DESCRIPTION — the translated structure name and description.

Common Use Cases and Queries

Typical uses include auditing which structures enforce cross-validation, driving migration scripts that compare cross-validation configuration between environments, and confirming the owning application for a given flexfield code in reports and interfaces.

List all cross-validated structures for a specific flexfield:

SELECT flex_code, flex_name, flex_structure_num,
       flex_structure_name, application_short_name
FROM   fnd_flex_cross_validation_v
WHERE  flex_code = 'GL#'
ORDER  BY flex_structure_num;

Count cross-validated structures by application:

SELECT application_short_name, COUNT(*) structures
FROM   fnd_flex_cross_validation_v
GROUP  BY application_short_name
ORDER  BY 2 DESC;

Resolve a structure name for a known flexfield and structure number:

SELECT flex_structure_name, flex_structure_description
FROM   fnd_flex_cross_validation_v
WHERE  flex_code = 'GL#' AND flex_structure_num = 101;