Results for “trigger_type”

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

Overview

HR_TRIGGER_STATUS_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and associated with the PAY (Payroll) product module. In EBS 12.1.1 and 12.2.2, the view presents the status and definition of database triggers that are owned by APPS and attached to tables in the HR schema. Its single, narrow function is to expose a filtered subset of the data dictionary view ALL_TRIGGERS, restricted to the intersection of the APPS trigger owner and the HR table owner.

The view is not a transactional or payroll data object. It is an administrative and diagnostic view used by DBAs, technical consultants, and support analysts to verify the state of HR trigger objects after patching, cloning, upgrades, or product installation. Because HR triggers are integral to payroll and human resources processing logic, their validity and enabled/disabled status have direct bearing on application behavior, and this view provides a supported, APPS-owned window into that metadata.

Underlying Base Objects

The view is defined over a single documented base object, ALL_TRIGGERS, which is exposed in the APPS schema as a SYNONYM. ALL_TRIGGERS is an Oracle data dictionary view that describes triggers owned by the current user or accessible to it, across all objects. The definition of HR_TRIGGER_STATUS_V applies a WHERE clause with two fixed predicates: OWNER = 'APPS' and TABLE_OWNER = 'HR'. Consequently, the view returns only those triggers created in the APPS schema whose base table resides in the HR schema.

Because the view references ALL_TRIGGERS rather than a stored application table, it is always current. It performs no materialization, caching, or snapshotting. Any change to trigger status, such as a trigger being disabled during an upgrade step or re-enabled afterward, is immediately reflected the next time the view is queried. The view itself holds no data and is not registered as an updatable or key-preserved object.

Key Columns

The view exposes fourteen columns inherited directly and unmodified from ALL_TRIGGERS:

• OWNER — the owner of the trigger; always APPS in this view.
• TRIGGER_NAME — the unique name of the trigger, the primary identifier used when a user searches for "trigger_name".
• TRIGGER_TYPE — the firing configuration, such as BEFORE STATEMENT, AFTER EACH ROW, or INSTEAD OF.
• TRIGGERING_EVENT — the DML or system event that fires the trigger (INSERT, UPDATE, DELETE, and combinations).
• TABLE_OWNER — the schema owning the base table; always HR here.
• BASE_OBJECT_TYPE — the type of the base object the trigger is attached to, typically TABLE or VIEW.
• TABLE_NAME — the HR table on which the trigger is defined.
• COLUMN_NAME — the specific column named in an UPDATE OF clause, when applicable.
• REFERENCING_NAMES — the correlation names (OLD and NEW) used inside the trigger body.
• WHEN_CLAUSE — the optional conditional expression governing firing.
• STATUS — the state of the trigger, ENABLED or DISABLED.
• DESCRIPTION — descriptive text about the trigger, where populated.
• ACTION_TYPE — the action performed by the trigger body.
• TRIGGER_BODY — the actual PL/SQL source executed when the trigger fires.

Common Use Cases and Queries

Typical usage centers on auditing trigger presence and status. To locate a trigger by name, a straightforward query applies the search term to TRIGGER_NAME:

• SELECT trigger_name, table_name, trigger_type, status FROM apps.hr_trigger_status_v WHERE trigger_name LIKE '%TRIGGER_NAME%';
• SELECT table_name, trigger_name, status FROM apps.hr_trigger_status_v ORDER BY table_name, trigger_name;
• SELECT trigger_name, table_name FROM apps.hr_trigger_status_v WHERE status = 'DISABLED';
• SELECT trigger_name, trigger_body FROM apps.hr_trigger_status_v WHERE table_name = 'PER_ALL_PEOPLE_F';

The view supports patch verification, post-clone validation, impact analysis before schema changes, and troubleshooting of DML anomalies traced to disabled HR triggers. It should be used for inspection only; trigger state changes must be performed through supported patching and administration utilities.