Search Results ams_list_queries_param_s

Overview

APPS.AMS_LIST_QUERY_PVT is the private implementation package body (API classification PVT) for Oracle Marketing list query processing within Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the AMS (Advanced Marketing) module by encapsulating the validation, persistence, and lifecycle management logic for list queries — the stored query definitions and associated parameters that determine which customers, prospects, or prospects segments are selected into a marketing list. The package is object type PACKAGE BODY, owner APPS, and status VALID. Because it is a private (PVT) package, its procedures are not exposed as a public API surface; they are invoked internally by the corresponding public list query packages and by the AMS list action framework.

Key Procedures and Functions

The package exposes twelve documented procedures and functions that together implement the full list query maintenance cycle:

• CREATE_LIST_QUERY — creates a new list query record for a marketing list, establishing the query definition used to drive list membership.
• UPDATE_LIST_QUERY — modifies an existing list query definition, applying changes to criteria and associated parameters.
• DELETE_LIST_QUERY — removes a list query record and its dependent parameter rows.
• DELETE_PARENT_LIST_QUERY — deletes the parent-level list query; supports the hierarchical relationship between a list and its sub-queries.
• LOCK_LIST_QUERY — acquires a lock on a list query row to serialize concurrent modification before update or delete operations.
• VALIDATE_LIST_QUERY — performs entity-level validation against the AMS API validation conventions, typically invoking the record-level validator.
• CHECK_LIST_QUERY_ITEMS — verifies the items (parameters or select actions) associated with a query, confirming that mandatory selections exist and are consistent.
• VALIDATE_LIST_QUERY_REC — the record-level validation routine called by the higher-level validation entry points.
• COPY_LIST_QUERIES — duplicates existing list query definitions, enabling reuse of query criteria across lists.

The remaining documented procedures follow the same create/update/delete/validate pattern typical of AMS private packages. No parameter signatures are reproduced here; parameter behavior follows the standard FND_API return-status and message-stack conventions.

Tables Accessed

• AMS_LIST_QUERIES_ALL — the primary transactional table holding list query headers; read and written by create, update, delete, and validation routines.
• AMS_LIST_QUERIES_ALL_S — the sequence/primary key source used to generate identifiers for new list query rows.
• AMS_LIST_QUERIES_PARAM — stores the query parameters (criteria) belonging to each list query; maintained alongside the header.
• AMS_LIST_QUERIES_PARAM_S — provides sequence numbers for parameter rows.
• AMS_LIST_SELECT_ACTIONS — referenced to resolve the select actions tied to a list query.
• DUAL — used for lightweight single-row lookups and constants.
• PLITBLM — the standard PL/SQL index-by table type used for in-memory collections during validation and processing.

Usage Notes

AMS_LIST_QUERY_PVT is invoked indirectly through AMS list query forms, the AMS list action framework (AMS_LISTACTION_PVT, AMS_LIST_SELECT_ACTIONS), and the public AMS_LIST_QUERIES_PKG wrapper. Dependent objects include AMS_LIST_QUERIES_VL (the view layer), AMS_UTILITY_PVT, and the standard FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and JTF_PLSQL_API infrastructure. The package is referenced by nine other packages and is not referenced by any database object directly. Customizations should call the public AMS API rather than this private body, since its interface is subject to change across patch levels.