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

User Creation

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)

2

Associate the user to the right user(s) group(s)

For S&OP Planners, first create a specific user group for the user 

Duplicate an existing user group and update name + user’s list :

For an S&OP Planner, associate 2 user groups : TS - WS - S&OP Manager + his/her own specific group 

For users with modification rights on a BU’s full scope : choose the authorized scope

Warning : this user will block other users from the same BU when connecting on the Workspace TS - A2 S&OP Planning



If the user also needs to have access to P&I workspaces, add him to the P&I - TS user group.

The scope of action will be the same than the one defined in Dynasys DIP.

3

If the user is S&OP Planner (prod planner and/or distribution planner and/or master planner)

> Add a new line in the MasterTable Supply planner 

> Create a condition for the new user (duplicate another one, and change the name and Windows ID) : "TS - Supply Planner - Country / User"

  • Condition type : filter applied to record codes 
  • Selection mask: User ID 
  • Parent master table: Supply Planner


> Update the advanced security for the Master Table Supply Planner and the Master Table SKU

Update the advanced security for the Master Table Resource :

If the user is not a prod planner (example : Ignacio Guerrero) => put Modify none 

> Add the user to the list in the Datafield TS - All Planners 

(you can also use the Workspace TS - A0 User Right / Tab "List of planners" to do this modification)

> Do an update of condition on the datafield TS - All planners 

> In the MasterTable Supply planner, 2 conditions  must be ticked:

> Update the security for Workspaces to give access to the user :

4

Give access to User Right Management Workspace (for S&OP Planners and Planning Managers) :

This workspace can be accessed by each user, but to prevent users from blocking each other, it is accessed with a specific user account. 

=> you need create a new user with this settings :

Name : Windows ID_URMS   

User type : Collaborator 

Account Activation : Disabled 

Membership group of definition : TS - WS - User right

the user will need to switch to this user to be able to access the Workspace (see dedicated wiki page)

5

Back-up management (for S&OP planners) 

To allow one user (User 1) to connect under someone else’s scope (User 2) with modification rights, we need to create a back-up user for User 2 

you need create a new user with this settings :

Name : Windows ID_Backup  

User type : Collaborator 

Account Activation : Disabled 

Membership group of definition : same as the normal user (in this case user MX70072)

User1 will need to switch to this back-up user (shortcut) to be able to change scope (see dedicated wiki page)

6

Give access to WW scope on read-only mode 

For SCE users for instance (need to access in modification mode for P&I workspaces, read-only for DIP-PP)

To allow one user to access the DIP-PP workspaces with a read-only authorization

> create a new user with this settings :

Name : Windows ID_WW  

User type : Collaborator 

Account Activation : Disabled 

Membership group of definition : same as the normal user

> Update the advanced security for the Master Table SKU  → allow no modification

> Update the security of the Workspace TS - A2 S&OP Review

This workspace is the same as TS - A2 S&OP Planning, but with no modification allowed

7

Add the new user to the DynaSys DiP1 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 DiP1.

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

**** Ask Laure Pichot-Plasse to add (or remove member) from SCo-$DynasysUsersDiP1 ****

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

> Search the group related to DynaSys DiP1 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



User is now in the Dynasys communication group

8

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




9

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"

  • No labels