Search Results ams_list_query_pvt_w




Overview
Explore in AI Chat

Overview

The APPS.AMS_LIST_QUERY_PVT_W package body is an Oracle E-Business Suite object belonging to the Oracle Marketing (AMS) application, the module responsible for campaign management, list generation, and targeted audience selection. Within this schema the package serves as the private implementation wrapper for list query processing, providing the executable PL/SQL logic that supports the definition, maintenance, and validation of list queries used by Oracle Marketing and its integrated modules. As a _PVT (private) package, it is not part of the public API surface and is intended for invocation by sibling packages and internal Marketing framework code rather than by external or customer-written integrations. The package is documented as VALID in the ETRM repository for release 12.1.1 and 12.2.2, and it is classified under the "OTHER" API category, confirming that it is a supporting, non-published component. It is referenced by two other database packages, indicating that it sits beneath the public list query API and supplies reusable internal logic to those callers.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within this package body. The following are explicitly named in the documented set:

  • CREATE_LIST_QUERY — Creates a new list query record, establishing the query definition used to drive list membership.
  • UPDATE_LIST_QUERY — Applies modifications to an existing list query definition.
  • VALIDATE_LIST_QUERY — Performs validation on a list query, confirming that required attributes and structural conditions are satisfied.
  • VALIDATE_LIST_QUERY_REC — A record-level validation routine, used to validate a single list query row or record structure.
  • CHECK_LIST_QUERY_ITEMS — Verifies the query item associations that make up a list query, ensuring item integrity before processing.

In addition to the functional routines above, the package contains six Rosetta table conversion utilities: ROSETTA_TABLE_COPY_IN_P2, ROSETTA_TABLE_COPY_OUT_P2, ROSETTA_TABLE_COPY_IN_P6, and ROSETTA_TABLE_COPY_OUT_P6 (as documented). These routines are PL/SQL table (index-by table) conversion helpers that move data between generic column tables and typed PL/SQL table structures. They rely on the JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_4000, and PL/SQL PLITBLM constructs for parameter passing. No parameter lists are reproduced here, in accordance with the documented metadata scope.

Tables Accessed

The documented dependency list for this package body shows a single table reference, PLITBLM, accessed through an APPS synonym. PLITBLM is the standard Oracle EBS work table used in conjunction with PL/SQL table buffering and Rosetta-style conversion routines; it does not represent a persistent business entity but rather a staging mechanism for passing data between PL/SQL and the calling environment. All business-level list query data manipulation is performed indirectly through the public package AMS_LIST_QUERY_PVT, on which this private wrapper depends, along with the FND_API error and message handling utilities. This layered design means the private package concentrates on validation, conversion, and control flow rather than direct table maintenance.

Usage Notes

Because AMS_LIST_QUERY_PVT_W is a private package body, it is not called directly from Oracle Forms, concurrent program definitions, or customer extensions. Its routines are invoked by the two dependent packages identified in the ETRM metadata, which in turn expose the public list query API used by the Oracle Marketing user interface and batch processes. Customizations that need to create, update, or validate list queries should therefore target the public AMS_LIST_QUERY_PVT package rather than this private implementation. Any change to this package body carries upgrade risk in both 12.1.1 and 12.2.2, since it is a standard Oracle-shipped object and is not supported for direct modification; the documented classification as a non-public API reinforces that it should be treated as an internal implementation detail of the Marketing list query framework.