Search Results xla_acct_class_assgns




Overview
Explore in AI Chat

Overview

XLA_ACCT_CLASS_ASSGNS is a Subledger Accounting (XLA) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the accounting class assignments associated with Post-Accounting Programs, which are the concurrent programs that transfer subledger journal entries from the XLA repository into the General Ledger interface tables. By mapping an accounting class to a program and assignment combination, the table determines which accounting classes a given post-accounting program will process, and under which assignment context it operates. This is a low-volume, setup-oriented table rather than a transactional one; it is populated when Subledger Accounting application configurations are defined and is referenced repeatedly at runtime as post-accounting jobs execute.

Based on the foreign-key and key structure mined from the ETRM metadata, the object is standalone with no outbound foreign keys. As a heuristic Data Vault modeling suggestion, it is best characterized as a satellite-like reference table whose natural business key is the composite of program and assignment plus accounting class; it holds descriptive assignment context rather than acting as a transactional hub or a pure relationship link.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 11 columns. The most significant are:

The surrogate primary key is XLA_ACCT_CLASS_ASSGNS_PK, defined over PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE, and ACCOUNTING_CLASS_CODE. A separate unique index, XLA_ACCT_CLASS_ASSGNS_U1, extends the same five columns with ZD_EDITION_NAME, making it the stronger business-key candidate when edition-aware uniqueness is required. The overlap between the two keys means the primary key alone does not guarantee edition-level uniqueness.

Common Use Cases and Queries

Typical uses include validating that a post-accounting program is mapped to the expected accounting classes before running a posting job, diagnosing why an accounting class is not being posted, and extracting setup documentation for audit or migration. A representative query joins the assignments to the accounting classes for a given program:

  • SELECT program_owner_code, program_code, assignment_code, accounting_class_code FROM xla_acct_class_assgns WHERE program_code = :p_program AND zd_edition_name = :p_edition;
  • Count distinct accounting classes per assignment to confirm complete coverage: SELECT assignment_owner_code, assignment_code, COUNT(DISTINCT accounting_class_code) FROM xla_acct_class_assgns GROUP BY assignment_owner_code, assignment_code;
  • Reconcile configuration between environments by comparing rows keyed on PROGRAM_OWNER_CODE, PROGRAM_CODE, ASSIGNMENT_OWNER_CODE, ASSIGNMENT_CODE, and ACCOUNTING_CLASS_CODE.

Because the table is small, queries are inexpensive, but filtering on ZD_EDITION_NAME is advisable in 12.2.x to avoid mixing editions during comparisons.

Related Objects

The metadata describes XLA_ACCT_CLASS_ASSGNS as standalone, so no outbound foreign keys are documented. In practice it is referenced alongside the following XLA configuration and processing objects, joined on the columns shown:

Administrators should treat this table as configuration data, modifying it through the Subledger Accounting setup UI rather than by direct DML, to preserve the integrity of the composite primary and unique keys.