Search Results permit_clearance_association

Overview

The APPS.EAM_SAFETY_ASSOCIATION_PVT package body implements the private business logic that governs safety-related associations within Oracle Enterprise Asset Management (eAM). Its central responsibility is to create, validate, and persist the relationships that link permits, clearances, work orders, and asset isolations to one another and to the maintenance activities they control. In eAM, a work permit authorizes a specific task to proceed, while a clearance certifies that the relevant isolation points have been secured. The package enforces the integrity of these linkages so that a work order cannot be executed against equipment that has not been properly isolated and cleared.

The package is part of the eAM safety framework alongside EAM_PROCESS_SAFETY_PUB, and its private status reflects its role as an internal implementation layer invoked by the public safety processing APIs rather than by external callers directly.

Key Procedures and Functions

The package exposes five documented procedures. PERMIT_CLEARANCE_ASSOCIATION, which the user searched for as permit_clearance_association, processes the association between permits and clearances, accepting a table of safety association records and returning a message token table together with a return status. It opens a savepoint at the start, retrieves the next value from EAM_SAFETY_ASSOCIATIONS_S, and honours the eAM debug flag via EAM_PROCESS_WO_PVT.get_debug.

CLEARANCE_WO_ASSOCIATION establishes the link between an approved clearance and the work order it authorizes. PERMIT_WORK_ORDER_ASSOCIATION performs the equivalent function for permits. ASSET_ISOLATION_ASSOCIATION associates isolation records with the asset or asset instance being worked upon. VALIDATE_TRANSACTION_TYPE performs the precondition check that confirms the supplied association is a valid, supported transaction type before any data is committed. The presence of four package-level exceptions confirms the error model: association, existence, transaction, and duplicate-association failures.

Tables Accessed

• EAM_SAFETY_ASSOCIATIONS — the primary table holding the association records inserted and queried by the procedures.
• EAM_SAFETY_ASSOCIATIONS_S — the sequence supplying surrogate keys for new association rows.
• EAM_WORK_PERMITS and EAM_WORK_CLEARANCES — the permit and clearance headers being linked to work.
• EAM_ISOLATIONS — isolation points associated with assets for safety lockout purposes.
• CSI_ITEM_INSTANCES — the installed asset instance used to resolve the physical equipment concerned.
• WIP_ENTITIES — the work order entity referenced by permit and clearance associations.
• PLITBLM — the standard EBS message repository used for error token resolution.

Usage Notes

Because this is a PVT (private) package, it is not intended for direct invocation by customers or third-party code. It is invoked internally by EAM_PROCESS_SAFETY_PUB and by the four documented packages that reference it, typically during work order release, permit approval, and clearance approval workflows. From a functional standpoint, users trigger this logic through the eAM work order and safety-related forms and through concurrent programs that process safety associations in bulk. Custom code should call the public safety APIs, which in turn delegate to this body, rather than calling the private procedures directly.