Search Results ams_trigger_results_s

Overview

APPS.AMS_CONTCAMPAIGN_PVT is a private (PVT classification) PL/SQL package body in the Oracle E-Business Suite Advanced Marketing (AMS) module. It implements the internal campaign trigger engine that evaluates marketing campaign activities against configurable business rules, records the outcome of each evaluation, and advances the trigger schedule. The package operates as the execution layer beneath the public AMS trigger APIs: it resolves trigger definitions, actions, and checks from the AMS schema, executes the associated SQL or metric logic, and persists results to the trigger results tables. Because the package is classified PVT, it is not intended as a public integration surface; it is expected to be invoked only by other AMS components, concurrent programs, or supported product code. Its dependency list includes FND_API, FND_MSG_PUB, FND_GLOBAL, FND_MESSAGE, and FND_PROFILE, confirming that it participates in the standard EBS API and message stack, and GL_CURRENCY_API and INV_CONVERT, indicating that campaign results may be expressed in multiple currencies or units of measure. In 12.1.1 and 12.2.2 the object is documented as VALID in the APPS schema, and ETRM records it as referenced by one other package while not itself referencing any database object outside the AMS and SYS/PLITBLM utility set.

Key Procedures and Functions

ETRM documents four procedures and functions within this package body:

• RECORD_RESULT — Persists the outcome of a trigger evaluation. This is the procedure responsible for inserting into AMS_TRIGGER_RESULTS and obtaining the surrogate key from AMS_TRIGGER_RESULTS_S, capturing which trigger fired, against which campaign activity, and with what result value.
• SCHEDULE_NEXT_TRIGGER_RUN — Determines and sets the next execution point for a trigger, allowing recurring or deferred trigger evaluations to be queued rather than executed immediately.
• VALIDATE_SQL — Verifies the syntactic and semantic validity of the SQL text stored in AMS_DISCOVERER_SQL or the trigger definition before that SQL is executed dynamically via DBMS_SQL.
• PERFORM_CHECKS — Executes the configured trigger checks (AMS_TRIGGER_CHECKS) against the relevant campaign metrics, evaluating conditions and driving the action path defined in AMS_TRIGGER_ACTIONS.

No parameter signatures are documented in the ETRM extract, and none should be assumed; the procedures are described here by purpose only.

Tables Accessed

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

• AMS_TRIGGERS — trigger definitions that drive evaluation logic.
• AMS_TRIGGER_ACTIONS — actions to be taken when a trigger condition is satisfied.
• AMS_TRIGGER_CHECKS — individual condition checks belonging to a trigger.
• AMS_TRIGGER_RESULTS and AMS_TRIGGER_RESULTS_S — the results table and its sequence, used by RECORD_RESULT to store evaluation outcomes.
• AMS_ACT_METRICS_ALL — activity metrics consulted during check evaluation.
• AMS_DISCOVERER_SQL — stored SQL used by discoverer-style queries and validated by VALIDATE_SQL.
• DBMS_SQL, DUAL, PLITBLM — dynamic SQL execution, scalar queries, and index-by-table bulk operations.

Usage Notes

AMS_CONTCAMPAIGN_PVT is normally invoked indirectly. Trigger evaluation is launched from AMS concurrent programs and from the campaign and trigger maintenance forms, which populate AMS_TRIGGERS, AMS_TRIGGER_ACTIONS, and AMS_TRIGGER_CHECKS; the package then performs the checks and records results. Because AMS_TRIGGER_RESULTS_S is referenced here, a search for that object typically leads to this package. Custom code should call the public AMS trigger APIs rather than this private package, since its interface may change between 12.1.1 and 12.2.2 without notice.