Search Results complete_uc_approval

Overview

APPS.AHL_UC_APPROVALS_PVT is a private PL/SQL package within the Oracle E-Business Suite Applications Technology layer that supports the approval workflow for Unit Configurations managed by the AHL (Product Lifecycle Management / Asset Lifecycle) modules. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking schema rather than the defining schema, a convention typical of EBS private APIs that are called only from within the trusted APPS server-side code base.

The package's core business purpose is to orchestrate the lifecycle of approval and quarantine actions on a Unit Configuration header. It provides the mechanism by which a submitted Unit Configuration enters the approval process, is completed, or is transitioned into and out of a quarantine state subject to approval. This supports governance requirements in regulated or quality-sensitive environments where changes to a physical or logical unit configuration must be reviewed and authorised before taking effect.

Key Procedures and Functions

• INITIATE_UC_APPROVALS — Called when a user submits a Unit Configuration for approval. It initiates the approval process for the identified Unit Configuration, taking the Unit Configuration header identifier and the object version number as the primary business inputs, alongside the standard EBS API parameters (API version, message list initialisation, commit flag, and validation level). It returns the standard x_return_status, x_msg_count, and x_msg_data out parameters. Note that the documented default for p_commit in this procedure is FND_API.G_FALSE.
• COMPLETE_UC_APPROVAL — Completes the approval of a Unit Configuration. This is the procedure most commonly associated with the search term complete_uc_approval. It finalises the approval action so that the approval status of the Unit Configuration is updated to reflect authorisation, allowing downstream processing to proceed.
• INITIATE_QUARANTINE — Begins the approval-driven quarantine process for a Unit Configuration, moving the record into a state pending approval of the quarantine action.
• INITIATE_DEACTIVATE_QUARANTINE — Initiates the process to deactivate an existing quarantine, again routed through the approval mechanism so that removal of the quarantine is formally authorised.
• COMPLETE_QUARANTINE_APPROVAL — Completes the approval step for a quarantine-related action, finalising either the quarantine or its deactivation. Together with INITIATE_QUARANTINE and INITIATE_DEACTIVATE_QUARANTINE, it forms the quarantine approval sub-cycle.

The package therefore exposes two logical sub-groups of procedures: one for the general Unit Configuration approval cycle (initiate and complete) and one for the quarantine approval cycle (initiate quarantine, initiate deactivation, and complete quarantine approval).

Tables Accessed

The package accesses AHL_UNIT_CONFIG_HEADERS through an APPS synonym. This is the master header table for Unit Configurations in the AHL schema, holding the configuration identity and its current approval or quarantine status. The initiate procedures read the header to validate the business key and object version, and the complete procedures update the header's status columns to record the outcome of the approval or quarantine decision. The p_object_version_number check indicates that Oracle's optimistic locking pattern is applied, so a concurrent modification to the header would cause the API to fail rather than overwrite data.

Usage Notes

As a private (PVT) package, AHL_UC_APPROVALS_PVT is not intended for direct invocation by external or custom code. It is referenced by two other packages, which act as the public entry points and encapsulate the calls to this package. In typical EBS 12.1.1 and 12.2.2 deployments, the procedures are invoked in response to user actions within the AHL forms-based UI — for example, when a user presses an Approve or Submit button on a Unit Configuration — and may also be driven by the Oracle Workflow approval framework as part of a configured approval process.

Because the documented p_commit default for INITIATE_UC_APPROVALS is FND_API.G_FALSE, callers retain control over the transaction boundary and are expected to commit explicitly. Any custom extension that needs to replicate this behaviour should call the public wrapper rather than the private package directly, and must always supply the correct p_api_version and object version number to avoid premature or conflicting updates to the header record.