Search Results find_owner

Overview

AMS_WFCMPAPR_PVT is a private PL/SQL package body in the Oracle Marketing (AMS) module of Oracle E-Business Suite, shipped under the APPS schema. Its stated purpose, per the embedded header comments, is to contain the workflow procedures that implement Campaign Approval in Oracle Marketing. The package was originally created in September 1999 and evolved through a series of revisions, including changes for JTF resource interaction, a bug fix for Bug 1226905, performance-oriented use of a faster JTF view, and a December 2002 revision that introduced NOCOPY parameters and message-level debug checks. Although the source header references version 115.17, the same package body is present and functional in both EBS 12.1.1 and 12.2.2, where it remains part of the campaign approval workflow infrastructure.

As a PVT (private) package, it is not intended for direct invocation by external code. Instead, it is called by Oracle Workflow function activities configured within the seeded Campaign Approval workflow item type, so that approval routing, status transitions, and notification document creation occur in a controlled, server-side manner.

Key Procedures and Functions

The documented interface exposes sixteen procedures and functions, all scoped to the campaign approval lifecycle:

• STARTPROCESS / ABORTPROCESS — Initialize and terminate the workflow process for a campaign approval item.
• SELECTOR — Determines the appropriate approver or routing branch based on the approval rules and campaign context.
• SET_ACTIVITY_DETAILS — Populates activity-level item attributes used by downstream workflow nodes.
• APPR_REQUIRED_CHECK, THEME_APPR_REQ_CHECK, OWNER_APPR_CHECK, FUND_APPR_REQ_CHECK, BA_OWNER_APPR_CHECK — A family of predicate routines that test whether approval is required for a given dimension: campaign/theme approval, owner approval, funding approval, and business-account owner approval respectively.
• CREATE_NOTIF_DOCUMENT — Generates the notification document presented to approvers.
• PREPARE_DOC — Assembles the approval document content from campaign metadata.
• UPDATE_STATUS_NA, UPDATE_STAT_APPRTA, UPDATE_STATUS_REJ, UPDATE_STAT_APPRBA, REVERT_STATUS — Status transition routines covering the not-applicable, approved-by-theme-approver, rejected, approved-by-business-account, and revert outcomes.
• Handle_Err (private helper) — Collects messages from the FND message stack and writes them into workflow item attributes for error reporting.

Tables Accessed

The package reads and writes a focused set of AMS and FND tables through APPS synonyms:

• AMS_CAMPAIGNS_ALL_B — Core campaign record whose approval state is evaluated and updated.
• AMS_APPROVAL_RULES and AMS_STATUS_ORDER_RULES — Govern whether approval is required and the permitted status progression.
• AMS_ACT_WF_REQUESTS and AMS_ACT_WF_REQUESTS_S — Persist workflow request and activity context tied to campaign actions.
• AMS_ACT_MARKET_SEGMENTS and AMS_ACT_MESSAGES — Supply activity segmentation and messaging data for the approval document.
• AMS_DELIVERABLES_ALL_B, AMS_EVENT_HEADERS_ALL_B, AMS_EVENT_OFFERS_ALL_B — Provide deliverable, event, and offer details included in approval content.
• AMS_OBJECT_ATTRIBUTES — Stores flexible attribute values relevant to the campaign object.
• FND_LANGUAGES and DUAL — Support language-sensitive lookups and singleton queries.

Usage Notes

AMS_WFCMPAPR_PVT is invoked indirectly. Its procedures are registered as function activities within the Campaign Approval workflow, so Oracle Workflow calls them as the approval process advances through its nodes. Direct calls from forms or concurrent programs are not expected, and the package is referenced by zero other PL/SQL packages according to the metadata, confirming its role as an endpoint implementation layer. Customers extending campaign approval should route changes through the workflow definition or by wrapping the documented procedures in a custom package rather than modifying the seed body.