Search Results validate_parent

Overview

The APPS.FA_ASSET_HIERARCHY_PVT package is a private PL/SQL API within the Oracle E-Business Suite Fixed Assets module (FA). It provides the internal programmatic foundation for creating and managing hierarchical relationships between assets, including parent-child associations, attribute derivation across hierarchy levels, and the automatic distribution of asset costs to the hierarchy's distribution sets. The package is classified as a PVT (private) API, meaning it is not intended for direct invocation by external integrators; instead, it is consumed by the public Fixed Assets APIs and by the forms and concurrent programs that govern asset hierarchy processing.

The hierarchy feature in Oracle Assets allows organizations to model roll-up structures in which a parent asset aggregates attribute and financial data from its children. FA_ASSET_HIERARCHY_PVT contains the core validation and derivation logic that enforces these relationships and ensures consistency between the hierarchy definition tables and the underlying asset records in FA_ADDITIONS.

Key Procedures and Functions

• VALIDATE_PARENT — Determines whether a supplied parent hierarchy identifier is a valid parent within the given book type code. This is the routine most directly associated with the validate_parent search term, and it underpins parent selection when assets are added or reassigned within a hierarchy.
• ADD_ASSET — Adds an asset to a hierarchy using the asset header record and asset hierarchy record structures provided through the FA_API_TYPES package. It persists the new hierarchy membership for the asset.
• DERIVE_ASSET_ATTRIBUTE — Derives asset attributes (header, descriptive, category, hierarchy, financial, and distribution attributes) for a hierarchy member. It accepts a derivation type and calling function parameter to control which attributes are recalculated, and returns the updated records via IN OUT NOCOPY parameters.
• LOAD_DISTRIBUTIONS — Populates the asset distribution table based on a hierarchy distribution set identifier and the number of asset units. It is responsible for expanding the hierarchy-level distribution definition into individual asset-level distribution lines.
• CREATE_BATCH — Creates a mass update batch for hierarchy-driven processing, using the asset header record, transaction record, and hierarchy options record as inputs.

All five functions return a BOOLEAN status, and the source header identifies version 120.1 as the shipped implementation.

Tables Accessed

Access to base tables is performed through APPS synonyms and includes:

• FA_ADDITIONS — the primary asset book table, read and written when assets are added to a hierarchy and when derived attributes are applied.
• FA_ASSET_HIERARCHY — stores the parent-child membership relationships validated by VALIDATE_PARENT and created by ADD_ASSET.
• FA_ASSET_HIERARCHY_PURPOSE — defines the purpose or usage context of a hierarchy assignment.
• FA_HIERARCHY_DISTRIBUTIONS — holds the hierarchy-level distribution definitions expanded by LOAD_DISTRIBUTIONS.
• FA_MASS_UPDATE_BATCH_HEADERS — records batch headers produced by CREATE_BATCH for subsequent mass update processing.
• PLITBLM — the standard Oracle Applications PL/SQL table used for transient collection handling.

Usage Notes

As a PVT-classified package, FA_ASSET_HIERARCHY_PVT is not part of the supported public API surface. It is referenced by two other packages within the Fixed Assets schema, which act as the callers for its validation, derivation, and batch-creation routines. Typical invocation occurs when an asset is created, adjusted, or transferred within a hierarchy-enabled book, and when a hierarchy mass update or distribution run is initiated from the Assets workbench or a concurrent program.

Custom code should not call these routines directly; developers requiring hierarchy functionality should use the public FA APIs, which internally route to this package. Because the package reads and writes core FA tables, direct invocation risks bypassing validation and derivation sequencing. The package is versioned for both 12.1.1 and 12.2.2, and its behavior is consistent across those releases.