Search Results bonus_entered_amount

Overview

The APPS.FA_XLA_EXTRACT_DEPRN_PKG package body is a Subledger Accounting (SLA) extraction utility within the Oracle E-Business Suite Fixed Assets module. Its principal business function is to generate the accounting event data that the SLA engine consumes when creating journal entries for depreciation and asset-related transactions. The package was generated from FA AAD (Application Accounting Definition) setups, meaning its extraction logic is driven by the accounting attribute mappings configured in Subledger Accounting rather than hand-coded business rules. This generated nature is significant: the extract population logic is a direct reflection of the AAD configuration active at generation time (the header comment records generation on 30-March-2009 by user ANONYMOUS). The package is relevant in both Oracle EBS 12.1.1 and 12.2.2, where the XLA extraction framework remains the mechanism for transferring Fixed Assets data into the accounting repository.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package body:

• LOAD_DATA — The main entry point invoked by the XLA extraction framework. It orchestrates the population of the extraction staging tables by calling the internal (private) load routines, of which load_header_data is visible in the source excerpt. load_header_data inserts header-level extraction records — including EVENT_ID, DEFAULT_CCID, BOOK_TYPE_CODE, PERIOD_NAME, PERIOD_CLOSE_DATE, and PERIOD_COUNTER — into the global temporary table FA_XLA_EXT_HEADERS_B_GT.

The package also declares FND_LOG constants (G_LEVEL_STATEMENT through G_LEVEL_UNEXPECTED) and a module name constant fa.plsql.fa_xla_extract_trx_pkg., enabling fine-grained debug logging at each runtime level. No parameter lists are published in the ETRM metadata; callers rely on the framework's standard invocation contract.

Tables Accessed

The package reads from and writes to the following documented objects (referenced through APPS synonyms):

• FA_ADDITIONS_B, FA_ASSET_HISTORY, FA_CATEGORY_BOOKS — asset identity, assignment history, and category-to-book accounting setup.
• FA_BOOK_CONTROLS, FA_MC_BOOK_CONTROLS — depreciation book parameters for the primary and reporting (Mrc) books, supplying the period context for extraction.
• FA_DEPRN_DETAIL, FA_MC_DEPRN_DETAIL, FA_MC_DEPRN_SUMMARY_H — the core depreciation amounts (cost, depreciation expense, adjustments such as bonus depreciation) that flow into the SLA event lines.
• FA_DEPRN_EVENTS, FA_DEPRN_PERIODS — depreciation event types and period-to-period-counter mapping used to identify the extract window.
• FA_DISTRIBUTION_ACCOUNTS, FA_DISTRIBUTION_HISTORY — the account distributions that determine the CCID used for each generated line.
• FA_XLA_EXT_HEADERS_B_GT, FA_XLA_EXT_LINES_B_GT — the global temporary tables that stage the header and line extract data for downstream XLA processing.
• GL_LEDGERS — ledger configuration, including the ledger's chart of accounts and currency context.

Collectively, these tables supply both the accounting event attributes and the amount values required to produce balanced subledger entries for depreciation.

Usage Notes

This package is not normally called directly by end users or custom code. It is invoked by the XLA extraction framework during the Subledger Accounting program flow — typically when running Create Accounting for the Fixed Assets application, or via the depreciation extraction concurrent process. Because the package is generated from AAD setups, changes to the accounting definition (for example, adding a new accounting attribute or altering the line mapping) require regeneration of the package body; manual edits are overwritten.

With respect to the search term bonus_entered_amount: this attribute is one of the tax-book depreciation columns sourced from the FA depreciation detail tables and carried through the extract into FA_XLA_EXT_LINES_B_GT. It represents a bonus depreciation amount entered in the tax book, made available to the SLA mapping so an AAD can route it to a distinct account. Administrators troubleshooting missing or misstated bonus depreciation journal lines should verify the tax book's depreciation setup, the active AAD mapping for bonus_entered_amount, and whether the package body has been regenerated since the last AAD change.