You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article outlines the process which needs to be followed when managing a request for transaction access, missing access and additional access (eg. Plant, Sales Org, etc.) in the PI1 and SI1 system.

Information

PI1 is the Production Environment and the SI1 is the Pre Production Environment.

Identifying the Tickets :

When the users mentions that he / she needs access to a Transaction, Plant, Sales org, etc. or if the user has added a screenshot of an error or the SU53, then it can be identified as a Missing Access. If the user needs access to a Transaction, then it can be identified as ticket for Transaction Access. The users generally exist in the system. These tickets may have the accompanying information like the Name of the User / IDReference User Name / IDSystems, etc. Below is an example of how the ticket may look like.

 

Approvals :

Before proceeding with these kind of tickets, we need to always check the approvals. The approvals for the PI1 and SI1 system are managed by the L0 Teams depending on the region. If there are approvals are missing in the ticket then the ticket has to be transferred to the respective L0 Team (Bangkok, Lisbon or Curitiba) asking them to get the approvals. Also, we need to ask for a Reference User ID if there is a confusion in obtaining the accurate role.

The request is approved if an agent from the L0 Team mentions that the it is approved or if the one requesting the access is the User's Manager. An example can be seen below :

 

 

  • No labels