Search Results schedule_next_trigger_run

Overview

APPS.AMS_CONTCAMPAIGN_PVT is a private PL/SQL package in the Oracle Marketing (AMS) module responsible for executing continuous campaigning logic. Continuous campaigning enables marketers to define recurring triggers that monitor customer behavior, transaction data, or other business events, and to fire associated actions when defined conditions are satisfied. The package encapsulates the runtime engine that evaluates trigger checks, records the outcome of each evaluation, schedules subsequent trigger executions, and validates the SQL statements that drive Discoverer-based condition queries.

The package is classified as PVT (private), meaning its interface is intended for internal consumption by Oracle Marketing's own modules rather than as a public API for customer extensions. Its header identifies the module as AMS_Campaign_PVT in early comments, reflecting historical naming before the object was finalized as AMS_CONTCAMPAIGN_PVT. The package was originally created in July 1999 and remains relevant through EBS 12.1.1 and 12.2.2, with a 2005 revision adding the ability to store the recipient of a notification action.

Key Procedures and Functions

• PERFORM_CHECKS — Evaluates the conditions configured against a continuous campaign trigger. It determines whether the trigger's criteria have been met for a given subject or population, forming the decision point that governs whether downstream actions should execute.
• RECORD_RESULT — Persists the outcome of check evaluation and any resulting action. As documented, it records results of both the check and the action, and a 2005 enhancement added storage of the identity of the notification recipient (who the NTF was sent to). This is the procedure surfaced by the search term "record_result."
• SCHEDULE_NEXT_TRIGGER_RUN — Computes and registers the next execution time for a continuous campaign trigger, supporting the recurring, always-on nature of continuous campaigning.
• VALIDATE_SQL — Validates SQL statements derived from Discoverer workbooks. The package declares an exception valid_no_columns (bound to Oracle error -1007) to detect when a Discoverer query returns a single column, which is the expected shape for a condition query.

Tables Accessed

The package operates against the core continuous campaigning and trigger infrastructure tables:

• AMS_TRIGGERS — Trigger definitions driving the campaign.
• AMS_TRIGGER_CHECKS — Condition definitions evaluated by PERFORM_CHECKS.
• AMS_TRIGGER_ACTIONS — Actions to be executed when checks pass.
• AMS_TRIGGER_RESULTS and AMS_TRIGGER_RESULTS_S — Stores evaluation and action outcomes via RECORD_RESULT.
• AMS_ACT_METRICS_ALL — Action metric data associated with executed actions.
• AMS_DISCOVERER_SQL — Discoverer workbook SQL consumed by VALIDATE_SQL.
• DBMS_SQL, DUAL, PLITBLM — Utilities for dynamic SQL parsing/execution and internal PL/SQL table management.

Usage Notes

AMS_CONTCAMPAIGN_PVT is invoked internally by Oracle Marketing's continuous campaigning engine rather than directly by end users. It is typically called by concurrent programs or background processes that evaluate triggers on a scheduled basis, with SCHEDULE_NEXT_TRIGGER_RUN chaining subsequent executions. The package is referenced by one other package within the application, confirming its role as an internal dependency. Custom code should not call this private package directly; extensions should use supported public APIs. When troubleshooting continuous campaign behavior or notification delivery, Record_Result is the relevant entry point for verifying what was checked, what action fired, and to whom the notification was sent.