Search Results ams_approval_submit_pvt




Overview
Explore in AI Chat

Overview

AMS_APPROVAL_SUBMIT_PVT is a private PL/SQL package in the Oracle EBS Marketing (AMS) application, owned by the APPS schema and classified as a PVT (private) API. Its purpose is to initiate the approval workflow for marketing objects that participate in Oracle Marketing's approval framework. The package exposes a single entry point, Submit_Approval, which submits a designated object — identified by both an object ID and an object type — into the approval process and assigns a new status to it. This functionality supports the marketing approval lifecycle that governs campaigns, offers, claims, and budget entities before they become active.

The package source header (amsvapss.pls, version 115.0, dated 2002/12/01) indicates it is a legacy component carried forward through the 12.1.1 and 12.2.2 releases. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it relies on the standard FND_API message and commit-handling conventions.

Key Procedures and Functions

The package documents one procedure:

  • Submit_Approval — the sole public routine. It accepts an API version, initialization and commit flags, a validation level, the target object ID, the target object type, and the new status ID. It returns the standard FND_API out parameters: return status, message count, and message data. Its role is to route the specified marketing object into the approval process and apply the requested status transition. The parameters follow the conventional Oracle EBS API signature pattern (p_api_version, p_init_msg_list, p_commit, p_validation_level, followed by x_return_status, x_msg_count, x_msg_data), which allows callers to standardize error handling and transaction control.

No other procedures or functions are documented in the package metadata.

Tables Accessed

The package references several Marketing and Trade Management base tables via APPS synonyms:

  • AMS_CAMPAIGNS_ALL_B — the campaign base table, holding the campaign definition that may be submitted for approval.
  • OZF_OFFERS — the offer entity, a primary object type routed through the approval framework.
  • OZF_CLAIMS_ALL — the claims entity, representing customer or channel claims subject to approval.
  • OZF_ACT_BUDGETS — the activity budget entity, used when budget records participate in the approval flow.

These tables supply the object identity and status context required to determine what is being approved and what status transition is being applied. The presence of both AMS and OZF tables confirms that this package serves cross-module approval submission across Marketing campaigns and Trade Management offers, claims, and budgets.

Usage Notes

Because the package is classified as private (PVT), it is not intended for direct invocation by external or customer-written code. It is instead called by other application components — the metadata notes it is referenced by one other package — which act as the public-facing wrapper for approval submission. Typical internal callers include the Marketing approval detail logic (the G_PKG_NAME constant references ams_approval_detail_pvt) and any form or concurrent program that needs to submit an object for approval.

When invoked, callers should pass p_commit = FND_API.g_false to defer the commit to the caller's transaction boundary, and should inspect x_return_status against FND_API.g_ret_sts_success before proceeding. The p_object_type parameter determines which of the underlying tables is queried, so it must match a supported object type. In EBS 12.1.1 and 12.2.2, this package continues to operate under the same legacy signature; customizations should avoid calling it directly and instead use the supported public APIs of the Marketing approval framework.