Search Results xla_assignment_defns_tl_u1

Overview

The XLA.XLA_ASSIGNMENT_DEFNS_TL table is the translation (TL) companion to the base XLA_ASSIGNMENT_DEFNS_B table within the Oracle Subledger Accounting (XLA) module of Oracle E-Business Suite. It stores the language-dependent, translated attributes for accounting class ledger assignment definitions — the configuration records that determine how subledger transactions are mapped to accounting method rules and ultimately to ledger accounts. Each row pairs a language-independent assignment definition with a specific LANGUAGE value, supplying the human-readable NAME that end users see in the Subledger Accounting setup user interface.

The object resides in the XLA schema, uses the APPS_TS_TX_DATA tablespace, and is classified as VALID in the ETRM 12.2.2 physical schema. Its heuristic Data Vault classification, mined from the foreign-key structure, is standalone. From a dimensional-modeling perspective this suggests the table behaves as a descriptive satellite-like object: it carries no outward foreign keys and is owned entirely by its parent definition, keyed by the combination of assignment identity plus language rather than by independent business relationships.

Key Information Stored

The table contains thirteen documented columns. The most significant are the identity and descriptive columns that form the composite business keys.

• PROGRAM_OWNER_CODE and PROGRAM_CODE — the owner indicator (S for Oracle seed data, C for customer-defined) and the language-independent program code identifying the owning subledger program.
• ASSIGNMENT_OWNER_CODE and ASSIGNMENT_CODE — the corresponding owner indicator and language-independent code for the accounting assignment definition.
• NAME — the translated program name displayed to users, populated per language.
• LANGUAGE and SOURCE_LANG — the standard language code of the translation and the source language from which it was derived.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — providing audit lineage back to FND_USER and FND_LOGINS.
• ZD_EDITION_NAME — the editioning column supporting Online Patching and cross-edition read consistency in EBS 12.2.

The primary key, XLA_ASSIGNMENT_DEFNS_TL_PK, spans PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE, and LANGUAGE. Two unique indexes refine this. XLA_ASSIGNMENT_DEFNS_TL_U1 adds ZD_EDITION_NAME to the primary-key columns, while XLA_ASSIGNMENT_DEFNS_TL_U2 — the index referenced by the search term xla_assignment_defns_tl_u2 — enforces uniqueness on PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, NAME, LANGUAGE, and ZD_EDITION_NAME. This guarantees that within a given program and language, no two assignments share the same displayed name.

Common Use Cases and Queries

The table is most often queried to resolve a language-independent ASSIGNMENT_CODE into a user-facing name, or to report on configured assignment definitions in a single language. A typical lookup joins the translated name for a target language:

• SELECT assignment_code, name FROM xla.xla_assignment_defns_tl WHERE language = 'US' AND program_owner_code = 'S';
• Joining to the base table XLA_ASSIGNMENT_DEFNS_B on the four owner/code columns to combine language-independent attributes with the translated NAME.
• Validating translation completeness by comparing LANGUAGE counts against the base table's row count per assignment.
• Diagnosing unique-index violations on XLA_ASSIGNMENT_DEFNS_TL_U2, which typically indicate duplicate NAME values introduced during setup or data migration.

Related Objects

The table has no documented foreign keys to external objects, but its logical integrity and reporting context depend on the following:

• XLA_ASSIGNMENT_DEFNS_B — the base table supplying the non-translated columns; joins on PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, and ASSIGNMENT_CODE.
• XLA_ASSIGNMENTS — the parent assignment configuration referenced by the assignment codes.
• XLA_LEDGER_OPTIONS and XLA_ACCOUNTING_PROGRAMS — related setup governing how assignments drive accounting.
• FND_USER and FND_LOGINS — referenced by the WHO columns for audit reporting.
• FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG values.