Results for “lowest_level_flag”

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

Overview

The APPS.FA_ASSET_HRCHY_DETAILS_V view is a reporting and integration object within the Oracle E-Business Suite Fixed Assets module (OFA). It exposes the asset hierarchy structure maintained in FA_ASSET_HIERARCHY, enriched with descriptive information drawn from the FA_ADDITIONS asset repository. The view presents a flattened, query-friendly projection of the parent-child relationships that define asset hierarchies, together with the identifier of the asset assigned to each hierarchy node, the depreciation start date, and the LOWEST_LEVEL_FLAG that indicates whether a given node sits at the bottom of the hierarchy tree.

In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema (Status: VALID) and is intended for read-only consumption. It shields report developers, integrators, and downstream customizations from the underlying join logic between the hierarchy definition table and the asset master table, and it resolves the description attribute through a DECODE construct so that hierarchy nodes not yet associated with an asset inherit the hierarchy-level description instead. This makes the view particularly useful for inheritance of tax, tax book, or corporate book asset hierarchies and for any reporting requirement where the leaf-level flag drives the computation.

Underlying Base Objects

The documented base objects referenced by the view are two synonyms in the APPS schema: FA_ASSET_HIERARCHY and FA_ADDITIONS.

• FA_ASSET_HIERARCHY — The driving table. It stores hierarchy definition rows, including the surrogate ASSET_HIERARCHY_ID, the hierarchy NAME, the optional ASSET_ID link to a fixed asset, the PARENT_HIERARCHY_ID that establishes the self-referencing parent-child relationship, the LOWEST_LEVEL_FLAG indicating a terminal node, and the DEPRECIATION_START_DATE. The view uses an outer join on FA_ADDITIONS, so hierarchy rows without an associated asset are still returned.
• FA_ADDITIONS — The fixed assets master table. It is joined via FA.ASSET_ID(+) = AH.ASSET_ID and supplies the asset DESCRIPTION used as the fallback when a hierarchy row is populated with an asset. This is a synonym over the FA_ADDITIONS base table and is the authoritative source for asset-level attributes in the OFA module.

The view text is a simple SELECT from FA_ASSET_HIERARCHY with an outer join to FA_ADDITIONS, so no aggregations or analytic functions are applied; the row count and grain of the view therefore mirror the hierarchy definition table, one row per hierarchy node.

Key Columns

• ASSET_HIERARCHY_ID — Primary surrogate key identifying a single node in the hierarchy. Used as the join key when traversing parent-child links and as the unique identifier in reporting.
• NAME — The user-defined name of the hierarchy or hierarchy node as stored on FA_ASSET_HIERARCHY.
• DESCRIPTION — Derived column. When AH.ASSET_ID is null (or zero) the hierarchy description is returned; otherwise the FA_ADDITIONS asset description is returned via the DECODE(NVL(AH.ASSET_ID,0),0,AH.DESCRIPTION,FA.DESCRIPTION) expression.
• PARENT_HIERARCHY_ID — Self-referencing pointer to the parent node’s ASSET_HIERARCHY_ID. A null value typically denotes a root node; this column drives recursive traversal in CONNECT BY queries.
• LOWEST_LEVEL_FLAG — Flag identifying terminal (leaf) nodes in the hierarchy. This is the column users most frequently search for on this view; it enables filtering to bottom-level nodes only, which is essential when the hierarchy is used for roll-up versus detail reporting.
• DEPRECIATION_START_DATE — Depreciation start date associated with the hierarchy node, used for period-sensitive reporting.
• ASSET_ID — The fixed asset identifier linked to the node. When populated, it links the hierarchy row to FA_ADDITIONS and the broader asset reporting model.

Common Use Cases and Queries

Typical usages include reporting on hierarchy structure for corporate or tax books, identifying leaf-level nodes for detail-level depreciation analysis, and supplying integration extracts with parent-child context. A representative query returning only bottom-level nodes with their resolved descriptions is shown below.

SELECT asset_hierarchy_id,
       name,
       description,
       parent_hierarchy_id,
       depreciation_start_date,
       asset_id
FROM   apps.fa_asset_hrchy_details_v
WHERE  lowest_level_flag = 'Y'
ORDER  BY parent_hierarchy_id, name;

A recursive traversal using CONNECT BY can be used to print the hierarchy tree, leveraging PARENT_HIERARCHY_ID:

SELECT LEVEL,
       asset_hierarchy_id,
       parent_hierarchy_id,
       name,
       lowest_level_flag,
       asset_id
FROM   apps.fa_asset_hrchy_details_v
START WITH parent_hierarchy_id IS NULL
CONNECT BY PRIOR asset_hierarchy_id = parent_hierarchy_id;

Because the view is defined in the APPS schema, it is accessible to any responsibility granted the standard APPS synonyms, and it should be treated strictly as a read-only reporting object. No DML should ever be issued against it, since it is a non-updatable join view over Fixed Assets base tables.