Search Results amw_process_pvt_w

Overview

AMW_PROCESS_PVT is an Oracle EBS private (PVT) PL/SQL package owned by the APPS schema. It belongs to the Application Management Workbench (AMW) module, which provides the underlying infrastructure for managing setup processes and configuration items across Oracle applications. The package encapsulates the core business logic for creating, maintaining, validating, and removing process definitions stored in the AMW_PROCESS tables. Because it is classified as a PVT package, it is intended strictly for internal consumption by other AMW components and is not a published public API. The package header declares AUTHID CURRENT_USER, meaning that runtime privilege checks are performed against the invoking user rather than the package owner, and it exposes the record type process_rec_type, which mirrors the full column set of the AMW_PROCESS table, including audit columns, descriptive flexfield attributes, and process-specific fields such as significant_process_flag, standard_process_flag, approval_status, certification_status, and process_owner_id. A package-level constant, G_DEFAULT_NUM_REC_FETCH, defaults the record fetch size to 30 for internal query operations.

Key Procedures and Functions

The ETRM documentation lists nine procedures and functions within the package body. They fall into three functional groupings.

• CREATE_PROCESS_REC — Constructs or initializes a process_rec_type record prior to a create operation, ensuring default and audit values are populated.
• CREATE_PROCESS — Performs the actual insertion of a new process definition into the AMW_PROCESS tables, typically called after record construction and validation.
• UPDATE_PROCESS_REC — Prepares an existing process record for modification, populating the record structure for an update call.
• UPDATE_PROCESS — Applies changes to an existing process definition in the underlying tables.
• DELETE_PROCESS — Removes a process definition. This is the procedure most directly associated with the user's search term "delete_process" and is the supported entry point for removing process records through private AMW logic.
• LOCK_PROCESS — Acquires a row-level lock on the process record, using the standard EBS PLITBLM locking construct, to prevent concurrent modification during a transaction.
• VALIDATE_PROCESS — Executes business-rule validations against a process definition before it is committed.
• VALIDATE_PROCESS_REC — Validates the contents of a process_rec_type record structure independent of the database operation, supporting pre-commit checks in calling code.
• CHECK_PROCESS_ITEMS — Verifies that dependent or associated process items exist or are in a valid state, used to guard create, update, and delete operations.

Tables Accessed

The package references four objects through APPS synonyms. AMW_PROCESS is the primary table holding process definitions, including the significant/standard process flags, approval and certification statuses, owner, and descriptive flexfield attributes. AMW_PROCESS_S is the corresponding DFF-less or shadow/sequence table, typically used in EBS for ID generation or supplemental storage. DUAL supports scalar and sequence lookups. PLITBLM is the standard EBS locking table used by LOCK_PROCESS to implement row-level locking. All access is performed as the APPS schema through these synonyms.

Usage Notes

Because AMW_PROCESS_PVT is a private package, it is not intended to be called directly from customer extensions. It is referenced by one other documented package and is typically invoked from AMW application forms, concurrent programs, or other private AMW packages that manage process lifecycle. The DELETE_PROCESS procedure, in particular, should be reached through the sanctioned UI or public interfaces rather than invoked directly; direct invocation bypasses any higher-level validations the calling layer may enforce. The presence of separate record-level and database-level validation routines indicates a two-phase convention: callers first build and validate a record structure, optionally lock the row, then commit the change. Developers extending AMW functionality should treat the record type process_rec_type as the canonical data contract and observe the audit and object version number columns when writing any custom logic against these tables.