Search Results trigger_type




Overview
Explore in AI Chat

Overview

APPS.PAY_TRIGGER_STATIC_V is a reporting view in the Oracle E-Business Suite APPS schema whose definition is a direct projection of the data dictionary view ALL_TRIGGERS. Because its sole source is ALL_TRIGGERS, the view effectively re-publishes Oracle's static data dictionary information about database triggers within the EBS naming and access model. In EBS 12.1.1 and 12.2.2 the object is documented in the E-Business Suite Technical Reference Manual (ETRM) under the Oracle Payroll product family, where it is classified as a view with the owner APPS and a referenced base object of ALL_TRIGGERS (a synonym).

The view contains no business logic, joins, or filters. Its purpose is to expose trigger metadata—such as the owning table, trigger name, trigger type, triggering event, action type, status, and the optional WHEN clause—through a stable APPS-owned interface. This allows the Payroll application and its supporting diagnostics to interrogate trigger definitions without querying the SYS-owned dictionary objects directly, which is consistent with the EBS practice of layering APPS views over underlying dictionary or application tables.

Underlying Base Objects

The documented base object is ALL_TRIGGERS, appearing in the ETRM metadata as a synonym. ALL_TRIGGERS is the standard Oracle data dictionary view that describes triggers on tables and views accessible to the current user. It is owned by SYS and is normally accessed through public synonyms. By defining PAY_TRIGGER_STATIC_V as a simple SELECT from ALL_TRIGGERS, Oracle ensures the view inherits the dictionary's semantics, including its public accessibility and its restriction to objects visible to the querying schema. The descriptor "STATIC" reflects that the view reports static, structural metadata about trigger definitions rather than runtime trigger execution data.

Key Columns

  • TABLE_NAME — the name of the table or view on which the trigger is defined.
  • TRIGGER_NAME — the unique name of the trigger.
  • TRIGGER_TYPE — the timing and level classification, for example BEFORE STATEMENT, BEFORE EACH ROW, AFTER EACH ROW, or INSTEAD OF.
  • TRIGGERING_EVENT — the DML or system event that fires the trigger, such as INSERT, UPDATE, DELETE, or combinations expressed with OR.
  • ACTION_TYPE — the type of action performed, typically PL/SQL or CALL.
  • STATUS — the enabled or disabled state of the trigger (ENABLED or DISABLED).
  • WHEN_CLAUSE — the optional boolean condition that must evaluate true before the trigger body executes; null when no condition applies.
  • DESCRIPTION — descriptive text associated with the trigger where one has been defined.

Common Use Cases and Queries

The view is used to inventory and audit trigger definitions, particularly for Payroll-related tables, and to confirm that triggers created during patch application are enabled as expected. A typical query lists all triggers associated with Payroll objects.

  • SELECT table_name, trigger_name, trigger_type, triggering_event, status FROM apps.pay_trigger_static_v WHERE table_name LIKE 'PAY%' ORDER BY table_name, trigger_name;
  • SELECT trigger_name, triggering_event, when_clause FROM apps.pay_trigger_static_v WHERE status = 'DISABLED';
  • SELECT table_name, trigger_name, action_type FROM apps.pay_trigger_static_v WHERE trigger_type = 'AFTER EACH ROW';

Because the view is a direct projection of ALL_TRIGGERS, results are limited to triggers on objects visible to the querying user. In EBS this normally means APPS-visible and publicly accessible objects. The view provides a convenient, supportable means of reviewing trigger metadata during diagnostics, upgrade validation, and post-patch verification without requiring direct access to SYS dictionary views.