When we receive a request for a User Creation for TS here are the following steps:

NB1 : Reuse desactivated users in priority

NB2 : Do user creation first in DEV or TEST, then in PROD during a weekly/monthly release

#Actions to do
1.

Create the user using the right User Type (Global Planner should be only for users that will run calculations)

  • What is the scope needed for the user ?
  • Is this user will replace an existing user?
    • Yes: Who ? Can we deactivate the old one ? When ?

Create the user as follows: 

> The user Name : Windows ID 

> The Description: <GBU> / <Role> / <Country> / <Last_name> <First_name>  (refer to DSCP - Descriptions & Roles and also add the new user to this file)

2.Create a user group for the S&OP Planner 
Associate the user to the right user(s) group(s)
3.

If the user is a S&OP Leader:

  • Create a new line in the MasterTable S&OP Leader with the User ID in the code and short name column + description on the name

Note: for a S&OP Leader, the user group used should be the Zone.

4. 

If the user is a S&OP Planner:

  • Create a new line in the Master Table S&OP Planner with the User ID in the code and short name column + description on the name and add the linked S&OP Leader 

  • Create a new condition "NOVECARE - S&OP - Country / User"
    • Condition type : filter applied to record codes 
    • Selection mask: User ID 
    • Parent master table: S&OP Planner
  • Update the advanced security for the Master Table S&OP Planner


  • On the material master table create a new Condition "NOVECARE - S&OP - Country / User (display)
    • Condition type: User input value
    • Parent master table: Material 

 

  • Update the advanced security for the Master Table material@MSS


  • Create the DF in order to update the condition (yUsers Scope Management > S&OP Planner - Viewer Scope);


  • Add the assignement calculation of Active SKUs with "SOP Planner filter" in the datafield. 


  • Add the DF on the sequence "ALL GBU - UPDATE CONDITIONS"

    • To add the datafield on the sequence:
      Right click on the datafield → Add to a sequence → All Gbu - Update Conditions 
      Actions → Update condition 
      Action to be performed in case of error → move to next action
      Be sure to place the new action before the save to server 
       
  • Do a right click on the SKU master table and go to Security
  • Advanced security tab
  • Check that the user group linked to you user the visibility's condition and modification's condition are the ones created on the Material master table for Visibility and S&OP Planner master table for modification


  • Give access to P&I workspaces. Go to shared workspaces → P&I - 0.Set-up(scope/baseline/ref months) click right and go to security 

    • change object's visibility and write permission to "Allow"


    • click ok and save.

Do the same thing for the other P&I workspaces.

5.Go to workspace user right management, assign the plant to the S&OP Planner (if you know the plant)
6.

Open the hierarchy → resource;

  • Do a right click on the Resources Master Table and go to Security → Advanced Security and add the condition (only if the user is using PP). 

7.

If changes are needed to be applied instantly an update of hierarchies must be done. 

The sequence : ALL GBU - UPDATE MASTER TABLE has to be wholly executed. It is mandatory to avoid the execution of single actions belonging to the sequence.    

NOTE : It is very important to test the changes to be applied. First by modeling in TEST or DEVELOPMENT environments, once the desired changes are correctly reflected they can be applied in the PRODUCTIVE environment.  

8

Add the new user to the DynaSys DiP3 user group

We use these groups in order to make announcements and to communicate. Therefore, by adding them to this group, they will receive information related to DiP3.

**** Since PO2 D1 this step has to be done by SCO team ****

**** Ask Gregory Ditte to add (or remove member) from SCo-$DynasysUsersDiP3 (Novecare) ****

> Go to your Google applications and look for "Groups"

> Search the group related to DynaSys DiP3 users and click on the logo "Add members"

> Input the new user's email and write a welcome message and make sure subscription = "each email", then press "Add members", down the screen

9

Email the Interface team to allow user to access to server (this step can be anticipate before DynaSys user creation)




10

Provide this information to the requester :

If you need access to the DiP-PP reporting available in BW reporting tool you need to create following tickets :

 1) For BW access, create a SAP Access Request via Service One => https://solvay-dwp.onbmc.com/dwp/app/#/catalog

 2) To be informed when DiP-PP data is up to date in the DiP-PP reporting, create a ticket to be added in the distribution list => https://solvay-dwp.onbmc.com/dwp/app/#/itemprofile/659, choosing "2. BW DynaSys Reporting: change distribution lists for BW update message"