Search Results dpp_approval_access_seq

Overview

APPS.DPP_APPROVAL_PVT is a private (PVT) PL/SQL package body in the Oracle EBS Applications schema that supports the approval-processing infrastructure for Oracle Demand Planning and its integration with the Oracle Approvals Management (AME) and Oracle Workflow engines. The package encapsulates the internal logic used to determine approvers, maintain the approval access list, drive notifications and events, and process end-user approval actions. Its name classifies it as a private API, meaning the procedures are intended for internal consumption by sibling packages such as DPP_EXECUTIONPROCESS_PVT, DPP_UTILITY_PVT, and other DPP approval-layer components rather than for direct customer extension. The package depends heavily on AME_API2, AME_UTIL, AME_UTIL2, and the AME_APPROVAL_GROUPS/AME_APPROVAL_GROUP_MEMBERS tables, indicating that AME rules supply the approver resolution logic while DPP_APPROVAL_PVT persists and manages the resolved access records. It also relies on the standard FND_API error-handling stack, FND_MSG_PUB for message publication, and the Workflow packages (WF_ENGINE, WF_EVENT, WF_NOTIFICATION) plus FND_PROFILE, FND_GLOBAL, and FND_FILE for runtime context and logging.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. GET_APPROVERS and GET_ALLAPPROVERS resolve the set of approvers applicable to a demand planning transaction, with the latter returning the complete candidate list rather than a filtered subset. ADD_ACCESS and REVOKE_ACCESS manage entries in the approval-access list, granting or removing the right of a user or resource to act on a transaction. CLEAR_ALL_APPROVALS removes all approval records associated with a transaction. UPDATE_USER_ACTION and PROCESS_USER_ACTION capture and then apply an end user's approval decision, with the latter performing the substantive state transition. RAISE_EVENT and SEND_NOTIFICATION handle outbound communication: RAISE_EVENT publishes a business event through the Workflow event system, while SEND_NOTIFICATION constructs and delivers a Workflow notification. Together these procedures form the lifecycle of an approval: resolve approvers, register access, notify, capture the response, and record the outcome.

Tables Accessed

The package reads and writes DPP_APPROVAL_ACCESS, the core table storing which approver may act on which demand planning transaction, and consumes DPP_APPROVAL_ACCESS_SEQ — the sequence referenced by the user's search term — to generate unique primary keys for new access rows during ADD_ACCESS. DPP_TRANSACTION_HEADERS_ALL is the transaction header source that defines the subject of approval. Approver identity and hierarchy data come from AME_APPROVAL_GROUPS and AME_APPROVAL_GROUP_MEMBERS. FND_USER and PER_PEOPLE_F/JTF_RS_RESOURCE_EXTNS supply user and resource attributes, while WF_ROLES and WF_DIRECTORY support role resolution. WF_EVENTS, WF_PARAMETER_LIST_T, and WF_PARAMETER_T back the event and notification payloads.

Usage Notes

DPP_APPROVAL_PVT is not referenced by any other database object and is not intended as a public entry point; it is invoked by the DPP approval orchestration layer and, indirectly, from Demand Planning forms and concurrent processes that initiate or act upon approvals. The DPP_APPROVAL_ACCESS_SEQ sequence is accessed exclusively through ADD_ACCESS, so administrators inspecting sequence values should understand that they correspond to rows in DPP_APPROVAL_ACCESS. Because the package is private and status VALID, customizations should avoid calling it directly and instead use the supported DPP approval flows or the AME configuration that feeds it.