cancel
Showing results for 
Search instead for 
Did you mean: 

person - address combination doesn't exists in BP

former_member198566
Active Participant
0 Kudos

Hi Experts,

While clicking on relationship tab in BP we are getting the error: person - address combination doesn't exists in BP.

Probably because of this we are getting the error: employee relationship between BP and BP org is missing while we run consistency check.

Note: We are on SRM 7.03 and we are replicating HR master data.

We tried to correct the user's inconsistency by moving user from one org node to another but no success. I see that the tables BUT050, BUT052 has incorrect mapping of BP.

Please suggest how to correct the relationship status for User's BP and inconsistencies in org structure.

Thank You.

Best Regards,

Abhishek

Accepted Solutions (0)

Answers (1)

Answers (1)

ivy_li
Active Contributor
0 Kudos

Hi,

Please read wiki for analysis of such error:

https://wiki.scn.sap.com/wiki/x/mQmGGg

If you still can't solve this, I suggest you raise an incident in SAP since such error is not easy to be solved without analysis in your system.

BR,
Ivy

former_member198566
Active Participant
0 Kudos

Hi

This wiki page is restricted by owner, unable to see the content. Request if you can share the details present in the link.

Thank You.

Best Regards,

Abhishek

ivy_li
Active Contributor
0 Kudos

Hi.
,

Sorry, this wiki is written by me. I will contact the responsible person to release it to all.

BR,
Ivy

former_member198566
Active Participant
0 Kudos

Thanks Ivy,

The link is still not open for us.

Request if you can share the details present in the link.

Thank You.

Best Regards,

Abhishek

ivy_li
Active Contributor
0 Kudos

Hi,

The content is not easy to write them all here.
Now the wiki is being checked internally, and will be released soon.
I will let you know in this discussion once it is available.

BR,
Ivy

ivy_li
Active Contributor
0 Kudos

Hi,

Sorry for the late response since I just now got notification that the wiki is released.
Please refer to it and hope it helps in analyzing the case:
https://wiki.scn.sap.com/wiki/x/mQmGGg

BR,
Ivy

former_member198566
Active Participant
0 Kudos

Thank you Ivy,

The error issue and analysis is exactly same as you have given in Wiki. As per the wiki you have suggested 2 notes:1508775 and 836353, but looks like these Notes are from 2010 which is no more relevant for SRM 7.03.

We managed to find the Notes 2008038 and 2214586 relevant to the issue. Lets see if it helps.

Thank You.

Best Regards,

Abhishek

ivy_li
Active Contributor
0 Kudos

Hi,

Even if you are using SRM713, it is OK to use the reports in note 1508775 and 836353.
The structures of storing user and relationship is not changed, so the Z-reports are available for all SRM release.

For note 2008038 and 2214586, they are not used to help to fix the data inconsistency issue, but help to figure out the root cause if your issue could be reproduced.

BR,
Ivy

former_member198566
Active Participant
0 Kudos

Thanks for clarification Ivy.

I will check again. When I checked the note in my development system it gave the  Impl. status as: Cannot be implemented. So I am confused if still it can be implemented even if the status shows as cannot be implemented in transaction snote.

Thanks.

Best Regards,

Abhishek

ivy_li
Active Contributor
0 Kudos

Hi,

I believe your issue is caused due to database inconsistency, so no note implementaion can solve this. That's why I suggest you read the wiki page to do troubleshooting to identify the missing entries in which table. Anyway, if you can't solve this from your side, I suggest you report incident to SAP since this is not easy to solve.

BR,
Ivy

former_member198566
Active Participant
0 Kudos

Hi,

While analyzing we could find that there is mismatch of the Org Unit Relationship in BUT050 table.

The issue is exactly same as you have described in wiki.

The issue started appearing after we upgraded from SRM 7.03 SP6 to SP10.

Best Regards,

Abhishek

ivy_li
Active Contributor
0 Kudos

Hi,

I could not suggest more, since I can't check all the details in your system.
You may refer to the solution in my wiki page, and if it doesn't help or you can't understand how it should be executed, please raise SAP incident to us and we will help to solve this after checking in your production system.

BR,
Ivy