Results for “pay_process_events”

50+ results




Overview
Explore in AI Chat

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

Overview

PAY_PROCESS_EVENTS is a payroll process event capture table owned by the HR schema within the Oracle E-Business Suite PAY (Payroll) product family. It records discrete events that occur during payroll processing, providing an auditable trail of assignment-level changes, their calculation context, and retroactive consequences. In the 12.1.1 and 12.2.2 releases, the table is documented as VALID and exposed through the ETRM (E-Business Suite Technical Reference Manual) with a physical schema of nineteen columns.

From a Data Vault modeling perspective, the metadata classification is heuristic and satellite-leaning. The table does not function as a pure hub or link: it carries descriptive and state-bearing attributes (status, change type, retroactive status) attached to a parent event group, and it holds a self-referencing foreign key. Modelers should treat PAY_PROCESS_EVENTS as a satellite hub hybrid, with ORG_PROCESS_EVENT_GROUP_ID acting as the grouping key and PROCESS_EVENT_ID serving as the surrogate identity.

The primary key is defined by two documented unique indexes, PAY_PROCESS_EVENTS_PK and PAY_PROCESS_EVENT_ID_PK, both keyed on PROCESS_EVENT_ID. This duplication of the unique constraint on the same column is a notable schema characteristic worth accounting for in any reverse-engineering exercise.

Key Information Stored

The most significant columns documented in the ETRM metadata are:

  • PROCESS_EVENT_ID — surrogate primary key and the unique business-key candidate, uniquely identifying each captured event.
  • ASSIGNMENT_ID — the assignment to which the event applies, linking the event to the payroll population.
  • EFFECTIVE_DATE — the date from which the event takes effect for payroll calculation.
  • CALCULATION_DATE — the date on which the event is processed during a payroll run.
  • CHANGE_TYPE — classification of the change that generated the event.
  • STATUS — the processing state of the event.
  • RETROACTIVE_STATUS — indicates whether the event triggers retroactive recalculation.
  • NOTED_VALUE — a value captured by the event, typically numeric or reference data.
  • EVENT_UPDATE_ID — foreign key to PAY_EVENT_UPDATES, tying the event to its update record.
  • ORG_PROCESS_EVENT_GROUP_ID — self-referencing foreign key that groups related events.
  • BUSINESS_GROUP_ID — the business group (enterprise) owning the event.
  • SURROGATE_KEY — an alternate surrogate identifier.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle framework.
  • DESCRIPTION — free-text descriptive text for the event.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include tracing retroactive events for a payroll period, reconciling assignment-level changes against calculation outcomes, and auditing grouped process events. A common pattern joins to PAY_EVENT_UPDATES on EVENT_UPDATE_ID:

  • SELECT p.PROCESS_EVENT_ID, p.ASSIGNMENT_ID, p.CHANGE_TYPE, p.RETROACTIVE_STATUS FROM HR.PAY_PROCESS_EVENTS p, HR.PAY_EVENT_UPDATES u WHERE p.EVENT_UPDATE_ID = u.EVENT_UPDATE_ID AND p.RETROACTIVE_STATUS IS NOT NULL;
  • Grouping by ORG_PROCESS_EVENT_GROUP_ID to reconstruct event clusters for a single payroll process.
  • Filtering on EFFECTIVE_DATE within a payroll period to isolate events affecting a specific run.

Related Objects

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

  • PAY_EVENT_UPDATES — referenced by PAY_PROCESS_EVENTS.EVENT_UPDATE_ID; supplies the update context for each event.
  • PAY_PROCESS_EVENTS (self-reference) — via ORG_PROCESS_EVENT_GROUP_ID, grouping child events under a parent event group.
  • PAY_EVENT_UPDATES (second reference) — the metadata documents EVENT_UPDATE_ID twice, reinforcing a dual or repeated linkage to the update table.
  • PAY_ASSIGNMENT_ACTIONS / PER_ALL_ASSIGNMENTS_F — implied relationship through ASSIGNMENT_ID for assignment detail.
  • PAY_PAYROLL_ACTIONS — implied through CALCULATION_DATE and payroll run context.

Collectively, these relationships position PAY_PROCESS_EVENTS as a central capture point for payroll event lifecycle data across EBS 12.1.1 and 12.2.2.