Search Results eam_work_order_route_s

Overview

EAM_WO_CHANGE_STATUS_PVT is a private PL/SQL package body in the APPS schema that encapsulates the internal logic Oracle Enterprise Asset Management (EAM) uses to transition work orders between lifecycle statuses and to manage the associated procurement and closeout operations. It is classified as a PVT (private) API, meaning it is not intended as a public integration surface; it is invoked by other EAM packages and by the EAM work order forms and concurrent processes. The package provides the core status-change engine for EAM work orders, coordinating updates to WIP entities, asset hierarchy records, and purchasing documents that must remain synchronized when a work order is released, completed, or closed. In a 12.1.1 / 12.2.2 environment it appears as a VALID object owned by APPS and is not referenced by any other database object, confirming its role as a lower-level implementation unit within the EAM module stack. The dependency list includes the public EAM packages EAM_PROCESS_WO_PVT, EAM_JOBCLOSE_PRIV, EAM_WORKORDER_UTIL_PKG, EAM_ASSET_LOG_PVT, and EAM_ERROR_MESSAGE_PVT, together with FND_API, FND_MSG_PUB, and FND_GLOBAL for the standard EBS error-handling and context framework. The user search term "eam_work_order_route_s" corresponds directly to one of the tables this package touches, EAM_WORK_ORDER_ROUTE_S, which stores the operation routing steps of an EAM work order.

Key Procedures and Functions

Three documented units are exposed in the package body:

• CHANGE_STATUS — the principal routine. It performs the actual transition of an EAM work order from one status to another, validating prerequisites, applying the corresponding WIP entity updates, and propagating dependent changes such as asset log entries and closeout handling.
• CREATE_OSP_REQ_AT_REL — creates an outside processing (OSP) requisition when a work order is released. It supports the case where a routing operation is outsourced, generating the purchasing requisition required before the operation can proceed.
• PO_REQ_EXISTS — a validation function that determines whether a purchasing requisition already exists for the work order or operation in question, preventing duplicate requisition creation during release or status-change processing.

Tables Accessed

The package reads and writes a broad set of EAM, WIP, and purchasing tables through APPS synonyms:

• EAM_WORK_ORDER_DETAILS, EAM_WORK_ORDER_ROUTE, and EAM_WORK_ORDER_ROUTE_S — work order header/detail, routing header, and routing step records that are updated as status changes propagate through the work order structure.
• EAM_WO_RELATIONSHIPS, MTL_EAM_NETWORK_ASSETS, and CSI_ITEM_INSTANCES — relationship and asset instance data used to maintain asset hierarchy and installed-base integrity.
• MTL_SYSTEM_ITEMS_B, MTL_PARAMETERS, HR_ORGANIZATION_INFORMATION, and ORG_ACCT_PERIODS — item, organization, and period validation used during status and accounting checks.
• PO_REQUISITIONS_INTERFACE_ALL, PO_REQUISITION_LINES_ALL, PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, and PO_DISTRIBUTIONS_ALL — purchasing tables used by CREATE_OSP_REQ_AT_REL and PO_REQ_EXISTS to create and verify outside processing requisitions.
• WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_OPERATIONS, WIP_OPERATION_RESOURCES, WIP_REQUIREMENT_OPERATIONS, WIP_EAM_DIRECT_ITEMS, WIP_DJ_CLOSE_TEMP (and _S), and WIP_OSP — WIP structures updated during release, completion, and close processing.

Usage Notes

Because this is a PVT package, it is invoked internally rather than called directly by customer code. Typical invocation paths include the EAM Work Order form when a user changes work order status, the EAM work order release and closeout concurrent programs, and higher-level EAM APIs such as EAM_PROCESS_WO_PVT that delegate status transitions to this body. It also participates in outside processing flows when an EAM routing operation is flagged as OSP, using CREATE_OSP_REQ_AT_REL and PO_REQ_EXISTS to ensure the correct requisition is raised. Customizations should avoid direct calls and instead use the supported public EAM APIs; changes to this package body are overwritten by EBS patching, and its dependencies on WIP_CHANGE_STATUS, WIP_CLOSE_UTILITIES, and WIP_CONSTANTS confirm that status and closeout behavior remains governed by standard WIP rules.