Search Results ams_deliverable_pub




Overview
Explore in AI Chat

Overview

APPS.AMS_DELIVERABLE_PUB is the public application programming interface for Oracle Marketing (AMS) deliverables in Oracle E-Business Suite 12.1.1 and 12.2.2. A deliverable represents a tangible or intangible marketing output — such as a brochure, an email campaign asset, an event collateral item, or a media placement — that is planned, tracked, and fulfilled against a marketing activity or campaign. This package exposes a stable, committed interface through which forms, concurrent programs, and custom extensions can create, maintain, lock, validate, and delete deliverable records without directly manipulating the underlying AMS base tables.

The package is classified as a PUB (public) API in the ETRM metadata, and its status is recorded as VALID in the APPS schema. It is a thin wrapper layer: all substantive business logic, validation, and error handling is delegated to the private implementation package AMS_DELIVERABLE_PVT. Dependencies shown in the metadata confirm this pattern — AMS_DELIVERABLE_PUB references AMS_DELIVERABLE_PVT, FND_API, and JTF_PLSQL_API, and is itself referenced by AMS_DELIVERABLE_PUB_W (a wrapper generated for the Business Events / workflow integration layer), AMS_DELIVERABLE_PVT, and its own package body. The use of FND_API indicates adherence to the Oracle Application Object Library API conventions, including standardized message handling and the x_return_status / x_msg_count / x_msg_data output triad.

Key Procedures and Functions

ETRM documents five core entry points, all of which correspond to the standard CRUD-and-control surface of an Oracle marketing public API.

  • CREATE_DELIVERABLE — Inserts a new deliverable record. The procedure accepts the identifying and descriptive attributes of the deliverable (such as name, type, owning marketing activity, and scheduling information) and performs the necessary defaulting and validation before committing the row.
  • UPDATE_DELIVERABLE — Modifies the attributes of an existing deliverable. Callers pass the primary key of the target record along with the changed values; the private package applies validation rules and concurrency handling before the update is persisted.
  • DELETE_DELIVERABLE — Removes a deliverable record. Deletion is subject to the referential and business-rule checks enforced by AMS_DELIVERABLE_PVT, preventing removal of records that are still referenced by dependent marketing objects.
  • LOCK_DELIVERABLE — Places an explicit lock on a deliverable, supporting the locking protocol used by Oracle Forms and by concurrent or batch processes that must prevent simultaneous modification of the same record.
  • VALIDATE_DELIVERABLE — Performs the business-rule validation pass for a deliverable without persisting changes. This procedure is typically invoked before create or update, or independently by callers that need to surface validation errors to the user interface.

All procedures follow the FND_API calling convention and report outcome through the standard return-status parameters rather than by raising unhandled exceptions.

Tables Accessed

The ETRM metadata for AMS_DELIVERABLE_PUB does not enumerate the base tables reached through APPS synonyms. Because the package is a wrapper over AMS_DELIVERABLE_PVT, the actual DML is performed against the AMS deliverable entity tables, principally the AMS_DELIVERABLES table, with the associated TL (translation) table holding language-specific name and description columns. The public package itself typically performs no direct SQL; the documented dependency list contains only package references (AMS_DELIVERABLE_PVT, FND_API, JTF_PLSQL_API, and STANDARD), which is consistent with a pure delegation model.

Usage Notes

AMS_DELIVERABLE_PUB is invoked in three principal contexts. First, Oracle Marketing setup and transaction forms call the procedures through the AMS_DELIVERABLE_PUB_W wrapper, which adapts the API for the Oracle Forms and Business Events layers. Second, concurrent programs and batch jobs that generate or update campaign deliverables invoke the same entry points. Third, custom integrations and extensions should call this PUB package rather than AMS_DELIVERABLE_PVT directly, since the private package is not a supported interface and may change between releases.

Callers must initialize the FND global context (via FND_GLOBAL.APPS_INITIALIZE) and check the returned x_return_status before proceeding. Because the procedures participate in the caller's transaction, the invoking code is responsible for issuing COMMIT or ROLLBACK. On upgrade from 12.1.1 to 12.2.2 the package remains VALID with the same procedure set, so existing custom calls require no modification.