Search Results submitted_for_approval

Overview

APPS.PV_AME_API_W is the Approval Management Engine (AME) integration wrapper for Oracle Process Manufacturing (OPM) partner and referral approval processing within Oracle E-Business Suite. The package body, defined in source file pvapprlb.pls (version 120.21, last updated 2006/12/01), exposes the PL/SQL interface through which OPM submits referral, deal registration, and duplicate map records into the AME approval framework and then tracks the resulting approver responses. It relies on standard EBS AME constructs such as ame_util.approverRecord2 and the JTF_NUMBER_TABLE collection type to exchange approver lists with the AME engine.

In the context of a user searching for submitted_for_approval, this package is the layer that transitions a referral into an approval workflow. The START_APPROVAL_PROCESS procedure is the entry point invoked to place a record into the approval hierarchy, which is the functional equivalent of marking a transaction as submitted for approval. Downstream queries against referral status columns (such as those exposed on the OPM partner/referral forms) reflect this transition.

Key Procedures and Functions

The documented package exposes two primary procedures:

• START_APPROVAL_PROCESS — Initiates the AME approval cycle for a given referral. It accepts an API version, standard FND_API initialization and commit flags, a validation level, a referral identifier, an optional partner identifier, country-change indicators (p_change_cntry_flag, p_country_code), and an approval entity discriminator (p_approval_entity, values such as PVREFFRL, PVDEALRN, or PVDQMAPR). It returns the standard EBS API triplet: x_return_status, x_msg_count, and x_msg_data. Internally it queries pv_referrals_b for partner, benefit, and benefit-type information before dispatching to AME. This is the procedure responsible for the "submitted for approval" state change.
• UPDATE_APPROVER_RESPONSE — Records an approver's action (approve, reject, or similar response) back into the AME/referral approval data, allowing the workflow to advance or terminate based on the collected responses.

The body also declares internal helpers not exposed as documented public APIs, including DEL_PRIOR_REP_APPR, GET_APPROVERS, and VALIDATE_APPROVAL. These support clearing prior approver rows, retrieving the current approver list for a referral, and validating an individual approver against a transaction, type, user, and person combination. The body defines the exception g_concurrent_update (ORA-00054), handling resource-busy conditions when the approval tables are locked by a concurrent process.

Tables Accessed

• PV_REFERRALS_B — The base referral table. Read by START_APPROVAL_PROCESS to obtain the partner, benefit, and benefit-type context required for approval routing.
• PV_GE_TEMP_APPROVERS / PV_GE_TEMP_APPROVERS_S — Temporary approver staging tables used to assemble and persist candidate approver lists during approval processing.
• JTF_RS_RESOURCE_EXTNS — Resource extension table used to resolve approvers to valid JTF resources.
• FND_USER — Used to validate and resolve approver user identities.
• PLITBLM — The standard EBS message/diagnostic table used by the API message-handling framework when populating x_msg_count and x_msg_data.

All tables are referenced through APPS synonyms, so access is controlled by the APPS schema grants.

Usage Notes

PV_AME_API_W is invoked when a user submits an OPM referral, deal registration, or duplicate map record for approval from the associated Oracle Forms UI, and by concurrent programs that batch-submit referrals into the AME pipeline. Custom integrations should call START_APPROVAL_PROCESS rather than writing to PV_GE_TEMP_APPROVERS directly, because the procedure enforces message handling, country-change logic, and the AME hand-off sequence. Callers must check x_return_status against FND_API.G_RET_STS_SUCCESS and drain messages via FND_MSG_PUB. Although the metadata reports no dependent packages, the runtime dependency on AME utilities and FND_API is implicit. The ORA-00054 exception indicates the package can collide with concurrent approval jobs, so retry logic is advisable in custom callers.