Results for “pay_event_updates_pk”

14 results




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

Overview

HR.PAY_EVENT_UPDATES is a transactional configuration table in the Oracle E-Business Suite Payroll (PAY) schema, owned physically by HR and registered in FND Design Data as PAY.PAY_EVENT_UPDATES. It defines the monitoring rules used by the continuous calculation (continuous calc) framework. Each row instructs the payroll engine which database object — a table and optionally a column — should be watched for changes during a continuous calculation process, and which change type should be recorded when such a change is detected. In effect, the table maps change-detection targets to event semantics, allowing the payroll process to react to modifications in dated tables without recalculating the entire population.

Rows are stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and the object carries standard Oracle EBS audit ("Who") columns plus an OBJECT_VERSION_NUMBER for optimistic locking. The metadata is populated in two ways: seeded rows carry a LEGISLATION_CODE, while customer-created rows carry a BUSINESS_GROUP_ID. The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning, suggesting that a warehouse model would treat PAY_EVENT_UPDATES as a hub keyed on EVENT_UPDATE_ID, with PAY_DATED_TABLES as a referenced hub and the change-type attributes as satellite-style descriptive data.

Key Information Stored

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

  • EVENT_UPDATE_ID — system-generated numeric primary key, enforced by the unique index PAY_EVENT_UPDATES_PK. This is the surrogate identifier and the target of downstream foreign keys.
  • DATED_TABLE_ID — foreign key to HR.PAY_DATED_TABLES, identifying the dated table whose changes are being monitored. Indexed through PAY_EVENT_UPDATES_FK1.
  • TABLE_NAME and COLUMN_NAME — the name of the table and column to monitor, respectively. These are the human-readable counterparts to the DATED_TABLE_ID reference.
  • CHANGE_TYPE — the classification assigned to a detected change; indexed through the non-unique index PAY_EVENT_UPDATES_N1, indicating it is a common filter predicate.
  • EVENT_TYPE — an additional documented attribute describing the kind of event associated with the update rule.
  • BUSINESS_GROUP_ID — populated for customer-defined data, scoping the rule to a specific business group.
  • LEGISLATION_CODE — populated for Oracle-seeded data, scoping the rule to a country/legislative context.
  • OBJECT_VERSION_NUMBER — incremented on each row update for concurrency control.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard audit columns referencing FND_USER and FND_LOGINS.
  • ZD_EDITION_NAME — editioning column associated with the 12.2 online patching (edition-based redefinition) architecture.

The documented unique index includes both EVENT_UPDATE_ID and ZD_EDITION_NAME in the 12.2.2 physical schema, reflecting editioning support. There is no separate natural business key; TABLE_NAME, COLUMN_NAME, and CHANGE_TYPE together behave as the semantic (non-unique) business identity of a rule.

Common Use Cases and Queries

Typical uses include auditing which tables and columns the continuous calc process monitors, determining the change type applied for a specific monitored object, and reconciling seeded versus customer-defined rules by legislation or business group.

Listing all monitored objects for a business group:

  • SELECT EVENT_UPDATE_ID, TABLE_NAME, COLUMN_NAME, CHANGE_TYPE FROM HR.PAY_EVENT_UPDATES WHERE BUSINESS_GROUP_ID = :p_bg_id;

Finding rules that emit a particular change type, using the PAY_EVENT_UPDATES_N1 index:

  • SELECT TABLE_NAME, COLUMN_NAME FROM HR.PAY_EVENT_UPDATES WHERE CHANGE_TYPE = :p_change_type;

Joining to the dated-table definition to resolve table metadata:

  • SELECT u.TABLE_NAME, u.COLUMN_NAME, u.CHANGE_TYPE, d.NAME FROM HR.PAY_EVENT_UPDATES u, HR.PAY_DATED_TABLES d WHERE u.DATED_TABLE_ID = d.DATED_TABLE_ID;

Identifying seeded rules by legislation:

  • SELECT TABLE_NAME, COLUMN_NAME, CHANGE_TYPE FROM HR.PAY_EVENT_UPDATES WHERE LEGISLATION_CODE IS NOT NULL;

Reporting use cases include change-impact analyses before payroll patches, validation that every monitored column still exists after an upgrade, and feeds into data-lineage documentation for continuous calculation.

Related Objects

The following objects are most significant, based on the documented foreign-key relationships:

  • HR.PAY_DATED_TABLES — referenced by PAY_EVENT_UPDATES.DATED_TABLE_ID (PAY_EVENT_UPDATES_FK1). Holds the dated-table registry entries that each update rule points to.
  • HR.PAY_PROCESS_EVENTS — references PAY_EVENT_UPDATES.EVENT_UPDATE_ID. This is the primary dependent transaction table; each process event row points back to the update rule that generated it.
  • PAY_EVENT_UPDATES_PK — the unique primary-key index on EVENT_UPDATE_ID (APPS_TS_TX_IDX), used for row lookup and enforced as the integrity anchor for inbound foreign keys.
  • PAY_EVENT_UPDATES_N1 — non-unique index on CHANGE_TYPE, supporting change-type filtering.
  • FND_USER and FND_LOGINS — implicit parent tables for the standard Who columns (LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN).

Because PAY_PROCESS_EVENTS depends on PAY_EVENT_UPDATES through a single-column foreign key (EVENT_UPDATE_ID), any purge or renumbering of update-rule rows must account for existing process-event references before deletion.