Search Results create_listentry

Overview

AMS_LISTENTRY_PUB is the public application programming interface for managing list entries within the Oracle Marketing (AMS) module of Oracle E-Business Suite. A list entry represents the association of a customer or prospect with a marketing list, and it forms the foundation used by campaign scheduling, list generation, and targeted marketing activities. The package provides a controlled, PL/SQL-based entry point for creating, maintaining, and validating these associations without requiring callers to manipulate the underlying AMS tables directly.

The package follows Oracle's standard API architecture, using a public (PUB) specification that delegates work to the corresponding private package, AMS_LISTENTRY_PVT, where the entry record type entry_rec_type is defined. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user, consistent with standard Oracle EBS API conventions. Because it is classified as a PUB interface, it is the supported surface for external integration and customization, insulating callers from internal table changes.

Key Procedures and Functions

• CREATE_LISTENTRY — Inserts a new list entry. It accepts the new record through the p_entry_rec parameter and returns the generated list_entry_id. The object version number is initialized to 1. Uniqueness of any supplied list entry identifier is enforced, and invalid flag values raise exceptions. If a flag column is omitted, a default is applied.
• UPDATE_LISTENTRY — Modifies an existing list entry using a record of new values. Optimistic locking is enforced through object version number comparison. When an attribute is passed as an FND_API missing value, that column is not updated, allowing selective modification.
• DELETE_LISTENTRY — Removes an existing list entry, providing the sanctioned deletion path consistent with API validation and locking rules.
• LOCK_LISTENTRY — Obtains a lock on a list entry so that concurrent modifications do not conflict, typically used before updates in multi-user environments.
• VALIDATE_LISTENTRY — Performs validation of a list entry record against business rules without necessarily persisting it, supporting pre-commit checks and data quality enforcement.
• INIT_ENTRY_REC — Initializes the entry record structure used by the create and update procedures, ensuring default and missing-value attributes are properly set before a caller populates the record.

Tables Accessed

The package operates against the AMS list entry tables through APPS synonyms, principally AMS_LIST_ENTRIES and related list header and lookup tables. AMS_LIST_ENTRIES stores the association between a marketing list and its members, and it is the primary target of the create, update, and delete operations. Supporting lookups are referenced to validate flag columns and status values. Because the API abstracts these tables, the documented interface remains stable even as physical schemas evolve.

Usage Notes

AMS_LISTENTRY_PUB is invoked from Oracle Marketing forms, concurrent programs that build or refresh marketing lists, and custom PL/SQL integrations. Callers should follow the standard API pattern: invoke FND_GLOBAL.INIT in the session, call INIT_ENTRY_REC to populate the record, then call the appropriate procedure while checking x_return_status for FND_API.g_ret_sts_success or error handling via message count and data. Commit behavior is controlled through the p_commit parameter. As documented API metadata indicates the package is referenced by two other packages, it also serves as a dependency for higher-level marketing APIs. When list entries are loaded in bulk, batch calls are preferred, and the object version number should always be carried forward on updates to satisfy concurrency controls.