Search Results pay_trigger_events_pk

Overview

PAY_TRIGGER_EVENTS is a core Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of database triggers that are generated dynamically by the Oracle Payroll engine. Rather than relying solely on statically defined database triggers, Oracle Payroll uses a metadata-driven mechanism in which trigger definitions are stored as rows, and the corresponding PL/SQL trigger text is constructed at runtime from associated components, declarations, initialisations, and support code. PAY_TRIGGER_EVENTS is therefore best understood as the master registry of payroll trigger events, and each child table that references it contributes one piece of the dynamically assembled trigger body.

From a Data Vault modeling perspective, the foreign-key topology classifies PAY_TRIGGER_EVENTS heuristically as a hub. Five separate tables (functional triggers, components, declarations, initialisations, and support) each carry a foreign key of EVENT_ID pointing back to this table, and all of them behave as satellites or dependent links keyed by that hub identity. This makes the table a natural anchor for any integration or warehouse model that needs to reference payroll trigger events by a stable business key.

Key Information Stored

The table holds 14 documented columns. The most important are:

• EVENT_ID — the surrogate primary key, defined by the unique index PAY_TRIGGER_EVENTS_PK (combined with ZD_EDITION_NAME in the 12.2.2 edition-aware schema). This is the join key used by all five child tables.
• SHORT_NAME — the human-readable business key. A second unique index, PAY_TRIGGER_EVENTS_UK1 (SHORT_NAME, ZD_EDITION_NAME), guarantees uniqueness on this column alone, making it the primary business-key candidate.
• TABLE_NAME — identifies the database table on which the dynamically generated trigger is defined.
• DESCRIPTION — free-text explanation of the trigger event's purpose.
• GENERATED_FLAG — indicates whether the trigger has been generated from its stored definitions.
• ENABLED_FLAG — controls whether the trigger event is active in the payroll engine.
• PROTECTED_FLAG — marks events that should not be modified or deleted by users, typically seeded Oracle definitions.
• TRIGGERING_ACTION — the DML action (for example INSERT, UPDATE, or DELETE) that fires the trigger.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE follow the standard EBS WHO column convention.
• ZD_EDITION_NAME — the editioning column introduced in Release 12.2 for online patching, allowing multiple editions of a trigger definition to coexist.

Common Use Cases and Queries

Typical scenarios include auditing which trigger events are enabled, tracing the complete generated code for an event, and diagnosing why a payroll DML trigger fires unexpectedly. A simple lookup by business key:

• SELECT event_id, table_name, triggering_action, enabled_flag FROM pay_trigger_events WHERE short_name = :p_short_name;
• SELECT short_name, table_name, generated_flag, protected_flag FROM pay_trigger_events WHERE enabled_flag = 'Y';

To reconstruct the full definition of an event, join the child tables on EVENT_ID: PAY_TRIGGER_DECLARATIONS, PAY_TRIGGER_INITIALISATIONS, PAY_TRIGGER_COMPONENTS, PAY_TRIGGER_SUPPORT, and PAY_FUNCTIONAL_TRIGGERS. Reporting queries frequently list protected versus customer-defined events, or count events per target table. Administrators should treat seeded rows (where PROTECTED_FLAG = 'Y') as read-only.

Related Objects

The following tables reference PAY_TRIGGER_EVENTS through the EVENT_ID foreign key and together supply the dynamically generated trigger text:

• PAY_FUNCTIONAL_TRIGGERS — EVENT_ID → PAY_TRIGGER_EVENTS.EVENT_ID; defines the functional trigger body.
• PAY_TRIGGER_COMPONENTS — EVENT_ID → PAY_TRIGGER_EVENTS.EVENT_ID; constituent code components of the trigger.
• PAY_TRIGGER_DECLARATIONS — EVENT_ID → PAY_TRIGGER_EVENTS.EVENT_ID; PL/SQL declaration sections.
• PAY_TRIGGER_INITIALISATIONS — EVENT_ID → PAY_TRIGGER_EVENTS.EVENT_ID; initialisation logic executed by the trigger.
• PAY_TRIGGER_SUPPORT — EVENT_ID → PAY_TRIGGER_EVENTS.EVENT_ID; supporting procedures and helper code.

Together these objects form the complete metadata model from which Oracle Payroll assembles and manages its dynamic triggers in Release 12.1.1 and 12.2.2.