Search Results mpa_header_desc_owner

Overview

XLA_LINE_DEFN_JLT_ASSGNS_F_V is a formatted (denormalized) view in the APPS schema belonging to the XLA — Subledger Accounting product family. It presents the configuration of journal line definition assignments for the "Joint Line Type" (JLT) construct used within Subledger Accounting's accounting program infrastructure. The underlying table, XLA_LINE_DEFN_JLT_ASSGNS, stores the mapping between an application's accounting line types and their descriptive attributes, and this view enriches those rows with translated names, lookup meanings, and natural-side information. Because Subledger Accounting is the engine that transforms subledger transactions into journal entries, this view is central to understanding how individual accounting lines are built and described during journal creation. The user's search term "mpa_option_code" maps directly to the MPA_OPTION_CODE column exposed by this view; that column is sourced from XLA_ACCT_LINE_TYPES_B and represents the Multi-Period Accounting (MPA) option applicable to the accounting line type — that is, the setting governing how the line behaves across accounting periods (for example, whether it supports period-end accrual, deferral, or reversal processing).

Underlying Base Objects

The view is defined over the following documented objects:

• XLA_LINE_DEFN_JLT_ASSGNS — the driving base table containing one row per joint line type assignment, providing the AMB context, application, event class/type, line definition code, accounting line code, description codes, active flag, and the MPA-related columns.
• XLA_ACCT_LINE_TYPES_B — the base table for accounting line types, supplying NATURAL_SIDE_CODE and MPA_OPTION_CODE.
• XLA_ACCT_LINE_TYPES_TL — the translated (language) table for accounting line types, supplying the NAME column rendered as ACCOUNTING_LINE_NAME.
• XLA_DESCRIPTIONS_TL — the translated descriptions table, joined twice (XDT and XDT2) to supply description and MPA header description names.
• XLA_LOOKUPS — an APPS view over lookup types/codes, joined three times (LK, LK2, LK3) against lookup type 'XLA_OWNER_TYPE' to resolve owner meanings for the accounting line type, the description type, and the MPA header description type.

Outer joins (+) are applied to the description and owner-type lookups so that assignments without a matching description or owner still return a row.

Key Columns

• AMB_CONTEXT_CODE, APPLICATION_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE — identify the subledger accounting context and the event the line definition serves.
• LINE_DEFINITION_OWNER_CODE / LINE_DEFINITION_CODE — identify the parent line definition; together with the accounting line code they scope the assignment.
• ACCOUNTING_LINE_CODE, ACCOUNTING_LINE_NAME, ACCOUNTING_LINE_TYPE_CODE, ACCOUNTING_LINE_OWNER — describe the accounting line and its owner (resolved via XLA_LOOKUPS).
• DESCRIPTION_CODE, DESCRIPTION_TYPE_CODE, DESCRIPTION_NAME, DESCRIPTION_OWNER — the description assignment and its translated name.
• MPA_NUM_JE_CODE, MPA_GL_DATES_CODE, MPA_PRORATION_CODE, MPA_HEADER_DESC_CODE — Multi-Period Accounting control settings for the assignment.
• MPA_OPTION_CODE — the MPA option from the accounting line type, the value most commonly searched by implementers.
• MPA_HEADER_DESC_NAME, MPA_HEADER_DESC_TYPE_CODE, MPA_HEADER_DESC_OWNER — the MPA header description and its owner meaning.
• NATURAL_SIDE_CODE, INHERIT_DESC_FLAG, ACTIVE_FLAG — natural side (debit/credit), description inheritance, and enablement flag.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns; OBJECT_VERSION_NUMBER supports optimistic locking.

Common Use Cases and Queries

Typical uses include reporting the line-definition configuration for a subledger, tracing MPA_OPTION_CODE back to its accounting line type, and auditing owner/description lookups. A sample query listing assignments with their MPA option is:

• SELECT line_definition_code, accounting_line_code, accounting_line_name, mpa_option_code, natural_side_code, active_flag FROM xla_line_defn_jlt_assgns_f_v WHERE application_id = :p_app AND event_class_code = :p_ec ORDER BY line_definition_code, accounting_line_code;
• SELECT accounting_line_code, mpa_num_je_code, mpa_gl_dates_code, mpa_proration_code, mpa_header_desc_name FROM xla_line_defn_jlt_assgns_f_v WHERE active_flag = 'Y' AND mpa_option_code IS NOT NULL;
• SELECT mpa_option_code, COUNT(*) FROM xla_line_defn_jlt_assgns_f_v GROUP BY mpa_option_code;

Because the view resolves translated names and lookup meanings using USERENV('LANG'), results reflect the session language. It is well suited to configuration validation and to integration extracts that must present accounting line definitions in human-readable form.