Message Number list used by SAP ABAP Class CL_GRAC_HR_TRIGGER (HR Trigger)
SAP ABAP Class CL_GRAC_HR_TRIGGER (HR Trigger) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | GRAC_WF_REQUEST - 214 | Action type is &1 for request type &2 | |
2 | Message Number | GRAC_WF_REQUEST - 300 | A user must be assigned to employee ID &1 | |
3 | Message Number | GRAC_WF_REQUEST - 299 | Default Role added to request. Role ID is &1 and name is &2 | |
4 | Message Number | GRAC_WF_REQUEST - 287 | &1 &2 &3 &4 | |
5 | Message Number | GRAC_WF_REQUEST - 286 | Info Type Field New Value Old Value | |
6 | Message Number | GRAC_WF_REQUEST - 285 | The info type changes from the HR system are as follows: | |
7 | Message Number | GRAC_WF_REQUEST - 284 | Manager &1 is not assigned to employee &2 in the GRC system | |
8 | Message Number | GRAC_WF_REQUEST - 283 | Manager information does not exist for Employee Id &1 | |
9 | Message Number | GRAC_WF_REQUEST - 258 | Role &1 in connector &2 is not added because it is not in sync with ERM | |
10 | Message Number | GRAC_WF_REQUEST - 246 | You must add roles before you can create a request | |
11 | Message Number | GRAC_WF_REQUEST - 221 | Request no. &2 was retrieved for request ID &1 | |
12 | Message Number | GRAC_WF_REQUEST - 220 | No data saved for Request ID &1 | |
13 | Message Number | GRAC_WF_REQUEST - 219 | Request created; request ID is &1 | |
14 | Message Number | GRAC_WF_REQUEST - 218 | Rules are not satisfied for Employee ID &1 | |
15 | Message Number | GRAC_WF_REQUEST - 217 | Rules satisfied; action ID is &1 for employee ID &2 | |
16 | Message Number | GRAC_WF_REQUEST - 215 | No Action type found for Request type &1 | |
17 | Message Number | GRAC_WF_REQUEST - 014 | Enter the user details | |
18 | Message Number | GRAC_WF_REQUEST - 213 | No data found for Action ID &1 | |
19 | Message Number | GRAC_WF_REQUEST - 212 | Request type is &1 for action ID &2 | |
20 | Message Number | GRAC_WF_REQUEST - 211 | Data updated successfully with request ID &1 | |
21 | Message Number | GRAC_WF_REQUEST - 210 | Data saved successfully with request ID &1 | |
22 | Message Number | GRAC_WF_REQUEST - 199 | Role could not be found | |
23 | Message Number | GRAC_WF_REQUEST - 198 | Role ID is &1 and name is &2 | |
24 | Message Number | GRAC_WF_REQUEST - 197 | Data not found for User &1 | |
25 | Message Number | GRAC_WF_REQUEST - 197 | Data not found for User &1 | |
26 | Message Number | GRAC_WF_REQUEST - 195 | Validity is delimited to &1 as role is not present in new position | |
27 | Message Number | GRAC_WF_REQUEST - 194 | Request User Data filled successfully for ReqID &1 User &2 | |
28 | Message Number | GRAC_WF_REQUEST - 193 | Req Owner Data Filled with ReqID &1 Priority &2 ReqType &3 ProcessID &4 | |
29 | Message Number | GRAC_WF_REQUEST - 191 | Roles fetched for the position &1 | |
30 | Message Number | GRAC_WF_REQUEST - 186 | Employee detail obtained for user ID &1 | |
31 | Message Number | GRAC_WF_REQUEST - 185 | User ID is &1 for employee ID &2. |