Search Results op_comp

Overview

APPS.EAM_OP_COMP is a PL/SQL package in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its name reflects its central role: the management of operation completion processing for EAM work orders. In EAM, a work order represents maintenance or repair activity performed against an asset; each work order carries one or more operations (routing steps), and each operation must be completed with associated transaction data such as completion quantities, resource usage, and status changes. EAM_OP_COMP encapsulates the business logic that validates and records these operation completions, providing a controlled programmatic interface so that completion transactions are applied consistently regardless of the calling context.

The package holds a VALID status in the APPS schema and is classified as an "OTHER" API type. It exposes two documented program units: OP_COMP and GET_OP_DEFAULTS. In Oracle EBS 12.1.1 and 12.2.2, the package is used alongside the public transaction API EAM_WORKORDERTRANSACTIONS_PUB and the EAM Operations JSP user interface, which both depend on it.

Key Procedures and Functions

OP_COMP — The principal completion routine. It performs the core operation-completion processing for an EAM work order operation: applying the completion transaction, updating operation and work order state, and driving any dependent data such as asset status history and workflow. It is the internal counterpart to the public completion APIs invoked from the EAM transaction layer.

GET_OP_DEFAULTS — A retrieval routine that supplies default values for an EAM operation. It is typically invoked by the user interface before a completion transaction is entered, so the form or JSP can pre-populate operation attributes derived from setup and work order data, reducing manual entry and enforcing standards.

No parameter lists are documented in the ETRM metadata; accordingly, only the purposes above are asserted.

Tables Accessed

The package operates across EAM and WIP tables (reached through APPS synonyms):

• EAM_OP_COMPLETION_TXNS and EAM_OP_COMPLETION_TXNS_S — the base and sequence tables holding operation completion transaction records written by the completion logic.
• EAM_ASSET_STATUS_HISTORY and EAM_ASSET_STATUS_HISTORY_S — capture asset status transitions triggered when a completion affects asset condition or availability.
• EAM_WORK_ORDER_DETAILS — the work order header/detail data that the completion validates against.
• WIP_OPERATIONS, WIP_OPERATION_NETWORKS, WIP_ENTITIES, and WIP_DISCRETE_JOBS — EAM work orders are built on WIP structures, so operation, network, entity, and discrete job records are read and updated during completion.
• WIP_EAM_PARAMETERS — provides EAM-specific system parameters that govern completion behavior.
• EAM_ENABLE_WORKFLOW and EAM_WORKFLOW_EVENT_S — control and queue workflow events raised by completion processing.
• WF_PARAMETER_LIST_T — the Oracle Workflow parameter list type used when passing event attributes.
• DUAL and PLITBLM — standard utility references (PLITBLM is the PL/SQL integer table type used for list handling).

Usage Notes

EAM_OP_COMP is not an end-user entry point; it is invoked indirectly. The EAM Operations JSP calls into it to display defaults and to submit completions from the web UI, while EAM_WORKORDERTRANSACTIONS_PUB, the documented public transactions API, delegates to it for the underlying completion work. Integrators and customers writing custom extensions should prefer the public PUB API and treat EAM_OP_COMP as an internal dependency, since its signature is not published as a supported interface. Typical invocation is therefore from the EAM work order completion screens, the public transaction API, or from custom PL/SQL that already operates through the supported EAM interfaces. Because it writes both EAM completion tables and WIP operation records and can raise workflow events, it must be called within a transaction that handles commit and rollback appropriately.