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

Compare with Current View Page History

« Previous Version 4 Next »


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



1.Special Chem 







  • No labels