Search Results pay_event_groups_pk
Overview
PAY_EVENT_GROUPS 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 provide grouping for user control of event monitoring. In practical terms, the table defines named logical groupings of payroll events (for example, date-tracked events such as hires, terminations, or element entry changes) that administrators can monitor, report on, and manage as a single unit rather than individually. It also participates in proration configuration through PRORATION_TYPE and the TIME_DEFINITION_ID reference to PAY_TIME_DEFINITIONS.
From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies this object as hub-leaning. Its central surrogate identifier, the event group, is referenced by multiple downstream transactional and configuration tables, which is consistent with the behavior of a durable business entity hub rather than a pure link or satellite. This classification is a modeling suggestion only; in the native EBS schema the table functions as a conventional configuration master.
Key Information Stored
The table contains 14 documented columns. The most significant are:
EVENT_GROUP_ID— the surrogate primary key, enforced byPAY_EVENT_GROUPS_PK.EVENT_GROUP_NAME— the descriptive name of the group; part of the unique business key.EVENT_GROUP_TYPE— classifies the nature of the grouping.PRORATION_TYPE— indicates how proration is applied in relation to this group.TIME_DEFINITION_ID— foreign key toPAY_TIME_DEFINITIONS, tying the group to a time definition.LEGISLATION_CODE— the legislative context for which the group is valid; part of the unique business key.BUSINESS_GROUP_ID— the business group that owns the record; part of the unique business key.OBJECT_VERSION_NUMBER— optimistic locking / concurrency control column.ZD_EDITION_NAME— the editioning column present in the 12.2.2 schema, enabling online patching and edition-based redefinition.- Standard audit columns:
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN.
The documented unique index PAY_EVENT_GROUPS_UK1 spans EVENT_GROUP_NAME, LEGISLATION_CODE, BUSINESS_GROUP_ID, and ZD_EDITION_NAME. This is the business-key candidate users frequently search for ("pay_event_groups_uk1"). Note that in 12.2.2 both the PK and the UK include ZD_EDITION_NAME, reflecting the editioning model.
Common Use Cases and Queries
Typical scenarios include identifying which event groups are configured for a given legislation and business group, auditing proration configuration, and reporting on monitored date-tracked events.
SELECT event_group_id,
event_group_name,
event_group_type,
proration_type,
legislation_code,
business_group_id
FROM hr.pay_event_groups
WHERE legislation_code = :p_legislation
AND business_group_id = :p_bg_id;
To list events belonging to a group, join through PAY_DATATRACKED_EVENTS on EVENT_GROUP_ID. To trace element types that use a group for proration, join PAY_ELEMENT_TYPES_F.PRORATION_GROUP_ID back to EVENT_GROUP_ID. Reporting joins should always include BUSINESS_GROUP_ID and LEGISLATION_CODE predicates to respect the UK1 uniqueness scope.
Related Objects
PAY_TIME_DEFINITIONS— referenced byPAY_EVENT_GROUPS.TIME_DEFINITION_ID.PAY_DATATRACKED_EVENTS— referencesEVENT_GROUP_ID; the primary consumer of event groupings.PAY_ELEMENT_TYPES_F— referencesEVENT_GROUP_IDviaPRORATION_GROUP_ID.PAY_EVENT_GROUP_USAGES— referencesEVENT_GROUP_ID.PAY_RETRO_NOTIF_REPORTS— referencesEVENT_GROUP_ID.
Together these dependencies confirm the hub-leaning classification and illustrate that PAY_EVENT_GROUPS is a relatively small but widely referenced configuration master within the Payroll event monitoring subsystem.
-
Table: PAY_EVENT_GROUPS
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_EVENT_GROUPS, object_name:PAY_EVENT_GROUPS, status:VALID, product: PAY - Payroll , description: Provides grouping for user control of event monitoring , implementation_dba_data: HR.PAY_EVENT_GROUPS ,
-
INDEX: HR.PAY_EVENT_GROUPS_PK
12.2.2
owner:HR, object_type:INDEX, object_name:PAY_EVENT_GROUPS_PK, status:VALID,
-
Table: PAY_EVENT_GROUPS
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_EVENT_GROUPS, object_name:PAY_EVENT_GROUPS, status:VALID, product: PAY - Payroll , description: Provides grouping for user control of event monitoring , implementation_dba_data: HR.PAY_EVENT_GROUPS ,
-
INDEX: HR.PAY_EVENT_GROUPS_PK
12.1.1
owner:HR, object_type:INDEX, object_name:PAY_EVENT_GROUPS_PK, status:VALID,
-
TABLE: HR.PAY_EVENT_GROUPS
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_EVENT_GROUPS, object_name:PAY_EVENT_GROUPS, status:VALID,
-
TABLE: HR.PAY_EVENT_GROUPS
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_EVENT_GROUPS, object_name:PAY_EVENT_GROUPS, status:VALID,
-
PACKAGE BODY: APPS.PAY_EVG_SHD
12.2.2
-
PACKAGE BODY: APPS.PAY_EVG_SHD
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.PAY_EVG_SHD dependencies on PAY_EVENT_GROUPS
12.2.2
-
APPS.PAY_EVG_SHD dependencies on PAY_EVENT_GROUPS
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.PAY_EVG_SHD dependencies on FND_MESSAGE
12.2.2
-
APPS.PAY_EVG_SHD dependencies on FND_MESSAGE
12.1.1
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,