Search Results fa_deprn_row_struct




Overview
Explore in AI Chat

Overview

FA_STD_TYPES is a specification-only PL/SQL package in the Oracle E-Business Suite Fixed Assets (FA) module, owned by the APPS schema. It is not a business API in the conventional sense; rather, it is a shared type repository that centralizes the PL/SQL record and collection type definitions used throughout the Fixed Assets depreciation engine and summary-processing modules. The package header, shipped at version 120.26.12010000.1 (2008/07/28), exists primarily so that the many FA packages that participate in depreciation calculation, reporting, and asset processing can pass standardized, strongly typed structures between one another instead of redefining incompatible local types.

In the ETRM 12.2.2 metadata the package is classified as API classification OTHER, with zero documented procedures or functions, which confirms its nature as a declarative container. It is referenced by 54 other packages, underscoring its role as a foundational dependency for the depreciation subsystem. The identifier the user searched for, fa_deprn_row_struct, is the record type declared in this package that carries a single asset's depreciation inputs through the engine — the field list in the source excerpt (adj_cost, rec_cost, reval_amo_basis, deprn_rsv, reval_rsv, adj_rate, rate_adj_factor, capacity, and so on) defines exactly that structure.

Key Procedures and Functions

No procedures or functions are documented for APPS.FA_STD_TYPES in the ETRM metadata; the specification exposes only type and variable declarations. The published declarations include:

  • number_tbl_type — a PL/SQL associative-array (INDEX BY BINARY_INTEGER) of NUMBER, used to pass numeric sets such as costs, rates, and reserves.
  • date_tbl_type — an associative array of DATE, used for date-oriented collections such as period and Julian-date arrays.
  • boolean_tbl_type — an associative array of BOOLEAN, typically used for flag vectors in processing loops.
  • varchar2_tbl_type — an associative array of VARCHAR2(1000), used for text collections such as method codes or book names.
  • deprn_override_trigger_enabled — a package global BOOLEAN defaulting to TRUE, which holds the accessibility/override state against the FA_OVERRIDE_TABLE.
  • fa_deprn_row_struct — the depreciation row record type. Its documented fields cover adjusted cost, recoverable cost, revaluation amortization basis, depreciation reserve, revaluation reserve, adjusted rate, rate adjustment factor, production capacity, adjusted capacity, life-to-date production, asset number, depreciation calendar, ceiling name, bonus rule, book type code, method code, asset ID, DPIS and prorate Julian dates, depreciation start date, retirement date and retirement prorate date, asset life in months, year/period begin and end ranges, the reserve-known flag, and salvage value.

Tables Accessed

The package's documented table references reflect the depreciation data model even though the types themselves perform no DML. Referenced via APPS synonyms are FA_ADDITIONS and FA_ADDITIONS_B (asset identification and descriptive data), FA_BOOKS (book-level cost, reserve, and method attributes), FA_CALENDAR_TYPES (depreciation calendar definitions), FA_DEPRN_DETAIL (period-by-period depreciation expense and reserve detail), FA_DEPRN_SUMMARY (summarized depreciation balances), FA_DISTRIBUTION_HISTORY (accounting distribution of assets), and FA_TRANSACTION_HEADERS (transaction grouping for asset additions, adjustments, transfers, and retirements). These are the same tables consumed by the depreciation engine and summary modules that use the shared types.

Usage Notes

FA_STD_TYPES is invoked implicitly rather than executed. Any Fixed Assets package, form, or concurrent program that needs the standard depreciation row structure or the shared collection types references FA_STD_TYPES.fa_deprn_row_struct and the associated table types in its own specifications. The depreciation engine receives the row structure as an IN parameter (as noted in the source comments), and callers manipulate the deprn_override_trigger_enabled global to control override-table behavior during processing. Custom code extending depreciation logic should declare variables using these types rather than redefining them, preserving compatibility with the 54 dependent packages. Note that the associative-array types are PL/SQL-only and cannot be persisted to the database or passed to OAF/Java callers.