Build go live plan-role project

[Former Member]

Hi Gurus,

I have been asked to build go live plan for a role rebuild project that we are doing. On a 30000 foot view we are rebuilding the roles from scratch in our system as they were not in good shape earlier with unlimited access to users and hence we are rebuilding these. We have been live in SAP since 2 years and for these 2 years we were living with the crappy roles in place. Can anybody please help me to build the go live plan. Does go live plan and cutover plan mean the same? Please exaplin he differences if both are different. Also please help me identify the activities that need to be done after the user sign off in testing and before we say we are live in production with the new roles. Help is greatly appreciated

thanks

Anusha

[Former Member]

CUT OVER/Go live

This is a very big answer we go on and on with various plans:

Braintstorm within your team to see if you are prepared for the following: Who and what kind of access is required to do the following Basis/security/developers/Process integrators/Portal access etc...... based on your project will need access to SAP systems to

Shut down other linkedapps( Basis /infrastructure)

lock users out ( security)

Extend space as necessary ( basis )

pre-prepare activities

New install complete

Kickoff SGEN

Post Processing

Review SPAU List/ABAP Task

FI/CO Go-Live Tasks

Turn on monitoring

etc.......................................................

find :-

Has user master record been created in SAP ABAP system?

Is user id unlocked?

Are ABAP roles assigned to UMR in SAP ABAP system?

Are ABAP roles generated?

Are correct profiles that are associated with assigned ABAP roles assigned to UMR?

Are correct defaults set in ABAP system?

Is user id set as Dialog?

Are correct parameters assigned to all users?

Are portal roles & permissions assigned to all users?

GO live : You should have support for all the functional teams and validation team and various other team to monitor and sign off that the system is ready for access for all users

This is just a simple list sit with the business/support teams to decide what they need.

[Former Member]

Please excuse me for my ignorance. But to give you an idea on how this project has been worked out so far is. We have test scripts in place that are true representation of the day to day business processes. So each functional analyst has interacted with teh respective business process owner and his/her team to validate these test scripts thus confirming two things

1) all the tcodes that are listed on those test scripts is what is being done currently and 2) ALL the test scripts are accounted for.

so those tcodes that were not on any of these test scripts will not find a place in the any role.

This is the kind of approach we took. So literally the tcodes that are present on the test scripts is our bible to help us desinging the roles.

Also the approach we plan to take in administering the new roles in production environment is

1) for example we will select a few users in the purchasing department and assign new roles to them and take out the old roles. If they are able to perform all of their day to day functions which they were doing earlier with the old roles, then it is a good sign and then we will pick the next set of users and so on.

probably this might be useful toyou to guide me keeping in view these things

Thanks

Anusha

[Former Member]

whatever mess you have with roles, you will have to fix it from DEV ( perfrom unit test ) and do your necessary ( UAT/ use existing scripts ) in Quality system once that is done take approval from the business/technical team members and move it to Production.

create a clean up plan & test plan in (DEV/QA environment) for the few users

you have mentioned let them sign off , then move the roles to production assign it to the users.

few users at a time will be tedious process based on the number users and access variation

[Former Member]

Hi

Really how bad are your existing roles?

A brand new build will bring you many months of work (and pay) as you weedle out the daily influx of emails with SU53 screenshots

If you can manage to re-use your existing roles but in a more controlled manner you will (hopefully) save time, face and a few grey hairs, having remediated many end markets and having project managers demand a new build, I've 'been there' and ripped the T-shirt to shreads. Your test scripts will not find the detailed auth checks that a month or year end process will kick out (particularly in treasury)

Try to keep the roles if you can - they may look crappy to you right now but in a few months' time you may find you are re-assigning them as an emergency...