on 2014 Mar 19 3:58 AM
Request clarification before answering.
Dear Ajay,
For the logic to get the default investigation lead you can look in the class 'CL_EHHSS_INC_INV_LEAD_DETERM' and Method 'IF_EHHSS_INV_LEAD_DETERM~DETERMINE'.
I managed to get the default investigation lead via the BAdI: Investigation Lead Determination - EHHSS_INC_LEAD_DET.
But if I want to change the investigation lead afterwards I have the same issue like you:
Results List: No results found for Investigation Lead
Did you already solved this issue?
If yes, can you share me your solution?
Thanks in advance,
Gunther
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gunther,
I realize that this thread is a little old and you have probably resolved the problem already.
I had the same issue and after a couple hours of debugging, figured out what was causing the issue for me - hopefully it can save some other some time too.
The short answer (if you have not implemented the BADI):
The search is looking for agents (users) that are configured for a specific task (as Sagar mentioned the SAP standard one is TS00500118). So if you have not implemented the BADI then check that you have maintained agents on the task ot set it as a general one (transaction PFTC).
Longer answer (if you implemented the BADI):
If you have implemented the BADI then you must make sure you implement both methods that it provides. The search help instantiates the BADI via a helper class and queries which task it should be looking for agents for. If you do not have any custom workflows, then just return the SAP standard task in the "GET_TASK_ID_OF_PERFORM_INV" - same as the standard. This will then return search results - assuming you have maintained the task.
Here are some screenshots:
My BADI looks as follows:
I implemented the following method to pass back the task number:
Search results now return:
The reason we implemented this BADI at our client was that we didn't want to have the lead investigator defaulted.
Below is where the search helper class (CL_EHSS_INC_INC_SEARCH_HELPER) is invoked.
Regards, Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Balajee,
Thanks for your input. The BAdI for Investigation Lead Determination has already been implemented. The HR integration with incident management has also been done and I am able to get HR data for other fields like Responsible, Implementer, Approver.
Also, as far as I understand the Incident Manager should be the default Investigation Lead which is not happening in my case.
Dear Ajay
If Incident manager is not determining automatically as Investigation Lead , issue is with BadI Implementation only.
Check whether Enhancement spot : ES_EHHSS_INV_LEAD_DETERM of BadI : EHHSS_INV_LEAD_DETERM_BADI is activated or not . Check the methods in Enhancement spot level also activated or not.
Balajee
Hi Ajay,
Following logic is used to determine the default Investigation Lead when you save the application after selecting Investigation required.
1. Sytem will consider the login user as default investigation lead, but the Login user id will be assigned to Investigation Lead only when below conditions met
a. Login user is provided with "SAP_EHSM_HSS_INCIDENT_MANAGER" role
b. The Role "SAP_EHSM_HSS_INCIDENT_MANAGER" is assigned to the Incident Investigation Workflow(TS500118).
Above BADI is required to overwrite the default investigation lead, if there is no logic to overwrite then it will get the default investigation lead.
Thanks
Sagar Pilli
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.