S4 Employee business partner not updated with changes to the assigned user in infotype 0105

[GregRobinette]

This is in an S4 1909 system that was converted from ECC 6.0 EHP 7

An employee who has an employee (EE) business partner (BP) already created and working has the user id assignment changed in infotype 0105. The change is not an error but a valid change. The only way I have been able to find to change it is to run program RSUID_REMOVE_FALSE_BP_ASGN. This requires exception processing, separately scheduling and running this.

It seems like when a valid change is made to one of the infotypes (0105) that is updated by the /SHCM/RH_SYNC_BUPA_FROM_EMPL that it should be correctly updated in the EE BP. Does anyone out there in S4 EE BP/HCM land know if there is a solution to having valid user assignment in 0105 updated in the EE BP?

[former_member695561]

Good day Greg

Did you get a solution for the above? I'm facing the same issue.

Thanks

Mark Grant

[ArthurParisius]

Maybe you should add SAP ABAP to your tags. It might be that there is an ABAP solution.

[former_member641907 · Accepted solution]

Hello maybe it will help you: we had nearly the same issues in the customer project.
If you want to clear id assignment in infotype 0105 and use the programm RSUID_REMOVE_FALSE_BP_ASGN you have to do following steps:

1. Run the program: RSUID_CHECK_BP_RELATION to check the incorrect adress numbers

2. Delete the assignment in PA30 : 0105 / 0001 or direct in the table PA0105.

3. Now you can use the report RSUID_REMOVE_FALSE_BP_ASGN, for user you want to clear the assignment

4. Go to PA30 create the correct user assigment 0105/0001 again and SAVE it.

5. Now use the program /SHCM/RH_SYNC_BUPA_FROM_EMPL for selected employee-number.

There should be also a note from SAP for this procedure.

Best Regards, Alex M.

[GregRobinette]

Hi Alex,

We also discovered that path. We never could outright delete the assignment but had to use the change process to change the validity. The key issue was the delete icon did not work while changing the value and saving it did. Then we were able to run the rsuid process. That issue turned out to be a subset of an larger issue with the process for copying one system to another. In 1909 FPS00 we had to update the basis support packs to allow the proper import of the user file to allow even regular user functionality. Then we had further issue with the business partner/users due to address issues. SAP had us stop using the new tools in 1909 and use the old process (SCCN8 instead of SCC9N). We then had to use some special programs to 'fix' the business partner and address data before we could successfully run the EE synch prgam for re-assuigning the users to the EE BP.

[GregRobinette]

Update- We have been working with SAP.

The support team worked through this with us and here are some key points discovered.

In S4 on prem 1909 there were new tools introduced to make the client copy and system copy process better. These caused some disruption to our previous processes and SAP is working on resolving the issues in the new tools. In the meantime we worked to trace or find all the issues after using the older tool set to restore and copy the test system. We have an actionable set o programs to run to manage the creation of a test system with the appropriate users. It is my hope that SAP releases a note with the set of programs and instructions for this issue. We found out that there is at least one other client who has similar issues and we are collaborating with them.

[GregRobinette]

This issue keeps growing. As we have been trying to populate a test system with PRD level data by system copy using SCC9N we keep running into more issue with the business partners (BP). The vendor and customer BP are also failing due to address assignment issues. They all seem tied to the import of the user master and how that has new keys for the assoication of the addresses and users and that is then affecting the association of those addresses to the BP. Its clear that each system has unique ID's/keys for the system and that has to tie to users and that ties to addresses but that also use to be managed during a system copy and import of a new set of user masters. So far our high incidents with SAP have had no response other than to move it between teams at SAP.

[GregRobinette]

We still have not gotten a good well defined answer to this issue.

We have actually been learning a lot about the employee buinsss artner as we struggle through user dayta assignment during system copies.