Version Control

1. General overview

The Account Team Member (ATM) custom object has been created to manage Sales Representatives (Sales Rep) and Customer Service Representatives (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

There is a daily process running at 1AM CET, that adds or removes the account team member in SFDC.

4. Fields List

The fields to populate in the Account Team Member record are: User (lookup), Status (To insert, To delete).

5. What to do when.....

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

On WP1, the Sales Rep is identified with a code = the sales group. One of the parameter of this code is the email address of the Sales Rep.
When a new Sales Rep replaces an old one and take the ownership of all his portfolio, on SAP side, they "just" replace the email address of the previous Sales Rep by the new one.
The problem is that when doing that, the process which follows the changes done on an Account doesn't detect that something has changed as on the Account we still have the same code.

In such a situation, we need to "force" the send of the impacted accounts in order for CRM to get the new relation Account - new email address. This is generally done with the transaction BD12 in SAP.

5.2 A User if moving from 1 GBU to another one

6. Useful links

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

Accounts' Interfaces with SAP

WebMethods FSD

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