Search Results ams_list_wf




Overview
Explore in AI Chat

Overview

The APPS.AMS_LIST_WF package body is a PL/SQL workflow integration component within the Oracle E-Business Suite Marketing (AMS) module. Its principal business function is to orchestrate the Oracle Workflow processes that drive list generation and list-related business events. In Oracle Marketing, a "list" represents a targeted set of customers, prospects, or resources assembled for a campaign or telemarketing activity. The AMS_LIST_WF package acts as the bridge between the Marketing list data model and the Workflow Engine, enabling asynchronous and event-driven processing of list creation, target generation, and scheduled list activities.

The package is classified as an OTHER API in ETRM 12.2.2, meaning it is an internal support package rather than a formally published public API. It resides in the APPS schema and is marked VALID in both 12.1.1 and 12.2.2 environments. Notably, the metadata states that APPS.AMS_LIST_WF is not referenced by any database object, confirming it is invoked at runtime by application logic rather than being compiled as a dependency of other packages. The package itself, however, references two dependent packages that are tracked as "referenced by 2 other packages."

Key Procedures and Functions

ETRM documents nine procedures and functions within this package body:

  • STARTPROCESS — Initiates a workflow process associated with a list, establishing the workflow item context and launching the defined process activity.
  • GENERATE_LIST — Triggers the list generation logic, coordinating with the list generation package to populate the list of targets based on the defined selection criteria.
  • CHECK_SCH — Validates and evaluates scheduling conditions for a list, determining whether the associated process should proceed based on schedule state.
  • GEN_TARGET — Generates target records for the list, populating the activity list membership.
  • CHECK_TAR — Verifies target-related conditions, likely confirming that targets exist or meet qualifying criteria before subsequent workflow steps execute.
  • STARTLISTBIZEVENTPROCESS — Raises and starts the business event workflow process for a list, integrating with the Workflow Event system to broadcast list-related business events.
  • WF_INIT_VAR — Initializes workflow item attributes and variables prior to process execution.
  • WF_ABORT_PROCESS — Terminates an in-flight workflow process associated with a list, used for error handling or cancellation.
  • CHECK_ITEM_KEY — Validates the workflow item key to ensure the workflow instance for a list is correctly identified and active.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

  • AMS_ACT_LISTS — Stores activity list membership, i.e., the generated target entries produced by GEN_TARGET.
  • AMS_LIST_HEADERS_ALL — The master list header table; read to retrieve list definitions and updated as list status changes during processing.
  • JTF_RS_RESOURCE_EXTNS — Holds resource extension attributes for the CRM resource model, used when resolving list targets to resources.
  • WF_ITEM_ACTIVITY_STATUSES — The Workflow runtime table tracking the activity status of each workflow item; queried and updated by CHECK_ITEM_KEY, WF_ABORT_PROCESS, and related routines.
  • WF_PARAMETER_LIST_T — The Workflow parameter list type used to pass attributes into and out of workflow processes.

Usage Notes

AMS_LIST_WF is invoked indirectly through the Marketing list generation and campaign execution flows, and through Oracle Workflow event subscriptions. It is not typically called directly from custom code; instead, the standard Oracle Marketing forms (such as the List Definition and List Generation windows) and concurrent programs call the underlying AMS_LISTHEADER_PVT and AMS_LISTGENERATION_PKG packages, which in turn invoke the workflow entry points in this package. Because the package is not referenced by any database object, it functions as a leaf-level runtime utility. Developers extending list processing should treat the nine documented routines as internal and prefer the published Marketing APIs for customization.