Skip to Content
avatar image
Former Member

Business partner of organizational unit is not consistent

Hi,

Client is on SRM 4.0. When we are trying to search a user in the org structure, and when clicking on "Check" for this user, it was showing fine. But when we are searching any BP in the org strucutre, then immediately the BP name is vanishing against the BP of the user and when doing the "Check" it is showing the below two messages:

Business Partner of organizational unit XXXXXXX is not consistent

User cannot be repaired becasue the organizational unit contains errors

When checking in BBP_CHECK_USRES, the user is not showing as defective. It is green.

Similarly, the the organizational unit check is also showing as green.

System is advising to run BBP_BP_OM_INTEGRATE. When we run this for the org units, these are coming as green.

Users are able to create the shopping carts and also are able to create confirmations. But the problem is happening for some of the users where the system is not allowing to create shopping basket / confirmation.

Strange thing is that, when we are searching the user by user id in the org structure, then the check is showing no messages. But if we search the same user using the BP number, then in the check, the messages are coming. And once the messages appear, it is appearing for all the users in the org strucutre even at the root node level.

Any help is highly appreciated.

Thanks & Regards,

Aswini

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jun 25, 2010 at 03:16 PM

    Hi Aswini,

    There are some possibilities to raise these kind of errors messages:

    1) User with inconsistent data.

    Please, check the instructions described in the following notes:

    597475 - Repair users with inconsistent address data

    -> use the report B_REPAIR_EBP_USER_2 to make the user consistent.

    419423 - Repairing incorrect EBP users

    350129 - Creating business partner for organizational unit

    When you create the Org Units have you fully completed the address

    data, e.g post coe, telephone/fax number etc..

    If not, please enter a full address, save the data and see if this

    generates the Business Partner.

    Remember, that you can delete this user and create a new user.

    2) Error in the positions after HR replication

    Please, implement the following notes and retest the scenario:

    1056873 - Incorrect SRM users after HR distribution

    1016450 - Replication of persons deletes positions in SRM

    After implementing these notes you should send the employee

    corresponsing to the user in error with his position (using

    transaction PFAL or report RHALEINI in UPDATE mode for all periods.

    3) the user was deleted and a new was created and during these two

    actions the user opened documents. So, in this case, the new user

    becomes inconsistent

    If the user is deleted from SU01 still the BP and S which is related to

    that user will be retained (we can see this in PPOMA_BBP) transaction.

    In this case we can create the user again using SU01 and can be attached

    with the old 'S' and 'BP'.

    2. If the user is completed deleted ie., all relations BP and S.

    The new user has created.

    In this case if the new user is corrupted we can delete this

    user (since the new user doesn't create any documents so far). But the

    old documents should refer to the new BP related to the new user.

    ========================

    Also, another option would be to follow the below instructions

    After applying the notes 1056873 & 1016450, send the employees

    corresponding to the users in errors with their positions (using

    transaction PFAL or report RHALEINI in UPDATE mode for all periods,

    using evaluation path A008) ? If not, please do this and it must repair

    the SRM users. Please test and give me the feedback.

    Hope this helps,

    Kind Regards,

    Matthew

    Add comment
    10|10000 characters needed characters exceeded