Search Results check_list_query_items

Overview

APPS.AMS_LIST_QUERY_PVT_W is a private API wrapper package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. It encapsulates the internal business logic used to create, maintain, and validate list queries — the saved selection criteria that drive marketing lists, target groups, and campaign audience definitions. The package is declared with AUTHID CURRENT_USER, indicating that it executes with the privileges of the invoking schema rather than the definer, which is characteristic of generated PL/SQL wrapper layers in the EBS technology stack.

The source header identifies the package as the "_PVT_W" (private wrapper) companion to the underlying AMS_LIST_QUERY_PVT package. Wrapper packages of this type are generated to expose strongly typed PL/SQL collection interfaces over the canonical private API, bridging the gap between internal table-based structures and the JTF/VARCHAR2 and NUMBER table types used by Oracle Forms, OAF pages, and other EBS clients. The parameter naming convention (p7_a0 through p7_a20) reflects this generated origin, where positional arguments map to entity attributes.

Key Procedures and Functions

The package exposes eleven documented procedures, which fall into three functional groups.

• Rosetta conversion procedures — ROSETTA_TABLE_COPY_IN_P2, ROSETTA_TABLE_COPY_OUT_P2, ROSETTA_TABLE_COPY_IN_P6, and ROSETTA_TABLE_COPY_OUT_P6. These marshal data between PL/SQL nested tables (AMS_LIST_QUERY_PVT.SQL_STRING_TBL and LIST_QUERY_ID_TBL_TYPE) and the generic JTF_VARCHAR2_TABLE_4000 and JTF_NUMBER_TABLE types used across the EBS API layer.
• Transaction procedures — CREATE_LIST_QUERY and UPDATE_LIST_QUERY. These perform the insert and modify operations against list query records, following the standard EBS API signature with p_api_version_number, p_init_msg_list, p_commit, p_validation_level, and the x_return_status, x_msg_count, and x_msg_data output parameters for error handling. CREATE_LIST_QUERY returns the generated identifier through x_list_query_id.
• Validation procedures — VALIDATE_LIST_QUERY, VALIDATE_LIST_QUERY_REC, and CHECK_LIST_QUERY_ITEMS. These enforce business rules on list query definitions. CHECK_LIST_QUERY_ITEMS is the procedure most directly associated with the user's search term; it verifies the query items associated with a list query, confirming that the member criteria are internally consistent and reference valid source columns before the query is committed or executed.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed via an APPS synonym. PLITBLM is a generic PL/SQL index-organized or interim table used by EBS APIs to stage collection data during bulk operations and message list processing — the "PLITBLM" designation derives from PL/SQL Indexed Table By Limited Memory. Within AMS_LIST_QUERY_PVT_W, this table participates in the temporary storage and traversal of list query item collections during validation and DML operations. The persistent list query data itself resides in the AMS list query base tables, which are manipulated by the underlying private package rather than directly by this wrapper.

Usage Notes

AMS_LIST_QUERY_PVT_W is not intended for direct invocation by end users or custom developers. It is referenced by two other packages within the AMS schema, which act as its callers — typically the public API layer and the concurrent or forms-driven control logic that manages marketing list queries. Invocation occurs through:

• Oracle Forms or OAF-based marketing setup and list management screens, where user actions trigger the wrapper through the public API stack.
• Concurrent programs that batch-process marketing list definitions, including validation runs and list refresh operations.
• Higher-level AMS packages that require the strongly typed collection interface this wrapper provides.

Custom code should reference the public API rather than this private wrapper. Direct calls risk breakage across patch levels, as the generated parameter signatures (p7_a0 through p7_a20, with sentinel defaults such as 0-1962.0724 and fnd_api.g_miss_date) are subject to regeneration whenever the underlying entity definition changes. The package behaves identically in EBS 12.1.1 and 12.2.2; the source header revision 115.10 confirms a stable implementation across both release trains.