{"id":37,"date":"2008-10-27T12:53:34","date_gmt":"2008-10-27T02:53:34","guid":{"rendered":"http:\/\/supportingelement.wordpress.com\/?p=37"},"modified":"2008-10-27T12:53:34","modified_gmt":"2008-10-27T02:53:34","slug":"setting-up-mass-triggers","status":"publish","type":"post","link":"https:\/\/supportingelement.com\/index.php\/2008\/10\/27\/setting-up-mass-triggers\/","title":{"rendered":"Setting up Mass Triggers"},"content":{"rendered":"

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.<\/p>\n

Unfortunately, the process of creating Mass Triggers is poorly documented in PeopleBooks. This example should help fill the gaps.<\/p>\n

To setup Mass Triggers:<\/p>\n

Create SQL Object<\/h5>\n

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.<\/p>\n

\"\"<\/a><\/p>\n

Create Trigger Event Definition<\/h5>\n

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.<\/p>\n

\"\"<\/a><\/p>\n

Product Related > Global Payroll & Absence Mgmt
\n> Triggers > Retro Event Definitions<\/p>\n

Create Mass Trigger Definition<\/h5>\n

The Component, Record Name, Retro Event Definition and selected Fields are used to define the Mass Trigger Definition.<\/p>\n

\"\"<\/a><\/p>\n

Product Related > Global Payroll & Absence Mgmt
\n> Triggers > Mass Trigger Definitions<\/p>\n

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.<\/p>\n

\"\"<\/a><\/p>\n

Product Related > Global Payroll & Absence Mgmt
\n> Triggers > Mass Trigger Definitions<\/p>\n

Create Mass Trigger Generation Logic<\/h5>\n

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 ;-).<\/p>\n

\"\"<\/a><\/p>\n

The follow screen shows the PeopleCode used to generate Mass Triggers. The GenerateMassTriggers function takes Component and Record names as parameters.
\n\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

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\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4,8,9,21],"tags":[],"class_list":["post-37","post","type-post","status-publish","format-standard","hentry","category-all-posts","category-configuration","category-global-payroll","category-hrms","category-peoplesoft"],"_links":{"self":[{"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/comments?post=37"}],"version-history":[{"count":0,"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/posts\/37\/revisions"}],"wp:attachment":[{"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/media?parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/categories?post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/supportingelement.com\/index.php\/wp-json\/wp\/v2\/tags?post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}