Results for “pay_event_procedures”

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

Overview

PAY_EVENT_PROCEDURES is a Payroll (PAY) module configuration table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the executable code—typically a PL/SQL procedure or function name—that the payroll engine invokes when a specific payroll event is detected against a dated table. In effect, it is the dispatch or action registry for the event-driven payroll architecture, binding an event trigger (defined in the dated and time tables) to the server-side logic that must run in response.

Under a heuristic Data Vault classification mined from its foreign key structure, this object leans toward a satellite. It carries descriptive payload—procedure name, column name, procedure type—and dependent attributes keyed back to parent reference tables such as PAY_DATED_TABLES and PAY_TIME_DEFINITIONS. This is a modeling suggestion, not a prescriptive design; implementations that build a raw vault around PAY may treat it accordingly.

Key Information Stored

The table contains fifteen documented columns. The most functionally significant are:

• EVENT_PROCEDURE_ID — Surrogate primary key (PAY_EVENT_PROCEDURES_PK). Uniquely identifies each event-to-code binding within an edition.
• DATED_TABLE_ID — Foreign key to PAY_DATED_TABLES, identifying the dated table whose change detection raises the event.
• TIME_DEFINITION_ID — Foreign key to PAY_TIME_DEFINITIONS, identifying the time-based interval definition that scopes the event evaluation.
• PROCEDURE_NAME — The name of the executable code to run when the event is detected. This is the operative payload of the row.
• PROCEDURE_TYPE — Classifies the kind of procedure or handler, distinguishing categories of executable logic.
• COLUMN_NAME — The specific column on the dated table that the event logic monitors.
• BUSINESS_GROUP_ID — Business group partitioning, enabling multi-tenant configuration within a single installation.
• LEGISLATION_CODE — Restricts the binding to a specific legislative context, supporting country-specific payroll behavior.
• ZD_EDITION_NAME — Editioning attribute introduced with the 12.2 Online Patching (ad/zd) model, enabling multiple editions of the same logical row.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard who-column tracking and optimistic locking.

The unique index PAY_EVENT_PROCEDURES_PK is defined over EVENT_PROCEDURE_ID and ZD_EDITION_NAME, reflecting the edition-aware business key required in 12.2.x deployments.

Common Use Cases and Queries

Typical uses include auditing which procedures fire for a given dated table, diagnosing missing or unexpected payroll event behavior, and verifying that a customization survived an upgrade or patch. A representative query joining the parent reference tables:

SELECT p.procedure_name, p.procedure_type,
       p.column_name, p.legislation_code,
       d.table_name
FROM   pay_event_procedures p,
       pay_dated_tables d
WHERE  p.dated_table_id = d.dated_table_id
AND    p.business_group_id = :p_bg_id;

Because 12.2 introduced editioning, queries that must return current data should filter on the active edition, for example AND p.zd_edition_name = 'SET1', or join to the run-time edition view. Migration and clone validation scripts frequently compare row counts and PROCEDURE_NAME values across source and target environments to confirm configuration parity.

Related Objects

The following objects are most significant in relation to PAY_EVENT_PROCEDURES:

• PAY_DATED_TABLES — joined via DATED_TABLE_ID; defines the dated tables monitored for events.
• PAY_TIME_DEFINITIONS — joined via TIME_DEFINITION_ID; defines the time intervals governing event evaluation.
• PAY_EVENT_PROCEDURES_PK — the unique index / primary key constraint.
• PAY_DATED_TABLE_RELATED_COLUMNS — column-level metadata complementing COLUMN_NAME.
• PAY_EVENT_ACTIONS / PAY_PAYROLL_ACTIONS — runtime processing context where detected events are handled.
• PAY_ACTION_PARAMETERS and related PAY setup tables — configuration dependencies for procedure invocation.
• Fast Formula and PL/SQL procedure definitions referenced by PROCEDURE_NAME — the executed logic itself.

Collectively these relationships make PAY_EVENT_PROCEDURES a focal point for understanding and troubleshooting Oracle Payroll event-driven processing.