Search Results xla_je_categories




Overview
Explore in AI Chat

Overview

XLA_JE_CATEGORIES is a Subledger Accounting (XLA) reference table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the journal category assignments used when Subledger Accounting generates journal entries. Each row maps a specific event class within a given application to a journal category name, scoped to a particular ledger. In this way the table controls how subledger transactions are classified and reported at the general ledger level, ensuring that accounting events originating from Payables, Receivables, Assets, or other source applications carry the correct GL journal category.

The table resides in the XLA schema and is documented as a standalone object. Under the heuristic Data Vault classification supplied in the ETRM metadata, it is modeled as a standalone structure rather than a hub, link, or satellite. This reflects the fact that it is a configuration/setup table with a composite primary key rather than a transactional entity participating in a formal hub-and-spoke relationship graph. Note that this classification is a modeling suggestion; the physical implementation remains a standard Oracle RDBMS table.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • APPLICATION_ID — identifies the source application (for example, Payables or Receivables) that owns the accounting event. Part of the composite primary key.
  • LEDGER_ID — the ledger for which the journal category mapping applies. Part of the composite primary key.
  • ENTITY_CODE — the entity/event entity that further qualifies the mapping. Part of the composite primary key.
  • EVENT_CLASS_CODE — the event class (such as INVOICE or PAYMENT) to which the journal category is bound. This column participates in the unique business key but not in the primary key.
  • JE_CATEGORY_NAME — the journal category name that is passed through to the generated accounting entries.
  • PROCESSING_UNIT_SIZE — controls the batch size used when processing journal entries for this category.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The surrogate primary key is XLA_JE_CATEGORIES_PK, defined on (APPLICATION_ID, LEDGER_ID, ENTITY_CODE). The business-key candidate is the unique index XLA_JE_CATEGORIES_U1, defined on (APPLICATION_ID, LEDGER_ID, ENTITY_CODE, EVENT_CLASS_CODE), which enforces that a given application, ledger, entity, and event class combination yields exactly one journal category.

Common Use Cases and Queries

Typical uses include diagnosing why a subledger transaction was assigned a particular journal category, validating Subledger Accounting setup, and reporting on category assignments per ledger. Because the table is small and configuration-oriented, it is normally joined to event class and application reference views.

  • Determine the journal category configured for Payables invoices in a ledger: 
    SELECT je_category_name
FROM   xla_je_categories
WHERE  application_id = 200
AND    ledger_id      = :ledger_id
AND    entity_code    = :entity_code
AND    event_class_code = 'INVOICE';
  • List all categories configured for a ledger, joined to FND_APPLICATION for readability.
  • Reconcile the presence of rows against Subledger Accounting Accounting Methods.
  • Validate uniqueness when copying setup between ledgers.

Related Objects

  • XLA_EVENT_CLASSES — join on APPLICATION_ID and EVENT_CLASS_CODE to resolve event class descriptions.
  • XLA_ACCOUNTING_METHODS — defines the accounting method that consumes journal categories.
  • XLA_JE_CATEGORIES_TL / _VL — translated and view-layer representations where available.
  • GL_JE_CATEGORIES — the GL journal categories referenced by JE_CATEGORY_NAME.
  • FND_APPLICATION — resolves APPLICATION_ID to the source product short name.
  • XLA_ACCOUNTING_EVENTS — the transactions ultimately classified using these categories.