Search Results eam_wo_comp_utility_pvt




Overview

APPS.EAM_WO_COMP_UTILITY_PVT is a private (PVT) PL/SQL package within the Oracle Enterprise Asset Management (EAM) module. Its documented purpose is to encapsulate the low-level write operations that persist work order component and completion data into the underlying EAM and WIP transaction tables. The package forms part of the internal implementation layer that supports the public work order processing API, EAM_PROCESS_WO_PUB, and serves as the utility engine behind component-level DML for EAM work orders.

The package header (EAMVWCUS.pls, version 120.1, dated October 2005) carries the Oracle EAM copyright and is classified as a private package, indicating it is not intended for direct invocation by customer code. It is referenced by one other package, which is the expected coupling for a utility that is called from an orchestration or processing layer rather than exposing a public interface.

Key Procedures and Functions

  • Perform_Writes — The primary entry point. It accepts an EAM work order component record based on the EAM_PROCESS_WO_PUB.eam_wo_comp_rec_type structure and determines the appropriate insert or update action, returning a status code and a message token table for error reporting.
  • Insert_Row — Creates a new work order component row. Like the other procedures, it takes the EAM work order component record and returns a return status and message token table.
  • Update_Row — Modifies an existing work order component row, using the same record-based input and token-based error output convention.

The package also declares two PL/SQL types, Lot_Serial_Rec_Type and Lot_Serial_Tbl_Type, used to carry lot number, serial number, and quantity information, plus the INVENTORY_ITEM_NULL constant. All procedures share a consistent signature pattern: an IN record parameter, an OUT NOCOPY return status, and an OUT NOCOPY message token table drawn from EAM_ERROR_MESSAGE_PVT.

Tables Accessed

  • EAM_WORK_ORDER_DETAILS and WIP_EAM_WORK_REQUESTS — the core work order header and EAM request records against which component operations are performed.
  • EAM_JOB_COMPLETION_TXNS — captures job completion transactions associated with work order components.
  • EAM_ASSET_STATUS_HISTORY and EAM_ASSET_STATUS_HISTORY_S — the asset status history base table and its sequence, recording status transitions triggered by completion activity.
  • MTL_MATERIAL_TRANSACTIONS_S — the material transaction sequence used when generating inventory transactions for component issues or completions.
  • MTL_SYSTEM_ITEMS — validates and resolves inventory item definitions for components.
  • WIP_DISCRETE_JOBS — the discrete job record linked to EAM work order execution.
  • EAM_WO_STATUSES_V — the status view used to validate or derive work order status transitions.
  • DUAL and PLITBLM — the standard single-row utility table and the PL/SQL index-by table used for internal processing.

Usage Notes

Because EAM_WO_COMP_UTILITY_PVT is classified as a private package, it is invoked indirectly rather than by end users or typical custom extensions. Callers reach it through the public work order processing layer, most commonly EAM_PROCESS_WO_PUB, which in turn is driven by EAM work order forms, the work order completion and component transaction flows, and any concurrent program or interface that performs bulk work order component updates.

The consistent record-based interface and the shared EAM_ERROR_MESSAGE_PVT token table mean that error handling is centralized: callers pass an EAM work order component record and inspect the returned status and message tokens rather than trapping individual exceptions. This pattern supports both single-record operations originating from the EAM Work Orders form and set-based processing in batch or interface contexts. Custom development should target the public API layer; direct calls to this private package are inadvisable because its signature and internal behavior are subject to change across EBS releases, including 12.1.1 and 12.2.2.