HR Trigger Enhancement

[Former Member]

Dear Expert,

For integration of GRC with HR the standard logic was working fine without any issue the workflows triggered during Hiring and Termination

But there is a requirement from business to have workflows only for staff employees and non-staff the workflow shouldn’t be triggered

For this requirements I was looking for BRF+ Structure and the standard Fields Defined are Connector, Tab.name (info type), Sub type, Field Name, New Field Val, Old Field Val, to satisfy the requirement I need to add PERSG (Employee group) in the structure and as you know structure is binded with DDIC element to achieve so I have performed the following

Under the functional Module GRAC_HR_TRIGGER_EVENT_RECIEVER following structures appended with PERSG (Employee group)

1. GRAC_S_HR_TRIGGER_USER_DATA

2. GRAC_S_HR_TRIGGER_BRFP

Then after structure appending we refresh the binding in BRF+ and values, we modified structure and table type then decision table everything simulated (functions, decision table...) and working perfectly with BRF+

We also tested manually (debugging) as per the instruction from Wiki for “Debugging HR Trigger - GRAC_HR_TRIGGER_EVENT_RECIEVER” and its working absolute correct with request generation (as per the instruction from SE37 with functional Module GRAC_HR_TRIGGER_EVENT_RECIEVER) also SLG1 log showing complete steps and successful generation of data

When we try to test from PA40 the requests are not generating and SQM1 log is empty as well no log in SLG1

We understand that the GRC side every part working perfectly after structure appending but still data not passed to GRC

We check the same @ Back end side (HR ECC system with Plugin GRCPIERP) we follow the steps from Wiki to debug HR PA40 Log “Debugging HR Trigger - PA40 and infotypes logged” in class /GRCPI/CL_IM_GRIA_HRINFADD and method IN_UPDATE we found the employee group field is not in the following standard structure /GRCPI/GRIA_S_HR_USER_DATA we appended the structure to make it compatible with GRC Appended structure as described above and put necessary breakpoints with developer and analyze the steps but still data not populated in appended field mentioned structure

Issue: data is not being populated in the new appended field to the structure /GRCPI/GRIA_S_HR_USER_DATA complete data is populating except new Field appended to the structure PERSG (Employee group) also there is no log for the request generation after hiring process from PA40

CAN ANYONE PUT SOME LIGHT ON THE ABOVE ISSUE MAY BE EXISTING ENHACENMENT POINT OR BADI WILL FRESOLVE THIS

THANKS AND REGARDS

MUJTABA SIDDIQUI

[Former Member · Accepted solution]

Dear All,

the solution for the above issue is acomplished through development

as recieved reply from SAP 

Prerequsits steps: first need to apply following notes (you need to check on which support pack you are working) as consider you are on SP13 or higher

1890158, 1970860, 1672664 and 1827500

from the above i have modified bonded strcutures need to remove all modifications make all strcutures as standard

then apply the following steps  as mentioned from SAP reply

If you want to send OR avoid sending the data for specific
info-types to GRC, you need to enhance the implementation of the BADI “/GRCPI/GRIA_HRINFADD_NEW”
in the GRC HR Plugin system. Further you need to amend the method highlighted
below to customize the code suiting to your requirement for HR action.

NOTE: BADI “/GRCPI/GRIA_HRINFADD_NEW” is available in the HR
system where GRC Plugin GRCPIERP is installed.

Within the following method, you need to define your logic
to DELETE or POPULATE the highlighted table.

For example use case: You want the
GRC request to be created only if employee type is “PERMANENT” employee. If the
employee is a “CONTRACT” employee, NO REQUEST SHOULD BE CREATED.

SOLUTION: You need to write the logic with “IF”
condition based on employee data, if employee type is “Permanent”, send an
empty “ET_TRIG_DATA1” table. IF THIS DATA IS SENT BLANK, no data will be sent
to GRC and hence no request will be created.

But, if the data is passed by this table, GRC receives the data from this table
in this BADI, and hence the request will be created in GRC.