Procedure to delete a user from SRM Org

[harishsarathy29]

Hi,

What is the procedure to delete the user properly from SRM Org.

I think it is not correct to delete the user from SRM Og, by just right click and delete.

Thanks in adv.

Harish

[robin_janke · Accepted solution]

Don't delete, just adjust the validity period of the user. Otherwise you will have trouble trying to access shopping carts/orders by that person (for example any shopping carts still awaiting approval, monitor shopping cart)

Regards,

Robin

[ricardo_cavedini]

Hello,

In fact a user can only be deleted if all documents (not only the open ones) were archived, as it says in SAP Note #676820:

"If you nevertheless want to delete a user who still has documents in the system, you must first archive this data. Afterwards you can delete the user."

This is a must for an R/3 system to avoid making documents inconsistent by deleting its user.

You can also follow recommendations below:

Option 1:

Leave the documents in the system and just block the user via BBPUSERMAINT.

Advantage: No archiving and closing of documents necessary.

Disadvantage: The EBP user remains in the system, from the business point of view some documents are not properly closed (e.g. like no GR done, no Invoice created, documents on status "hold").

Option 2:

Use the central purchaser for closing of all SC follow-on objects.

Disadvantage: SCs on status "Hold" can not be entered by any other person than the requester, so this might block the deletion of some documents.

Option 3:

Close all the open documents to make them archivable by using a different user.

This can be done as follows:

a) Replace the user to be deleted by a general "Completion user":

Goto transaction BP for the business partner of the user (in PPOMA_BBP its ID starts with "BP") and enter his ID, choose the BP role "Employee", then goto tabstrip "Identification" where you see under "User name" the name of the SU01-user. Replace this SU01-user with the name of the Completion user (e.g. the system administrator or his subsitute).

b) Now this completion user can access all the open documents, as a matter of course all necessary attributes, roles and authorizations for a complete EBP user must be assigned.

Kind regards,

Ricardo

Edited by: Ricardo Cavedini on Dec 15, 2009 10:08 PM

[former_member183819]

lock the user and remove his profile .

so that he can do any thing on our system.

it is very difficult to close all the docuemnt if you are deleted.

there should not be any opening docuemnts

https://wiki.sdn.sap.com/wiki/display/SRM/Team+purchasing#Teampurchasing-Whatisteampurchasing%3F

The function Team purchasing was added with SRM 7.0. Within Team Purchasing the team members can take over shopping carts of others and process them. Former when an employee was on vacation or left the company, nobody else (beside of the administrator) could process his SCs. Now with the Team purchasing the users can define substitutes themselves, who are able to take over their SCs. The substitution authority can be also inherited, so for example when Purchaser2 is substitute of Purchaser1, and Purchaser3 is substitute of Purchser2, then Purchaser3 can also take over the SC from Purchaser1.

br

muthu