Search Results fa_deprn_rule_details




Overview

FA_DEPRN_RULE_DETAILS is a reference configuration table in the Oracle Assets (OFA) module of Oracle E-Business Suite, owned by the FA schema. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the table stores the detail information that defines depreciable basis rules. Each row captures the behavioral attributes governing how a depreciation basis rule is applied to assets, including rate sourcing, asset type applicability, and various reduction and reserve treatment flags. The table is therefore a configuration-driven extension of the parent rule definition held in FA_DEPRN_BASIS_RULES, and it is consulted by the depreciation engine when computing depreciation for assets assigned to a given basis rule.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. In practical terms, FA_DEPRN_RULE_DETAILS behaves as a satellite table hanging off the parent business key in FA_DEPRN_BASIS_RULES, recording descriptive rule attributes rather than acting as an independent hub or a many-to-many link. This classification is a heuristic suggestion derived from the single foreign key relationship, not a prescriptive constraint.

Key Information Stored

The table is documented with 17 columns in the 12.2.2 physical schema. The surrogate primary key is DEPRN_RULE_DETAIL_ID, enforced by the FA_DEPRN_RULE_DETAILS_PK constraint, and it uniquely identifies each rule detail row. A secondary unique index, FA_DEPRN_RULE_DETAILS_U1, spans DEPRN_RULE_DETAIL_ID and ZD_EDITION_NAME and functions as a business-key candidate, reflecting the edition-aware storage pattern used in 12.2.x multi-tenant deployments.

The most significant columns include:

Common Use Cases and Queries

Typical usage centers on configuration validation, depreciation diagnostics, and rule-impact reporting. Administrators query this table to confirm which basis rules permit reduction rates or end-of-fiscal-year reserve handling before running the depreciation program. Developers join it to the parent rule table to reconstruct a complete rule definition for troubleshooting unexpected depreciation amounts.

A representative query joining parent and detail follows:

  • SELECT b.deprn_basis_rule_id, d.rule_name, d.rate_source_rule, d.deprn_basis_rule, d.asset_type, d.allow_reduction_rate_flag, d.use_eofy_reserve_flag FROM fa.fa_deprn_basis_rules b, fa.fa_deprn_rule_details d WHERE b.deprn_basis_rule_id = d.deprn_basis_rule_id;
  • SELECT * FROM fa.fa_deprn_rule_details WHERE deprn_basis_rule_id = :p_basis_rule_id ORDER BY rule_name;

Reporting use cases include audit listings of active rule details, extraction of flags into downstream subledger or tax reconciliation models, and impact analysis before modifying a shared basis rule.

Related Objects

The principal related object is FA_DEPRN_BASIS_RULES, joined via the documented foreign key FA_DEPRN_RULE_DETAILS.DEPRN_BASIS_RULE_ID referencing FA_DEPRN_BASIS_RULES. This parent table holds the header-level basis rule definition, while FA_DEPRN_RULE_DETAILS supplies its detail attributes. Downstream, depreciation processes and reporting tools such as the depreciation program, the Fixed Assets accounting reports, and the standard Assets inquiry forms consume these rows indirectly. Related configuration objects include other FA depreciation setup tables that reference the same basis rules, and the primary key constraint FA_DEPRN_RULE_DETAILS_PK combined with the unique index FA_DEPRN_RULE_DETAILS_U1 defines the integrity boundaries for joins. No additional foreign keys from other tables into FA_DEPRN_RULE_DETAILS are documented in the provided ETRM metadata.