Results for “ams_deliverable_pub_w”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_DELIVERABLE_PUB_W is a public PL/SQL package in the APPS schema that forms part of the Oracle Marketing (AMS) deliverable management infrastructure within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary role is to provide a controlled, API-based interface for creating and maintaining deliverable records—the reusable marketing artifacts such as collateral, offers, or content that flow through campaign execution and lead generation processes.

As a "_PUB" package, it is intended for external or cross-module consumption rather than internal-only use. The package depends on FND_API, Oracle's standard application programming interface utility library. That dependency signals that the procedures follow the Oracle EBS API conventions for message handling, return status, and error stacking, which allows calling programs to interpret outcomes consistently. ETRM classifies the object as status VALID and API classification OTHER, indicating it is a supported entry point but not one of the core transactional APIs such as those governing campaigns or lists.

The package body is documented separately from the specification, and the specification exposes exactly two procedures. Dependencies are limited to the FND_API package and the SYS.STANDARD package, confirming that the implementation is thin and delegates most business logic to underlying tables and shared API utilities.

Key Procedures and Functions

Two procedures are documented for AMS_DELIVERABLE_PUB_W:

• CREATE_DELIVERABLE — Establishes a new deliverable record. The procedure accepts the identifying and descriptive attributes of the deliverable, validates them through the FND_API framework, and inserts the corresponding row. It returns a standard API status and message so callers can detect validation failures, duplicate definitions, or missing mandatory values.
• UPDATE_DELIVERABLE — Modifies an existing deliverable record. It applies changes to the specified deliverable, again routing validation and error reporting through FND_API conventions. Typical uses include revising descriptive text, reassigning ownership, or adjusting attributes that affect how the deliverable is presented during campaign execution.

The ETRM metadata does not publish parameter lists for these procedures. Parameter signatures should be confirmed from the package specification in the target environment before any custom integration is written, because Oracle does not guarantee that undocumented parameter ordering or data types remain stable across patch levels.

Tables Accessed

The documented metadata does not enumerate the underlying base tables reached through APPS synonyms. Because the procedures create and update deliverable records, they necessarily operate against the AMS deliverable entity tables within the Marketing schema. Direct table references are obscured by the synonym layer, so the dependency report lists no explicit table names.

What the metadata does confirm is the absence of downstream package dependencies: AMS_DELIVERABLE_PUB_W is not referenced by any other package. This has two implications. First, the package is a pure consumer of application data rather than a shared service relied upon by other APIs. Second, changes to its behavior cannot cascade into unrelated modules, which reduces the blast radius of customization or debugging activity.

Usage Notes

This package is typically invoked from Oracle Marketing forms that manage deliverables, from concurrent programs that mass-create or refresh deliverable definitions, and from custom PL/SQL integrations that need to populate deliverable data as part of a campaign or content migration.

Because the procedures conform to FND_API conventions, callers should always inspect the returned status and message stack rather than assuming success on completion of the call. When invoking the package from custom code, wrap the call in standard error-handling logic that surfaces FND_API messages to the user. In 12.1.1 and 12.2.2 the object is delivered VALID in APPS, but as with any seeded API, direct updates to the AMS deliverable tables bypass validation and are not supported; the procedures here are the sanctioned path for inserting and modifying that data.