Setting up Mass Triggers

By | October 27, 2008

Mass Triggers are new to version 8.9 and are useful in triggering retrospective calculation when setup tables are changed. For example, if an allowance rate is changed retrospectively Mass Triggers can be used create Iterative and Retro triggers for Employees who have the Earning assigned via EDAP.

Unfortunately, the process of creating Mass Triggers is poorly documented in PeopleBooks. This example should help fill the gaps.

To setup Mass Triggers:

Create SQL Object

The SQL object must return Employee ID, Employee Record Number and the Effective Date of the Trigger. In the following example the SQL Object uses parameters of the Earning Pin Number and Effective Date of the changes to the Earning to select Employees who have EDAP entries impacted by the changes. The SQL then returns the Employee ID, Employee Record and the greater of Effective Date of the Changes or EDAP Begin Date.

Create Trigger Event Definition

A Retro Event Definition is required for the configuration of Mass Triggers. An existing Event Definition can be used for this purpose, however in this scenario a new Definition has been configured.

Product Related > Global Payroll & Absence Mgmt
> Triggers > Retro Event Definitions

Create Mass Trigger Definition

The Component, Record Name, Retro Event Definition and selected Fields are used to define the Mass Trigger Definition.

Product Related > Global Payroll & Absence Mgmt
> Triggers > Mass Trigger Definitions

The SQL Object is bound to the Mass Trigger Tables using the parameters defined in the SQL Object. In this case the Pin Number and Effective Date of the config changes is passed.

Product Related > Global Payroll & Absence Mgmt
> Triggers > Mass Trigger Definitions

Create Mass Trigger Generation Logic

Finally, PeopleCode is required on the Mass Trigger record (in this scenario the “GP_ERN_DED” record). This step is not mentioned in PeopleBooks, but is nicely documented in the code comments of the “GP_MT_TRG_DFN” record (where else would you expect it ;-).

The follow screen shows the PeopleCode used to generate Mass Triggers. The GenerateMassTriggers function takes Component and Record names as parameters.

6 thoughts on “Setting up Mass Triggers

  1. Vaibhav Jain

    Thanks Pual for this, it is really helpful.
    But i am facing an issue here, the retro is getting generated but it is corrective instead of forwarding.

    Can you please help me in resolving this issue.

  2. Paul Clarke

    Hi Jain,

    The “Retro Method” is controlled by the “Retro Process Definition”.

    “Set Up HRMS > Product Related > Global Payroll & Absence Mgmt > Triggers > Retro Process Definitions”

    I would recommend substantial regression testing if you change from “Corrective” to “Forwarding”.

    I hope this helps.

    Cheers Paul.

  3. Vaibhav Jain

    Thanks paul for the prompt response.
    Actually Retro Process definition is already set to “Forwarding” and the same has been used in the compensation data where it is working fine.
    I don’t know why it is not working for mass trigger, is there any possiblity that it is getting overwritten somewhere else.

  4. Paul Clarke

    Hi Jain,

    You might be able to work out what it’s doing if you run a trace.

    Sorry, that’s the best I can offer without access to the system.

    Cheers Paul.

  5. Vaibhav Jain

    Paul,

    It got resolved, actually it was a “Forwarding” retro only but only issue was it is not passing the delta, as i haven’t added my element in retro overrides.
    Actually I am novice in GP and thats why doing these silly mistakes.

    Thanks a lot for providing your help and time, have a great day ahead.

Comments are closed.