Search Results fa_xla_ext_lines_stg_gt

Overview

FA_XLA_EXT_LINES_STG_GT is a staging table owned by the FA (Assets) schema in Oracle E-Business Suite, supporting the OFA – Assets product. It serves as an intermediate staging structure used by the Subledger Accounting (XLA) engine during the generation of accounting entries for asset transactions. The table temporarily holds transaction line data — including asset attributes, category details, distribution accounts, and source references — prior to validation, transfer into the final accounting event model, and eventual posting to the general ledger. In release 12.1.1 and 12.2.2, this object is populated by the Create Accounting process for Assets and typically contains short-lived rows scoped to a specific accounting run.

Based on the heuristic Data Vault classification derived from the foreign key structure, the table can be modeled as a standalone structure. It does not appear as a natural hub, link, or satellite because no upstream foreign key references it; instead, it functions as a transient staging container whose joined dimensions (project assets, group assets, categories, employees, super groups, depreciation basis rules) supply the descriptive context at extraction time.

Key Information Stored

The table carries 308 documented columns spanning asset definition, transaction context, category flexfields, accounts, and ledger information. The most operationally significant columns include:

• EVENT_ID and LINE_NUMBER – identifiers of the XLA accounting event and the staged line within the event.
• TRANSACTION_HEADER_ID and TRANSACTION_TYPE_CODE – link the staged line to the originating asset transaction and classify it (for example additions, adjustments, retirements).
• ASSET_ID, ASSET_NUMBER, and BOOK_TYPE_CODE – identify the asset and depreciation book affected.
• CAT_ID and CAT_TYPE – reference the asset category driving default accounts and depreciation rules.
• ENTERED_AMOUNT, COST, and CURRENCY_CODE – capture the monetary basis of the staged accounting line.
• LEDGER_ID, GENERATED_CCID, and GENERATED_OFFSET_CCID – specify the accounting ledger and the debit/credit account combinations produced.
• DISTRIBUTION_ID and DISTRIBUTION_TYPE_CODE – tie the line to the originating distribution and its accounting type.
• SOURCE_TYPE_CODE, SOURCE_LINE_ID, and SOURCE_TRANSACTION_HEADER_ID – provide traceability back to the feeder source.

The documented unique index FA_XLA_EXT_LINES_STG_GT_U1 on (EVENT_ID, TRANSACTION_HEADER_ID) acts as the primary business-key candidate, uniquely identifying staged lines within a given accounting event. The physical schema does not document a separate surrogate primary key, so the composite unique index serves that identification purpose.

Common Use Cases and Queries

Typical usage focuses on diagnosing Create Accounting errors, reconciling subledger output, and tracing how asset transactions map to ledger entries. A common query pattern joins the staging table to FA_GROUP_ASSETS or PA_PROJECT_ASSET_LINES_ALL to validate that the correct source records participated in the run:

• Identifying failed or unposted asset accounting lines by filtering on EVENT_ID and accessing the associated XLA event status.
• Reconciling ENTERED_AMOUNT against the underlying transaction amount for additions and retirements.
• Auditing GENERATED_CCID account combinations against the asset category default accounts to verify account derivation.
• Reporting on transaction type distribution (TRANSACTION_TYPE_CODE) for a given BOOK_TYPE_CODE and LEDGER_ID.

Because the table is a staging ground, queries should generally be time-bounded by run ID or event ID rather than relying on persistent historical content.

Related Objects

The documented foreign key relationships link this table to several core Assets and cross-module objects:

• FA_GROUP_ASSETS – joined via GROUP_ASSET_ID for grouped asset transactions.
• FA_SUPER_GROUPS – joined via SUPER_GROUP_ID for super-group member context.
• FA_DEPRN_BASIS_RULES – joined via DEPRN_BASIS_RULE_ID to resolve the depreciation basis rule applied.
• PA_PROJECT_ASSET_LINES_ALL – joined via PROJECT_ASSET_LINE_ID for capitalized project assets.
• BEN_TCS_CAT – joined via CAT_ID to obtain category-level attribute detail.
• PSB_EMPLOYEES – joined via EMPLOYEE_ID where asset assignment to an employee is relevant.
• XLA_EVENTS and related XLA accounting tables – the downstream destination of staged lines after validation.

Together these relationships confirm the table's role as the Assets-side feeder into the XLA accounting pipeline.