Results for “generated_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PAY_TRIGGER_EVENTS_V view is a payroll-module reporting object that exposes the configuration of trigger events used by Oracle Payroll's event-driven processing framework. A trigger event defines a database table, the action that fires when data changes on that table, and the state flags governing whether the trigger is generated, enabled, or protected from modification. The view joins the base trigger-event definition table to Oracle Application Object Library reference data so that raw identifiers are resolved into human-readable application and table names.

The view is defined over PAY_TRIGGER_EVENTS and enriches each row with the owning application name and the descriptive text of the underlying table. Because Oracle EBS delivers this object with a status of VALID in the APPS schema, it is available to any reporting, integration, or diagnostic query running with APPS-level privileges. It is most commonly used to audit which tables are wired into payroll event processing, to confirm whether a trigger is active, and to detect rows that have been marked as protected against regeneration.

Underlying Base Objects

The documented base objects referenced by the view are FND_APPLICATION_ALL_VIEW (a view), FND_GLOBAL (a package), FND_TABLES (a synonym), and PAY_TRIGGER_EVENTS (a synonym). The view's defining SQL joins FND_TABLES to FND_APPLICATION_ALL_VIEW on APPLICATION_ID, then joins the result to PAY_TRIGGER_EVENTS on TABLE_NAME.

• PAY_TRIGGER_EVENTS — the primary driver table holding one row per trigger event, keyed by EVENT_ID.
• FND_TABLES — supplies the table description that the view presents as TABLE_DESCRIPTION.
• FND_APPLICATION_ALL_VIEW — resolves the APPLICATION_ID to the APPLICATION_NAME displayed in the output.
• FND_GLOBAL — the standard EBS session context package, referenced for runtime identification of the current user, login, and responsibility.

The join on TABLE_NAME means that only trigger events whose target table is registered in FND_TABLES with a matching application will appear in the result set. Events pointing at unregistered tables are silently excluded.

Key Columns

• EVENT_ID — the primary identifier of the trigger event.
• APPLICATION_NAME — the application that owns the target table, resolved from FND_APPLICATION_ALL_VIEW.
• TABLE_NAME — the database table whose changes drive the event.
• SHORT_NAME — the abbreviated internal name of the event.
• DESCRIPTION — the trigger event description from PAY_TRIGGER_EVENTS.
• TABLE_DESCRIPTION — the description of the target table from FND_TABLES.
• GENERATED_FLAG, ENABLED_FLAG, PROTECTED_FLAG — status flags indicating whether the trigger has been generated, is currently active, and is protected from automatic regeneration or deletion. The PROTECTED_FLAG is the column most frequently queried, as it distinguishes seed data that must not be modified from customer-defined events.
• TRIGGERING_ACTION — the action performed when the event fires.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include auditing enabled versus disabled events, identifying protected (seed) events prior to upgrade or patching, and reconciling trigger configuration across environments. The following examples illustrate standard access patterns.

• List all enabled events for a given application:
  SELECT event_id, application_name, table_name, short_name, trigger_action FROM pay_trigger_events_v WHERE application_name = 'Oracle Payroll' AND enabled_flag = 'Y';
• Identify protected events that should not be altered:
  SELECT table_name, short_name, protected_flag FROM pay_trigger_events_v WHERE protected_flag = 'Y';
• Review events whose triggers have not yet been generated:
  SELECT event_id, table_name, short_name, generated_flag FROM pay_trigger_events_v WHERE generated_flag = 'N';