Creation of Events When HR Master Data is Changed


There are two tables for controlling the creation of events when HR master data is changed.

HR objects require this "special treatment" because the creation mechanisms mentioned so far cannot be used in this area for technical reasons.

The various infotypes of an HR master record are stored in the tables PA* and PB* . Changes to these tables are to be published by the creation of events.


Assignment HR information - object type

The assignment between the table and the object type is made in table T588V . For an entry in this table, the key structure of the table for HR information must agree with the key of the object type.

Field name



Table for HR information


Object type

An example entry in table T588V :

T588V-TBNAM: PA0006 ( HR master record infotype 0006 (addresses))

T588V-BUSOB: ADDRESSEMP ( employee address)

Assignment change - event

Those changes that are to cause an event to be created are listed for each table in table T588W . The event (event ID and object type) to be triggered is also specified. This event to be triggered can also be determined using a function module with a predefined interface.

The existing entries in the table provide an orientation.

Field name



Table for HR information


Operation for event

Permitted values:
INS Insert Create a record
DEL Delete Delete a record
UPD Update Change a record
REQ Request Create a locked record
APP Approve' Unlock a locked record
APC ApproveCancel Lock a valid record
RQC RequestCancel Delete a locked record


Document-triggering field group

This field is not processed.


Item numbers of events

If two events are to be triggered for a table for the same operation, they must be numbered.


Object type for which the triggering event is defined.


Event for object type
(alternative to specifying function module)


Name of function module
(alternative to specifying event)

The event ID is determined using the function module as an alternative to direct entry in the field EVENT .


Maintain the tables using the view maintenance transaction SM30 .