Search Results update_trigger

Overview

AMS_TRIGGER_PVT is a private API wrapper package in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments within the Advanced Marketing (AMS) product family. Its purpose is to provide an internal, application-facing layer that consolidates calls to the three core trigger APIs: Create_Trigger, Update_Trigger, and Activate_Trigger. In addition to orchestrating these APIs, the package invokes the engine API responsible for either canceling or starting a workflow process. This centralized control point ensures that trigger-related business logic—such as creating a trigger row, associating threshold checks and actions, and activating trigger workflows—is executed in a consistent order and with uniform validation. Because it is classified as a Private (PVT) package, it is not exposed to external customers as a public API; instead, it is consumed by other AMS packages and internal engine components.

The package header shows an original creation date in 1999, with later modifications reflecting standards changes and the addition of the activate_trigger procedure in 2006, indicating that it is a longstanding component of the AMS trigger framework.

Key Procedures and Functions

Three documented procedures are exposed by AMS_TRIGGER_PVT:

• CREATE_TRIGGER — Creates rows in the ams_triggers, ams_trigger_checks, and ams_trigger_actions tables to satisfy the caller’s trigger definition. It accepts a trigger record, an optional threshold check record, and a threshold action record, and returns identifiers for the created trigger check, trigger action, and trigger. The procedure handles the full creation lifecycle of a trigger entity.
• UPDATE_TRIGGER — Modifies an existing trigger definition. This is the procedure the user searched for under the term "update_trigger." It applies changes to the trigger and its associated threshold checks and actions, ensuring that updates remain consistent with the private wrapper’s validation and orchestration logic.
• ACTIVATE_TRIGGER — Added in 2006, this procedure activates a trigger and initiates or cancels the associated workflow process through the engine API. It bridges the trigger definition and the runtime workflow behavior.

Tables Accessed

The package references three documented tables via APPS synonyms:

• AMS_TRIGGERS — Stores the master trigger definitions, including trigger header information.
• AMS_TRIGGER_ACTIONS — Holds the actions to be taken when a trigger fires. Historically, a separate trigger actions table was phased out, and this table is the current repository for action mappings.
• WF_PARAMETER_LIST_T — A Workflow parameter list table used when invoking workflow processes to start or cancel trigger-related workflows.

These tables support the creation, update, and activation flows, with WF_PARAMETER_LIST_T specifically supporting the engine API interaction for workflow control.

Usage Notes

Because AMS_TRIGGER_PVT is a private package, it is not intended for direct invocation by end users or external customizations. It is referenced by two other packages within the AMS module, which likely serve as the public entry points for trigger creation, update, and activation. Typical invocation occurs through:

• Forms or OAF pages — Trigger setup and maintenance screens in the Advanced Marketing module indirectly call this package via its public callers.
• Concurrent programs or workflow engine calls — Activation routines, including workflow start and cancel operations, rely on the activate_trigger procedure and the engine API.
• Internal AMS code — Other private packages invoke it to maintain trigger data integrity during setup or runtime processing.

Custom code should avoid calling AMS_TRIGGER_PVT directly; instead, it should use the supported public APIs that wrap it. When troubleshooting trigger updates in 12.1.1 or 12.2.2, developers may trace into UPDATE_TRIGGER to understand how trigger, threshold check, and action changes are persisted and how workflow state is synchronized.