Search Results delete_item_sec_assoc

Overview

AMS_ITEM_SECTION_PVT is a private (PVT) PL/SQL package in the Oracle Applications (APPS) schema that supports the Oracle Marketing (AMS) module's item section functionality. An "item section" represents a stored association between an inventory item and a marketing section, qualified by an owning organization and an effective date range. This package provides the programmatic maintenance layer for those associations, exposing the underlying insert and delete logic that the marketing application uses to keep section membership synchronized with item and organization data.

The package header carries the standard Oracle EBS private API signature, declaring AUTHID CURRENT_USER so that execution privileges are resolved against the calling schema rather than the definer. The dated header comment (amsvpses.pls 115.2, 2002) indicates the package is a long-standing component of the AMS codebase that has been carried forward unchanged into the 12.1.1 and 12.2.2 releases. Because it is classified as PVT, it is intended for internal consumption by AMS forms, business logic, and other packaged APIs rather than as a supported integration point.

Key Procedures and Functions

The package exposes two documented procedures, both operating on the local section_rec_type record structure that carries section_id, inventory_item_id, organization_id, start_date, and end_date.

• CREATE_ITEM_SEC_ASSOC — Creates a new item-to-section association. It accepts the standard Oracle API control parameters (API version, message list initialization, commit flag, and validation level) together with the inbound section_rec_type record, and returns the standard x_return_status, x_msg_count, and x_msg_data outputs. It is the counterpart to the delete routine and is used whenever an item is added to a marketing section.
• DELETE_ITEM_SEC_ASSOC — Removes an existing item-to-section association. This is the procedure surfaced by the user's search term delete_item_sec_assoc. Its parameter profile mirrors CREATE_ITEM_SEC_ASSOC exactly, taking the same control parameters and the same section_rec_type inbound record, and returning the same three standard out parameters. Callers identify the association to be removed by populating the record with the relevant section, item, organization, and date values.

Both procedures follow the Oracle Application Object Library API conventions, notably the use of FND_API.G_MISS_NUM and FND_API.G_MISS_DATE as default sentinel values in the record type, which allows the caller to distinguish "not supplied" from a genuine value. Validation level, message list initialization, and commit behavior are all caller-controlled, giving the invoking transaction flexibility over error handling and unit-of-work boundaries.

Tables Accessed

The documented table reference for this package is the APPS synonym PLITBLM. The item section association records maintained by CREATE_ITEM_SEC_ASSOC and DELETE_ITEM_SEC_ASSOC are persisted through this synonym, which resolves to the underlying AMS base table holding section membership rows. All access occurs through the APPS synonym layer, consistent with standard EBS multi-org and privilege conventions, and no other tables are documented as referenced by this package.

Usage Notes

Because AMS_ITEM_SECTION_PVT is a private package, it is not published in the EBS integration repository as a customer-facing API. It is invoked from within the AMS application's own PL/SQL stack — typically in response to user actions in the marketing forms that manage item sections and list membership — and it relies on the caller to supply a valid, fully populated record and to handle the returned status codes. Custom code should not call this package directly; instead, integrations should use the corresponding public AMS APIs or interface tables. The package is referenced by zero other packages according to the documented metadata, reinforcing that it is a leaf-level, single-purpose maintenance unit. When troubleshooting the delete_item_sec_assoc path, the relevant diagnostic signals are the x_return_status value (FND_API.G_RET_STS_SUCCESS, ERROR, or UNEXPECTED_ERROR) and the accompanying message count and data, together with whether the caller requested commit or deferred the transaction to an enclosing unit of work.