Search Results update_genealogy

Overview

The APPS.EAM_REBUILD package body supports the Enterprise Asset Management (EAM) rebuild workflow within Oracle E-Business Suite 12.1.1 and 12.2.2. In EAM, a rebuild represents the process by which a repairable asset or component is disassembled, restored, and reassembled into service, frequently creating or updating transactional records in inventory and asset repositories. This package encapsulates the server-side logic that coordinates rebuild-related transactions together with genealogy maintenance, ensuring that the relationship between components and their parent asset is preserved during the rebuild.

The package is registered in the E-Business Suite Technical Reference Manual (ETRM) metadata with an API classification of OTHER and is owned by the APPS schema. It is referenced by one additional package, indicating that it functions as a supporting utility within a larger call chain rather than as a top-level entry point. The package body carries a revision header referencing version 120.4, last modified in June 2006, and the source excerpt specifically documents changes made for "IB" concerning the update_genealogy procedure.

Key Procedures and Functions

• CREATE_REBUILD_JOB — The single procedure documented in the ETRM metadata for this package. It serves to create and register a rebuild job within Oracle EAM, establishing the work order context in which asset repair activities are executed and tracked.
• update_genealogy — Although not listed among the documented procedures in the ETRM metadata, this procedure appears in the source excerpt and is significant because the user search term "update_genealogy" refers directly to it. It accepts a temporary transaction identifier (p_tempId) and returns status and error message outputs. Its purpose is to invoke the genealogy API (WIP_EAM_GENEALOGY_PVT.UPDATE_EAM_GENEALOGY) against the serial number and item associated with a rebuild transaction, recording an asset-to-item genealogical relationship. A fix for Bug 3733049 ensured that update_eam_genealogy is called even when no serial number exists, by initializing the serial status variable. The procedure also skips the genealogy call when the serial status equals WIP_CONSTANTS.DEF_NOT_USED.

Tables Accessed

• CSI_ITEM_INSTANCES — Stores installed base instance records representing the asset instances involved in rebuild genealogy.
• EAM_ORG_MAINT_DEFAULTS — Provides EAM maintenance defaults for the organization, such as default parameters used when creating rebuild jobs.
• MTL_EAM_ASSET_ACTIVITIES — Captures asset activity records that link maintenance operations to assets.
• MTL_MATERIAL_TRANSACTIONS_TEMP — The temporary inventory transaction table queried in update_genealogy to retrieve the rebuild serial number, rebuild item ID, organization ID, and transaction date.
• MTL_PARAMETERS — Organization parameter information, used to validate or resolve organization-level settings during rebuild processing.
• MTL_SERIAL_NUMBERS — Queried to determine the current status of the rebuild serial number for a given inventory item, controlling whether the genealogy call proceeds.
• MTL_SYSTEM_ITEMS — Item master details used to validate or resolve the rebuild item identifier.

Usage Notes

EAM_REBUILD is an internal server-side package and is not typically invoked directly by end users. It is most commonly called from EAM rebuild user interfaces, transaction processors, or concurrent programs that manage rebuild job creation and asset genealogy updates. The update_genealogy procedure is invoked in the context of processing temporary material transactions, using the transaction temporary ID to locate the associated rebuild serial and item. Custom code that integrates with EAM rebuilds should call the documented CREATE_REBUILD_JOB procedure rather than interact directly with the underlying tables, and any extension involving genealogy should respect the serial status checks described above to avoid data inconsistencies.