Results for “override_allowed_flag”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FA_HIERARCHY_RULE_DETAILS_V is an Oracle EBS Assets (OFA) view owned by the APPS schema. It exposes the configuration rows that drive hierarchy-based asset assignment and defaulting logic in Oracle Assets. In EBS 12.1.1 and 12.2.2, hierarchy rule sets allow an organization to define how asset attributes (such as depreciation basis, category, or life) are derived by traversing a reporting or accounting hierarchy rather than from a single static source. This view presents the individual rule details belonging to each hierarchy rule set, keyed by HIERARCHY_RULE_SET_ID.

For reporting and integration purposes, the view acts as the readable access point to the hierarchy rule configuration. Because it is a simple projection over the base table without complex joins, it is safe to query directly from custom reports, concurrent programs, or interfaces without incurring the performance penalties associated with generalized flexfield or descriptive flexfield views.

Underlying Base Objects

The view is defined over a single base object, FA_HIERARCHY_RULE_DETAILS, which is exposed to APPS through a synonym. The view text selects ROWID and the full set of application columns from that table, applying no filtering, aggregation, or join logic. Consequently, the row count and cardinality of the view are identical to the underlying base table, and the view contains one row per rule detail line within a hierarchy rule set.

All identifiers and audit columns originate from the base table. No additional calculation, decode, or lookup resolution is performed at the view layer, which means any translatable or descriptive information must be joined separately from the relevant lookup or flexfield views.

Key Columns

Common Use Cases and Queries

A frequent requirement is to review all detail lines configured for a specific hierarchy rule set, typically located by searching on hierarchy_rule_set_id. The following query returns the full rule definition ordered by evaluation precedence:

  • SELECT hierarchy_rule_set_id, attribute_name, book_type_code, basis_code, precedence_level, override_allowed_flag, target_flag FROM apps.fa_hierarchy_rule_details_v WHERE hierarchy_rule_set_id = :p_rule_set_id ORDER BY precedence_level, attribute_name;

To audit which book types are referenced across all rule sets, a distinct projection is commonly used:

  • SELECT DISTINCT hierarchy_rule_set_id, book_type_code FROM apps.fa_hierarchy_rule_details_v ORDER BY hierarchy_rule_set_id;

For troubleshooting unexpected defaults, a report joining the view to the corresponding rule set header on HIERARCHY_RULE_SET_ID allows comparison of the configured precedence and override behavior against the values actually assigned to assets. Because the view performs no filtering, users should always restrict queries by HIERARCHY_RULE_SET_ID or BOOK_TYPE_CODE to avoid returning the complete rule configuration across the instance.