Search Results xla_accounting_class




Overview
Explore in AI Chat

Overview

The APPS.XLA_ACCT_CLASS_ASSGNS_F_V view is a documented Oracle E-Business Suite database object residing in the APPS schema. It presents accounting class assignments registered within the Subledger Accounting (XLA) architecture, providing a denormalized, reporting-friendly projection of the assignments that link subledger programs to specific accounting classes. The trailing _F_V naming convention indicates that this is a formulation view — a read-only, presentation-layer object intended for inquiry, reporting, and integration rather than for direct maintenance of transactional data.

In the context of the user search term xla_accounting_class, this view is the primary reporting surface for resolving the internal accounting class code stored against a program or assignment to its user-facing meaning. Rather than requiring report authors to join the base assignment table to the lookup view manually, the view performs that join internally, exposing a ready-to-use ACCOUNTING_CLASS_NAME column. Its role is therefore to simplify both out-of-the-box Oracle reports and custom BI Publisher, Oracle Reports, or OAF-based inquiries that need to present accounting class assignments in a readable form.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced objects:

  • XLA_ACCT_CLASS_ASSGNS — referenced as a SYNONYM. This is the base table holding the actual assignment rows, including the program, assignment, and accounting class codes together with standard WHO audit columns.
  • XLA_LOOKUPS — referenced as a VIEW. This is the lookup repository for the XLA_ACCOUNTING_CLASS lookup type, supplying the human-readable meaning for each accounting class code.

The join condition inside the view text restricts matches to rows where B.ACCOUNTING_CLASS_CODE = LKP.LOOKUP_CODE and LKP.LOOKUP_TYPE = 'XLA_ACCOUNTING_CLASS'. This guarantees that only valid accounting class lookup values are joined, and it scopes the lookup resolution to the correct lookup type so that codes sharing a value with other lookup types are not incorrectly matched. Because the view is a simple two-object join over a synonym and a lookup view, it inherits the underlying XLA data model and reflects changes in assignments as soon as they are committed.

Key Columns

The view projects the following columns, preserving the source column names (with the ROWID exposed as ROW_ID):

  • ROW_ID — the ROWID of the base assignment row, useful as a unique identifier for the returned record.
  • PROGRAM_CODE / PROGRAM_OWNER_CODE — identify the subledger program (and its owning application) to which the accounting class assignment applies.
  • ASSIGNMENT_CODE / ASSIGNMENT_OWNER_CODE — identify the specific assignment and its owning application, allowing the same program to carry different class assignments.
  • ACCOUNTING_CLASS_CODE — the internal code of the accounting class (for example, the code stored against the assignment).
  • ACCOUNTING_CLASS_NAME — the lookup MEANING resolved from XLA_LOOKUPS for the code, providing the displayed, user-readable class name.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns carried through from the base table.

Common Use Cases and Queries

Typical usages include validating which accounting class is assigned to a given program or assignment, building reports that must show the accounting class name rather than the raw code, and integration extracts that require a flattened assignment-to-class listing. A straightforward query filtering by program is shown below:

  • SELECT accounting_class_code, accounting_class_name, program_code, program_owner_code, assignment_code FROM apps.xla_acct_class_assgns_f_v WHERE program_code = :program_code ORDER BY assignment_code;
  • SELECT accounting_class_name, COUNT(*) FROM apps.xla_acct_class_assgns_f_v GROUP BY accounting_class_name ORDER BY 2 DESC;
  • SELECT f.program_code, f.assignment_code, f.accounting_class_name, f.last_update_date FROM apps.xla_acct_class_assgns_f_v f WHERE f.accounting_class_code = :class_code;

Because the object is a view, it must be queried rather than modified; all maintenance is performed against the underlying XLA_ACCT_CLASS_ASSGNS table through supported XLA setup or programmatic interfaces. In both 12.1.1 and 12.2.2, the view's definition and column semantics are consistent, making it a stable reference point for subledger accounting class reporting across these releases.