Defining Triggers and Segmentation Events

In Global Payroll, the mechanism used to detect online data changes that should result in a system action is called a trigger. Examples of common data changes that might use triggers are the hiring of a new payee, a change in pay rate, and a change in job location. There are three types of triggers: iterative, retroactive, and segmentation.

Before you can use a trigger to process a payee, perform segmentation, or perform retroactive processing, you must set up a trigger definition. The definition indicates that when a particular change to the database occurs, the system should generate the desired trigger. You define trigger event IDs on the Trigger Definition page (Set Up HCM, Product Related, Global Payroll & Absence Mgmt, Triggers, Trigger Definitions) in the Global Payroll core application.

The following table lists records with triggers for Global Payroll for Switzerland.

Record	Type	Trigger Event ID	Retro Event Definition ID
ADDRESSES	Iterative
COMPENSATION	Iterative
COMPENSATION	Retro	COMPENSATI	CHE RETRO
CONTRACT_DATA	Iterative
EMPLOYMENT	Iterative
GPCH_AB_MATERN	Iterative
GPCH_AB_MATERN	Retro	CH AB MATE	CHE RETRO
GPCH_AL_EMPLMT	Iterative
GPCH_AL_EMPLMT	Retro	CH AL EMPL	CHE RETRO
GPCH_CA_DATA1	Iterative
GPCH_CA_DATA1	Retro	CH CA DAT1	CHE RETRO
GPCH_CA_DATA2	Iterative
GPCH_CA_DATA2	Retro	CH CA DAT2	CHE RETRO
GPCH_EO_NOR_VW	Iterative
GPCH_EO_NOR_VW	Retro	CH EO CALC	CHE RETRO
GPCH_EO_RTO_VW	Iterative
GPCH_EO_RTO_VW	Retro	CH EO RTO	CHE RETRO
GPCH_GR_DAT1_VW	Iterative
GPCH_GR_DAT1_VW	Retro	CH GR DATA	CHE RETRO
GPCH_GR_DAT2_VW	Iterative
GPCH_GR_DAT2_VW	Retro	CH GR DAT2	CHE RETRO
GPCH_PK_DAT_DTL	Iterative
GPCH_PK_DAT_DTL	Retro	CH PK DTL	CHE RETRO
GPCH_SI_DATA	Iterative
GPCH_SI_DATA	Retro	CH SI DATA	CHE RETRO
GPCH_TX_DATA	Iterative
GPCH_TX_DATA	Retro	CH TX DATA	CHE RETRO
GPCH_TX_LAWDATA	Iterative
GPCH_TX_LAWDATA	Retro	CH TX DATA	CHE RETRO
GP_ABS_EVENT	Iterative
GP_ABS_EVENT	Retro	GPABSEVENT	CHE RETRO
GP_ABS_OVRD	Iterative
GP_ABS_OVRD	Retro	GPABSOVRD	CHE RETRO
GP_PI_MNL_DATA	Iterative
GP_PI_MNL_DATA	Retro	GPPIMNLDAT	CHE RETRO
GP_PI_MNL_SOVR	Iterative
GP_PI_MNL_SOVR	Retro	GPPIMNLSOV	CHE RETRO
GP_PYE_OVRD	Iterative
GP_PYE_OVRD	Retro	GPPYEOVRD	CHE RETRO
GP_PYE_OVR_SOVR	Iterative
GP_PYE_OVR_SOVR	Retro	GPPYEOVRSO	CHE RETRO
GP_PYE_SECT_DTL	Iterative
GP_PYE_SECT_DTL	Retro	GPPYESECTD	CHE RETRO
GP_RTO_TRGR	Iterative
GP_SEG_TRGR	Iterative
JOB	Iterative
JOB	Retro	JOB	CHE RETRO
JOB	Segmentation
JOB	Segmentation
JOB_JR	Iterative
PERSON	Iterative
PERS_DATA_EFFDT	Iterative
SCH_ASSIGN	Iterative
SCH_ASSIGN	Retro	SCHASSIGN	CHE RETRO
SCH_MNG_SCH_TBL	Iterative
TL_PAYABLE_TIME	Iterative
WKF_CNT_TYPE	Iterative

Note: Global Payroll for Switzerland is designed to have a retroactive limit as of January 01 of the current year.

The following table lists segmentation events for Global Payroll for Switzerland:

Name	Description	Segment Type
COMPRATE	Comp Rate Segmentation	Element
JOB	Job Segmentation	Period

Adjusting Trigger Effective Dates

When you define retro triggers on the Trigger Definitions-Field Values page, you can enter a positive or negative number in the Offset Days field to increase or decrease the retro trigger effective date in relation to the date of a field value change. For example, if you enter -1 in the Offset Days field for one of the values listed in the Field Values group box, and you retroactively enter that value into the database with an effective date of October 1, 2014, the system automatically adjusts the trigger effective date to September 30, 2014 (one day earlier). The system then processes pay periods going back to September 2014 rather than October 2014.

Global Payroll for Switzerland uses the offset days feature to define the triggers for retroactive terminations entered in the JOB record using the Action field (Set Up HCM, Product Related, Global Payroll & Absence Mgmt, Triggers, Trigger Definitions, Trigger Definitions. Click the List Field Values link on the Trigger Definitions page).

Note that the offset for termination triggers is -1.

The reason for this offset is that the PeopleSoft system considers the effective date of a termination entered in the Action field in JOB to be the first day that a payee is no longer working (in other words, the day before the termination is the last day the payee is considered active); however, the effective date of the trigger generated in response to this termination is identical to the termination date. This can create problems when the termination date in the JOB record is equal to the pay period begin date (meaning, the last day worked is the last day of the prior pay period). For example, assume that you enter a termination in JOB on February 1 after processing and closing the January calendar. In this situation, the system generates a trigger with an effective date of February 1, which is within the current period—a period in which the payee is "inactive" and is not picked up for processing. Because there is no trigger in the prior, closed period (January), this period will not be recalculated and any rules set up to generate termination payments will not be processed. To avoid this problem, Global Payroll for Switzerland sets the offset days for the TER, RET, LOA, LOF, TWP, and TWB action values in the JOB record equal to -1.

Important! If you define additional action values to trigger retroactive termination payments, you should set the offset days to -1.