Search Results pay_trigger_support

Overview

PAY_TRIGGER_SUPPORT is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to allow a support package for a dynamically generated trigger to be linked to that trigger. In the Oracle Payroll architecture, payroll formulas and rules are compiled into dynamically generated database triggers that fire during payroll processing, and this table stores the supporting PL/SQL package code (or references to it) associated with each such trigger event. It therefore functions as a metadata repository for the generated code layer that underpins payroll business rules.

From a Data Vault modeling perspective, the ETRM relationship data classifies this table as satellite-leaning. The table does not represent a standalone business concept (hub) or a pure many-to-many association (link); instead it hangs off the PAY_TRIGGER_EVENTS table via a foreign key and carries descriptive and code-bearing attributes. This suggests it is best modeled as a satellite attached to the trigger event hub or link, capturing the support-package detail for each trigger event.

Key Information Stored

The table is documented with five columns. The most important are:

• SUPPORT_ID — the surrogate primary key, defined by the PAY_TRIGGER_SUPPORT_PK unique index (in combination with ZD_EDITION_NAME). It uniquely identifies each support-package record.
• EVENT_ID — the foreign key to PAY_TRIGGER_EVENTS, establishing which trigger event the support package is linked to. This is the principal business-key column and the join path to the parent event definition.
• HEADER_CODE — stores the package header or specification code associated with the generated trigger support logic.
• BODY_CODE — stores the package body or implementation code for the support logic.
• ZD_EDITION_NAME — the editioning column introduced by the EBS 12.2 online patching (edition-based redefinition) model. It appears in the primary key index, meaning uniqueness is scoped per edition.

The primary key is PAY_TRIGGER_SUPPORT_PK on SUPPORT_ID, and the documented unique indexes also include ZD_EDITION_NAME alongside the key and two system LOB indexes.

Common Use Cases and Queries

Typical scenarios center on diagnosing payroll trigger behavior and inspecting the generated support code. A common query joins the support table to the trigger events table:

• Listing all support packages for a given trigger event: SELECT s.support_id, s.event_id, s.header_code, s.body_code FROM hr.pay_trigger_support s WHERE s.event_id = :event_id;
• Auditing generated trigger code, for example retrieving the body code to compare against a known baseline or a patched version.
• Reconciling trigger support entries against PAY_TRIGGER_EVENTS to find events that lack a support package or that carry multiple support records.
• Edition-aware queries in 12.2.2 should reference ZD_EDITION_NAME or rely on the editioning views so that only the current edition's rows are returned.

Reporting use cases include impact analysis before applying a patch (identifying which trigger events have custom support code) and troubleshooting payroll run failures that trace back to generated trigger logic.

Related Objects

The primary related object is the foreign-key parent:

• PAY_TRIGGER_EVENTS — joined via PAY_TRIGGER_SUPPORT.EVENT_ID = PAY_TRIGGER_EVENTS.EVENT_ID. This is the defining parent relationship documented for the table.

Beyond the documented FK, the table logically interacts with the broader Payroll trigger framework, including PAY_TRIGGER_SUPPORT's consumers among generated trigger packages and the payroll formula/rule compilation objects that produce trigger events. In EBS 12.2.2, editioning views and the ZD_EDITION_NAME column tie the table into the AD editioning infrastructure, so edition-aware query patterns and the associated editioning view definitions are also relevant dependents.