Search Results xla_assignment_defns_b_u1

Overview

The XLA.XLA_ASSIGNMENT_DEFNS_B table is a core Subledger Accounting (SLA) definition object within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the ledger assignments for Post-Accounting Programs, which are the executable routines that generate and transfer subledger journal entries into the General Ledger. In practical terms, this table defines which accounting program is bound to which ledger, and whether that assignment is currently active. It acts as the configuration bridge between an accounting method's program definition and a specific target ledger, ensuring that posting and transfer processes only execute against the correct books. The table resides in the APPS_TS_TX_DATA tablespace and is owned by the XLA schema, which is the standard product schema for Subledger Accounting and the SLA data model.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone, meaning it does not participate in a documented hub, link, or satellite hierarchy through foreign key relationships. It can therefore be modeled as a simple configurational reference table rather than a transactional fact or a formal Data Vault hub.

Key Information Stored

The table defines assignment records through four business-key columns that are also the composite primary key XLA_ASSIGNMENT_DEFNS_B_PK: PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, and ASSIGNMENT_CODE. The owner code columns use S for Oracle-seeded definitions and C for user-defined (custom) definitions, providing a clear separation between delivered and customer-maintained content. The program and assignment code columns are each stored in a language-independent format to support multilingual deployments.

The LEDGER_ID column ties each assignment to a specific ledger via its internal identifier, while ENABLED_FLAG controls whether the assignment definition is active, using standard Y/N values. Together these two columns determine, at runtime, whether a given accounting program is bound to a given ledger and available for execution.

The remaining columns are standard Oracle "Who" audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support audit tracking and reference FND_USER and FND_LOGINS. The unique index XLA_ASSIGNMENT_DEFNS_B_U1 extends the primary key with ZD_EDITION_NAME, which is the editioning column used for Online Patching (ADOP) in Release 12.2.2, allowing the same logical row to exist across multiple editions during patch cycles.

Common Use Cases and Queries

The most frequent operational use is verifying which accounting programs are assigned to a given ledger. Administrators and support analysts query by ledger to confirm the assignment is active before troubleshooting posting failures:

• Listing active assignments for a ledger: SELECT PROGRAM_CODE, ASSIGNMENT_CODE, ENABLED_FLAG FROM XLA.XLA_ASSIGNMENT_DEFNS_B WHERE LEDGER_ID = :ledger AND ENABLED_FLAG = 'Y';
• Isolating user-defined versus Oracle-seeded definitions: filter where PROGRAM_OWNER_CODE = 'C' or ASSIGNMENT_OWNER_CODE = 'C'.
• Audit reporting using the Who columns to identify who changed an assignment and when.
• Migrating SLAM (Subledger Accounting Method) configurations between environments by extracting assignment definitions for a target ledger.

Because posting and transfer programs depend on these assignments, disabled flags are a common root cause when subledger journals fail to reach General Ledger.

Related Objects

Although the metadata records this object as standalone, in the broader SLA schema it is referenced by program definition and ledger configuration objects. The most significant related objects include:

• XLA.XLA_PROGRAM_DEFNS_B and its translation table XLA_PROGRAM_DEFNS_TL — joined on PROGRAM_OWNER_CODE and PROGRAM_CODE.
• XLA.XLA_ASSIGNMENT_DEFNS_TL — the translated description table sharing the assignment key columns.
• XLA.XLA_LEDGERS / GL_LEDGERS — joined via LEDGER_ID.
• XLA.XLA_ACCOUNTING_PROGRAMS — the runtime program registry that consumes assignment definitions.
• FND_USER and FND_LOGINS — referenced by the Who columns.

These relationships allow reporting that traces each ledger assignment back to its program definition, translated name, and the user who configured it.