Search Results xla_validation_lines_gt




Overview
Explore in AI Chat

Overview

XLA_VALIDATION_LINES_GT is a Subledger Accounting (XLA) table in the EBS database, owned by the XLA schema. It is a Global Temporary Table (GT) used by the Subledger Accounting validation engine to stage and validate accounting line data before it is written to the final SLA tables. During the Create Accounting process, the subledger populates this structure with candidate journal lines, and the validation engine applies a series of checks — account combination validity, party assignment, ledger currency balancing, suspense handling, and intercompany posting rules — and records the outcome of each check in the flag and status columns on each row.

The 72 documented columns mirror most of the attributes found on the permanent accounting line tables, making this a working copy of the line data as it moves through validation. The table is populated per concurrent process run and is scoped by EVENT_ID and related identifiers, so its logical grain is one row per candidate accounting line within a validation run. Regarding modeling classification, the metadata heuristically classifies this object as standalone; it is best treated as a transient staging/validation structure rather than a persisted Data Vault hub, link, or satellite, and should not be modeled as a durable entity in downstream designs.

Key Information Stored

The table stores the validation state of each candidate accounting line alongside its accounting attributes. The most significant columns fall into several groups:

No surrogate primary key or unique index is documented in the available metadata; this is consistent with a temporary staging table populated by a concurrent program rather than a keyed persistent entity. The natural line identifier is the combination of EVENT_ID, AE_HEADER_ID, and AE_LINE_NUM.

Common Use Cases and Queries

The primary use case is diagnosing Create Accounting failures. Because validation results are captured per line, querying rows where ERROR_FLAG = 'Y' isolates the specific lines that failed and the status columns identify which check failed. A typical diagnostic query joins the staging rows to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to inspect the offending account combination:

  • SELECT ae_line_num, code_combination_id, accounting_entry_status_code, error_flag FROM xla_validation_lines_gt WHERE error_flag = 'Y';
  • Aggregating ENTERED_DR and ENTERED_CR by LEDGER_ID and PERIOD_NAME supports pre-post balancing and suspense analysis.
  • Filtering on SUBSTITUTED_BY_SUSPENSE_FLAG or SUSPENSE_CODE_COMBINATION_ID identifies lines routed to a suspense account during validation.
  • Filtering on BAL_SEG_VALID_STATUS or MGT_SEG_VALID_STATUS supports balancing segment and management segment diagnostics for intercompany and clearing entries.

Because this is a temporary table, its contents are private to the session or transaction that populates it and are not reliable for historical reporting. Reproducing validation output after a run requires rerunning Create Accounting or querying the permanent SLA tables that receive the validated lines.

Related Objects

XLA_VALIDATION_LINES_GT interacts with the following significant objects:

  • GL_ENCUMBRANCE_TYPES — referenced through ENCUMBRANCE_TYPE_ID, per the documented foreign key, linking validation lines to encumbrance type definitions.
  • XLA_AE_HEADERS and XLA_AE_LINES — the destination tables for validated accounting entries; the staging line's AE_HEADER_ID and AE_LINE_NUM correspond to these records.
  • XLA_EVENTS — the source subledger events identified by EVENT_ID and ENTITY_ID.
  • XLA_ACCOUNTING_PROGRAMS and XLA_EVENT_TYPES — define the accounting program and event type context referenced by PRODUCT_RULE_CODE and EVENT_TYPE_CODE.
  • GL_CODE_COMBINATIONS and GL_LEDGERS — resolve CODE_COMBINATION_ID, LEDGER_ID, and LEDGER_COA_ID to account and ledger definitions.
  • XLA_ACCOUNTING_ERRORS — captures validation errors surfaced during processing of lines staged in this table.