Search Results xla_assignment_defns_tl_pk

Overview

XLA_ASSIGNMENT_DEFNS_TL is the translation (TL) table for accounting class ledger assignments in the Oracle Subledger Accounting (XLA) module of Oracle E-Business Suite. It stores the language-dependent descriptive columns — principally the user-visible Name of an assignment definition — for the base table XLA_ASSIGNMENT_DEFNS_B. In Oracle EBS 12.1.1 and 12.2.2, each Subledger Accounting method, application accounting definition, and accounting class can be associated with a specific ledger through an assignment definition; this table holds the multilingual text that labels those assignments so they can be presented to users in their session language.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone — no foreign key dependencies are mined from the schema. That classification suggests the table functions as a self-contained code/description reference rather than a true hub, link, or satellite in a normalized Data Vault model.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• PROGRAM_OWNER_CODE and PROGRAM_CODE — identify the owning program (for example, the application product and program that generated the assignment definition).
• ASSIGNMENT_OWNER_CODE and ASSIGNMENT_CODE — uniquely identify the specific accounting class ledger assignment to which the translation belongs.
• NAME — the translated, user-visible name of the assignment definition; this is the primary descriptive text stored in this TL table.
• LANGUAGE — the NLS language code (for example, US for American English) in which the NAME value is expressed.
• SOURCE_LANG — indicates the source (base) language of the row, used by the multilingual translation framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns capturing audit trail information.
• ZD_EDITION_NAME — the edition identifier used by Oracle's edition-based redefinition (EBR) infrastructure introduced in 12.2, enabling online patching.

The surrogate/business primary key is XLA_ASSIGNMENT_DEFNS_TL_PK, composed of (PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE, LANGUAGE). Two additional unique indexes act as business-key candidates: XLA_ASSIGNMENT_DEFNS_TL_U1 extends the primary key with ZD_EDITION_NAME, while XLA_ASSIGNMENT_DEFNS_TL_U2 substitutes NAME for ASSIGNMENT_CODE, enforcing uniqueness of the translated name per assignment and language.

Common Use Cases and Queries

Typical scenarios include building multilingual reports that display assignment definition names in the user's native language, and joining the TL table to its base table to retrieve both descriptive and operational attributes.

A common pattern retrieves a translated name for a given assignment:

• SELECT tl.name, tl.language FROM xla_assignment_defns_tl tl WHERE tl.program_owner_code = :poc AND tl.program_code = :pc AND tl.assignment_owner_code = :aoc AND tl.assignment_code = :ac AND tl.language = USERENV('LANG');
• Join to XLA_ASSIGNMENT_DEFNS_B on the four assignment key columns plus LANGUAGE to combine descriptive and functional fields.
• Report available translations by selecting DISTINCT language values for an assignment to audit localization coverage.

Because 12.2 uses edition-based redefinition, reporting queries should generally filter or rely on ZD_EDITION_NAME being resolved to the current run edition by the database.

Related Objects

The most significant related objects include:

• XLA_ASSIGNMENT_DEFNS_B — the base (non-translated) table sharing the same key columns and supplying functional attributes.
• XLA_ASSIGNMENT_DEFNS_VL — the multilingual view that unions the base and translated tables, commonly used by forms and reports.
• XLA_ACCT_CLASS_ASSGNS — associates accounting classes with ledger assignments and typically joins on the assignment key columns.
• XLA_LEDGERS and XLA_LEDGER_RELATIONSHIPS — define the ledgers and relationships the assignments target.
• FND_LANGUAGES — provides the valid LANGUAGE codes referenced by the TL table.
• FND_APPLICATION — maps PROGRAM_OWNER_CODE and ASSIGNMENT_OWNER_CODE to application names.

These joins let developers navigate from a translated assignment name outward to the ledgers, accounting classes, and applications it governs.