Results for “pay_event_updates”

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

Overview

PAY_EVENT_UPDATES 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 process event update transactions — that is, to register the incremental changes that occur against dated payroll tables so that event-driven processing (such as payroll action/event handling and date-tracked data maintenance) can be tracked, propagated, and reconciled. The table therefore sits at the intersection of the payroll event framework and the payroll dated-table framework, capturing which object and column were touched, what kind of change occurred, and which dated table row was involved.

The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault model. In practical terms, that suggests modeling EVENT_UPDATE_ID as a hub-style business key whose descriptive attributes (object name, column name, change type, event type, legislation) may be treated as satellite context. This is a modeling suggestion only; the physical table is a standard EBS transactional table with WHO columns and an edition-tracking column.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• EVENT_UPDATE_ID — the surrogate primary key, enforced by PAY_EVENT_UPDATES_PK. This is the column users most commonly search for when tracing an event update from a child record back to its definition.
• DATED_TABLE_ID — foreign key to PAY_DATED_TABLES, identifying the dated payroll table affected by the update.
• TABLE_NAME and COLUMN_NAME — the object and column subject to the change, allowing generic, metadata-driven processing without hard-coding each dated table.
• CHANGE_TYPE and EVENT_TYPE — classify the nature of the update and the event category that triggered it.
• BUSINESS_GROUP_ID and LEGISLATION_CODE — the enterprise/legislative context, enabling multi-organization and localized processing.
• OBJECT_VERSION_NUMBER — optimistic locking for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
• ZD_EDITION_NAME — editioning support, part of the unique index PAY_EVENT_UPDATES_PK (EVENT_UPDATE_ID, ZD_EDITION_NAME). This composite makes EVENT_UPDATE_ID plus ZD_EDITION_NAME the documented business-key candidate.

Common Use Cases and Queries

Typical scenarios include auditing which dated tables and columns were modified by a payroll event, establishing traceability between PAY_PROCESS_EVENTS rows and the update definitions they reference, and building metadata-driven reports over change activity by legislation or business group.

Representative query patterns:

• Look up a specific update definition: SELECT * FROM pay_event_updates WHERE event_update_id = :id;
• Join to the dated table metadata: SELECT e.event_update_id, e.table_name, e.column_name, d.* FROM pay_event_updates e, pay_dated_tables d WHERE e.dated_table_id = d.dated_table_id;
• Trace child events: SELECT p.* FROM pay_process_events p WHERE p.event_update_id = :update_id;
• Filter by legislative context: ... WHERE legislation_code = :leg AND business_group_id = :bg;

Related Objects

• PAY_DATED_TABLES — joined via PAY_EVENT_UPDATES.DATED_TABLE_ID = PAY_DATED_TABLES.DATED_TABLE_ID.
• PAY_PROCESS_EVENTS — references this table through PAY_PROCESS_EVENTS.EVENT_UPDATE_ID.
• PAY_EVENT_UPDATES_PK and PAY_EVENT_UPDATE_ID_PK — the primary key constraints documented against EVENT_UPDATE_ID.

The FK relationships confirm PAY_EVENT_UPDATES as a hub-like reference point consumed by PAY_PROCESS_EVENTS and anchored to PAY_DATED_TABLES.