This chapter provides an overview of mass triggers and discusses how to:
Set up mass triggers.
Process mass trigger action events.
See Also
This feature enables you to generate employee triggers based on changes to setup tables. Mass triggers can be established for specific records on specific components. A set of SQL objects defines the population affected by the setup table change. Once the affected employees are determined, you can review the trigger details before accepting the changes.
To set up mass triggers you must:
Define the component/record and fields that activate the trigger on the Mass Trigger Definition page.
Set up the SQL objects that will check the records to determine the population affected by the setup table change. You must define the SQL objects using PeopleTools and select them on the Mass Trigger SQL page.
See Using SQL Objects.
Set up your system so that the records used in the mass trigger definitions declare and call the function Generate_Triggers in one of their field's SavePostChange PeopleCode.
The mass trigger event process occurs in three steps:
After saving the page containing the component/record and fields that activate the mass trigger, the event and the field values are stored in the mass trigger result table (GP_MT_TRIGGER). The event status is set to Unexpanded.
The system evaluates the SQL objects and writes the results to the mass trigger results table (GP_MT_RESULT), which records the impacted population. The event status is set to Expanded, if all objects expand successfully.
The system generates a list of retro and iterative triggers for the impacted population. Once completed, the event status is set to Triggers Generated.
You can view the events and their results on the Mass Trigger Events component. The system enables you to do the following:
Delete a trigger event using the Mass Trigger Events page. This includes the mass trigger, the impacted population, and the generated payee triggers. Deletion cannot occur if any of the generated triggers have been processed.
See Deleting an Event.
Manually expand an event using the Affected Employees page. You may want to generate triggers after correcting an erroneous SQL object. Manually expanded triggers can do the following:
Generate the impacted population and the retroactive and iterative triggers for events that have a status of Unexpanded.
Generate retroactive and iterative triggers for events that have a status of Expanded.
Global Payroll trigger-generation logic is stored in the FUNCLIB_GP.TRGR_FUNCTIONS FieldFormula PeopleCode. In order for a record to generate triggers, the GENERATE_TRIGGERS function stored there must be declared and called from the record in SavePostChange PeopleCode. We describe this function in detail with supporting examples in the chapter on defining retroactive, segmentation, and iterative triggers. In this section, we summarize only the main setup steps.
Using Generate_Triggers PeopleCode
To declare and call the Generate_Triggers function:
Declare the function that generates triggers:
Declare Function Generate_Triggers PeopleCode FUNCLIB_GP.TRGR_FUNCTIONS FieldFormula;
Declare a local date variable as:
Local date &L_DT;
Invoke the function as:
Generate_Triggers(EMPLID, &L_DT);
The function Generate_Triggers is defined in FUNCLIB_GP.TRGR_FUNCTIONS.FieldFormula and needs two parameters when it is invoked. These parameters are:
&P_EMPLID
Identifies the EMPLID for which a trigger should be generated. Use field EMPLID for &P_EMPLID.
&P_FIXED_DT
Holds the value of the trigger effective date for records with a Trigger Effdt Type of Fixed Date. It is ignored for records with a Trigger Effdt Type of Effdt or Begin-End Date. Use &L_DT for &P_FIXED_DT.
The variable &L_DT needs to be assigned a value only in the case of Fixed Date type triggers.
See Also
This section discusses how to:
Define mass triggers.
Use SQL objects.
View the SQL statement.
Page Name |
Definition Name |
Navigation |
Usage |
GP_MT_TRG_DFN |
Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Mass Trigger Definitions, Mass Trigger Definition |
Define which record activates the trigger. |
|
GP_MT_TRG_SQL |
Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Mass Trigger Definitions, Mass Trigger SQL |
Specify which SQL objects must be executed in order to retrieve the population impacted by a mass trigger event. |
|
GP_MT_SQLTXT_SEC |
Select the View SQL Definition link on the Mass Trigger SQL page. |
View the SQL definition. |
Access the Mass Trigger Definition page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Mass Trigger Definitions, Mass Trigger Definition).
Trigger Event ID |
Associate a Trigger Event ID with the record (table) to link the mass trigger to the retroactive process ID that processes the generated payee triggers. |
Ignore Terminated Employees |
Select to ignore terminated employees when processing the mass trigger. |
Field Name |
List the fields that cause the system to generate a mass trigger event. Fields used as input parameters on the SQL Objects page need not be listed here. The system inserts them after saving. |
Access the Mass Trigger SQL page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Triggers, Mass Trigger Definitions, Mass Trigger SQL).
SQL Object ID |
Select any stand alone SQL object defined in Application Designer. These objects contain placeholders for input parameters. |
View SQL Definition |
Click to access the SQL Definition page. |
Sequence number |
Enter the number of the respective placeholders in the SQL object. |
Field Name |
Enter the fields used to fill the SQL object placeholders at runtime. Available fields prompt from the record listed above. Once saved, the system adds these fields to the Mass Trigger Definition page. |
Access the View SQL Definition page (click the View SQL Definition link on the Mass Trigger SQL page).
Use this page to view a description of the SQL statement as well as view the actual SQL text.
This section discusses how to:
Delete an event.
Expand an event manually.
View retroactive triggers.
View iterative triggers.
Page Name |
Definition Name |
Navigation |
Usage |
GP_MT_TRIGGER |
Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Mass Trigger Events |
View all mass trigger events listed for a component/record. Delete an event. |
|
GP_MT_MSG_SEC |
Click theMessages link on the Mass Trigger Events page. |
View a message. |
|
GP_MT_MSGLNG_SEC |
Click the Details link on the Mass Trigger Event Messages page. |
View message details. |
|
GP_MT_TRG_VAL |
Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Field Values |
View the field values valid before and after the mass trigger event. |
|
GP_MT_RESULT |
Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Affected Employees |
View the list of employees affected by the mass trigger event. Manually expand an event. |
|
GP_MT_RTO_TRG |
Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Retro Triggers |
View the retroactive triggers generated for a mass trigger event. |
|
GP_MT_ITER_TRG |
Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Iterative Triggers |
View the iterative triggers generated for a mass trigger event. |
|
GP_MT_ITER_SEC |
Click the Triggers by Calendar Group link on the Iterative Triggers page. |
View triggers by calendar group for a payee. |
Access the Mass Trigger Events page (Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Mass Trigger Events).
Click the Delete button to delete an event before processing the trigger. This action deletes the event's results tables, thus removing the field values, the list of affected employees, the retroactive triggers and the iterative triggers generated for the event. Only the users who created the trigger event can delete it.
Access the Affected Employees page (Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Affected Employees).
Expand/Refresh Employee List |
Select to manually expand an event. Once activated, the system deletes the current list and generates a new one. All related retroactive and iterative triggers are also deleted and regenerated. The refresh button can only be activated if none of the related triggers have been processed. Only the user who created the mass trigger event can activate it. |
Employee ID |
The system generates this list when storing the mass trigger event. |
As of Date |
The date as of which retroactive or segmentation processing occurs. |
Access the Retro Triggers page (Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Retro Triggers).
Trigger Effective Date |
Corresponds to the As of Date on the Affected Employees page. |
Trigger Status |
Can either be Unprocessed, In Process, Processed, or Cancelled. |
Calendar Group ID |
This is the ID used for processing the retroactive trigger. |
Access the Iterative Triggers page (Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review/Expand Mass Triggers, Iterative Triggers).
When a mass trigger is expanded, an iterative trigger is generated for every affected employee and for every calendar group ID that is currently open. Click the Triggers by Calendar Group link to access the Calendar Groups page and view the calendar groups for which an iterative trigger has been created.