Search Results xla_ae_lines_gt




Overview
Explore in AI Chat

Overview

XLA_AE_LINES_GT is a global temporary table in the Subledger Accounting (XLA) product schema. It is the staging area used by the Subledger Accounting Engine during the creation of accounting entries. When a subledger event is processed through the Create Accounting program, the engine first populates this table with candidate accounting lines before validating, rounding, and ultimately transferring the surviving rows into the permanent XLA_AE_LINES table. Because the contents are session-scoped, XLA_AE_LINES_GT is typically purged automatically on commit or at session termination, depending on the ON COMMIT clause of the corresponding temporary table definition.

The table holds 318 columns in the documented 12.2.2 physical schema, mirroring the structure of the permanent accounting-lines fact while carrying additional temporary identifiers. The heuristic Data Vault classification mined from the foreign-key structure is standalone; it should be treated as a staging structure rather than a conformed hub, link, or satellite, since it has no dependencies to conformed dimensions and is consumed only within the accounting program's runtime.

Key Information Stored

The business-key candidate documented by the unique index XLA_AE_LINES_GT_U1 is the composite of LEDGER_ID, REF_AE_HEADER_ID, TEMP_LINE_NUM, AE_HEADER_ID, HEADER_NUM, and EVENT_ID. There is no separate surrogate primary key exposed in the metadata; AE_LINE_NUM is the accounting-line identifier that becomes the stable key once the row is persisted to XLA_AE_LINES. The most operationally significant columns include:

Common Use Cases and Queries

Because the table is populated only during the Create Accounting run for the current session, direct reporting against XLA_AE_LINES_GT from a separate session will often return no rows. It is most useful for debugging the accounting engine in the same session and for examining how amounts are derived before they reach the permanent tables. A typical diagnostic pattern joins the temporary lines back to the permanent header:

  • Validate line counts: SELECT COUNT(*) FROM xla_ae_lines_gt WHERE ledger_id = :ledger AND event_id = :event.
  • Inspect generated amounts: SELECT ae_line_num, entered_dr, entered_cre, accounted_dr, accounted_cr FROM xla_ae_lines_gt WHERE ae_header_id = :header.
  • Compare against persisted lines: SELECT g.temp_line_num, g.code_combination_id, g.entered_dr, l.entered_dr FROM xla_ae_lines_gt g, xla_ae_lines l WHERE g.ae_header_id = l.ae_header_id AND g.ae_line_num = l.ae_line_num.

Common scenarios include troubleshooting unposted or suspended accounting, verifying currency conversion rates applied by the engine, and confirming that the rounding logic (UNROUNDED_ACCOUNTED_DR, DOC_ROUNDING_ACCTD_AMT) behaves as expected before the line is transferred to the final fact.

Related Objects

  • XLA_AE_LINES — permanent accounting-lines table; receives the surviving rows from the temporary table.
  • XLA_AE_HEADERS — accounting header joined through AE_HEADER_ID and REF_AE_HEADER_ID.
  • XLA_EVENTS — event definitions linked through EVENT_ID.
  • XLA_DISTRIBUTION_LINKS — source distribution mapping used to build the accounting lines.
  • GL_ENCUMBRANCE_TYPES — referenced by the documented foreign key on ENCUMBRANCE_TYPE_ID.
  • GL_CODE_COMBINATIONS — referenced indirectly through CODE_COMBINATION_ID and ALT_CODE_COMBINATION_ID.
  • Create Accounting program (XLAACCCP / XLAACCUP concurrent requests) — the primary consumer that populates and reads this temporary table.

These relationships make XLA_AE_LINES_GT an internal staging construct rather than a query surface for end-user reporting; production reporting should target XLA_AE_LINES and XLA_AE_HEADERS instead.