Search Results eam_workflow_event_s

Overview

APPS.EAM_OP_COMP is a valid PL/SQL package body in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its business function centers on recording and validating the completion of operations within EAM work orders, which represent maintenance and repair activities performed against assets. The package bridges the EAM work order execution model with the underlying Oracle Work in Process (WIP) structures that store discrete jobs, operations, and operation networks, since EAM leverages WIP entities as its execution engine for asset maintenance work.

A significant portion of the package's dependency footprint relates to EAM workflow integration. The presence of EAM_ENABLE_WORKFLOW, EAM_WORKFLOW_EVENT_S, WF_CORE, WF_EVENT, and WF_PARAMETER_LIST_T indicates that EAM_OP_COMP raises and propagates business events when operations reach completion, delegating event delivery to the Oracle Workflow event system. This allows downstream subscribers, notifications, and approval flows to react to shop-floor completion activity. This dependency on EAM_WORKFLOW_EVENT_S is directly relevant to users searching for that object.

Key Procedures and Functions

ETRM documents two program units within the package body:

OP_COMP — The principal routine for processing an operation completion. It drives the update of EAM completion transaction records and the corresponding WIP operation and entity status, and it is responsible for the workflow event signaling associated with the completion action. It also interacts with asset status history, implying that completion can trigger an asset status transition recorded for audit and reporting.
GET_OP_DEFAULTS — A retrieval routine that returns default attribute values for an operation, supporting data entry and validation paths used by the completion flow and by callers that need WIP/EAM operation defaults before initiating a transaction.

Parameter lists are not reproduced here; only the documented program names and their functional intent are asserted.

Tables Accessed

The package reads and writes the following documented objects through APPS synonyms:

EAM_OP_COMPLETION_TXNS and EAM_OP_COMPLETION_TXNS_S — Store the operation completion transaction headers and their identifier sequence; the core persistence target of OP_COMP.
EAM_ASSET_STATUS_HISTORY and EAM_ASSET_STATUS_HISTORY_S — Capture asset status changes resulting from completion, providing the audit trail and sequence.
EAM_WORK_ORDER_DETAILS — Supplies work order context associated with the operation being completed.
EAM_WORKFLOW_EVENT_S — Supports generation of workflow event identifiers for events raised during completion.
EAM_ENABLE_WORKFLOW — Consulted to determine whether workflow event generation is enabled.
WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS, WIP_OPERATION_NETWORKS, WIP_EAM_PARAMETERS — Provide and update the underlying WIP job, entity, operation, and network records, and read EAM-specific WIP parameters.
WF_PARAMETER_LIST_T, DUAL, PLITBLM — Support workflow parameter list construction and standard PL/SQL utility operations.

Usage Notes

EAM_OP_COMP is not referenced by any database object, so it is invoked directly rather than through a wrapping database trigger or view. Typical invocation occurs from EAM work order execution forms and from concurrent or background processes that post operation completions, and from custom extensions that must drive the same completion logic programmatically. Callers should expect the package to update EAM completion transaction and asset status history tables while propagating changes into WIP, and to conditionally publish Oracle Workflow events. The package relies on FND_API, FND_GLOBAL, FND_MESSAGE, EAM_DEBUG, APP_EXCEPTION, and WF_EVENT/WF_CORE for error handling, message resolution, debugging, and workflow dispatch, consistent with Oracle's standard API conventions.

SEQUENCE: EAM.EAM_WORKFLOW_EVENT_S 12.2.2
owner:EAM, object_type:SEQUENCE, object_name:EAM_WORKFLOW_EVENT_S, status:VALID,
SYNONYM: APPS.EAM_WORKFLOW_EVENT_S 12.1.1
owner:APPS, object_type:SYNONYM, object_name:EAM_WORKFLOW_EVENT_S, status:VALID,
SYNONYM: APPS.EAM_WORKFLOW_EVENT_S 12.2.2
owner:APPS, object_type:SYNONYM, object_name:EAM_WORKFLOW_EVENT_S, status:VALID,
SEQUENCE: EAM.EAM_WORKFLOW_EVENT_S 12.1.1
owner:EAM, object_type:SEQUENCE, object_name:EAM_WORKFLOW_EVENT_S, status:VALID,
12.1.1 DBA Data 12.1.1
PACKAGE BODY: APPS.EAM_OP_COMP 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_OP_COMP, status:VALID,
12.1.1 DBA Data 12.1.1
PACKAGE BODY: APPS.EAM_JOBCLOSE_PRIV 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_JOBCLOSE_PRIV, status:VALID,
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
PACKAGE BODY: APPS.EAM_JOBCLOSE_PRIV 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_JOBCLOSE_PRIV, status:VALID,
PACKAGE BODY: APPS.EAM_OP_COMP 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_OP_COMP, status:VALID,
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1
PACKAGE BODY: APPS.EAM_COMPLETION 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_COMPLETION, status:VALID,
PACKAGE BODY: APPS.EAM_COMPLETION 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_COMPLETION, status:VALID,
PACKAGE BODY: APPS.EAM_PROCESS_WO_PVT 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_PROCESS_WO_PVT, status:VALID,
PACKAGE BODY: APPS.EAM_PROCESS_WO_PVT 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:EAM_PROCESS_WO_PVT, status:VALID,
APPS.EAM_COMPLETION dependencies on EAM_WORKFLOW_EVENT_S 12.2.2
APPS.EAM_OP_COMP dependencies on EAM_WORKFLOW_EVENT_S 12.2.2
APPS.EAM_PROCESS_WO_PVT dependencies on EAM_WORKFLOW_EVENT_S 12.1.1
APPS.EAM_COMPLETION dependencies on EAM_WORKFLOW_EVENT_S 12.1.1
APPS.EAM_PROCESS_WO_PVT dependencies on EAM_WORKFLOW_EVENT_S 12.2.2
APPS.EAM_JOBCLOSE_PRIV dependencies on EAM_WORKFLOW_EVENT_S 12.1.1
APPS.EAM_JOBCLOSE_PRIV dependencies on EAM_WORKFLOW_EVENT_S 12.2.2
APPS.EAM_OP_COMP dependencies on EAM_WORKFLOW_EVENT_S 12.1.1
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1