Search Results eam_process_clearance_pvt




Overview
Explore in AI Chat

Overview

The APPS.EAM_PROCESS_CLEARANCE_PVT package is a private (PVT) PL/SQL API within the Oracle Enterprise Asset Management (EAM) module. Its central business function is to manage and process work clearances — the safety and permit-to-work controls that govern when maintenance work may begin, be suspended, or be completed on an asset. In the EAM safety model, a work order cannot proceed until all required clearances (lockout/tagout, isolation, permits) are established and released. This package implements the transactional logic behind those lifecycle transitions, orchestrating validation, workflow event propagation, and the copying of clearance definitions onto new work orders.

Because it is classified as a PVT package rather than a PUB (public) API, it is intended for internal consumption by other EAM components. The Oracle ETRM metadata lists it as VALID in release 12.2.2 and records that it is referenced by two other packages, confirming its role as a supporting engine rather than a directly called interface.

Key Procedures and Functions

The documented package exposes five procedures/functions:

  • PROCESS_WORK_CLEARANCE — The primary driver that processes a work clearance record, applying business rules and routing the clearance through its lifecycle states.
  • WORK_CLEARANCE — Encapsulates the core handling logic for an individual work clearance, including its state-dependent processing.
  • RAISE_WORKFLOW_EVENTS — Raises the Oracle Workflow business events associated with clearance activity, allowing downstream workflow processes and notifications to be triggered.
  • VALIDATE_TRANSACTION_TYPE — Validates the transaction type supplied to a clearance operation, ensuring only supported transaction categories are processed.
  • COPY_WORK_CLEARANCE — Copies clearance data from an existing source record to a new work clearance, supporting the template/reuse pattern common in work order creation.

Parameter signatures are not published in the documented metadata and should be obtained from the package specification in the APPS schema.

Tables Accessed

The package reads and writes several EAM and Workflow tables through APPS synonyms:

Usage Notes

EAM_PROCESS_CLEARANCE_PVT is invoked indirectly. Its documented callers are EAM_CLEARANCE_WORKFLOW_PVT and EAM_PROCESS_SAFETY_PUB (a public API), and it in turn references EAM_PROCESS_SAFETY_PUB and EAM_ERROR_MESSAGE_PVT. This dependency pattern indicates it sits beneath the public safety API and the workflow layer, responding to clearance actions initiated from the EAM work order forms or workflow activity nodes.

Typical invocation occurs when a user creates, updates, or releases a work clearance from the maintenance work order UI, or when a workflow process advances a clearance to the next state. Customizations should not call the PVT package directly; instead, developers should use the public EAM_PROCESS_SAFETY_PUB API, which mediates access to this private logic and preserves upgrade safety.