Search Results permit_work_order_association




Overview
Explore in AI Chat

Overview

APPS.EAM_SAFETY_ASSOCIATION_PVT is a private PL/SQL package in Oracle E-Business Suite Enterprise Asset Management (EAM). It supports the safety-association layer of the EAM safety framework, which links permits, clearances, asset isolations, and work orders so that maintenance work is executed only when the required safety controls are in place. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, a standard convention for EAM private packages that are invoked from public APIs such as EAM_PROCESS_SAFETY_PUB.

The declared source header identifies the file as EAMVSAAS.pls and carries the ETRM copyright marker dated 2011. Because the package is classified as PVT (private), it is not intended for direct customer invocation; it is the implementation layer beneath the public safety-association APIs and is referenced by four other packages. Common behavior for this package includes validating that the transaction type supplied by a caller is consistent with the safety association being processed before any association rows are inserted or updated.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions in this package:

  • PERMIT_CLEARANCE_ASSOCIATION — Processes the association between a permit and a clearance. The source excerpt shows the parameter list as a permit-clearance association table typed against EAM_PROCESS_SAFETY_PUB.eam_safety_assoc_tbl_type, together with a message-token table and a return-status variable. Comment text above the declaration refers to "CLEARANCE_PERMIT_ASSOCIATION."
  • CLEARANCE_WO_ASSOCIATION — Processes the association between a clearance and a work order, using a clearance-to-work-order association table.
  • PERMIT_WORK_ORDER_ASSOCIATION — Processes the association between a permit and a work order, using a permit-to-work-order association table.
  • ASSET_ISOLATION_ASSOCIATION — Processes the association of an asset isolation record. The parameter list is not reproduced in the excerpt and is therefore not documented here.
  • VALIDATE_TRANSACTION_TYPE — Validates that the transaction type supplied during safety-association processing is valid for the requested operation. This is the entry point most commonly searched for by implementers diagnosing safety-association errors. The precise parameter list is not provided in the ETRM metadata excerpt and must be confirmed against the deployed package specification.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • EAM_SAFETY_ASSOCIATIONS — The base transactional table holding safety-association records created by the association procedures.
  • EAM_SAFETY_ASSOCIATIONS_S — The corresponding sequence or surrogate-key table used to generate unique association identifiers.
  • EAM_WORK_PERMITS — Stores work permit records that are linked to clearances and work orders.
  • EAM_WORK_CLEARANCES — Stores clearance records associated with permits and work orders.
  • EAM_ISOLATIONS — Stores asset isolation records used by asset-isolation association processing.
  • CSI_ITEM_INSTANCES — Supplies the installed-base (asset) instance records against which associations are validated.
  • WIP_ENTITIES — Supplies work order entity information used when associating safety records to work orders.
  • PLITBLM — A standard PL/SQL index-by table utility used internally for bulk collections handling.

Usage Notes

EAM_SAFETY_ASSOCIATION_PVT is normally invoked indirectly. The public wrapper EAM_PROCESS_SAFETY_PUB calls the association procedures after the calling form or concurrent program passes a safety-association collection, message-token table, and return-status variable. Typical callers include EAM Work Order and Permit/Clearance forms, asset-isolation maintenance screens, and custom extensions that must attach a permit, clearance, or isolation to a work order.

Because VALIDATE_TRANSACTION_TYPE is a private validation helper, errors such as invalid transaction type during safety-association creation usually originate here and surface through the message-token table. Custom code should call the public API rather than this package, check the returned status, and use the message tokens for diagnostics. Confirm the exact parameter signature against the deployed specification in EBS 12.1.1 or 12.2.2 before writing any direct call.