Search Results pay_event_group_usages




Overview
Explore in AI Chat

Overview

PAY_EVENT_GROUP_USAGES is a Payroll (PAY) module table owned by the HR schema. As stated in the ETRM documentation, its purpose is to "provide grouping for user control of event monitoring." In practical terms, the table acts as an assignment or mapping entity that links payroll event groups to element sets, allowing administrators to scope which payroll events are monitored for which groupings of elements. This supports the configuration of event monitoring controls, whereby a user can associate a defined event group with a specific element set so that monitoring logic applies only to the relevant combination.

The ETRM metadata classifies this object heuristically as standalone rather than as a hub, link, or satellite. Where a Data Vault model is contemplated, this classification suggests the table may be treated as an independent entity rather than a pure junction, although its two foreign keys to PAY_EVENT_GROUPS and PAY_ELEMENT_SETS mean it also carries link-like characteristics between those two parent entities. The designation reflects the mined foreign-key structure and should be regarded as a modeling suggestion, not a prescriptive rule.

Key Information Stored

The documented physical schema for 12.2.2 contains 12 columns. The most significant are listed below.

The unique indexes define the documented business-key candidates. PAY_EVENT_GROUP_USAGES_PK covers (EVENT_GROUP_USAGE_ID, ZD_EDITION_NAME). PAY_EVENT_GROUP_USAGES_UK1 covers (EVENT_GROUP_ID, ELEMENT_SET_ID, ZD_EDITION_NAME), which enforces that a given event group is not assigned more than once to the same element set within an edition. This UK1 is the meaningful business key; the PK is purely a surrogate identifier.

Common Use Cases and Queries

Typical use cases involve auditing and reporting on event-monitoring configuration. A common query joins to the parent event group and element set to display the effective monitoring scope:

  • Report all event-group-to-element-set assignments for a business group, filtered by LEGISLATION_CODE.
  • Identify element sets that have no event group assigned (left-join anti-pattern against PAY_ELEMENT_SETS).
  • Detect duplicate assignments for remediation before new configuration is loaded.
  • Extract configuration for migration between environments, keyed on the UK1 columns.

A representative SQL pattern selects the descriptive attributes from the parents while constraining the usage rows:

SELECT eg.event_group_name, es.element_set_name, u.legislation_code
FROM pay_event_group_usages u, pay_event_groups eg, pay_element_sets es
WHERE u.event_group_id = eg.event_group_id
AND u.element_set_id = es.element_set_id
AND u.business_group_id = :p_bg_id;

Reporting should restrict by ZD_EDITION_NAME to the active edition in 12.2.x, since the editioning column is part of every unique index.

Related Objects

The following objects are most significant, based on the documented foreign keys and the table's role in event monitoring.

  • PAY_EVENT_GROUPS — parent referenced via EVENT_GROUP_ID; holds event group definitions.
  • PAY_ELEMENT_SETS — parent referenced via ELEMENT_SET_ID; holds element set definitions.
  • PAY_ELEMENT_SET_USAGES — related usage table governing element set membership.
  • PAY_EVENT_GROUP_USAGES_PK and PAY_EVENT_GROUP_USAGES_UK1 — unique indexes enforcing row identity and the business key.
  • PAY_EVENT_GROUPS_API / related PAY APIs — programmatic maintenance of event group configuration, which indirectly maintains usage rows.

Because the table is classified as standalone, no dependent child tables are documented; it functions as a leaf configuration table beneath its two parents.