cancel
Showing results for 
Search instead for 
Did you mean: 

SRM User id Error

Former Member
0 Kudos

SRM User id shows defective in when checked with transaction BBP_CHECK_USERS…. Suggested to repair it.

We closed all the shopping carts & tried to repair it but system is

throwing same error message as “user id can not be repaired because

there are open shopping carts ”

We checked entire cycle upto invoice posting all carts were closed

still we were getting error as open shopping carts exist.

System is not allowing us to do user repair.Also we transferred all the carts to different user than tried again still getting same error.

Please advice how to proceed in this case.

Sanjay Karkun

We don't have any replication of error in quality also.Let us know what

can be done to repair user

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Sanjay

U can use the follwoing steps:

Bring up LBBP_UTILITIES_2U11 in DISPLAY mode via SE38

Find 2nd occurrence of CRMD_PARTNER and set Breakpoint

In new window, execute Execute BBP_CHECK_USERS

Do check on user and then select ‘Repair level 2’ and <Execute>

At Breakpoint, single step past Read statement and modify SY-SUBRC to 4

Remove Breakpoint from pgm

Execute(F8) the program.

<b><b>But the issue is that all the SC realtioship will be lossed with user.</b> Before reparing the user this way consult the business.</b>

with regards

Manjunath

Former Member
0 Kudos

Hi

<b>Please go through this -></b>

Which SRM versionare you using ?


Users in the EBP system should only be created with the administrator service (BBPUSERMAINT), the Internet self-service (BBPAT03), the WAP service for user administration (WAPBBPUSER) or the transaction for mass creation of users (USERS_GEN).You find the Internet services in the launchpad of the browser if you have been assigned the corresponding role.

The address data of users should only be changed with Internet services.

You can use the attached report to check incorrect EBP users and to repair this users, if necessary.For this purpose implement the attached report into your system.

Note:The report is contained in your system and is called "B_REPAIR_EBP_USER_2".The current version of the report exists in your system as of the following R/3 Support Packages:

in EBP Release 2.0B as of EBP Support Package 24

in EBP Release 2.0C as of EBP Support Package 17

in EBP Release 3.0A as of EBP Support Package 10

in EBP Release 3.5A as of EBP Support Package 2.

The report has two input fields and 5 selection options:

'UNAME'

Here enter the user ID of the user with whom the problem occurs.
'COUNTRY'

Here enter the ISO code of the country to which the user should be assigned. The input help displays a list of all valid countries.

'CHECK'

If this option is selected, no change is made in the database.Only some checks are performed and if necessary an output occurs.Even if the output does not result in an error, a repair of the user may be necessary.The check routines only check some frequent error constellations.

'LEVEL1'

If this option is selected, the user is repaired.You should always first try to repair the user with this option.
If the problem still exists after this repair attempt, you should try to repair the user with option 'LEVEL2'.

'LEVEL2'

If this option is selected, the user is repaired.In this case all objects associated with the user (position, head office of person and business partner) are deleted and newly created.The attributes maintained for the user are not changed.

During the execution of the report sometimes a dialog box is displayed, in which you must enter an organizational unit.Search for the organizational unit, to which the user is assigned, by entering the name of the organizational unit (not the number) as search text.The dialog box is only displayed if the organizational unit could not be determined automatically.

If the problem still exists after this repair attempt, you should try to repair the user with option 'LEVEL3'.
Take the below warnings regarding the repair of the users with level 2 and 3 into account.


'LEVEL3'

In this case all objects associated with the user (position, head office of person and business partner) as well as the user are deleted and newly created. The attributes maintained for the user are not changed.The user also keeps his roles and authorizations as well as his old password.

During the execution of the report sometimes a dialog box is displayed, in which you must enter an organizational unit.Search for the organizational unit, to which the user is assigned, by entering the name of the organizational unit (not the number) as search text.The dialog box is only displayed if the organizational unit could not be determined automatically.

During this action the work items that the user has in his workflow inbox may be lost.

In rare cases it may be necessary to create the user again after using option 'LEVEL3' to repair the user.In this case proceed as described in Note 385928 and afterwards create the user again.This is only required if the repair was carried out incompletely, for example because the report terminated during the repair.
Take the below warnings regarding the repair of the users with level 2 and 3 into account.


"HRACTIVE"

Set this parameter if you obtain the organizational structure of your EBP system by replication from a HR system (as described in Note 312090).If you do not replicate your organizational structure from an SAP-HR system, you must leave this parameter unchanged.

Warning:

Bear in mind that all open goods receipts and invoices of the user must be closed for local purchase orders in the EBP system before you carry out a repair with level 2 or 

3.
Therefore, you must not repair any users with level 2 or 3 who have open purchase orders or shopping baskets.All user operations must be completely closed before carrying out a repair operation with level 2 or 3. However, repairs with level 1 can be carried out any time.On the other hand repairs with level 1 are always harmless.

The execution of the repair with level 2 or 3 does not cause any problems

if the users have been created again and no documents (shopping baskets, invoices, purchase orders) have yet been created.
if the system is not a production system.

<b>Related SAP OSS Notes -></b>

Note 419423 - Repairing incorrect EBP users

Note 671521 - EBP 4.0: User repair Level2 BBP_CHECK_USERS incorrect

Note 785802 - PPOMA_BBP: 'Defective' users in EBP

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi,

See the foll threads for more hints:

<b></b>

BR,

Disha.

<b>Pls reward points for useful answers.</b>

Former Member
0 Kudos

Hi,

Kindly let me know your mail id so that I can send step wiase process for user repair.

Brgds/Gopesh