Search Results ams_list_entries_s




Overview
Explore in AI Chat

Overview

APPS.AMS_LISTENTRY_PVT is a private (PVT classification) PL/SQL package body in the Oracle Marketing (AMS) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It encapsulates the business logic that governs individual list entries within a marketing list. A list entry associates a customer, prospect, or party with a specific marketing list and, where applicable, with a campaign, campaign schedule, and source code. The package provides the internal application programming interface through which the Oracle Marketing forms and concurrent processes create, maintain, validate, and delete these entries. Because the object is classified as PVT, it is intended for internal use by other AMS packages and the AMS product user interface rather than as a published integration API for external callers.

Key Procedures and Functions

  • CREATE_LISTENTRY — Creates a new list entry record for a marketing list, applying the package's internal defaulting and validation rules before the row is inserted.
  • UPDATE_LISTENTRY — Modifies an existing list entry, re-validating the record and propagating any relevant changes.
  • UPDATE_LISTENTRY_SOURCE_CODE — Updates the source code associated with a list entry, allowing the origin or channel of the entry to be reclassified.
  • DELETE_LISTENTRY — Removes a list entry from the marketing list, performing the associated cleanup logic.
  • LOCK_LISTENTRY — Acquires a lock on the list entry record to support concurrency control during updates within a transaction.
  • VALIDATE_LISTENTRY — Executes business validation on the entry, checking required attributes such as list header, party, and related campaign data.
  • CHECK_ENTRY_ITEMS — Verifies the entry items or attributes associated with a list entry for completeness and consistency.
  • CHECK_ENTRY_RECORD — Checks whether the underlying entry record exists and is in a state suitable for the requested operation.
  • INIT_ENTRY_REC — Initializes the in-memory entry record structure with default values prior to population and processing.
  • COMPLETE_ENTRY_REC — Finalizes the entry record, populating derived or dependent attributes before the record is persisted.
  • GET_LISTPINCODE — Retrieves the list PIN code, used to identify or secure access to a marketing list and its entries.

Tables Accessed

The package operates against several AMS tables through APPS synonyms. AMS_LIST_ENTRIES holds the list entry rows and is the primary table maintained by the create, update, and delete procedures; AMS_LIST_ENTRIES_S is the corresponding sequence, named in the user search, used to generate the surrogate primary keys for new entries. AMS_LIST_HEADERS_ALL provides the list header context to which each entry belongs. AMS_CAMPAIGNS_ALL_B and AMS_CAMPAIGN_SCHEDULES supply campaign and schedule information used when entries are linked to campaign activity. AMS_SOURCE_CODES supplies valid source code values, and DUAL is used in standard PL/SQL expressions. The package also depends on FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, AMS_UTILITY_PVT, and JTF_PLSQL_API for the standard EBS API framework, message handling, and utility routines, plus MDSYS.SDO_GEOMETRY for spatial attribute support.

Usage Notes

AMS_LISTENTRY_PVT is typically invoked from the Oracle Marketing list management forms and from AMS internal code that processes list entries, rather than being called directly by external integrations. It is referenced by four other packages in the AMS schema, which rely on it as the private implementation layer behind higher-level list entry operations. The presence of FND_API and FND_MSG_PUB dependencies indicates that the procedures use the standard EBS API error and message stack; callers should therefore check the message stack and the returned API status when invoking these routines within custom code or extensions. Direct updates to AMS_LIST_ENTRIES that bypass this package risk skipping the validation and record-completion logic it enforces.