Search Results update_eam_genealogy

Overview

WIP_EAM_GENEALOGY_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that maintains the genealogy relationships between parent and child assets during Enterprise Asset Management (EAM) rebuild activities. In the EAM model, a rebuild represents the disassembly of a parent asset into its constituent components and the subsequent reassembly of those components into a rebuilt asset, preserving an auditable parent-child chain of custody. This package supplies the genealogy specifications that support that process, and its routines are designed to be called in conjunction with the inventory transaction APIs so that a miscellaneous transaction is recorded before the genealogy linkage itself is written. The package is declared AUTHID CURRENT_USER, meaning that execution privileges are resolved against the calling user rather than the package owner, which is standard for EAM private APIs invoked from higher-level EAM flows.

Key Procedures and Functions

• CREATE_EAM_GENEALOGY — Establishes a new genealogy link between a child object and its parent. It accepts identifiers for the child and parent (object ID, serial number, inventory item, and organization), subinventory and locator context, the date range for which the relationship is active, and the originating and updating transaction identifiers. The p_from_eam flag distinguishes calls originating from the EAM module. Output parameters return the standard concurrent-style message count, message data, and return status.
• UPDATE_EAM_GENEALOGY — Modifies an existing genealogy record. This is the procedure most commonly associated with the search term "update_eam_genealogy." It identifies the target record through the object type and object ID (or serial number), plus inventory item and organization, and allows the subinventory and locator attributes of the relationship to be changed. Like the create routine, it observes the standard API version, initialization, validation-level, and commit conventions.
• GET_LOCATORCONTROL_CODE — Retrieves the locator control code, which determines whether a locator must be supplied for a given inventory organization and item. This supports validation logic within the genealogy routines.
• DYNAMIC_ENTRY_NOT_ALLOWED — A validation helper that rejects locator values entered dynamically when the locator control setup does not permit it.

Tables Accessed

The package reads and writes MTL_OBJECT_GENEALOGY, the core repository of parent-child object relationships. It references CSI_ITEM_INSTANCES for installed base instance data and MTL_SERIAL_NUMBERS for serialized asset identification. Inventory setup and validation draw on MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_ITEM_SUB_INVENTORIES, and MTL_SYSTEM_ITEMS. WIP_DISCRETE_JOBS and WIP_EAM_PARAMETERS supply work order and EAM configuration context. DUAL is used for trivial single-row queries.

Usage Notes

WIP_EAM_GENEALOGY_PVT is a private (PVT) package and is not intended as a public integration point. It is referenced by eight other packages, which indicates it is invoked internally by higher-level EAM rebuild and genealogy APIs. Direct invocation typically occurs from EAM rebuild forms or from custom PL/SQL that must repair or adjust genealogy records, most frequently through UPDATE_EAM_GENEALOGY when a child component's subinventory or locator assignment changes. Callers must supply a valid API version, honor the FND_API initialization and commit conventions, and check x_return_status and the message outputs before committing.