Search Results create_trigger

Overview

AMS_TRIGGER_PVT is a private PL/SQL API wrapper within the Oracle E-Business Suite (EBS) Advanced Marketing (AMS) module, implemented in the APPS schema. Its primary business function is to encapsulate and orchestrate the three distinct Trigger APIs used by the marketing application: create, update, and activation operations. As a Private (PVT) API, it is not intended for direct external invocation by customers; rather, it serves as an internal consolidation layer consumed by other AMS packages and public API wrappers. The package header comments explicitly describe its purpose as "a Private API Wrapper to Call the Three Trigger APIs," and it additionally calls the engine API to cancel or start the workflow process associated with a trigger. This dual responsibility—persisting trigger definitions and coordinating workflow engine state—makes AMS_TRIGGER_PVT central to how marketing triggers are managed and executed within Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM catalog documents three procedures within this package:

• CREATE_TRIGGER — Creates a new row in the AMS_TRIGGERS, AMS_TRIGGER_CHECKS, and AMS_TRIGGER_ACTIONS tables to satisfy caller requirements. It accepts a trigger record, threshold check record, and threshold action record as inputs, and returns the generated trigger check identifier, trigger action identifier, and trigger identifier. This procedure is the principal entry point for defining a new marketing trigger.
• UPDATE_TRIGGER — Modifies an existing trigger definition, allowing callers to revise trigger criteria, associated checks, and actions. It complements CREATE_TRIGGER by maintaining the integrity of previously defined triggers.
• ACTIVATE_TRIGGER — Added on 02/17/2006, this procedure activates a trigger and, per the package header, invokes the engine API to start or cancel the associated workflow process. This makes it the operational bridge between static trigger metadata and live workflow execution.

Internally, the package also contains the private routine ams_trigger_checks, referenced in the header comments as a supporting helper for create and update operations.

Tables Accessed

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

• AMS_TRIGGERS — The master table holding the core trigger definition. CREATE_TRIGGER inserts into it and returns the new trigger identifier.
• AMS_TRIGGER_ACTIONS — Stores the actions to be executed when a trigger fires. Although a historical comment (15-Feb-2001) notes that this table "will not be used anymore," ETRM metadata confirms it remains referenced within the package's data model.
• WF_PARAMETER_LIST_T — A Workflow parameter list table used when the engine API is invoked to start or cancel the workflow process associated with trigger activation.

Usage Notes

AMS_TRIGGER_PVT is classified as a PVT (private) API and is documented as referenced by two other packages. It is therefore not intended to be called directly from customer forms, concurrent programs, or custom code. Instead, it is invoked indirectly—typically through the public AMS trigger APIs or the marketing module's internal framework—when the application creates, updates, or activates a trigger. The package relies on the standard FND_API initialization conventions (p_api_version, p_init_msg_list, p_commit, p_validation_level, x_return_status, x_msg_count, x_msg_data), ensuring error handling and message stacking consistent with Oracle EBS API standards. Custom implementations requiring trigger manipulation should route requests through the supported public APIs rather than calling AMS_TRIGGER_PVT directly, as its signature and behavior may change across releases.