Search Results check_trig_req_items

Overview

APPS.AMS_TRIG_PVT_W is a private PL/SQL API package belonging to the Oracle Marketing (AMS) module of Oracle E-Business Suite. It exists to service the trigger entity used within campaign and marketing activity processing. In EBS terminology, a "trigger" is a record-driven event definition — a condition or action that fires when associated marketing activity criteria are satisfied. The package encapsulates the server-side create, update, validation, and completion logic that surrounds the public trigger API surface, shielding callers from the underlying validation framework and record state machine.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the calling schema rather than the APPS owner. The header identifies it as an internal/private implementation package (the "_PVT_W" suffix denotes a private worker package generated in the JTF/AMS API style), and the source header revision ($Header: amswtrgs.pls 115.13 2003/07/03) indicates the code has been stable since the 11.5.x stream and carries forward into 12.1.1 and 12.2.2 without functional change.

Key Procedures and Functions

• CREATE_TRIGGER — Inserts a new trigger record. It follows the standard EBS API signature convention (p_api_version, p_init_msg_list, p_commit, p_validation_level, plus x_return_status, x_msg_count, and x_msg_data OUT parameters), returns x_trigger_id, and accepts a long positional argument list (p7_a0 through p7_a31) in which the logical column names are substituted by generic placeholders with FND_API missing-value defaults.
• UPDATE_TRIGGER — Applies modifications to an existing trigger row using the same convention, again exposing positional attributes that map to columns of the underlying trigger schema.
• VALIDATE_TRIGGER — Performs attribute-level and entity-level validation prior to a persistence call, enforcing required fields, domain constraints, and cross-attribute consistency.
• CHECK_TRIG_ITEMS — Validates the line/item details associated with a trigger definition.
• CHECK_TRIG_RECORD — Validates the trigger record itself, typically invoked at the top of create or update processing.
• CHECK_TRIG_REQ_ITEMS — The routine the user's search term refers to. It verifies that the required item set for a trigger is present and complete before the record is accepted, guarding against incomplete trigger definitions reaching the transaction tables.
• INIT_TRIG_REC — Initializes an in-memory trigger record structure with default values, preparing the PL/SQL record for population by higher-level callers.
• COMPLETE_TRIG_REC — Finalizes the trigger record, typically restoring or resolving derived attributes after initialization and validation.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables it touches. In practice the package operates on the AMS trigger and trigger-item tables — the parent trigger definition table and its associated detail tables — through APPS-owned synonyms. These are read to validate existing records and written during create and update processing; the check routines read only, while create_trigger and update_trigger perform insert and update DML.

Usage Notes

AMS_TRIG_PVT_W is not intended for direct customer invocation. It is consumed by the public AMS trigger API layer, by Oracle Marketing forms (such as the trigger setup and campaign activity screens), and by concurrent programs that create or refresh trigger definitions. Customizations should call the corresponding public API rather than this private worker package, because the private signatures use positional placeholders (p7_a0…p7_a31) that are not stable across patches. The metadata records zero dependent packages, confirming it sits at a leaf of the call graph. Developers diagnosing "check_trig_req_items" failures should treat the message as an incomplete-attribute diagnostic raised during create or update trigger validation.