General

A User will have a Role and a Scope :

• the Role depends on his fonction and define which workspaces he can access
• the Scope defines which DF/data he has access to

Each user will have :

• one (or many) role(s)
• one (or many) scope(s)
• one profile (viewer, global planner…)

Each role/scope will be defined through a User Group.

The steps to create a new user are :

• Create User

Note : Avoid to re-use an old user for traceability/connection dashboard

• Create scope User group(s) 
• Define security for the scope User group(s)
• Assign User group(s) to the new user

User role

• General overview of the user roles

Each role is linked to :

• Workspaces,
• Shortcuts,
• Calculations
• Write/Read on models

The Security is set-up in the Workspace and the Forecast models.

The User group to assign a role to a user are generally defined during the project phase. No new user group should be defined for a new user creation.

• User and type of access per GBU

When receiving a request for an access, the first step is to collect all required information :

• User Name
• Windows ID
• GBU
• Role (refer to list below)
• Scope (refer to list below)

• 
  

  GBU	Role	Scope	Type of role	User group	Type of access
  AROMA PERFORMANCE	Demand Planner	Zone	Global Planner		Remote
  	Sales Rep.	Sales group code (WP1) Account Manager code (PF1)	Collaborator		Remote (Migration to web planned in March 2021)
  	Global Key Account Manager	GBU Ship-To Group name/code	Viewer		Remote (Migration to web planned in March 2021)
  NOVECARE	S&OP Manager	Windows Login + set-up by Main Shipping plant / Main Production plant	Global Planner		Remonte
  	Sales Manager	Sales group code (WP1) Account Manager (PF1)	Collaborator		Web
  	Sales Assistant (CSR - Customer Service Representative)	ZI Partner code (WP1) CSS Representative code (PF1)	Collaborator		Web
  	Global Key Account Manager	Ship-To KA name/code	Viewer		Web
  	RMD (Regional Market Director)	Zone and BfC Market	Viewer		Web
  	BDM (Business Development Manager)	Zone and BfC Market	Viewer		Web
  PEROX	Demand Planner	Zone	Global Planner		Remote
  	Account Manager		Collaborator		Web
  	Global Key Account Manager	GBU Ship-To Group	Viewer		Web
  SILICA	Demand Planner	Zone	Global Planner		Remote
  	Sales Rep.	Sales Group code	Collaborator		Web
  	Sales Assistant (CSR - Customer Service Representative)	ZI Partner code	Collaborator		Web
  	Global Key Account Manager	Ship-to KA name/code	Viewer		Web
  SA&D	Demand Planner	Zone	Global Planner		Remote
  	Account Manager	Account Manager (PF1)	Collaborator		Remote
  	Sales Assistant (CSR - Customer Service Representative)	CSS Representative code (PF1)	Collaborator		Remote
  SPECIAL CHEM	S&OP Manager	Windows Login + set-up by BfC Market	Global Planner		Remonte
  	Sales Manager	Sales group code (WP1) Account Manager (PF1)	Collaborator		Web
  	Sales Assistant (CSR - Customer Service Representative)	ZI Partner code (WP1) CSS Representative code (PF1)	Collaborator		Web
  	Global Key Account Manager	GBU Ship-To Group	Viewer		Web
  TS	Demand Planner	Zone + BU	Global Planner		Remote
  	Product Manager	Manually set-up	Collaborator		Web
  	Sales Rep.	Sales group code (WP1)	Collaborator		Web
  	RSD	List of Sales Rep.	Collaborator		Web
  	Pricing Team	Full GBU	Collaborator		Remote

  
  

  The Server access is only required for Remote access. For Web access, no remote access is required.

• User creation

User naming should follow the rule below :

GBU - User role - Name

Example :

List of the GBU code is available here

The email of the user should also be registered in the External user name :

The available user roles for the GBU users are :

• Global Planner for Demand /S&OP Planners
• Collaborator for Sales Manager
• Viewer for users who just need view access

NB : Do not give "Administrator" to GBU users, they would be able to get connected during the import processes

Administrator and Super user are for SBS users for system maintenance

• User Group mailing

New users should also be added in the corresponding Google group :

$DynasysUsersDP

$DynasysUsersDP2

$DynasysUsersDP3

If users are Key Users (=Demand planners), they should be also added in the following Google group :

$DynasysDP-KeyUsers

$DynasysDP2-KeyUsers

$DynasysDP3-KeyUsers

• Switch user feature

This feature allows a user to switch to an other scope.

For example for a Sales Manager who is also a Global Key Account or a S&OP Planner who have different roles in the process.

1.SILICA 

Demand Planner AP / EU / NA / LA

• Create the user :

• Login : Windows ID

• Description : SI - DP / First and last Name

• Assign the following user groups : 

• dp - SILICA - EU (or AP, NA, LA)

• SILICA - GBU

Customer Service Rep. CSR 

• Create the user :

• Login : Windows ID

• Description : SI - CSR  / First and last Name

• Assign the user to following user groups:

• SILICA - GBU

• SILICA - Role CSR (for EU, AP, LA)

• SILICA - Role CSR NA ( for NA)

• Create the user Group :

• Duplicate an existing one, example : csr - ccartall

• Name : csr - LOGIN

• Assign to this user group the user created

• Delete any other existing assignments copied from duplicata

• Create condition : 

• Under table CSR

• Name : csr - LOGIN

• Type : Filter applied to record codes

• Selection mask : code of the CSR (Search in CSR table the name of the CSR you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

  >>> this step should be done during a release.

• Update the security of master tables: “ CSR”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

• • Repeat this step for all master tables which are parents of “CSR” table (the most important one is : Material:Shipto@DC table)

Sales Rep. SREP

• Create the user :

• Login : Windows ID

• Description : SI - SREP  / First and last Name

• Assign the user to following user groups:

• SILICA - GBU

• SILICA - Role Sales Rep (for EU, AP, LA)

• SILICA - Role Sales Rep NA ( for NA)

• Create the user Group :

• Duplicate an existing one, example : sr - oguillou

• Name : sr - LOGIN

• Assign to this user group the user created

• Delete any other existing assignments copied from duplicata

• Create condition : 

• Under table Sales Rep.

• Name : sr - LOGIN

• Type : Filter applied to record codes

• Selection mask : code of the SREP (Search in Sales Rep. table the name of the SREP you want to create, use his code in this field)

  • Add ^ at the beginning of the code

  • add $ at the end of the code

    >>> this step should be done during a release.

• Update the security of master tables: “ Sales Rep.”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

  • Repeat this step for all master tables which are parents of “Sales Rep.” table (the most important one is : Material:Shipto@DC table)

Global Shipto Key Account SHKA

• A user who is CSR or SREP can be also a SHKA (he will not be able to modify the SHKA scope)

• Create the user Group :

• Duplicate an existing one, example : SHKA - Bridegestone

• Name : SHKA - ShiptoKAName

• Assign the user to the user group created

• Delete any other existing assignments copied from duplicata

• Create condition : 

• Under table Shipto KA 

• Name : SHKA - ShiptoKACode

• Type : Filter applied to record codes

• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code

  • add $ at the end of the code

  >>> this step should be done during a release.

• Update the security of only master table “Material:Shipto@DC ” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

For Modification Condition put Modify None

2.PEROX

Perox - Demand Planner AP / EU

• Create the user :
• Login : Windows ID
• Description : PE - DP / First and last Name
• Assign the following user groups : 
• DP - PEROX - EU (or AP)
• PEROX - GBU
• PEROX - Role Account Manager

Perox - Demand Planner NA

• Create the user :
• Login : Windows ID
• Description : PE - Demand Planner / First and last Name
• Assign the following user groups : 
• DP - PEROX - NA
• PEROX - GBU

Perox - Account Manager

• Create the user :
• Login : Windows ID
• Description : PE - Account Manager  / First and last Name
• Assign the user to following user groups:
• PEROX - GBU
• PEROX - Role Account Manager (for EU and AP)
• PEROX - Role Account Manager NA ( for NA)
• Create the user Group :
• Duplicate an existing one, example : PE - am - AHONGSAT
• Name : PE - am - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Account Manager
• Name : PE - am - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the account manager (Search in Account manager table the name of the account manager you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

• Update the security of master tables: “Account Manager” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

Repeat this step for all master tables which are parents of “Account Manager” table (the most important one is : Material:Shipto@DC table)

Perox - Global Key Account Manager

• A user who is Account Manager can be also a GKAM of a specific zone 
• Create the user Group :
• Duplicate an existing one, example : GKAM - Ecolab - EU
• Name : GKAM - GBUShip-toGroupName - Zone
• Assign the user to the user group created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table GBU Ship-to Group 
• Name : GKAM - GBUShip-toGroupCode
• Type : Filter applied to record codes
• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

• Create condition : 
  • Condition GKAM - GBUShip-toGroupCode
  • AND
  • Condition Zone
• Under table Ship-to@BU 
• Name : GKAMxZONE - GBUShip-toGroupName Zone
• Type : Combined Condition 

>>> this step should be done during a release.

• Update the security of master tables: “Ship-to@BU” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before : GKAMxZONE - GBUShip-toGroupName Zone)
• Repeat this step for all master tables which are parents of “Ship-to@BU” table (the most important one is : Material:Shipto@DC table)

3.AROMA 

Demand Planner AP / EU / NA / LA

• Create the user :
• Login : Windows ID
• Description : PA - Demand Planner / First and last Name

• Assign the following user groups : 
• AROMA - Role Demand - Scope EU (or AP, NA, LA)
• AROMA - GBU

Sales Rep. SREP

• Create the user :
• Login : Windows ID
• Description : PA - SREP  / First and last Name
• Assign the user to following user groups:
• AROMA - GBU
• AROMA - Role Sales Rep
• Create the user Group :
• Duplicate an existing one, example : sr - smulas
• Name : sr - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Sales Rep.
• Name : sr - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the SREP (Search in Sales Rep. table the name of the SREP you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

Update the security of master tables: “ Sales Rep.”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “Sales Rep.” table (the most important one is : Material:Shipto@DC table)

Global Key Account Manager GKAM

• A user who is SREP can be also a GKAM
• Create the user Group :
• Duplicate an existing one, example : GKAM - GCBU219577
• Name : GKAM - GBUShip-toGroupCode
• Delete any other existing assignments copied from duplicata
• Assign the user to:
• the user group created
• AROMA - Role GKAM

• Create condition : 
• Under table GBU Ship-to Group 
• Name : GKAM - GBUShip-toGroupCode
• Type : Filter applied to record codes
• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

Update the security of master tables: “Material:Shipto@DC” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before : GKAM - GBUShip-toGroupCode)

• For Modification Condition put Modify None

4.SPECIAL CHEM

Sales Employee

• Create the user:
  • Name: Windows ID
  • Description : CH - DP / First & Last Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Employee

• Create the user Group :
  • Duplicate an existing one, example : CH – SE - DCANGIAN
  • Name : CH – SE - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Complete the Sales Employee ID table * :
  • Under table Sales Employee ID
  • Records > Lock Data
  • Add a line:
    • Code: Solvay address mail
    • Name: First & Last Name
    • Short name: Windows ID

• Create condition* :
  • Under table Sales Employee ID
  • Name: SM – SE - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Solvay address mail

*This step should be done during a release

• Linking the Sales Employee to the Sales Employee ID
  • Under table Sales Employee
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her email address in all the lines of the "Sales Employee ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC table” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

Sales Assistant

• Create the user:
  • Name: Windows ID
  • Description : CH - SA / First & Last Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Assistant

• Create the user Group :
  • Duplicate an existing one, example : CH – SA - BTONG
  • Name : CH – SA - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Complete the Sales Assistant ID table* :
  • Under table Sales Assistant ID
  • Records > Lock Data
  • Add a line:
    • Code: Windows ID
    • Name: First & Last Name

• Create condition* :
  • Under table Sales Assistant ID
  • Name: SA – CH - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Windows ID

*This step should be done during a release

• Linking the Sales Assistant to the Sales Assistant ID
  • Under table Sales Assistant
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her Windows ID in all the lines of the "Sales Assistant ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

Global Key Account Manager (GKAM)

A user who is SREP can be also a GKAM

• Create the user:
  • Name: Windows ID
  • Description : CH - SE / First & Last Name

• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Employee

• Create the user group:
  • Duplicate an existing one, example : CH - GKAM - TFAC
  • Name: CH - GKAM - Name of GKAM Dimension
  • Delete any other existing assignments copied from duplicata
  • Duplicate an existing one, example : CH – SE - DCANGIAN
  • Name : CH – SE - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Assign the user to:

• The user group created CH - GKAM - Name of GKAM Dimension
• The user group created CH - SE - Windows ID

==> PART 1 : Sales Employee 

• Complete the Sales Employee ID table * :
  • Under table Sales Employee ID
  • Records > Lock Data
  • Add a line:
    • Code: Solvay address mail
    • Name: First & Last Name
    • Short name: Windows ID

• Create condition* :
  • Under table Sales Employee ID
  • Name: SM – SE - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Solvay address mail

*This step should be done during a release

• Linking the Sales Employee to the Sales Employee ID
  • Under table Sales Employee
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her email address in all the lines of the "Sales Employee ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC table” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

==> Part 2 : GKAM

• Create condition* :
  
  • Under the table of GKAM Dimension example : Enterprise Customer Group, Enterprise Material Group …
  • Name: CH - GKAM - Name of GKAM Dimension
  • Condition type : Filter applied to record codes 
    • Update the security of master tables:
      
      • Right click > Security > Advanced security >
      • Go to user group line (created step before)
      • Put the condition (created before : CH - GKAM - Name of GKAM Dimension

*This step should be done during a release

Demand Planner

xxx

4.TECHNOLOGY SOLUTIONS

Sales Rep. SREP

• Create the user:
  • Name: Windows ID
  • Description : TS - SREP - Country code / Last & First Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Create the user Group :
  • Duplicate an existing one
  • Name : TS – SREP – Country Code / LAST & First Name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Under table Sales Employee ID
  • Name: TS - Country Code / LAST & First Name
  • Condition Type: Filter applied to record codes 
  • Selection mask : input the user's email address
  • Parent master table: Sales Employee ID

>>> This step should be done during a release... (Exclusive access needed!)

• Update the Sales Employee ID table, add the user's email address into the table and tick the related condition you just created in the previous step

• Update the security of master tables: “ Sales Employee”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)
• Repeat this step for all master tables which are parents of “Sales Employee” table (the most important one is : Material:Shipto@DC table)

RSD

xxx

PRICING TEAM

• Create the user :

• Login : Windows ID

• Description : TS - DP / First and last Name

• Assign the following user groups : 

• TS - Princing Team

DEMAND PLANNER

• Create the user :

• Login : Windows ID

• Description : TS - DP / First and last Name

• Assign the following user groups : 

• TS - DP- ...

PRODUCT MANAGER

5.NOVECARE

Sales Employee

• Create the user:

• Login: Windows ID

• Description: NOVECARE - SREP - Country Code / LAST and first name

• Assign the user to the following user groups:
  • NOVECARE - Sales rep (KG)
    
    

• Create the user group:

  • Create a new condition or duplicate an existing one, example: NOV - SREP - CR / SOLIS Ellis

  • Name: NOV - SREP - Country Code / LAST and first name

  • Assign to this user group the user created

  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 

Under table Sales Employee ID

• • Name: NOV - SREP - Country Code / LAST and first name
  • Type: Filter applied to record codes
  • Selection mask: User email address (Search in Sales Employee table the name of the Sales Employee you want to create, use the email address in the corresponding field)

>>> This step should be done during a release.

• Update the security of master tables: “Sales Employee ID”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “Sales Employee ID” table (the most important one is : Material:Shipto@DC table)

Customer Service Rep. CSR

• Create the user:

• Login: Windows ID

• Description: NOVECARE - CSR - LAST and first name

• Assign the user to the following user groups:
  • NOVECARE - CSR

• Create the user group:

  • Create a new condition or duplicate an existing one, example: NOV - CSR – GUIDA Faustine

  • Name: NOV - CSR - LAST and first name

  • Assign to this user group the user created

  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 
  • Under table CSR
  • Name: NOV - CSR - LAST and first name
  • Type: Filter applied to record codes
  • Selection mask: code of the CSR (Search in CSR table the name of the CSR you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables: “CSR  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “CSR table (the most important one is : Material:Shipto@DC table)

S&OP Planner

• Create the user:

• Login: Windows ID

• Description: NOVECARE - S&OP Manager - Country Code / First and last name

• Assign the user to following user groups:

  • NOVECARE - S&OP Planner

• Create the user Group:
  • Create a new condition or duplicate an existing one, example: NOV – S&OP Manager – MX / Alejandro Ramirez
  • Name: NOV - S&OP Manager - Country Code / First and last name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Add ^ at the beginning of the code 
  • Add $ at the end of the code
• Under table S&OP Planner
• Name: NOV - S&OP - Country Code / First and last name
• Type: Filter applied to record codes
• Selection mask: code of the S&OP Planner (Search in S&OP Planner table the name of the S&OP planner you want to create, use his code in this field)

>>> This step should be done during a release.

• Update the security of master tables: “S&OP Planner”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “S&OP Planner” table (the most important one is : Material:Shipto@DC table)

+ Link between S&OP Leader and S&OP Planner: Update the S&OP Planner table and assign the correct S&OP Leader to the correct S&OP Planner, depending on the zone.

S&OP Leader

• Create the user:
  • Login: Windows ID
  • Description: NOVECARE - S&OP Leader Mini Zone - Country Code / First and last name
  • Assign the user to following user groups:
    • NOVECARE - S&OP Planner

• Create the user Group:
  • Create a new condition or duplicate an existing one, example: NOV - S&OP Leader - EU / Julien GENA
  • Name: NOV - S&OP Leader - Mini Zone / First and last name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Under table S&OP Leader
  • Name: NOV - S&OP Leader - Mini Zone - First and last name
  • Type: Filter applied to record codes
  • Selection mask: code of the S&OP Leader (Search in S&OP Leader table the name of the S&OP planner you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables: “S&OP Leader”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “S&OP Leader” table (the most important one is : Material:Shipto@DC table)

Global Key Account Manager (GKAM) / Regional Key Account Manager (RKAM)

A user who is SREP can be also a GKAM 

• Create the user group:
  • Duplicate an existing one, example: NOV - GKAM L'OREAL
  • Name: GKAM - ShiptoKAName
  • Assign the user to the user group created
  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 

• Under table Shipto KA 

• Name: GKAM - ShiptoKACode

• Type: Filter applied to record codes

• Selection mask: code of the GBU Ship-to Group (ask the requester for the code)

  • Add ^ at the beginning of the code

  • Add $ at the end of the code

>>> This step should be done during a release.

• Create combined condition:
• Under table ShiptoKA
• Name: SHKA x Zone - ShiptoKAName Zone

exemple: SHKA x Zone - BERCEN NA

• Condition type: Combined condition
• Left operand: Add condition previously created
• Right operand: Zone Shipto - Zone

>>> This step should be done during a release.

• Update the security of the 3 master tables Material:Shipto/ Material:Shipto@BU / Material: Shipto@DC:

For each master table: 

• •  Right click > Security > Advanced security 
  • Go to user group line (created step before)
  • Put the condition 

>>> This step should be done during a release.

Regional Market Director (RMD) / Business Development Manager (BDM)

A user who is SREP or BDM can also be a RMD

• Create the user:
  • Login: Windows ID
  • Description: NOVECARE - BDM Market Name x Mini Zone First and last name
  • Assign the user to following user groups:
    • NOVECARE - RMD (KG)
    • NOVECARE - BDM (KG)

• Create the user Group:
  • Create a new condition or duplicate an existing one, example: NOV - RMD MARKET AGRO - NA
  • Name: NOV - RMD Market Market Name - Mini Zone
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 
  • Under table XXX
  • Name: XXX
  • Type: Filter applied to record codes
  • Selection mask: code of the XXX (Search in XXX table the name of the XXX you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables:
  • “Material:Shipto@DC” > Right click > Security > Advanced security 
  • Go to user group line (created step before)
  • Put the condition 

>>> This step should be done during a release.

6.SA&D

Account Manager

• Create the user :
• Login : Windows ID
• Description : SD - Account Manager  / First and last Name
• Assign the user to following user groups:
• SA&D - GBU
• SA&D - Role Account Manager (Except NA, LA)
• SA&D - Role Account Manager (LA)
• SA&D - Role Account Manager (NA)
• Create the user Group :
• Duplicate an existing one, example : SD - AM - DE04512
• Name : SD - AM - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Account Manager
• Name : SD - AM - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the account manager (Search in Account manager table the name of the account manager you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code