Search Results pay_functional_triggers_pk

Overview

PAY_FUNCTIONAL_TRIGGERS is a Payroll (PAY) module table owned by the HR schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the triggers contained in a functional area. In practical terms, the table functions as an intersection or mapping entity that associates a functional area (the business context in which payroll processing logic executes) with a specific trigger event (the discrete occurrence that fires during processing). Each row therefore declares that a given event is active, or in scope, for a given functional area.

The ETRM relational metadata classifies this object heuristically as a link table in a Data Vault modeling sense. This classification is a modeling suggestion derived from the foreign key structure rather than an Oracle-declared attribute. It indicates that the table resolves a many-to-many relationship between two parent entities rather than acting as a hub (holding a unique business concept) or a satellite (holding descriptive attributes over time). The two parents are PAY_FUNCTIONAL_AREAS and PAY_TRIGGER_EVENTS, referenced through the AREA_ID and EVENT_ID foreign key columns respectively.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns. The most significant are summarized below.

• TRIGGER_ID — Surrogate primary key, uniquely identifying each trigger mapping row. Enforced by the PAY_FUNCTIONAL_TRIGGERS_PK index, which the metadata documents as spanning (TRIGGER_ID, ZD_EDITION_NAME).
• AREA_ID — Foreign key to PAY_FUNCTIONAL_AREAS; identifies the functional area to which the trigger belongs.
• EVENT_ID — Foreign key to PAY_TRIGGER_EVENTS; identifies the trigger event associated with the area.
• ZD_EDITION_NAME — Editioning column introduced by the EBS 12.2 online patching architecture, present in both unique indexes and therefore part of the effective key.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit trail columns recording when, by whom, and through which login the row was last modified.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns recording row creation metadata.

The business-key candidate is captured by the PAY_FUNCTIONAL_TRIGGERS_UK1 unique index across (AREA_ID, EVENT_ID, ZD_EDITION_NAME). This confirms that the natural uniqueness of the row is the pairing of one functional area with one event; the surrogate TRIGGER_ID exists primarily for referential convenience. In 12.1.1 the editioning column is absent, so the keys reduce to TRIGGER_ID for the primary key and (AREA_ID, EVENT_ID) for the unique key.

Common Use Cases and Queries

Typical usage centers on determining which trigger events are configured for a given functional area, or conversely, which areas use a particular event. This supports impact analysis before modifying payroll trigger configuration and helps diagnose why a processing rule did or did not fire.

A representative join enumerates events per area:

• SELECT pft.trigger_id, pfa.area_id, pte.event_id FROM pay_functional_triggers pft JOIN pay_functional_areas pfa ON pft.area_id = pfa.area_id JOIN pay_trigger_events pte ON pft.event_id = pte.event_id;
• Reverse lookup by event: filter on EVENT_ID to find all functional areas referencing a given trigger event.
• Change auditing: query rows ordered by LAST_UPDATE_DATE to detect recent configuration changes made through the application.
• Data Vault staging: treat the table as a link load, joining the two parent hubs on AREA_ID and EVENT_ID.

Because rows are referentially constrained to both parents, queries should always account for the foreign key dependencies when filtering, and should include ZD_EDITION_NAME predicates in 12.2.2 environments where multiple editions may coexist.

Related Objects

The most significant related objects, based on documented foreign key and primary key relationships, are:

• PAY_FUNCTIONAL_AREAS — Parent table; joined on PAY_FUNCTIONAL_TRIGGERS.AREA_ID = PAY_FUNCTIONAL_AREAS.AREA_ID.
• PAY_TRIGGER_EVENTS — Parent table; joined on PAY_FUNCTIONAL_TRIGGERS.EVENT_ID = PAY_TRIGGER_EVENTS.EVENT_ID.
• PAY_FUNCTIONAL_TRIGGERS_PK — Primary key index on (TRIGGER_ID, ZD_EDITION_NAME).
• PAY_FUNCTIONAL_TRIGGERS_UK1 — Unique business-key index on (AREA_ID, EVENT_ID, ZD_EDITION_NAME).

Application logic elsewhere in the PAY module depends on these relationships to drive payroll trigger evaluation, and downstream configuration or diagnostic views typically resolve trigger definitions by traversing this link table to its two parents.