Results for “fnd_flex_value_destination_v”

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

Overview

FND_FLEX_VALUE_DESTINATION_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the FND — Application Object Library product and exposes only those key flexfield values that participate in a structured hierarchy and are flagged as summary (parent) values. Because the view joins the value definition layer with the hierarchy translation layer, it presents each qualifying flexfield value alongside the name and level of the hierarchy node to which it has been assigned. In practice, the view answers the recurring question of where a given parent value sits within an account hierarchy and what that destination is called in the user's language.

The term DESTINATION in the object name reflects this orientation: rather than describing the hierarchy as a whole, the view describes each summary value as a destination within it. It is read-only and does not store data; all content is derived at query time, which makes it suitable for reporting, data extraction, and integration lookups, but unsuitable as a transactional target.

Underlying Base Objects

The view is defined over two documented objects: FND_FLEX_VALUES_VL, exposed in the APPS schema as a view, and FND_FLEX_HIERARCHIES_TL, exposed as a synonym. The join is an outer join from the value layer to the hierarchy translation layer, so a summary value is returned even when no translated hierarchy row is available for the current session language. Language filtering is applied by matching the translation row to USERENV('LANG'), ensuring the hierarchy name and level are returned in the session's language. The join conditions link the value set and the structured hierarchy level on the value side to the flex value set and hierarchy ID on the translation side. A filter restricts output to rows where SUMMARY_FLAG = 'Y', eliminating detail or child values from the result set.

Key Columns

• FLEX_VALUE_SET_ID — Identifier of the key flexfield value set to which the value belongs. This is the primary grouping key for all reporting on the view.
• FLEX_VALUE — The stored value of the parent segment, for example an account segment such as 1000 or a company code. This is the value visible in transactional data and is the same value concatenated into concatenated segment strings.
• DESCRIPTION — The descriptive text attached to the flexfield value in the current language, sourced from the values view. It provides the business-friendly label for the value.
• HIERARCHY_NAME — The translated name of the hierarchy to which the value is assigned. Because the join is an outer join, this column may be null for values whose hierarchy translation is unavailable in the session language.
• HIERARCHY_LEVEL — The level of the value within the structured hierarchy, exposing depth for roll-up and drill-down reporting. This column is frequently the object of searches for hierarchy_level when users need to determine at which tier a parent value resides.

Common Use Cases and Queries

Typical usage includes hierarchy-aware reporting on account segment values, validation of hierarchy assignments before period close, and extraction feeds for downstream analytics that require the human-readable hierarchy name and depth alongside the raw segment value. The following query lists all summary values for a given value set, ordered from the top of the hierarchy downwards:

SELECT flex_value_set_id,
       flex_value,
       description,
       hierarchy_name,
       hierarchy_level
FROM   apps.fnd_flex_value_destination_v
WHERE  flex_value_set_id = :p_value_set_id
ORDER  BY hierarchy_level, flex_value;

To locate a specific value and determine its hierarchy placement, a lookup on FLEX_VALUE is sufficient:

SELECT flex_value, description, hierarchy_name, hierarchy_level
FROM   apps.fnd_flex_value_destination_v
WHERE  flex_value = :p_flex_value;

Because only summary values are exposed, the view should be joined back to FND_FLEX_VALUES_VL when both parents and children are required in a single report. All queries should be run against the APPS synonym or fully qualified APPS object, and the view should be treated strictly as a read-only reporting interface.