Search Results fa_xla_ext_lines_b_gt




Overview
Explore in AI Chat

Overview

FA_XLA_EXT_LINES_B_GT is a table owned by the FA (Assets) schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It resides in the OFA – Assets product module and carries a VALID status in the data dictionary. The name and column profile identify it as a global temporary staging table used by the Subledger Accounting (XLA) and Assets transaction-accounting engine. The "_GT" suffix denotes that rows are private to a session or transaction and are typically populated during the accounting-line generation phase of the Asset Additions, Adjustments, Transfers, Retirements, Revaluations, and Depreciation processes. Once the XLA engine reads the staged rows and writes the resulting journal entries to the SLA schemas, the rows are truncated or released on commit.

From a heuristic Data Vault modeling perspective, the FK analysis classifies this object as standalone. Its extraction feed to a warehouse would most naturally be modeled as a satellite, since it holds descriptive transaction-line attributes keyed to an accounting event, ledger, and line number rather than acting as a true hub of business entities.

Key Information Stored

The documented physical schema contains 320 columns and one unique index, FA_XLA_EXT_LINES_B_GT_U1, defined on (EVENT_ID, LINE_NUMBER, LEDGER_ID). This composite unique key is the business-key candidate; it identifies one transaction line within one accounting event for one ledger. There is no documented single-column surrogate primary key, so the unique index functions as the row identifier.

The most significant columns include:

Common Use Cases and Queries

Consultants and developers inspect this table during periods when XLA has not yet posted, or when troubleshooting asset accounting entries. Because it is a global temporary table, meaningful investigation must occur within the owning session or before commit. A representative diagnostic query reconciles staged lines to the resulting SLA entries:

  • SELECT event_id, line_number, ledger_id, asset_number, transaction_type_code, entered_amount FROM fa_xla_ext_lines_b_gt WHERE event_id = :event_id ORDER BY line_number;
  • Joining to FA_ADDITIONS_B on ASSET_ID to verify the asset exists for a given accounting event.
  • Grouping by BOOK_TYPE_CODE and LEDGER_ID to validate transaction totals against expected batch controls.
  • Filtering on DISTRIBUTION_TYPE_CODE and TRANSACTION_TYPE_CODE to isolate depreciation versus addition lines during period close reconciliation.

Related Objects

The FK metadata documents direct parent references that are useful for joining when reconciling staged lines:

In practice, the table is consumed by the XLA Accounting Program and related SLA APIs, and it feeds the FA_ADDITIONS and FA_TRANSACTION_HEADERS accounting flows that ultimately produce subledger journal entries.