This article outlines the process which needs to be followed when managing access in the SAP GWP - NEPTUNE  system


SAP GWP - NEPTUNE  is the production system 

SAP GWD - NEPTUNE is the DEVELOPMENT system 

SAP GWQ - NEPTUNE  is the Quality system 


Tickets :

The tickets for the management of users in the SAP GWP - NEPTUNE systems can be of different types. These can be :

  • User Creations - With a Reference User / Without a Reference User
  • User Modifications - Addition / Removal of roles
  • Transaction Access
  • User Unlock / Validity Extension / Password Reset
  • Missing Access, etc.
  • User Creations -  With a Reference User  / Without a Reference User

           When we receive User Creations, after we check the approvals, we always need either the Reference User or the list of all the roles which have to be added to the user. In this case of the new user creation, if the user only mentions the 

           transactions which the user needs, then it is always a good idea to ask for the Reference User as otherwise the role added or the solution provided might not be too accurate Once we have the required information, the user group has 

            be set in the Logon Data tab and the roles have to be added to the user account using the IDM (Identity Management) through the Permissions tab






****If the user belongs to  GBU :- composite material :-

Step-by-step guide

Ticket:-

https://sbs-support.solvay.com/a/tickets/6029463

  • If the user is asking for the access SAP GWP/Neptune system for  GBU Composite Material on
  • Then in this case we have to assign the below role .:-


            PR: COMPMAT - NEPTUNE - IM PRODUCTION

  •   once above role is approved by the approver in IDM then user will have all the access in SAP GWP/Neptune System  for the GBU Composite Material.



****IF THE GBU :- OTHER THEN COMPOSITE MATERIAL :-

Reference ticket :-

   https://solvay-smartit.onbmc.com/smartit/app/#/workorder/AGGEMRVSDG4EQARI5A1HRH5PZEY17T


As we can see in the above ticket USER BELONGS TO GBU :- GBU SODA ASH AND DERIVATIVES

**IN GWP IF THE GBU IS OTHER THEN COMPOSITE MATERIAL THEN WE HAVE TO FOLLOW THE BELOW SAME PROCESS FOR EVERY CASE 

STEP BY STEP GUIDE :-

1.  We will check the USER ID IN SAP LOGON if the user is existing or not by using transaction SU01D



  • IN THE USERS TAB WE WILL ENTER  USER ID OF THE USER IF THE USER IS NOT EXISTING THEN WE WILL ENTER THE REFERENCE USER ID

           AND WE WILL COPY THE INDIRECT ROLES OF THE REFERENCE USER AND WE WILL ASSIGN TO USER IN IDM


Once this is done and saved in the IDM, we need to mirror the values in the SAP GWP system tabs of the Reference User to the user who needs the access. This includes the information in the tabs Logon Data, Defaults and Parameters. This is followed by the password reset and the same is informed to the user and the ticket is Resolved.



Transaction Access OR USER MODIFICATION

In case of a Transaction Access, the corresponding role to the transaction has to be found out through the transaction SUIM (User Information System → Roles → Roles by Complex Selection Criteria) based on the users Existing roles, Country, GBU, Function, etc.


Once the role is found out, the same is assigned to the user in the IDM and ticket is Resolved.

Missing Access

Missing Access is handled similar to the Transaction access. The only difference would be that the Object and the Object value will be different. The Object and the Object values are obtain by the SU53 screenshots or the text files which is sent by the user.

Once the role is found out, the same is assigned to the user in the IDM and ticket is Resolved.


User Unlock / Validity Extension / Password Reset

The user unlock and the validity extensions are supposed to be done through the IDM through the Logon Data tab and the same is reflected in the system. The password resets are all done directly in the system and have to be done always while performing a new user creation.


USER UNLOCK  :-


STEP BY STEP GUIDE :-

  • If we get  the ticket regarding the " Reactivation of the user " in SAP GWP - NEPTUNE system 
  • First we have to check in SAP LOGON by using  " SU01D "  transaction 

 


  • After entering SU01D TRANSACTION AND CLICK ENTER IT WILL TAKE US TO BELOW ATTACHED SCREENSHOT 


After entering the user id click on Highlighted specs sign it will take us in the below attached screenshot


Check in LOGON DATA tab always you can find there if the user is locked or USER IS Active if the user it will show  " USER IS LOCKED " BUT IN THE BELOW ATTACHED SCREENSHOT WE CAN SEE USER IS ACTIVE 



  • if the user is " IN - ACTIVE OR LOCKED IN SAP GWP "
  • Then in the above case if the user belongs to  " SOLVAY " THEN We have to provide the following Link but before providing the following Link check the user in IDM ALSO if the user is " LEAVER FLAG OR NOT " :-

              https://docs.google.com/document/d/1aTLwZssalj7422FsPNzC0jOVG5TjaVatxR9Jb5tzmKc/edit


  • If the user belongs to Third  party Such as :- Domo e.t.c At  that time we have to reactivate the user manually also we have to reset the password also


PASSWORD RESET :- 


For the password reset we have to use the following transaction IN SAP LOGON

Transaction :-  ZCA_USER_PARAM



Validity Extension :-



Step-by-step guide

  •  Ticket :-

                    https://sbs-support.solvay.com/a/tickets/6270624

  • Suppose if the Validity date Expire / End of  any of the user in the required / Mentioned SAP system then we can check it by the single click in the LOGON DATA TAB inside the required mentioned SAP System for example you can see the attached the below screenshot :-

              


  • Sometimes user also provided us the error screenshot in the ticket like that :-

              


  •  In order to correct the expired / Ended validity date we have to add a note in the ticket :-

           Veerle Ravijts ( veerle.ravijts@solvay.com ) OR Nipun Tomar ( nipun.tomar@solvay.com )

           for example you can see the attached  below screenshot :-

          


  • After correcting the Validity date of the user in the required / mentioned SAP system

          We can check it again by the single click in the LOGON DATA TAB inside the required mentioned SAP System

          for example you can see the attached the below screenshot :-