BW system has 3 environments

         1.WBP (Production Environment

         2.WBV (Pre Production Environment)

         3.WBQ (Quality Environment)

        

In this article let us discuss the user creation in WBP system (same procedure follows for WBV and WBQ system as well)


User creation in WBP system

          Pre analysis need to be done before before creating a user in BW system:-

1. Whenever we get a ticket on BW user creation first we need to check for which BW environment he is requesting access for Production , Pre production , or Quality.

2. Next step is to check whether the requested user exist in that particular system or not , once we make confirm that user does not exist we can proceed with the ticket.

3. Once we make sure he is not exist in WBP system third analysis is to check the GBU and Location to which he is requesting access.

4. Final Analysis is to check the user details in IDM , Suppose if user not belongs to the GBU and location to which he had requested access , then we need to ask for the justification with                user that Why he/she has requested access to the GBU or location which they are not belong


                                                                                                                              

                         


         We have a standard BW catalogue where we get all the BW Roles , below is the G drive link to the Catalogue

         


Note : In WBP we have Business role and Privilege roles , One business role can have multiple privilege roles , we need to assign all the privilege roles associated with Business role.

We get to know the privileges associated with business roles from BW Catalogue.


         We have two methods to create a user in WBP system

              1. Using Reference use

              2. Without using Reference user


1. Using Reference user

  •  In this case users will mention  any reference user details in the ticket to mirror the same access to their profile in WBP system. Here again we need to make an analysis whether the         user and reference user profile match in IDM in terms of GBU , Job Function and the location where they belong , we can only proceed if they match or else we need to ask for the           justification for the roles reference user having.

                 


  • Once we make sure reference user matches the profile of user , we need to check the roles of reference user in SAP LOGON
  • Lets take below is the screenshot of roles of reference user , here P01 , P02 , P04 etc represents the privilege roles associated with BR reference user having which can be copy directly to the user under privilege roles in IDM , and  M03 , M19 , M41 represent the business roles , So we need to get the business role associated with this privilege from BW catalogue , attached a screenshot to get the BR for M03 privilege from BW catalogue(M03 represent IM stock in BW catalogue).

     


 


  • Business Roles in BW catalogue which have star(*) at the end represents the roles which are assigned according to the GBU of user, when we are assigning this role in IDM we get a list of GBU , we need to select the right GBU to which the user belongs or requested access for.

             




2. Without using reference user

  • In this case users will mention the BW application names to which they need access in the ticket itself. Privilege roles include company access , plant access , family , GBU etc , users also mentions the company code ,  plant code and GBU they need access.

                       


  • Once we get all the required information in ticket , we can assign the respected business roles and the privileges associated with the business role to the user.
  • After the assignment of the roles same will go for approvals from the approver , once it is approved user can have the required access.
  • Let us take an example , suppose if any user requested access to BW application : Sprint-Purchasing , we need to follow this procedure : Go to BW catalogue-Search for Sprint purchasing BR-assign the BR to the user-Now look for the perimeter roles associated with Sprint - Purchasing-Perimeter roles associated are Company access , Plant access , GBU access and Area sprint access-Assign these perimeter roles in Privilege role assignment-Now user can have access to Sprint Purchasing BR.


Tickets for Reference






  • No labels