Search Results fa_api_types




Overview

APPS.FA_DEPRN_RULE_DETAILS_PKG is a server-side PL/SQL package within the Oracle E-Business Suite Fixed Assets (FA) module. It encapsulates the data-maintenance logic for depreciation rule details, the child records that define how a depreciation basis rule spreads depreciation across periods and fiscal years. Depreciation rule details constitute the operational core of the FA depreciation engine: they determine the rate or amount applied in each period, the associated depreciation method, and the effective dates that govern when a rule line becomes active. Because these rows feed directly into the depreciation calculation process, the package exists to provide a controlled, consistent interface for inserting, updating, deleting, and loading these detail rows without exposing callers to the underlying table structure.

The package is classified under the ETRM as API classification OTHER, indicating that it is a supporting internal package rather than a fully documented public API. It is not referenced by any other documented package in the schema, so its consumers are principally the Fixed Assets forms and the rule-loading infrastructure rather than downstream PL/SQL code.

Key Procedures and Functions

ETRM documents seven procedures and functions in the package. Six are enumerated in the published metadata:

  • INSERT_ROW — Creates a new depreciation rule detail record, populating the columns required to associate a detail line with its parent rule and to define its period-by-period behavior.
  • LOCK_ROW — Acquires a row-level lock on an existing depreciation rule detail, used to serialize concurrent modification and to guarantee that validation and update operate on a stable copy of the row.
  • UPDATE_ROW — Applies changes to an existing depreciation rule detail, typically preceded by LOCK_ROW to prevent lost updates.
  • DELETE_ROW — Removes a depreciation rule detail record, used when a rule line is retired or corrected.
  • LOAD_ROW — Loads a depreciation rule detail from a batch or seed source, supporting bulk population of rule data rather than interactive entry.
  • LOAD_SEED_ROW — A variant of the load routine intended for seeding reference or installation data, ensuring that baseline depreciation rule details are established during setup or upgrade.

The seventh documented procedure or function is not enumerated in the available metadata. Its existence is recorded, but its name and purpose cannot be stated without risk of invention.

Tables Accessed

The package operates against three documented tables, reached through APPS synonyms:

  • FA_DEPRN_RULE_DETAILS — the primary transactional table holding the rule detail rows. It is the direct target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOAD_ROW, and LOAD_SEED_ROW, and the source for LOCK_ROW.
  • FA_DEPRN_RULE_DETAILS_S — the corresponding translated or shadow table, maintained in step with the base table so that descriptive attributes are available across languages and audit contexts.
  • FA_DEPRN_BASIS_RULES — the parent depreciation basis rules table, referenced to validate that a detail row is attached to a valid, active basis rule before it is committed.

The dependency listing recorded by ETRM shows FA_API_TYPES among the objects referenced by this package. FA_API_TYPES is a shared PL/SQL type specification that defines the record and table types used across the Fixed Assets public APIs; the presence of this dependency indicates that the package's interface passes or consumes those shared structures, which is the reason a search for "fa_api_types" surfaces this package. The package also depends on the SYS.STANDARD package, which is a normal consequence of PL/SQL compilation rather than a functional dependency.

Usage Notes

In practice, FA_DEPRN_RULE_DETAILS_PKG is invoked from the Fixed Assets depreciation rule setup forms, where the form's block-level DML is routed through the package's insert, lock, update, and delete routines. The load procedures support concurrent programs and installation routines that create or refresh depreciation rule details in bulk, including seeded rows delivered with the application.

Because the package is classified as OTHER rather than a published API, customizations should avoid calling it directly where a supported alternative exists; direct DML against FA_DEPRN_RULE_DETAILS bypasses validation and should also be avoided. Any custom integration that must manipulate depreciation rule details should be validated against the release in use, since the package body is not part of Oracle's documented public interface and its behavior, though stable, is not contractually guaranteed.