Search Results create_pricelist_header

Overview

AMS_DELIVERABLE_PVT is a private PL/SQL package body in the Oracle E-Business Suite Advanced Marketing (AMS) module, owned by the APPS schema. It encapsulates the core business logic that supports the AMS Deliverables entity, which represents marketing collateral, kits, price lists, and other tangible or intangible items associated with marketing activities and campaigns. The package is classified as a Private (PVT) API, meaning it is intended for internal consumption by other AMS packages and frameworks rather than direct invocation by external applications or end users. Its primary responsibilities include creating, updating, deleting, locking, and validating deliverable records, as well as managing the associations between deliverables and their component items.

The source header indicates that the package has been maintained since at least 2000, with significant updates through 2010 (version 120.2). The user search term "jtf_amv" likely relates to the JTF (Java Tools Framework) AMV (Application Module View) territory, reflecting the integration of AMS deliverables with the broader CRM Foundation/JTF architecture used in Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package body:

• CREATE_DELIVERABLE — Creates a new deliverable record, presumably populating the base and translation tables, and establishing any initial associations.
• DELETE_DELIVERABLE — Removes a deliverable record and its dependent data from the AMS schema.
• LOCK_DELIVERABLE — Acquires a lock on a deliverable record to prevent concurrent modification, consistent with the standard EBS API concurrency model.
• UPDATE_DELIVERABLE — Modifies an existing deliverable's attributes and related associations.
• VALIDATE_DELIVERABLE — Performs business rule validation on deliverable data before commit, returning status and message information.
• CHECK_DELIV_ITEMS — Verifies the integrity and completeness of items associated with a deliverable, such as kit components.
• CHECK_DELIV_RECORD — Validates the deliverable record itself, likely checking for required fields and referential integrity.
• INIT_DELIV_REC — Initializes a deliverable record type structure, a common pattern in EBS private APIs for preparing PL/SQL record variables.
• COMPLETE_DELIV_REC — Finalizes or populates a deliverable record structure, possibly after defaulting and validation.

Additionally, the source excerpt reveals older procedures such as CREATE_PRICELIST_HEADER, CREATE_PRICELIST_LINE, and DELIVERABLE_CANCELLATION, suggesting the package evolved from earlier price-list-centric functionality into a general deliverable management API.

Tables Accessed

The package reads and writes a range of AMS and shared EBS tables through APPS synonyms. The primary entity tables are AMS_DELIVERABLES_ALL_B (base table), AMS_DELIVERABLES_ALL_B_S (likely a sequence or security table), and AMS_DELIVERABLES_ALL_TL (translation table for multilingual support). Component items are stored in AMS_DELIV_KIT_ITEMS, while AMS_OBJECT_ASSOCIATIONS links deliverables to other CRM objects. Budget and setup data are accessed via AMS_ACT_BUDGETS, AMS_CUSTOM_SETUPS_B, and AMS_CUSTOM_SETUP_ATTR. User status lookups reference AMS_USER_STATUSES_B, and language validation uses FND_LANGUAGES. Inventory item references use MTL_SYSTEM_ITEMS_B. DUAL and PLITBLM (a PL/SQL table-to-integer mapping utility) support procedural logic.

Usage Notes

As a private API, AMS_DELIVERABLE_PVT is not intended for direct invocation from external custom code. It is referenced by seven other packages within the AMS and JTF stack, which serve as the public-facing wrappers. The package is typically invoked from AMS Forms (such as the Deliverables and Campaigns forms), concurrent programs that process marketing deliverables, and higher-level public APIs that enforce the standard EBS API contract. Developers extending AMS functionality should call the public wrapper packages rather than this private body, adhering to Oracle's API layering conventions. The debug flags at the top of the package body (AMS_DEBUG_HIGH_ON, AMS_DEBUG_LOW_ON, AMS_DEBUG_MEDIUM_ON) enable FND_MSG_PUB-based logging for troubleshooting.