Search Results eam_work_orders




Overview

EAM_REQUEST_UTILITY_PVT is a private PL/SQL utility package belonging to the Oracle Enterprise Asset Management (EAM) module, the maintenance and work order solution within Oracle E-Business Suite. Its primary business function is to support the request-to-work-order lifecycle: converting and linking maintenance work requests into executable work orders, associating service requests with work order entities, cleaning up related records, and propagating attachments from requests to the resulting work orders. It acts as a supporting layer beneath the public EAM work order APIs and is not intended for direct invocation by external code. The package operates as a dependent of the EAM process work order framework, referencing standard EAM request record structures such as EAM_PROCESS_WO_PUB.eam_request_rec_type for its input context.

Key Procedures and Functions

  • INSERT_ROW — Creates or updates the association between a work request and a work order. For request type 1 (work request processing), it updates the existing WIP_EAM_WORK_REQUESTS row, setting the wip_entity_id and advancing the work request status to the designated "In Process/Converted" status (work_request_status_id = 4), along with standard audit columns populated from FND_GLOBAL. For request type 2 (service request processing), it inserts a new row into EAM_WO_SERVICE_ASSOCIATION to link the work order entity to the originating service request, capturing the association identifier, maintenance organization, wip_entity_id, service request ID, enable flag, and the full set of descriptive flexfield attribute columns. The procedure returns a status flag and a message token table for error reporting.
  • DELETE_ROW — Removes association records created by the package, used when a request-to-work-order linkage is reversed or cleaned up (for example, on cancellation or rollback of a conversion). This keeps the WIP_EAM_WORK_REQUESTS and EAM_WO_SERVICE_ASSOCIATION data consistent with the state of the source requests.
  • COPY_WR_ATTACHMENT_TO_WO — Copies attachments attached to the work request over to the corresponding work order, so that documentation, images, or supporting files captured against the request remain available on the generated work order. It works in conjunction with the FND_ATTACHED_DOCUMENTS data model.

Tables Accessed

  • WIP_EAM_WORK_REQUESTS — The core EAM work request table. INSERT_ROW updates the request row to link it to the newly created work order entity and to advance its status. This table is central to the work order conversion process.
  • EAM_WO_SERVICE_ASSOCIATION — Stores the relationship between work order entities and service requests. INSERT_ROW and DELETE_ROW maintain records here, including the enable flag fix and flexfield attributes.
  • FND_ATTACHED_DOCUMENTS — The standard Oracle attachment repository. COPY_WR_ATTACHMENT_TO_WO reads work request attachments and inserts equivalent rows for the target work order.

Usage Notes

As an API classification of "PVT" (private), EAM_REQUEST_UTILITY_PVT is not exposed to end users through standard application forms or concurrent program parameters directly. It is instead invoked internally by the EAM process work order public layer and by at least one other dependent package, which orchestrates work order creation, service request integration, and attachment propagation. The procedures are typically called within the same transaction that creates or converts a work order, ensuring the request status update, association insert/delete, and attachment copy are committed atomically. Custom development should avoid calling this package directly; instead, developers should use the public EAM work order APIs (such as EAM_PROCESS_WO_PUB) and let those routines delegate to this private utility. Understanding this package is relevant when troubleshooting why a work request did not convert to a work order, why a service request is not linked to a work order, or why attachments are missing after work order generation.