User Registration Problem

[Former Member]

Hi experts,

i have a strange problem with SAP E-Recruiting. Extremely rarely we have the problem, that a new registered user has no initial password. As a consequence, login without the help of our admins is not possible.

After a short debugging session i have the following information:

1. The user-creation by Web-Dynpro-Component HRRCF_C_UNREG_APPLWZD_UI, Method REGISTER of Component-Controller looks good so far. Besides, there are no authorization problems of our service-user.
2. After that, the standard-workflow of SAP unlocks with the aid of a Smartform the user and creates a confirmation mail.
3. The relevant function module of this Smartform is BAPI_USER_CHANGE. Unfortunately, i found no errors in these components.

So I have no run-time errors, i see nothing in slg1 and nothing noticeable in my systemtrace. Moreover, this error appears strangely sporadic. The only thing i can definitely confirm is, that concerned users have no change documents of the workflow user (see screenshot). Any ideas why?!?

SAP_BASIS: SAPKB74003

ERECRUIT  : SAPK-61701INERECRUIT

Regards Michael

[Former Member · Accepted solution]

check out transaction SWEQADM. Maybe there are wf events that are not triggered? Otherwise there would be an error in the SLG1 I would think...

[Former Member · Accepted solution]

That's a good idea! Unfortunately, the event-queue was disabled so far. After activating, we will monitor the log and trace in the next days. Maybe using the event-queue already solved this problem. I will get back to you...

[romanweise · Accepted solution]

Hello Michael,

the missing event queue might be a reason for your issue because without event queue the workflow work process might be "too fast". In certain cases it can run faster than the candidate data is committed to the data base. In such a case the workflow won't run correctly and no password would be sent. To check if this is the case you have to have a look at the workflow log (SWi1) or to the mail protocol (SOST). The candidate should have not gotten a mail with a Password.

If the candidate got a mail but the password is not working there is a bug in the standard implementation of the smartform. The coding where you found the call of the function module BAPI_USER_CHANGE only knows the success case. An error case is not existing. If the module fails for any reason (e.g. user is locked, generated password is not allowed, ...) it will send the mail without actually setting the password. If this is the case check that the password Generation rules and the password check rules on the server are aligned. In addition I usually add a max 5 times do loop just for security.

Kind Regards

Roman 

[Former Member · Accepted solution]

Hi Roman,

we finally found the problem! As you have already mentioned, the password generation rules were not aligned to the server password rules(this document describes all profile parameters for logon and password. So we adapt our function module for password generation to fix this bug.

Thanks for help, Roman!

Regards Michael