Results for “xla_analytical_dtls_vl”

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

Overview

XLA_ANALYTICAL_DTLS_VL is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes analytical detail definitions that drive the Subledger Accounting analytical criteria engine. Analytical criteria allow subledger transactions to be selected and grouped for accounting rule application, and each criterion is composed of one or more analytical details that reference transaction attributes or flexfield segments. This view provides the translatable, language-aware presentation layer for those detail definitions.

The "_VL" suffix indicates a "view with language" object. The view joins the base definition table, XLA_ANALYTICAL_DTLS_B, to its translation table, XLA_ANALYTICAL_DTLS_TL, returning the NAME and DESCRIPTION values appropriate to the session language. This makes the view suitable for reporting, integration extracts, and LOV (list of values) population where human-readable labels are required alongside the technical detail codes. It is the query layer typically used by forms, concurrent programs, and custom reports that must present analytical detail metadata to end users.

Underlying Base Objects

The view is defined over two synonym objects registered in ETRM: XLA_ANALYTICAL_DTLS_B and XLA_ANALYTICAL_DTLS_TL. XLA_ANALYTICAL_DTLS_B holds the language-independent definition rows, while XLA_ANALYTICAL_DTLS_TL holds the translated NAME and DESCRIPTION for each supported language. The join correlates rows on four key columns so that a single logical detail resolves to exactly one translation row per language:

• ANALYTICAL_CRITERION_CODE equals ANALYTICAL_CRITERION_CODE
• ANALYTICAL_CRITERION_TYPE_CODE equals ANALYTICAL_CRITERION_TYPE_CODE
• AMB_CONTEXT_CODE equals AMB_CONTEXT_CODE
• ANALYTICAL_DETAIL_CODE equals ANALYTICAL_DETAIL_CODE

The translation side is additionally filtered by T.LANGUAGE = USERENV('LANG'), so the view returns only the row matching the caller's language environment. The view also carries B.ROWID as ROW_ID, which preserves a row identifier for downstream processing. Because all columns except NAME and DESCRIPTION originate from the _B table, the view is effectively a read-only, language-resolved projection of the base definition.

Key Columns

• ROW_ID — the ROWID of the base definition row (B.ROWID), used as a stable identifier for the detail.
• ANALYTICAL_CRITERION_CODE / ANALYTICAL_CRITERION_TYPE_CODE — identify the analytical criterion to which the detail belongs. Both are required for correct correlation against headers and translations.
• ANALYTICAL_DETAIL_CODE — the technical identifier of the individual analytical detail.
• AMB_CONTEXT_CODE — the Application Matching/Attribute context code scoping the detail, forming part of the composite key.
• GROUPING_ORDER — sort order used when grouping analytical details within a criterion.
• VIEW_COLUMN_NUM — the ordinal position of the column the detail maps to in the analytical criteria view. This is the column users frequently search for as "view_column_num"; it dictates placement of the detail in the generated analytical view output and is significant when diagnosing column alignment in analytical criteria extraction.
• DATA_TYPE_CODE — indicates the datatype of the underlying analytical detail value.
• NAME / DESCRIPTION — the language-resolved label and description from XLA_ANALYTICAL_DTLS_TL.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, inherited from the base table.

Common Use Cases and Queries

Typical uses include reporting the analytical details attached to a given criterion, ordering details by their view column position, and populating selection lists with translated names. A representative query resolves all details for a criterion:

• SELECT analytical_criterion_code, analytical_detail_code, view_column_num, grouping_order, data_type_code, name FROM xla_analytical_dtls_vl WHERE analytical_criterion_code = :criterion ORDER BY grouping_order;
• SELECT analytical_detail_code, view_column_num, name FROM xla_analytical_dtls_vl WHERE view_column_num IS NOT NULL ORDER BY view_column_num; — to diagnose view column mapping.
• SELECT b.analytical_detail_code, c.name, b.grouping_order FROM xla_analytical_dtls_vl b, xla_analytical_criteria_vl c WHERE b.analytical_criterion_code = c.analytical_criterion_code; — joining to the criterion-level view for a full picture.

Because the view enforces language resolution internally, callers need not join translations directly, and results reflect the session's NLS language automatically.