Objectives and Scope

Table of Content

The purpose of this Section is to provide a step by step procedure for the User Transference between GBUs, in compliance with Solvay Information Security Policies.

This procedure applies to:

CORE CRM Salesforce.com IS solution
All CORE CRM end Users and their GBU User Responsible
IT users: both Solvay internal employees working for IS and external IT subcontractors

User GBU Transference Principles

This Operational Procedure follows the same Key principles as described in the CORE CRM User Access Management section.

User GBU Transference: Is when a Solvay employee with CORE CRM access is transferred from GBU A to GBU B. meaning, end contract with GBU A, and start new contract with GBU B, that might or might not require a transference Period.

Syensqo IS - Customer Support > SPP - User Maintenance > image2018-2-20 17:36:56.png

All Requests should be record in IS Ticketing System, Freshdesk.
All situations not described in this document shall be treated as exceptions and individually evaluated with IS CRM Build - Security team.

User GBU Transference Procedure
1.	Log in the SSP CRM
2.	Run this report Export Details Export Done Downloaded file	========================================= =========================================================================
3	Open xls file provided by HR	example May 2018
3.1	Column A : delete later Column B : keep Column C : delete later Column D : keep Column E : keep Column F : keep Column G : keep Column H : delete later Column I : keep Column J : delete later Column K : delete later Column L : Keep Column M : delete later Column N : Keep Column O : delete later Column P : Keep Column Q : Keep Column R : delete later Column S : delete later Column T : delete later Column U : delete later Column V : delete later	mark for deletion Header = Region mark for deletion Header = Country Header = Site Header = Site Name Header = Employee mark for deletion Header = Email mark for deletion mark for deletion Header = Position mark for deletion header = functional area mark for deletion header = Organizational Unit Header = Operational Manager mark for deletion mark for deletion mark for deletion mark for deletion mark for deletion
3.2	Delete useless columns ("delete later" in previous step)
3.3	Save data in a file
4	Fields Mapping
4.1	Compare field by field SFDC report (Point 2) and HR Database (Point 3.3)	common field : Header = Email (HR extract) and Email (SFDC report)
5	Identify the differences
6	Update SFDC fields (Master data := HR extract)
7	mirror these updates on Role, Profile, territories