Results for “xla_diag_ledgers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_DIAG_LEDGERS is a Subledger Accounting (XLA) repository table that records the ledgers processed by the Oracle E-Business Suite Subledger Accounting diagnostic framework. The diagnostic framework is used to validate, troubleshoot, and reconcile subledger accounting configurations and generated journal entries across one or more ledgers. Each row in XLA_DIAG_LEDGERS represents a specific ledger context in which a diagnostic accounting request was executed, tied to the application, accounting request, and product rule that drove the diagnostic run.

The table resides in the XLA schema and is classified as VALID in the EBS data dictionary for releases 12.1.1 and 12.2.2. In both releases, the underlying physical structure is documented with 22 columns. Based on the mined foreign-key and uniqueness structure, the heuristic Data Vault classification for this object is standalone. This means the table does not exhibit clear hub, link, or satellite dependency patterns from FK mining alone; it should be treated as an independent diagnostic staging or configuration-parameter table rather than a core transactional entity. Modeling suggestions should therefore avoid inferring parent-child relationships solely from the primary key columns.

Key Information Stored

The primary key of XLA_DIAG_LEDGERS is XLA_DIAG_LEDGERS_PK, composed of LEDGER_ID, APPLICATION_ID, ACCOUNTING_REQUEST_ID, PRODUCT_RULE_CODE, PRODUCT_RULE_TYPE_CODE, and AMB_CONTEXT_CODE. A unique index, XLA_DIAG_LEDGERS_U1, mirrors this same column set, indicating that the composite key also serves as the business-key candidate for uniqueness.

• LEDGER_ID — identifies the ledger processed by the diagnostic framework; central to every query against this table.
• APPLICATION_ID — the application (subledger) associated with the diagnostic run, distinguishing Payables, Receivables, Assets, and similar sources.
• ACCOUNTING_REQUEST_ID — links the diagnostic record to the specific accounting request being examined or generated.
• PRODUCT_RULE_CODE and PRODUCT_RULE_TYPE_CODE — identify the accounting product rule and its type applied during the diagnostic.
• AMB_CONTEXT_CODE — the application message builder context used to resolve the diagnostic parameters.
• PRIMARY_LEDGER_ID and SLA_LEDGER_ID — distinguish the primary ledger from the Subledger Accounting ledger, a distinction critical in multi-ledger and secondary-ledger configurations.
• CURRENCY_CODE, START_DATE_ACTIVE, and END_DATE_ACTIVE — define the ledger currency and the effective active period of the diagnostic ledger row.
• DESCRIPTION_LANGUAGE and NLS_DESC_LANGUAGE — control language and NLS description attributes.
• Standard WHO and request columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, and REQUEST_ID provide audit and concurrent program traceability.

Common Use Cases and Queries

Typical usage centers on troubleshooting and reconciliation of subledger accounting diagnoses. A DBA or functional consultant may query which ledgers have been processed for a given diagnostic accounting request:

• Ledger scope reporting — identify all LEDGER_ID values associated with a specific ACCOUNTING_REQUEST_ID to confirm diagnostic coverage.
• Multi-ledger analysis — compare PRIMARY_LEDGER_ID and SLA_LEDGER_ID to verify that primary and SLA ledgers are correctly paired in secondary ledger scenarios.
• Effective-dating checks — filter by START_DATE_ACTIVE and END_DATE_ACTIVE to confirm the diagnostic ledger row was active when the run occurred.
• Audit and traceability — join REQUEST_ID and PROGRAM_ID back to FND_CONCURRENT_REQUESTS to correlate diagnostic output with the concurrent program that produced it.
• Sample SQL pattern — a frequent pattern is SELECT LEDGER_ID, APPLICATION_ID, ACCOUNTING_REQUEST_ID, PRODUCT_RULE_CODE FROM XLA_DIAG_LEDGERS WHERE LEDGER_ID = :ledger_id, optionally constrained by AMB_CONTEXT_CODE or CURRENCY_CODE.

Related Objects

The documented FK structure suggests this table is largely standalone, so relationships are inferential through the shared diagnostic key columns rather than enforced referential constraints. Significant related objects include:

• XLA_DIAG_LEDGERS variants and diagnostic output tables sharing the LEDGER_ID and ACCOUNTING_REQUEST_ID keys.
• XLA_LEDGERS / GL_LEDGERS — resolve LEDGER_ID, PRIMARY_LEDGER_ID, and SLA_LEDGER_ID to ledger names, charts of accounts, and currencies.
• FND_APPLICATION — resolves APPLICATION_ID to the subledger application short name.
• XLA_ACCOUNTING_REQUESTS — resolves ACCOUNTING_REQUEST_ID to the accounting request header.
• XLA_PRODUCT_RULES — resolves PRODUCT_RULE_CODE and PRODUCT_RULE_TYPE_CODE to accounting rule definitions.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — resolve REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for audit and traceability.