Search Results validate_listentry

Overview

APPS.AMS_LISTENTRY_PUB is the public PL/SQL API package for the Oracle Marketing (AMS) list entry entity. A list entry represents the association of a party, customer, or prospect with a marketing list, and it is the fundamental vehicle through which Marketing drives campaign membership, targeting, and segmentation. The package provides a controlled, business-rule-enforcing interface for the full lifecycle of a list entry: creation, modification, deletion, concurrency locking, and validation. It is classified as a PUB (public) API in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, meaning it is intended for direct invocation by external callers such as forms, concurrent programs, and custom code. Internally it delegates to the private package AMS_LISTENTRY_PVT, which holds the entity's record type definitions and the underlying DML logic.

Key Procedures and Functions

• CREATE_LISTENTRY — Inserts a new list entry. The header notes state that the object version number is initialized to 1; if a primary key is supplied, uniqueness is verified and an exception is raised for duplicates; otherwise a unique identifier is drawn from the sequence. Flag columns are validated as 'Y' or 'N', and defaulted when omitted.
• UPDATE_LISTENTRY — Modifies an existing list entry. The API raises an exception when the object version number does not match the persisted value, enforcing optimistic concurrency control. Attributes passed as FND_API.g_miss_char/num/date are treated as "no change" and are not written to the column.
• DELETE_LISTENTRY — Removes a list entry from the repository.
• LOCK_LISTENTRY — Acquires a row-level lock on the list entry so that callers can serialize changes and avoid lost updates during read-modify-write sequences.
• VALIDATE_LISTENTRY — Performs the entity's validation checks against the supplied record without persisting it, allowing callers to pre-screen data before invoking create or update.
• INIT_ENTRY_REC — Initializes the entry record structure, populating FND_API.g_miss_char/num/date placeholders so that the update path can distinguish supplied attributes from unsupplied ones.

Tables Accessed

The documented metadata does not enumerate the base tables touched by this package. By naming convention and by the entity it serves, the package operates on the Marketing list entry table (AMS_LIST_ENTRIES) and its associated TL and intersection structures, reached through APPS synonyms. The create path writes a new row and generates its primary key, the update path modifies existing columns after version checking, and the delete path removes the row. Validation and lookup activity reads the same structures to confirm uniqueness of the primary key and the integrity of flag columns.

Usage Notes

AMS_LISTENTRY_PUB is the supported entry point for programmatic manipulation of list entries and is referenced by two other packages within the application. Callers are expected to set up the standard FND_API environment — API version, initialization of the message list, commit flag, and validation level — and to inspect the returned status, message count, and message data after every call. The commit flag should remain false when the API participates in a larger transaction, with the caller controlling the commit boundary. Because the update path honors FND_API.g_miss_char/num/date and enforces the object version number, callers should first invoke LOCK_LISTENTRY, re-query the record, apply changes, and then call UPDATE_LISTENTRY. The header comment explicitly warns against passing FND_API.g_miss values into flag columns on create. The package is AUTHID CURRENT_USER, so it executes with the privileges of the calling schema; callers should therefore invoke it from the APPS schema or an appropriately granted custom schema. The validate procedure is useful in forms-level validation and batch pre-processing to surface errors before the destructive create, update, or delete calls.