Search Results amw_process_s

Overview

AMW_PROCESS_PVT is a private PL/SQL package body in the APPS schema that implements the business logic layer for the Process entity within Oracle E-Business Suite's Enterprise Asset Management / Maintenance Management (EAM) module. The package follows the standard EBS three-tier API architecture in which a private (PVT) body encapsulates validation, DML persistence, and locking logic, while a public wrapper package exposes the callable interface. In this design, AMW_PROCESS_PVT is invoked internally by the companion package AMW_PROCESS_PKG, which typically publishes the supported, public-facing API signatures. The private package is responsible for the actual row-level operations against the process definition tables, enforcing business rules, managing concurrency, and communicating errors through the FND message infrastructure.

The object is documented in ETRM as VALID in both Oracle EBS 12.1.1 and 12.2.2. It is not directly referenced by any database object, confirming its role as an internal implementation package rather than a shared service layer.

Key Procedures and Functions

The documented interface of AMW_PROCESS_PVT comprises nine procedures and functions that together implement a complete create, read, update, delete, and validation lifecycle for process records:

• CREATE_PROCESS — The primary creation entry point for a process record. It coordinates validation and performs the initial insert through the recursive record-level procedure.
• CREATE_PROCESS_REC — The record-level (recursive) counterpart to CREATE_PROCESS, performing the actual DML against the process tables with the assembled attribute values.
• UPDATE_PROCESS — The primary update entry point, orchestrating validation and invoking the record-level update logic.
• UPDATE_PROCESS_REC — Executes the record-level update against the process entity, applying changed attribute values.
• DELETE_PROCESS — Removes a process definition and enforces any referential or business constraints governing deletion.
• LOCK_PROCESS — Obtains a row-level lock on the process record to serialize concurrent modifications and support optimistic or pessimistic concurrency control.
• VALIDATE_PROCESS — Performs entity-level validation of the process before persistence, typically aggregating record-level checks.
• VALIDATE_PROCESS_REC — Validates the attributes of an individual process record, raising and registering FND messages when business rules are violated.
• CHECK_PROCESS_ITEMS — Verifies the presence and integrity of associated process item details, guarding against invalid or incomplete item associations.

Parameter lists are not reproduced here as they are not part of the documented metadata.

Tables Accessed

The package operates against the following tables through APPS synonyms:

• AMW_PROCESS — The principal process definition table, storing the header-level attributes of each process. This is the primary target of the create, update, delete, and lock operations.
• AMW_PROCESS_S — The translated (TL) table associated with AMW_PROCESS, holding language-specific descriptive columns. It is read and written to persist translated values alongside the base record.
• DUAL — Used for singleton queries and procedural evaluations.
• PLITBLM — The standard PL/SQL indexed-table-of-varchar2 type used for passing collections of identifiers or messages within the package logic.

Dependencies further confirm use of FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, and JTF_PLSQL_API, indicating adherence to the standard EBS API error-handling and message-stack conventions.

Usage Notes

AMW_PROCESS_PVT is not intended to be called directly by external code. It is invoked by AMW_PROCESS_PKG, which in turn may be called from EAM setup forms, concurrent programs, or custom extensions that need to create or maintain process definitions. The package has no reverse dependencies, meaning it sits at the bottom of the process API call stack. Developers integrating with process definitions should call the public package AMW_PROCESS_PKG, which delegates to the private routines described above, ensuring that validation, locking, and FND message handling remain consistent.