Employee Lookup application problems

[Former Member]

Hi all,

I have encountered two problems after application configuration.

1) Everything is fine unless user enters special character into the search field. We use cyrillic alphabet in our system and naturally employee data is stored using it, but application returns nothing as search result.

During debugging I figured out that 'RS_CHECK_VARIABLE' fm call for search string causes this trouble. It checks string for following condition.

IF to_upper( condense( val ) ) CN 'ABCDEFGHIJKLMNOPQRSTUVWXYZ_1234567890/!#$%&-<=>?@{|}~'.
     RAISE EXCEPTION TYPE cx_abap_invalid_name
       EXPORTING
         name = val_str.
   ENDIF.

Is there any workaround for this case?

2) There is a CL_HCM_EMP_LKP_ADDL_API class used inside this search method. Class constructor tries to create application log with object = 'EMP_LKP' parameter. But this object is missing in SLG0 transaction, so any attempt to save log entries raise an exception. I added this object on my own, but think this is not a right decision.

Thanks in advance,

Rustam.

[kammaje_cis · Accepted solution]

Rustam, For me this sounds like a clear bug. Why don't you raise it to SAP?

[Former Member · Accepted solution]

Thanks for your answer, Krishna.

Actually, yesterday I was going to report an incident. But then decided to ask community first, if anyone has faced this problem already. Since I am sure I am not the only person who tried to use cyrillic letters within this application.

I will raise this issue to SAP now and post here their answer.

[Former Member · Accepted solution]

Have you raised the bug to SAP or found a solution?

Wouldn't it be possible to "fix" this by implementing the BAdI HCM_B_EMP_LKP?

You could call a copy of class cl_hcm_emp_lkp_addl_api and change the function module in the method get_search_results to a copy of RS_CHECK_VARIABLE.

In this copy you could change the string of allowed characters or implement a completely different check.

[suresh_datti · Accepted solution]

Pl take a look at SAP Notes 2217129 & 2211351.

~Suresh

[Former Member · Accepted solution]

Hi, Hendrik.

Yes, I've raised it to SAP and they proposed me a solution.

Kindly apply the following note to resolve the issue:

2217129 - Employee Lookup(OData): Fixes for search.

If you have already implemented the note, kindly de-implement,

download the latest version of the note and re-implement it.

Once the note is applied successfully, kindly perform the following to

clean up the cache:

1. execute /IWBEP/CACHE_CLEANUP transaction in ECC

2. Clear Browser cache

(if you are using IE to run the application you need to clear the temp

files. To do that:

step 1. goto start --> run --> %temp% --> delete all the files in temp

folder(skip the ones which cannot be deleted)

step 2. goto start --> run --> temp --> delete all the files in temp

folder(skip the ones which cannot be deleted))

3. Open the browser in private mode(mozilla firefox, IE) / incognito

mode(google chrome) and run the application.

Unfortunately, by the time I got the answer I was not working on Fiori, so I can not confirm wether this one works or not.

[Former Member · Accepted solution]

As you can see in the original post, the string that is checked also does not contain the mutated vowels in german: ä,ö and ü. Also the ß is missing.

Will this be fixed by these notes too? I couldn't find anything in the description that hints at that.