Skip to Content
-1
Former Member
Jun 24, 2009 at 06:39 PM

Effects of deleting users in live Production system

475 Views

Hello everyone !

Hopefully the Subject line was not too scary.

So here is the cause and the proposed solution

We have a payroll program that dumps a file with a list of active users in our Production system which is then picked up by a custom SAP program and changes are made to the user master depending upon if the user is a "New", "Change" or "Lock". At no point, is a user master deleted from SAP. A terminated user in the payroll amounts to locking out of the user and revoking of all roles.

There are several limitations/flaws in the program logic because of which it does not seem to generate the correct list of users. The custom SAP program works just fine.

In order to resolve these issues, someone came up with the solution of deleting and recreating the user masters every time this file runs. This would mean ALL the users will be deleted and recreated every pay period (bi weekly) and will be done by modifying the SAP custom program.

Question

Assuming the licensing is not an issue, can some of you please shed some light on what could be the implications of doing this as far as the operations are concerned ? What are the possible problems you see happening ? What kind of testing do you think should be done before flipping the switch ?

I tested out a few scenarios by myself which comprised of deleting a user while a job was running under his name, creating a PO and then deleting it etc and most of them seem to be okay.

As a Basis and Security Admin, I am a bit reluctant to take this way out for the fear of the unknown. No matter how much we test this out, I think there could be some surprises that would be difficult to resolve when we decide to implement this in our Production systems.

Any comments/suggestions will be highly appreciated.

Thanks,

Kunal