on 08-06-2015 1:58 PM
Hi together,
we have an issue and get an error during the change of the preferred correspondence E-Mail address in the candidate profile and tab "Personal Settings" (see screenshot 1).
For this error we get the following SLG1 notification (see screenshot 2):
"Errors occurred during call of function module BUPA_CENTRAL_CHANGE
Message no. R11335
Diagnosis
The business partner BAPIs were called up incorrectly. The indicator IV_X_SAVE was given differing settings when the modules were called.
Within a LUW, the indicator must be consistently set or not set.
System Response
The indicator IV_X_SAVE should be set or not set once off. Up to COMMIT WORK the content of the field may not be changed, as problems will otherwise occur with the internal memory, thus leading to runtime errors."
Do you have an idea, what issue causes this error and if there is a helpful note that could fix it?
Thank you already for your help!
Hi Manuel,
we do have the same issue. The mail address for an internal candidate is not updated due to the described error. This is valid for 1 system and 2 system installations. From my point view the reason is that the function module BAPI_BUPA_CENTRAL_CHANGE is used in HRRCF_MDL_PERS_EMAIL_SAVE to save the data to business partner. But this function module doesnt work as the system is in a LUW which is opened in CL_HRRCF_CANDIDATE_BUPA_BL->MAINTAIN_PERS_DATA. If you check the method CHANGE_PERSONAL_DATA in class CL_HRRCF_CANDIDATE this LUW is considered correctly and depending of the LUW state the function module BUPA_CENTRAL_CHANGE or BAPI_BUPA_CENTRAL_CHANGE is used to save the changes. For the change personal data process related to the internal candidate private address the LUW will be closed in CL_HRRCF_M_PSETTINGS->SC_SAVE_PERS_SETTINGS. I would say the only correct solution is a correction of the function module HRRCF_MDL_PERS_EMAIL_SAVE to consider the LUW state like its done in CL_HRRCF_CANDIDATE_BUPA_BL->MAINTAIN_PERS_DATA. Reinitialization of the BUP_MEMORY may result in unexpected behaviour as the LUW logic is overrided.
Best Regards
Gerd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please check if IV_X_SAVE Issue | SCN helps?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It doesn't have to be in this WD component but mostly it is influenced already by the calls to it to don't make the commit work.
Have you tried the ANST tool?
The corrections we shipped for the iv_x_save are quite old but probably you can also search the notes in the Support Portal and make sure you have them in your system?
Regards,
Nicole
Hi Nicole,
Thank you for your help again!
We could find a workaround by modifying the class CL_HRRCF_M_PSETTINGS.
Here we have replaced the method SC_SAVE_PERS_SETTINGS with a new method, that has the additional coding:
CALL FUNCTION 'BUP_MEMORY_CENTRAL_INIT'. " ADDED
This new method ZSC_SAVE_PERS_SETTINGS is replacing the old method SC_SAVE_PERS_SETTINGS.
Now the saving functionality works.
But we unfortunately still get another issue:
When we have saved the Personal E-Mail Address and then change the Preferred E-Mail Address back to the Business E-Mail Address, then the Personal E-Mail Address is blank, but all values (including old Personal E-Mail Address values) are saved in the BusinessPartner.
Now if we change the Preferred E-Mail Address back to the Personal E-Mail Address and type in the same Personal E-Mail Address as before, we get the following error:
Basically, the error appears, because the old Personal E-Mail Address was saved in the BusinessPartner and thus, it is already reserved.
Do you know this problem and you know how we could solve this?
I think, we need to delete the old Personal E-Mail Address from the BusinessPartner, as soon as we change the Preferred E-Mail Address back to Business E-Mail Address.
Thank you for your help!
User | Count |
---|---|
4 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.