Version Control

1. General overview

The Account Team Member (ATM) custom object has been created to manage Sales Representative (Sales Rep) and Customer Service Representative (CSR) coming from SAP.
But as we're receiving those information from SAP per Account and Sales view, it has been decided to also used it for the GBU Segmentation Pull and Push interfaces.

Each time, someone does an update on an Account in SAP, the system sends to Core CRM, the list of the sales views of this Account and for each of them, indicates the corresponding Sales Rep and CSR.
All those information are stored in the the ATM object, waiting for the batch running once a night which will update the Account Team Member object, the standard one.

3. The batch

4. Fields List

5. What to do when.....

5.1 A Sales Rep is replacing another one by taking his code

5.2 A User if moving from 1 GBU to another one

6. Useful links

Mapping CRM - WM - SAP (Tab: CG Update Core => PRS)

System data Flow CRM - Dataiku - Mappy - SAP (slides) + Mappy queries in Dataiku existing flows (text doc)

Accounts' Interfaces with SAP

WebMethods FSD

Corporate Group links Management

Mappy - Novecare Sales rep. usage Guide

The best way to get IT support is to use the new Service One Platform.