INTRODUCTION 

Objectives and scope of this procedure

This OP explains how to create a user when he doesn't exist in SRM7.

Requirements

• User to be created in SRM7 must have a user ID in GRC tool
  
  
• Check if the user already exists in SRM7 (transaction SU01). If he already exists, check his validity date. If it is in the past, just reactivate the user by changing the end of validity date to 31.12.9999
  
  
• The creation of the SRM7 account of a user needs to be done when user needs access as requester, as approver, to display or as administrator:
  
  
  1. If user is a requester:
     
     1.1. BIP Application Manager/ End User Partner (EUP) requesting the user creation must create a ticket with the Procurement Organization excel file in which he must set up the new user.
            He also has to provide the name of the manager / financial approver and position (in the financial approval structure) of the hierarchical manager of the user.
            Check the Application Manager/EUP on SRM AM & WW Controllers list.
     
     1.2 If user to be created is from NAM region (US, CA or MX), account creation request needs to be submitted by his manager or by End User Partner of the site, through the Form.
           
     1.3 For EMEA region, there is the possibility to use a Form to account creation request. This form should be submitted by user´s manager or by EUP of the site. 
           However, if the form was sent by the user or another person (ex: user colleague), SRM7 team can accept the request but need to ask for approval to user's manager with EUP of the site in copy. If needed, for additional clarification, escalate to Dirk Vercammen (responsible to give training to EUP's in EMEA zone).
     
           If the Form was not sent SRM7 team will proceed according to 1.1, however, team can always inform about the Form for future requests.
     
     
  2. If user is only an approver:
     Requesting the creation of the assignment of the user to an approval position is enough to proceed with user creation (in this case user is assigned to "Users for Approval Only – TO USE" structure).
            According with the type of approver - Technical (TC), Purchasing (PU) or Financial (FI) - request must be sent by Application Manager (for TC), Purchasing Key User (for PU) or Application Manager or WW/Zone/Function Controller (for FI).
  
        3. If user needs access only to display shopping carts (usually Service Centers Provisioning and Accounts Payable teams):
           Request must be submitted by manager of the user.
  
         4. If user is a new member in the Data & Analysis / SRM7 team access needs to be provided as administrator.
  
  

• Once user is created, user data must not be changed in SRM7 (last name, first name and e-mail address) unless in order to be updated according to an Active Directory change (information available in GRC).
  
  
• Users created for Brazilian companies / plants (except for company ZBR1) also have to be created in the platform of Mercado Eletronico.

• • Once the SRM7 accesses have been provided, a ticket requesting to grant accesses in Mercardo Eletronico should be created to PtP D&A LAM/NAM
  • For this request, we must send the user ID and advise if it is a requester or approver

For users created on the departments related to Purchasing & Supply Chain we have to contact the buyer responsible for this project, Mr. Jefer Citadini, asking if the new user will be a purchasing approver, before contact the Mercado Eletronico to create the user in the platform.

• WHO IS THE TEAM RESPONSIBLE TO PROVIDE ACCESS TO THE USER:
  
  
  • SBS PTP D&A SRM Team:
    • Access requests related to end users in BP2, BV2 and BQ2
      (Access to create and approve shopping carts as well as to visualize – general requests)
  • IS-SD-AUTHORIZATION Team:
    • Access requests related to IS users, auditors and technical users in BP2, BV2, BQ2, BD2
      (Access to specific roles and transactions)

Validation

Go to BP2, Tcode - SU01 – Check if the user exits:


If not, proceed with creation through GRC tool:

Freshdesk ticket handling

When a ticket arrives to the PTP D&A SRM Freshdesk Group, the ticket is pick up by a team member.
The ticket needs to be updated (if needed) to the correct classification "PTP Request ", PTP-Process "Data & Analysis, PTP-Subprocess "SRM7" and PTP-Category "Approval structures maintenance".

• Make analysis of the request to see the person responsible to validate the request.
• Check if the ticket requester is the Site Application manager /WW Controller/Purchaser Key User or was validated by Site Application manager/WW Controller/Purchaser Key User. To check the person responsible to validate see the link below:

{+}https://docs.google.com/spreadsheets/d/1_5H3sPBO7bN3HJvOcx_hRUsmujwLHhYKoTXEpmRxU3M/edit#gid=2051071738+

If not an approved requester, the team contact the Site Application manager (AM)/WW Controller/Purchaser Key User to validate the request.  (1)
Change the status of the ticket to "Need for more information"
If yes, proceed with the changes

•  Make the necessary changes
•  After the modifications are done the team member Inform all involved parties in the loop of the changes made.

The ticket can now be closed.
Change the Ticket status to "Closed".

(1) When an email is sent asking for more details (requester) or some kind of approval (AM + WW Controller), always put all involved parties in the loop (Requester + AM/WW Controller);

• If no feedback was provided, after 3 days we send the 1st reminder asking for feedback;

• If no feedback was provided, after 3 days we send the 2nd reminder asking for feedback;

• Finally if no feedback was provided, after 3 days we send a 3rd message with the following text:

*Dear xxxx,
As we didn't received any feedback for our question/s it's not possible to our Team proceed with your request.
 
Please be informed that we need your site Application Manager/ WW Controller/Purchaser Key User approval to proceed with your account creation as requested (for example).
 
Dear Application Manager, we will proceed with the closure of this ticket.
 
If you can provide us the requested feedback please just reply to this message and the ticket will automatically re-open in order to our Team proceed with requested actions.
 
Always at your disposal,
SRM Team*

STEPS OF THE PROCESS

User Creation on GRC tool

Go to the URL link (with Internet Explorer): http://pyjsapr3.ibm.be.solvay.com/AE/index.jsp

 
#1#2

#1#2#3#4

#1

#1#2#3

#1

#1

#1#2#3#4

#1#2

#1#2#3#4#5#6

#1#2#3#4

#1

#1

Note: GENERIC users can be created in SRM if already created in GRC, but only as requester never with an approval position.

Confirmation of the user creation

Go to BP2, Tcode - SU01
Check if the user was correctly created.

Assign the user to the Procurement Organization structure

Go to BP2, Tcode - USERS_GEN
#1

#1#2

#1#2#3

#1#2

#1#2

#1#2

Manage the requester attributes in the structure

Go to BP2, Tcode - PPOSA_BBP

Define Manager / Financial Approver:
#1#2#3#4#5#6

#1#2#3#4

Provide access to catalogs to the user:

 #1#2#3

Provide access to an additional delivery address:

#1#2#3

 Provide access to other co-plants:

#1#2

#1#2#3#4

Note: Extended Attribute "Output limit" (defined on "PO Value Limits") is inherited at users' level from the country department (self approval limit).

Self approval limit amount can be checked on "Financial Validation Thresholds" table (level 0).

Create user in Work Cycle

When a user receives access to SRM7, the user also needs to receive access to Work Cycle.

- If the user is a PF1 user, SRM7 Team will also create this access.

- If the user is a WP1 user, SRM7 Team doesn’t need to do any action as the access will be automatically created.

In order to create the access, go to PF1_020 and access t-code /COCKPIT/WUM

REFERENCES

ATTACHMENTS

End of document