Search Results runtime_property_function




Overview
Explore in AI Chat

Overview

FND_DESCR_FLEX_COL_USAGE_VL is an Application Object Library (FND) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the column-usage definitions that drive Descriptive Flexfields (DFF), exposing, in a single language-aware row, both the technical configuration of each descriptive flexfield segment and its translated end-user presentation attributes. The "_VL" suffix denotes a "view with language" — the view joins a base (non-translated) table to its translation table and filters the translation by USERENV('LANG'), returning prompt and description text in the session's current language.

Because descriptive flexfields store their runtime behavior and their displayed labels in separate structures, this view is the standard consolidated source for reporting and integration. It allows developers, report authors, and integrators to resolve the physical database column that backs a DFF segment, the enabled/required/display flags governing that segment, the value-set binding used for validation, and the prompt text the user actually sees — without manually joining the base and translation tables.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

  • FND_DESCR_FLEX_COLUMN_USAGES — the non-translated base table holding the physical and functional configuration of each descriptive flexfield column: application, flexfield name, context code, column names, sequence, flags, value set binding, defaults, and range information.
  • FND_DESCR_FLEX_COL_USAGE_TL — the translation table supplying the language-specific presentation attributes: FORM_LEFT_PROMPT, FORM_ABOVE_PROMPT, and DESCRIPTION.

The two are joined on the composite key APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, and APPLICATION_COLUMN_NAME, with the translation side additionally constrained by T.LANGUAGE = USERENV('LANG'). The view surfaces the base table's ROWID as ROW_ID.

Key Columns

  • APPLICATION_ID — the application owning the descriptive flexfield.
  • DESCRIPTIVE_FLEXFIELD_NAME — the internal DFF name (for example, a title or context-bearing flexfield identifier).
  • DESCRIPTIVE_FLEX_CONTEXT_CODE — the context/segment qualifier under which the column applies.
  • APPLICATION_COLUMN_NAME — the underlying database column (for example, ATTRIBUTE1…ATTRIBUTE15 or a descriptive column) that stores the segment value.
  • END_USER_COLUMN_NAME — the friendly segment name shown to the user.
  • COLUMN_SEQ_NUM — display and processing order of the segment.
  • ENABLED_FLAG, REQUIRED_FLAG, SECURITY_ENABLED_FLAG, DISPLAY_FLAG — control whether the segment is active, mandatory, subject to security, and visible at runtime.
  • DISPLAY_SIZE, MAXIMUM_DESCRIPTION_LEN, CONCATENATION_DESCRIPTION_LEN — sizing and concatenation controls for the displayed segment.
  • FLEX_VALUE_SET_ID, RANGE_CODE — the value set used to validate and constrain entered values, and the accepted range.
  • DEFAULT_TYPE, DEFAULT_VALUE — defaulting behavior applied to the segment.
  • FORM_LEFT_PROMPT, FORM_ABOVE_PROMPT, DESCRIPTION — translated prompt and descriptive text from the TL table.

Common Use Cases and Queries

Typical uses include documenting DFF configuration, mapping segment values to physical columns for reporting or data conversion, and auditing which value sets and flags govern a flexfield. A representative query lists all enabled segments for a given flexfield and context:

  • SELECT application_column_name, end_user_column_name, column_seq_num, required_flag, flex_value_set_id, form_left_prompt FROM fnd_descr_flex_col_usage_vl WHERE descriptive_flexfield_name = :p_flexfield AND descriptive_flex_context_code = :p_context AND enabled_flag = 'Y' ORDER BY column_seq_num;
  • To identify the physical storage column for a named segment: SELECT application_column_name FROM fnd_descr_flex_col_usage_vl WHERE descriptive_flexfield_name = :p_flexfield AND end_user_column_name = :p_segment;

Because the view is language-filtered, results reflect the prompt text for the session language, making it well suited to multilingual reporting without additional joins.