Results for “source_id_flex_code”

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

Overview

XLA_DESCRIPT_DETAILS_FVL is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Subledger Accounting (XLA) product. It exposes description detail setup used by Subledger Accounting to control how journal line descriptions are derived and displayed. The "FVL" suffix indicates it is a flexfield-value view that joins translatable description detail definitions to their language-specific text and, where applicable, to the source definitions held in XLA_SOURCES_VL. In EBS 12.1.1 and 12.2.2 this view serves as a reporting and integration surface for examining the description rules configured for subledger journal entries.

The view is particularly relevant when investigating VALUE_TYPE_CODE, since that column determines whether a given description detail derives its value from a source, from a literal text string, or from a flexfield segment. Because the view resolves both the language-specific literal and the source-level attributes in a single row, it is the preferred access point for diagnostics and extracts rather than querying the base tables individually.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced objects:

• XLA_DESCRIPT_DETAILS_B (SYNONYM) — the base table holding description detail definitions, including sequence, value type, source identifiers, and audit columns.
• XLA_DESCRIPT_DETAILS_TL (SYNONYM) — the translatable table supplying the LITERAL text for the current session language.
• XLA_SOURCES_VL (VIEW) — the source definition view supplying source name, datatype, flexfield application, structure code, and segment code.

The join is driven from XLA_DESCRIPT_DETAILS_B, outer-joined to XLA_SOURCES_VL on SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE, and inner-joined to XLA_DESCRIPT_DETAILS_TL on DESCRIPTION_DETAIL_ID with the language restricted to USERENV('LANG'). The outer join to the sources view permits rows whose value type does not reference a source, such as literal or flexfield segment entries, to remain visible.

Key Columns

• DESCRIPTION_DETAIL_ID — primary identifier of the description detail.
• DESCRIPTION_PRIO_ID — the description priority (rule set) to which the detail belongs.
• AMB_CONTEXT_CODE — the application message builder context associated with the detail.
• USER_SEQUENCE — ordering of the detail within its description rule.
• VALUE_TYPE_CODE — indicates the derivation method for the value; this governs whether SOURCE_* or LITERAL or FLEXFIELD_SEGMENT_CODE is meaningful.
• SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE — the source definition keys, resolved to SOURCE_NAME and SOURCE_DATATYPE_CODE through XLA_SOURCES_VL.
• SOURCE_FLEX_APPL_ID, SOURCE_ID_FLEX_CODE, SOURCE_SEGMENT_CODE — key flexfield information for source-based values.
• LITERAL — the language-specific text when the value type is literal.
• FLEXFIELD_SEGMENT_CODE, DISPLAY_DESCRIPTION_FLAG — flexfield segment reference and display control.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ROW_ID.

Common Use Cases and Queries

Typical uses include auditing description rule configuration, tracing why a journal line description resolved to a particular value, and extracting description setup for documentation or migration.

• Listing all literal-based details for a priority:
  SELECT d.description_detail_id, d.user_sequence, d.literal FROM xla_descript_details_fvl d WHERE d.value_type_code = 'LITERAL' AND d.description_prio_id = :prio_id ORDER BY d.user_sequence;
• Reviewing source-backed details with their names:
  SELECT d.description_detail_id, d.source_name, d.source_datatype_code FROM xla_descript_details_fvl d WHERE d.value_type_code = 'SOURCE';
• Locating a detail by its sequence within a rule set, and confirming the resolved language literal via USERENV('LANG').

Because the view already resolves the translatable literal and the source attributes, queries against it avoid the manual joins otherwise required across the three underlying objects. Access is granted through the APPS schema, and the view inherits standard EBS multi-language behavior through USERENV('LANG').