Search Results lock_deliv_kit_item

Overview

APPS.AMS_DELIVKITITEM_PVT is a private PL/SQL API package within the Oracle E-Business Suite Advanced Marketing (AMS) module. It encapsulates the business logic for managing deliverable kit items — the individual components that make up a deliverable kit, which is a collection of deliverables grouped and released together. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, and its header carries a version marker dating to the 11i lineage (amsvdkis.pls 115.12), confirming it is a long-standing object that persists into EBS 12.1.1 and 12.2.2.

The package is classified as PVT (private). It is not intended as a public integration surface; instead it is called by other AMS packages — the ETRM metadata records that it is referenced by five other packages. It provides the canonical create, update, delete, lock, and validation operations for the AMS_DELIV_KIT_ITEMS entity, together with internal helper routines for record initialization and completeness checking.

Key Procedures and Functions

The package exposes nine documented procedures and functions:

• CREATE_DELIV_KIT_ITEM — Inserts a new deliverable kit item. The header comments specify that object_version_number is initialized to 1, that a passed-in deliverable_kit_item_id triggers a uniqueness check with an exception raised on duplicates, and that an absent ID is generated from a sequence. Flag columns are validated as 'Y' or 'N'. The procedure writes a row to AMS_DELIV_KIT_ITEMS and, where applicable, an attachment record.
• UPDATE_DELIV_KIT_ITEM — Modifies an existing deliverable kit item record.
• DELETE_DELIV_KIT_ITEM — Removes a deliverable kit item.
• LOCK_DELIV_KIT_ITEM — Acquires a row-level lock on the kit item, supporting concurrent update control and optimistic locking via object_version_number.
• VALIDATE_DELIV_KIT_ITEM — The routine matching the user's search term "validate_deliv_kit_item". It performs validation of a deliverable kit item record before create or update processing, checking required and referential data and raising exceptions on failure.
• CHECK_DELIV_KIT_ITEM_ITEMS — Verifies the set of items associated with a deliverable kit.
• CHECK_DELIV_KIT_ITEM_RECORD — Verifies the integrity of a single kit item record.
• INIT_DELIV_KIT_ITE_REC — Initializes a deliv_kit_item_rec_type record structure with default values prior to population by the caller.
• COMPLETE_DELIV_KIT_ITEM_REC — Completes or finalizes the record structure, typically deriving or defaulting remaining attributes.

Tables Accessed

The package operates against four documented objects, reached through APPS synonyms:

• AMS_DELIV_KIT_ITEMS — The primary transactional table holding deliverable kit item rows; the target of insert, update, and delete operations.
• AMS_DELIV_KIT_ITEMS_S — The sequence supplying generated deliverable_kit_item_id values when the caller does not provide one.
• AMS_DELIVERABLES_ALL_B — The base deliverables table, consulted to validate that the referenced kit and part identifiers resolve to valid deliverables.
• DUAL — Used for single-row evaluations and sequence selection.

Usage Notes

Because AMS_DELIVKITITEM_PVT is a private package, it is not called directly by external integrations. It is invoked from the AMS deliverable kit maintenance forms and from the five AMS packages that reference it, which supply the deliv_kit_item_rec_type record and consume the returned identifier and API message tokens. The header explicitly instructs callers not to pass FND_API.g_mess_char, g_mess_num, or g_mess_date values into the record, and to rely on the package's own defaulting and validation logic. Typical invocation follows the standard EBS private API pattern: initialize the record with INIT_DELIV_KIT_ITE_REC, populate the business attributes, call VALIDATE_DELIV_KIT_ITEM, then call CREATE_DELIV_KIT_ITEM or UPDATE_DELIV_KIT_ITEM. Custom code should not bind to this package directly; the supported path is through the public AMS deliverable APIs or the standard EBS forms, since the private package's signature is not guaranteed across releases.