Search Results check_tar




Overview
Explore in AI Chat

Overview

APPS.AMS_LIST_WF is a PL/SQL package that provides the Oracle Workflow callback procedures used by Oracle Marketing (originally Oracle Marketing Online, or OMO) during list generation. The package header carries the version marker $Header: amsvwlis.pls 120.1 2005/06/27 05:42:09 appldev ship $ and is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner. Its stated purpose is to contain the workflow procedures for list generation in OMO. Functionally, the package binds the marketing list build process to a Workflow item type: it launches the workflow for a given list header, drives list generation and target generation activities, validates those activities, initializes workflow item attributes, and provides a controlled termination path. It is classified as OTHER in the ETRM registry and is referenced by two other packages.

Key Procedures and Functions

  • StartProcess — launches the workflow flow for a list build, accepting a list header identifier and an optional workflow process name.
  • Generate_List — workflow activity function that invokes generation of the list itself.
  • Check_SCH — workflow activity function that validates or checks the scheduling step of the flow.
  • Gen_Target — workflow activity function that performs target (audience) generation for the list.
  • Check_TAR — workflow activity function that validates the target generation step.
  • StartListBizEventProcess — starts an associated business event process for a given list header identifier.
  • Wf_Init_Var — initializes workflow item variables/attributes used by the list flow.
  • Wf_Abort_Process — aborts the workflow process for a given list header identifier, providing the termination path for failed or cancelled builds. This is the routine most commonly associated with the search term wf_abort_process.
  • Check_Item_Key — validates the workflow item key, ensuring the flow is bound to a legitimate list instance before activities execute.

Procedures declared with the standard workflow activity signature (itemtype, itemkey, actid, funcmode, result) — Generate_List, Check_SCH, Gen_Target, Check_TAR, Wf_Init_Var, and Check_Item_Key — are invoked directly by the Workflow Engine as activity callbacks.

Tables Accessed

  • AMS_LIST_HEADERS_ALL — master record for each marketing list; the package reads and updates list-level status during generation and abort.
  • AMS_ACT_LISTS — association between lists and marketing activities, used to determine the scope of target generation.
  • JTF_RS_RESOURCE_EXTNS — resource extension information supporting audience/target qualification of list members.
  • WF_ITEM_ACTIVITY_STATUSES — Workflow runtime status of activities; consulted to determine current flow position and updated when aborting or completing steps.
  • WF_PARAMETER_LIST_T — workflow parameter list type used to pass context between the package and the Workflow Engine.

Usage Notes

AMS_LIST_WF is not intended for ad hoc invocation from forms. It is driven by the Oracle Workflow Engine, which calls the activity procedures by name when the list generation process type executes. The StartProcess and StartListBizEventProcess entry points are typically launched from the Oracle Marketing list-generation UI or from concurrent processing that submits a list build. Wf_Abort_Process is invoked when a list build must be terminated — for example, when a user cancels generation, when an error condition is detected, or during administrative cleanup of stuck workflow items. Because the package is AUTHID CURRENT_USER, custom callers must ensure the invoking schema holds the necessary privileges on the AMS and Workflow tables. When troubleshooting stalled list builds, DBAs commonly query WF_ITEM_ACTIVITY_STATUSES for the affected item key and then call Wf_Abort_Process with the corresponding list header identifier. Since it is referenced by two other packages, changes to its public signatures should be assessed for downstream impact. The package has been stable since its 2001 creation, with the shipping version dated June 2005, and remains applicable to 12.1.1 and 12.2.2 environments.