Search Results xla_assignment_defns_b_pk

Overview

XLA_ASSIGNMENT_DEFNS_B is a Subledger Accounting (XLA) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the ledger assignments that determine which accounting ledgers are processed by Post-Accounting Programs within the Subledger Accounting architecture. Each row binds a program (identified by PROGRAM_OWNER_CODE and PROGRAM_CODE) to an assignment definition (identified by ASSIGNMENT_OWNER_CODE and ASSIGNMENT_CODE) and, critically, to a specific LEDGER_ID. This binding controls the scope of accounting processing, ensuring that post-accounting programs execute against the correct ledger and that accounting entries are generated and transferred only for the ledgers explicitly assigned to the program.

The table resides in the XLA schema and, in the ETRM 12.2.2 documented physical schema, contains 12 columns. The metadata classifies the object as standalone under the heuristic Data Vault model, meaning it behaves as an independent reference/configuration entity rather than a dependent satellite or an associative link. In Data Vault terms, it is best modeled as a reference hub combined with descriptive attributes (LEDGER_ID, ENABLED_FLAG), reflecting that ledger assignments are maintained as discrete configuration records rather than transactional events.

Key Information Stored

Each record represents a single ledger assignment for a post-accounting program. The most significant columns are:

• PROGRAM_OWNER_CODE — identifies the application or product that owns the post-accounting program (for example, the subledger application identifier).
• PROGRAM_CODE — the specific post-accounting program being assigned.
• ASSIGNMENT_OWNER_CODE — the owner of the assignment definition; together with ASSIGNMENT_CODE, it forms the business identifier of the assignment.
• ASSIGNMENT_CODE — the assignment definition identifier linked to the program.
• LEDGER_ID — the accounting ledger to which the program assignment applies; this is the core business value driving processing scope.
• ENABLED_FLAG — indicates whether the ledger assignment is active (Y) or inactive (N).
• ZD_EDITION_NAME — the edition identifier used by the Subledger Accounting editioning model (relevant in 12.2.x).
• CREATION_DATE, CREATED_BY — audit columns capturing record creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification.

The surrogate primary key is defined by XLA_ASSIGNMENT_DEFNS_B_PK over (PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE). The unique index XLA_ASSIGNMENT_DEFNS_B_U1 extends this with ZD_EDITION_NAME — (PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE, ZD_EDITION_NAME) — confirming that the edition is part of the business-key candidate for 12.2.x editioned data.

Common Use Cases and Queries

Typical use cases include diagnosing why a subledger's accounting program is or is not processing a given ledger, auditing ledger-to-program assignments, and validating configuration after cloning or patching. A common diagnostic query joins the assignment to the ledger:

• SELECT a.assignment_code, a.program_owner_code, a.program_code, a.ledger_id, a.enabled_flag FROM xla_assignment_defns_b a WHERE a.program_code = :program AND a.ledger_id = :ledger_id;
• Reporting all active ledger assignments: filter WHERE enabled_flag = 'Y'.
• Reconciliation of editioned records: include ZD_EDITION_NAME in the WHERE clause to isolate the correct run edition.
• Join to GL_LEDGERS on LEDGER_ID to display ledger name, chart of accounts, and currency alongside each assignment.

This table is primarily a read/reference object; changes are normally performed through the Subledger Accounting setup UI rather than direct DML.

Related Objects

Because the metadata identifies the table as standalone, it has few enforced foreign keys, but it is functionally referenced by related XLA and GL objects. Key relationships include:

• XLA_ASSIGNMENT_DEFNS_TL — the translated-name counterpart keyed by the same primary key columns.
• GL_LEDGERS — joined via LEDGER_ID to resolve ledger attributes.
• XLA_ACCOUNTING_PROGRAMS / program definition objects — joined via PROGRAM_OWNER_CODE and PROGRAM_CODE.
• XLA_ASSIGNMENT_DEFNS_VL — the view combining base and translated assignment data.
• GL_LEDGER_CONFIGURATIONS — for validating active ledger configuration status.

These joins allow administrators to trace ledger assignments back to their accounting programs and forward to the ledgers they affect.