Search Results fa_asset_hierarchy_pvt




Overview

The APPS.FA_ASSET_HIERARCHY_PVT package body implements the private (PVT) programmatic layer supporting the Oracle E-Business Suite Asset Hierarchy feature within Oracle Assets. The Asset Hierarchy functionality allows organizations to model parent-child relationships across asset units—an essential capability for capital projects, CIP rollups, group asset structures, and asset lifecycle roll-up reporting. This private package encapsulates the validation, attribute derivation, distribution loading, and batch creation logic used when constructing or maintaining hierarchies through the concurrent manager or through the seeded public CUA (Common User Access) wrapper packages.

Because it is a private API (classification PVT), the package is not intended for direct invocation by external customizations. It is instead called by the public API layer, notably FA_CUA_ASSET_APIS and FA_CUA_HIERARCHY_PKG, both of which are listed as dependencies. This establishes a clear separation: the public CUA packages accept caller input and enforce public-API conventions, while FA_ASSET_HIERARCHY_PVT performs the internal procedural work of validating, deriving, and persisting hierarchical data.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within this package body:

  • VALIDATE_PARENT — Verifies the eligibility and correctness of a proposed parent asset relative to a child asset, ensuring that hierarchy assignments do not violate structural or business constraints before persistence.
  • ADD_ASSET — Inserts a specific asset into the hierarchy, establishing the parent-child linkage in the underlying hierarchy tables and applying any derived attributes.
  • DERIVE_ASSET_ATTRIBUTE — Computes and returns asset attributes retrieved or inferred from the hierarchy context. This logic is closely tied to FA_CUA_DERIVE_ASSET_ATTR_PKG, a listed dependency, which supplies shared attribute-derivation rules.
  • LOAD_DISTRIBUTIONS — Populates hierarchy distribution records into FA_HIERARCHY_DISTRIBUTIONS, supporting the allocation and roll-up treatment of asset costs across hierarchy members.
  • CREATE_BATCH — Constructs a mass-update batch header in FA_MASS_UPDATE_BATCH_HEADERS, enabling approved hierarchy changes to be processed in bulk rather than row-by-row.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • FA_ADDITIONS — The core asset book table; the package reads asset records when validating parents and adding assets to a hierarchy.
  • FA_ASSET_HIERARCHY — Stores the active parent-child asset relationships established or validated by the package.
  • FA_ASSET_HIERARCHY_PURPOSE — Defines the business purpose or context of a hierarchy (for example, reporting, rollup, or project tracking), consulted during validation and derivation.
  • FA_HIERARCHY_DISTRIBUTIONS — Receives distribution rows loaded by LOAD_DISTRIBUTIONS.
  • FA_MASS_UPDATE_BATCH_HEADERS — Target of CREATE_BATCH for batch-mode hierarchy updates.
  • PLITBLM — The standard PL/SQL index-by table of character strings used for passing row or column lists between modules.

Usage Notes

FA_ASSET_HIERARCHY_PVT is not invoked directly by end users or by custom code. It is reached indirectly through the public CUA packages FA_CUA_ASSET_APIS and FA_CUA_HIERARCHY_PKG, typically during concurrent program execution or form-driven asset hierarchy maintenance. The package also references FND_GLOBAL (for session and user context), FND_LOG (for debug and logging), FND_REQUEST (for submitting concurrent requests), and FA_SRVR_MSG (for server-side message resolution). Customizations requiring hierarchy manipulation should call the public CUA wrappers rather than this private body; the ETRM records that this package is referenced by two other packages and is not referenced by any higher-level database object beyond the public API layer, consistent with its role as an internal implementation component of the Asset Hierarchy feature set.