Search Results distribution_type_code

Overview

FA_XLA_EXTRACT_TRX_PKG is a generated PL/SQL package body owned by APPS within the Oracle E-Business Suite Fixed Assets (FA) module. Its name follows the FA_XLA_ prefix convention, indicating that it belongs to the Subledger Accounting (XLA) extraction layer for Fixed Assets transactions. The package was generated automatically from FA Application Accounting Definition (AAD) setups, as stated in its header comment: "Package generated From FA AAD setups." The generation timestamp recorded in the source is 30-03-2009, authored by user ANONYMOUS, which reflects the metadata-driven construction of subledger accounting extraction logic.

In Oracle EBS release 12.1.1 and 12.2.2, Subledger Accounting replaces the older transaction-based accounting engines. The FA_XLA_EXTRACT_TRX_PKG participates in this architecture by staging Fixed Assets transaction data into intermediate global temporary tables and related structures that the XLA accounting engine subsequently consumes, applies accounting rules to, and creates final subledger journal entries. The search term distribution_type_code is relevant here because the FA distribution account and distribution history tables accessed by this package carry a distribution type identifier that distinguishes, for example, cost, depreciation, and retirement distributions. This value is central to determining which accounting line type an extracted transaction line maps to during the XLA create-accounting process.

Key Procedures and Functions

The documented package metadata identifies a single procedure: LOAD_DATA. This is the public entry point of the package. In the standard generated FA XLA extraction pattern, LOAD_DATA orchestrates the extraction sequence: it drives the private staging routines that populate the global temporary staging tables from the underlying Fixed Assets transaction tables, then hands the staged rows to the XLA extraction framework for accounting event modeling and journal line creation.

The source excerpt also illustrates the private staging pattern typical of these generated packages, including a private procedure such as load_header_data_stg1, which inserts into fa_xla_ext_headers_b_gt columns including event_id, default_ccid, book_type_code, period_name, period_close_date, and period information. These private procedures are not part of the public API but form the internal data preparation layer invoked from within LOAD_DATA. The consistent FND_LOG instrumentation (G_LEVEL_PROCEDURE, G_LEVEL_STATEMENT, and related constants) allows runtime tracing through the standard Oracle logging framework when debugging extraction issues.

Tables Accessed

The package references, via APPS synonyms, a broad set of Fixed Assets transaction tables that supply the raw data for subledger accounting extraction. Asset master data is sourced from FA_ADDITIONS_B, while transactional detail comes from FA_ADJUSTMENTS, FA_ASSET_HISTORY, and FA_ASSET_INVOICES. Book-level and period-level context is derived from FA_BOOK_CONTROLS and FA_DEPRN_PERIODS, with category defaults supplied by FA_CATEGORY_BOOKS. Distribution-related data — the area most closely tied to distribution_type_code — is read from FA_DISTRIBUTION_ACCOUNTS and FA_DISTRIBUTION_HISTORY. FA_LOCATIONS and FA_LOOKUPS provide descriptive and reference lookups. Multi-currency and multi-book requirements are met by FA_MC_ADJUSTMENTS, FA_MC_ASSET_INVOICES, FA_MC_BOOK_CONTROLS, and FA_MC_RETIREMENTS, which mirror the primary book structures for reporting books.

Usage Notes

FA_XLA_EXTRACT_TRX_PKG is not intended for direct invocation by end users or custom code. It is invoked by the Subledger Accounting extraction infrastructure during the Create Accounting process for the Fixed Assets application, and by the FA accounting program that triggers subledger events. Because the package is generated from FA AAD setups, its content is regenerated whenever the accounting setups change, so any custom modifications would be overwritten. Developers investigating distribution_type_code behavior should trace the package's staging inserts against FA_DISTRIBUTION_ACCOUNTS and FA_DISTRIBUTION_HISTORY to confirm how distribution types flow into XLA event and journal line definitions. The package is referenced by zero other packages, confirming its role as a terminal extraction component consumed by the XLA engine rather than a shared library.