Results for “xla_assignment_defns_vl”

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

Overview

XLA_ASSIGNMENT_DEFNS_VL is a language-dependent (MLS) view owned by the APPS schema in Oracle E-Business Suite, defined within the XLA – Subledger Accounting product family. It exposes the definition of subledger accounting assignments, which determine how accounting rules are applied to transactions for a given ledger and application. The view is the user-facing, translated representation of assignment definitions; it joins the transactional base table (XLA_ASSIGNMENT_DEFNS_B) to the translation table (XLA_ASSIGNMENT_DEFNS_TL) and returns only the row whose LANGUAGE matches the session language via USERENV('LANG').

Because assignment definitions drive which accounting method and rule set are used for a subledger program, this view is the canonical reporting and integration layer for querying configured assignments. Reporting tools, concurrent programs, and custom interfaces reference the VL view rather than the underlying _B and _TL tables so that translated names are returned automatically and so that language handling is delegated to the view. The object status is VALID, confirming it is a supported, compiled view in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• XLA_ASSIGNMENT_DEFNS_B — the base table holding language-independent assignment data, including the program code, owner codes, assignment code, ledger, and enabled flag.
• XLA_ASSIGNMENT_DEFNS_TL — the translation table providing the NAME column per language.

The join is performed on the composite key of PROGRAM_CODE, PROGRAM_OWNER_CODE, ASSIGNMENT_CODE, and ASSIGNMENT_OWNER_CODE, with an additional predicate restricting T.LANGUAGE to the current session language. This means one row from the base table produces exactly one view row for the session language, provided a translation exists. The view also projects B.ROWID as ROW_ID, providing a stable row identifier for the base record.

Key Columns

• ROW_ID — ROWID of the underlying XLA_ASSIGNMENT_DEFNS_B row.
• PROGRAM_CODE / PROGRAM_OWNER_CODE — identify the subledger program and its owning application to which the assignment applies.
• ASSIGNMENT_CODE / ASSIGNMENT_OWNER_CODE — identify the assignment itself and its owning application; together with the program columns these form the composite key.
• LEDGER_ID — the ledger for which the assignment definition is configured.
• ENABLED_FLAG — indicates whether the assignment definition is active.
• NAME — the translated, user-visible name of the assignment, sourced from the _TL table.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, sourced from the base table.

Common Use Cases and Queries

Typical uses include verifying which assignments are configured for a ledger, driving downstream reporting on accounting configuration, and diagnosing why a subledger program is not applying expected rules. A basic query listing all enabled assignments with their translated names:

• SELECT assignment_code, name, ledger_id, enabled_flag FROM xla_assignment_defns_vl WHERE enabled_flag = 'Y';
• SELECT program_code, assignment_code, name FROM xla_assignment_defns_vl WHERE ledger_id = :ledger_id;
• SELECT b.assignment_code, t.name FROM xla_assignment_defns_vl t, xla_assignment_defns_b b WHERE ... — used when base-table attributes beyond those exposed by the view are required.

Note that the VL view is the preferred query point for translated output; direct queries against XLA_ASSIGNMENT_DEFNS_B bypass language handling and are appropriate only when translation is not required.