Search Results raise_workflow_status_pend_cls




Overview
Explore in AI Chat

Overview

EAM_WORKORDERTRANSACTIONS_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It provides the business logic required to complete Enterprise Asset Management (EAM) work orders and their operations, applying the associated material, resource, and accounting transactions. In the EAM execution flow, a work order releases to the shop floor, work is performed against its operations, and the order is finally completed. This package centralizes the completion transaction processing for that final step, together with several supporting utilities that update work order attributes and drive workflow status.

The package belongs to the standard EBS API classification PUB, meaning it is a supported, externally callable interface intended for use by other program units and custom extensions rather than a private implementation detail. It is therefore a key integration point for organizations automating maintenance and asset work order completion outside of the standard EAM forms.

Key Procedures and Functions

The ETRM documentation records six public program units:

  • COMPLETE_WORK_ORDER — Performs the completion of an entire EAM work order, including the associated operation and material transaction processing required to close the order.
  • COMPLETE_OPERATION — Completes an individual operation on a work order, supporting partial progress where the full order is not yet ready for closure.
  • SET_MANUAL_REB_FLAG — Sets the manual rebalance flag, controlling whether rebalancing of requirements is performed manually rather than by the standard process.
  • SET_OWNING_DEPARTMENT — Assigns or updates the owning department associated with the work order or operation.
  • UPDATE_EWOD — Updates records in the EAM work order details structure, refreshing the detail-level information used during completion.
  • RAISE_WORKFLOW_STATUS_PEND_CLS — Raises the workflow status to pending close, initiating or advancing the associated workflow so the work order proceeds toward final closure.

Tables Accessed

The package reads and writes a broad set of EAM, WIP, inventory, and financial tables through APPS synonyms. Completion transaction detail is stored in EAM_JOB_COMPLETION_TXNS and EAM_OP_COMPLETION_TXNS, while EAM_WORK_ORDER_DETAILS holds the work order header and line detail updated by UPDATE_EWOD. WIP tables — WIP_DISCRETE_JOBS, WIP_OPERATIONS, WIP_ENTITIES, and WIP_DJ_CLOSE_TEMP — support integration of EAM work orders with the discrete job model used for costing and closure, and BOM_DEPARTMENTS supplies department validation for SET_OWNING_DEPARTMENT.

Inventory and item information comes from MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS. Accounting period validation relies on ORG_ACCT_PERIODS, and PLITBLM is used as the PL/SQL table structure for bulk data handling. Together these tables reflect the package's role in driving both the transactional completion and the cost/accounting consequences of that completion.

Usage Notes

The package depends on FND_API (for the standard API return status, message, and error handling conventions), FND_GLOBAL (for session context such as user and responsibility identification), and the SYS.STANDARD datatype definitions. It is referenced by several other program units, including AHL_COMPLETIONS_PVT, AHL_WIP_JOB_PVT, EAM_COMPLETION, EAM_WO_COMP_UTILITY_PVT, and WIP_JOBCLOSE_PRIV, which indicates that it underpins maintenance completion processing across the EAM and depot repair (AHL) modules.

Typical invocation of COMPLETE_WORK_ORDER and COMPLETE_OPERATION occurs from the EAM work order completion forms and from concurrent or background processes that submit work order completion transactions. Because the package is classified as a public API, custom code should call these procedures rather than performing direct DML on the underlying completion tables, ensuring that validation, transaction records, and workflow status updates remain consistent with standard EBS behavior. Applications integrating EAM completions with external systems should also use these entry points so that inventory, WIP, and accounting period checks are enforced uniformly.