Search Results check_list_association

Overview

APPS.AMS_LIST_MAINT_PVT is a private (PVT) PL/SQL package within the Oracle Marketing (AMS) module of Oracle E-Business Suite, released under versions 12.1.1 and 12.2.2. It provides the internal maintenance infrastructure for marketing list management, handling the creation of source views, copying of list definitions, association validation, scheduling, generation submission, and Discoverer-based list interrogation. The package is declared with AUTHID CURRENT_USER, meaning that its unqualified database references resolve against the privileges of the invoking session rather than the package owner. Because it is classified as a private API, it is not intended for direct customer invocation; it is called by the public list-management interfaces, concurrent programs, and Oracle Forms that present the list workbench. The header comment dates to version 115.23 and documents corrective work spanning the original 2000 development cycle, indicating a long-lived component of the AMS list architecture.

Key Procedures and Functions

• CREATE_SOURCE_VIEW — Builds a database view from the column mapping metadata stored in AMS_LIST_SRC_TYPES and AMS_LIST_SRC_FIELDS. The mapping type is selected through a source-type parameter that distinguishes IMPORT from TARGET usage, and a source-type code identifies the specific mapping. Only columns mapped in FIELD_TABLE_NAME are projected, and each column is aliased to the corresponding SOURCE_COLUMN_MEANING. This dynamic DDL underpins the transfer of external or internal source data into marketing lists.
• COPY_LIST — Duplicates an existing list definition, including its associated entries and configuration, so that a new list can be created from a template or prior campaign without re-entry.
• CHECK_LIST_ASSOCIATION — Validates the relationships between a list and its dependent entities, ensuring that associations recorded in the source-type association tables remain consistent before further processing.
• SCHEDULE_LIST — Registers a list for timed processing, establishing the schedule under which generation or refresh activities will execute.
• SUBMIT_LIST_FOR_GENERATION — The entry point most commonly associated with the search term "submit_list_for_generation." It submits a list for generation processing, moving the list from a defined state into the queue that produces its member entries. Internally it selects the relevant actions from AMS_LIST_SELECT_ACTIONS and drives the population of AMS_LIST_ENTRIES.
• CREATE_DISCOVERER_URL — Constructs the Oracle Discoverer URL that allows users to browse or analyze a list through the Discoverer end-user layer.

Tables Accessed

The package operates across the core AMS list schema. AMS_LIST_HEADERS_ALL stores the list header definitions that anchor copy, schedule, and generation operations. AMS_LIST_ENTRIES holds the individual list members produced during generation and consumed during copy. AMS_LIST_SELECT_ACTIONS defines the selection criteria and actions that drive generation, and is read by SUBMIT_LIST_FOR_GENERATION to determine how entries are selected. AMS_LIST_SRC_TYPES and AMS_LIST_SRC_FIELDS together supply the mapping metadata used by CREATE_SOURCE_VIEW, while AMS_LIST_SRC_TYPE_ASSOCS records the associations validated by CHECK_LIST_ASSOCIATION. AD_DDL is the Applications DDL utility invoked to execute the dynamic CREATE VIEW statement generated inside CREATE_SOURCE_VIEW.

Usage Notes

AMS_LIST_MAINT_PVT is invoked indirectly. Oracle Forms in the marketing list workbench call these procedures when a user copies a list, schedules it, or presses the generate action; a concurrent program wrapper is responsible for the asynchronous generation run that SUBMIT_LIST_FOR_GENERATION initiates. Scheduled execution is normally performed through request submission rather than direct calls. Custom code should call the corresponding public AMS list APIs instead of this private package, since the signatures and behavior of private APIs may change between patch levels and are not covered by Oracle's public API compatibility policy. When troubleshooting a list that fails to generate, DBMS_OUTPUT tracing and review of the AMS_LIST_ENTRIES and AMS_LIST_SELECT_ACTIONS rows are the usual diagnostic path, together with confirmation that any required source view created by CREATE_SOURCE_VIEW exists and is valid. Invalid views remain the most frequent cause of generation failure, because the view is built dynamically and depends on the mapping rows being complete and correctly typed.