Search Results retrieve_asset_bom

Overview

APPS.EAM_COPY_BOM_PKG_W is a public wrapper package within the Oracle Enterprise Asset Management (eAM) module of Oracle E-Business Suite, shipped in releases 12.1.1 and 12.2.2. Its principal business purpose is to support the movement and retrieval of bill-of-material (BOM) structures between eAM asset definitions and Oracle Bills of Material / Work in Process records. In particular, the package enables the copy of an asset's component structure into a formal BOM definition, and conversely the retrieval of an asset BOM for downstream processing.

The "_W" suffix indicates that this is a wrapper layer. The header comment (EAMCPMRS.pls 120.2) confirms the file is part of the eAM copy-BOM infrastructure. The wrapper exposes strongly typed PL/SQL entry points while delegating the bulk of its work to the underlying eam_copy_bom_pkg package. It also contains a set of "Rosetta" conversion routines that translate between PL/SQL associative/collection types and Oracle's JTF_*_TABLE database collection types, which allow large multi-row datasets to be passed into and out of the eAM Java/Forms middle tier efficiently.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P2 / ROSETTA_TABLE_COPY_OUT_P2 — Conversion routines operating against the eam_copy_bom_pkg.t_bom_table type. COPY_IN_P2 marshals JTF number and varchar2 tables into the internal BOM table structure; COPY_OUT_P2 performs the reverse, extracting the internal table contents back into JTF tables for return to the caller.
• ROSETTA_TABLE_COPY_IN_P3 / ROSETTA_TABLE_COPY_OUT_P3 — Equivalent conversion routines for the component-level type eam_copy_bom_pkg.t_component_table. These marshal the component data elements (identifiers, quantities, and descriptive attributes) between JTF collection types and the internal component table.
• COPY_TO_BOM — Copies an asset's BOM structure into an Oracle Bills of Material definition. Inputs identify the organization (by id or code) and the asset (by asset number and asset group), together with the component data passed through the Rosetta P3 parameter set. It returns an x_error_code out parameter indicating success or the nature of any failure.
• RETRIEVE_ASSET_BOM — Retrieves the BOM associated with a specified asset or work-in-process context. Its parameters identify the organization, the WIP entity, the operation sequence number, and the department, and it returns the BOM rows via JTF number/varchar2 tables. This is the procedure most commonly referenced when callers search for "retrieve_asset_bom", as it is the public entry point for reading an asset BOM programmatically.

Tables Accessed

The documented metadata identifies a single referenced table, PLITBLM, accessed through an APPS synonym. PLITBLM is a standard Oracle EBS multi-purpose table used to hold temporary or persistent multi-row PL/SQL data across API and forms interactions. Its presence here reflects the package's use of collection-based data transfer: large BOM/component sets are staged in PLITBLM while the wrapper's Rosetta routines and the core eam_copy_bom_pkg logic process them. This design keeps the interface between the Java/Forms middle tier and the database within the JTF collection conventions.

Usage Notes

EAM_COPY_BOM_PKG_W is a server-side wrapper intended for programmatic invocation rather than direct end-user execution. It is typically invoked:

• From eAM forms and the associated middle-tier Java logic that manage assets and their BOM structures, particularly when a user chooses to copy an asset BOM into a manufacturing BOM.
• From concurrent programs or batch processes that migrate or synchronize asset component structures.
• From custom PL/SQL that needs to read an asset BOM — in such cases RETRIEVE_ASSET_BOM is called with organization, WIP entity, operation sequence, and department identifiers, and the returned JTF tables are consumed by the caller.

Because the package exposes collection-based parameters, callers must declare matching JTF table types in their own specification and handle the x_error_code returned by COPY_TO_BOM. Direct invocation should be validated against the target release's internal API policy, since wrapper packages are not always documented as formally supported public APIs.