Search Results continue_parent_process

Overview

AMS_APPROVAL_PVT is a private PL/SQL package in the APPS schema that provides the core approval engine for Oracle Marketing (AMS) and Oracle Trade Management (OZF) business objects. It is classified as a PVT package, indicating that it holds internal implementation logic consumed by other public packages rather than being called directly by end users or external integrations. The package centralises the rules that determine whether a marketing campaign, deliverable, event, or trade promotion budget line requires approval, identifies the appropriate approver, and drives the workflow that routes the document through single or multi-level approval chains. It depends on FND_API and the SYS STANDARD package, confirming that it conforms to the standard Oracle Application Object Library API conventions, including the use of the standard return status, message, and error-handling patterns.

Key Procedures and Functions

The package exposes 34 documented procedures and functions that fall into several functional groupings.

• Approval initiation: START_LINEAPPROVAL, START_LINE_APPROVAL, and STARTPROCESS launch the approval flow for a line or document. PREPARE_DOC prepares the document and SET_ACTIVITY_DETAILS and SET_APPROVER_DETAILS populate the activity and approver context used by the workflow.
• Approver resolution: GET_LINE_APPROVER_DETAILS and SET_APPROVER_DETAILS resolve who must approve a given line based on approval rules.
• Rule evaluation: CHECK_LINE_APPROVAL_RULE, CHECK_APPROVAL_RULES, and CHECK_LINE_FURTHER_APPROVAL evaluate whether further approval levels are required. CAN_CONTINUE_FLOW and CHECK_MORE_LINES_REMAINING determine whether the flow proceeds.
• Approval and rejection: APPROVE_BUDGET_LINE, REJECT_BUDGET_LINE, APPROVE_ACTIVITY_STATUS, and REJECT_ACTIVITY_STATUS record the outcome of an approver's decision at the line or activity level.
• Hierarchy handling: IS_PARENT_WAITING, CONTINUE_PARENT_PROCESS, and REVERT_STATUS manage parent-child relationships among lines and roll the flow back when required.
• Budget validation: CHECK_BUDGET_LINES validates the budget lines associated with a document before approval proceeds.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. AMS_APPROVAL_DETAILS and AMS_APPROVERS store approval state and the approver list. AMS_OBJECT_RULES_B holds the approval rules applied to marketing objects. OZF_ACT_BUDGETS and OZF_OFFERS carry trade management activity budget and offer data. QP_LIST_HEADERS_ALL_B supplies pricing list header information. FND_USER resolves user identities, FND_FORM_FUNCTIONS supports function-level security, and JTF_RS_ROLES_B plus JTF_RS_ROLE_RELATIONS resolve resource roles and their hierarchies. WF_ROUTING_RULES and WF_ROUTING_RULE_ATTRIBUTES link the approval logic to Oracle Workflow routing, and DUAL is used for scalar evaluations.

Usage Notes

AMS_APPROVAL_PVT is not intended for direct invocation by end users. It is called by eight dependent packages, including AMS_CAMPAIGNRULES_PVT, AMS_DELIVERABLERULES_PVT, AMS_DELIVERABLE_PVT, AMS_EVHRULES_PVT, AMS_SCHEDULERULES_PVT, OZF_ACTBUDGETRULES_PVT, OZF_ACTBUDGETS_PVT, and OZF_OFFER_PVT, each of which maps a specific business object onto the shared approval engine. Because the package conforms to FND_API conventions, custom code that must extend or bypass standard approval behaviour should invoke the public caller packages rather than this private package. Any customisation should respect the documented signature and the workflow routing rules configured in the E-Business Suite instance.