SAP BW/SF 

 A customer might not have any parent 

To investigate further to have one rule

SAP BW / File

QVSBS_BW_QRY_CPCOPA03_0001

To be confirmed by Ayoub and Franck

Identified with file 1zicl5VUcl1NyDLGZXQRDmQypY0-uwc4yUtuPRu1scxU . Group Mapping

By mapping with the GBU and C_SOLDID

If no match, then take

QVSBS_BW_QRY_CPCOPA03_0001 . C_SOLDID . C_CORPGR

For Ship-To, take

QVSBS_BW_QRY_CPCOPA03_0001 . C_SHIPID . TXTLG

If composed, take the name after "/"

table ACCOUNT:

Available in CORE and iCare 

QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_MVSDSO61_0001

QV_BW_QRY_CPCOPC07_0001

[C_SHIPID] Ship_to_party

Key_[C_SHIPID].[2C_SHIPID]

The attributes in the CORE in the table ACCOUNT 

Partner_Sub_type

Final customer that receives the product.  (it can be blank→ it is different than ship to mentioned above) 

It is linked to account reccording 

Identified with

QVSBS_BW_QRY_CPCOPA03_0001 . Sales_Employee__Sold_to__E_Mail_Address__Key_

Or

QVSBS_BW_QRY_CPCOPA03_0001 . Sales_Employee__Ship_to__E_Mail_Address__Key_

In CORE, Sales Rep (CSR Customer Service  Representative)  and account manger master data available in ACCOUNTTEAMMEMBER  → attributes: Account ID, USER, Team member role (coming from SAP).

One account can be managed by several GBUs so there is a one to many relation between account and CSR

In icare it is different. 

Master data of Sales rep and account manger are in SAP. The data flows daily basis to SF per GBU. This info are coming from sales area of the SAP side. Related to sales area in SAP. 

??When data integrated from SAP to SF, there are rules to make it at GBU level 

QVSBS_BW_QRY_CPCOPA03_0001 . C_SOLDID . TXTSH

Or

QVSBS_BW_QRY_CPCOPA03_0001 . C_SHIPID . TXTSH

QVSBS_BW_QRY_CPCOPA03_0001 . C_SOLDID . TXTLG

Or

QVSBS_BW_QRY_CPCOPA03_0001 . C_SHIPID . TXTLG

Country ship to: Country of the customer delivered

----------

Country sold to: Country of the sold-to company- Invoice party

QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_MVSDSO61_0001

QV_BW_QRY_CPCOPC07_0001

----------------

QV_BW_QRY_MVSDSO61_0001

Country (Key)_[C_SHIPID].[20COUNTRY]

[4CPCOPA03-SHIP_COUNTRY] Country of destination

[10COUNTRY] Ship-to party > Country (Name)

C_SHTCTRY

------------

Country (Name)_[C_SOLDID].[10COUNTRY]

"[0COUNTRY] Country if empty => [C_SHIPTID] Ship-to party\Attributes\[0COUNTRY] Country key"

QVSBS_BW_QRY_CPCOPA03_0001 . C_SOLDID . 0COUNTRY

Or

QVSBS_BW_QRY_CPCOPA03_0001 . C_SHIPID . 0COUNTRY

Naming unificationn has been defined in transparency dashboard (see the transformation column) 

From one GBU to another zone might be different. It has been unified 

available in SF 

What table?

Account . RCS_code_Account__c

To check→ in SAP it happens that there are two accounts for one customer. For example if customer change the VAT, a new account will be created. In SF it doesn't happen so that there is no one to one from SF to SAP. In such a case, the new account is replaced but all the changes in SAP are tracked an another attribute  (PRS_ID_history) .

Note: 

In general to track the changes in an attributes in SF,  ACCOUNTHISTORY is the table that include historical and changes of the records.  

Example, if a customer number change, the new one is in the main table and the old number is backed up in ACCOUNTHISTORY table. 

Account . SAP_Sold_To_Number__c

Or

QVSBS_BW_QRY_CPCOPA03_0001 . C_SOLDID

Or

QVSBS_BW_QRY_CPCOPA03_0001 . C_SHIPID

All the above codes are available in SF but the doubt/question is that if for a new customer, the corresponding data is available right away in the SF so that we won't have a gap when using SF as the source. It is also to check if data is available in both SF (icare and Core)

Currently in the transparency dash all the codes are from SF but it is better o explore if there is a better source. 

Account manager and sales rep are both are solvay employee. The data at the target application is used at CPC level. 

The info are available in all data sources but the challenge is that there are different values from one to another. 

It has been prioritized for Q4

It is only for iCare not for CORE

Refer to Sales rep ID comment

combination of sales area, division, and distribution channel defined for a GBU. 

Only in iCare  and should be empty for CORE

Franck comment: 

Three ways to get the data

• (Preferred solution) API 
• SF function to get the data
• (not preferred alternative) Googlesheet for mapping (only used for iCare)

1NVHMJOTRYA3tR7Pf6HCirAJb2ik7JCRD5b2CrLnSVuc

Note: it is used to get the market cluster (link with market cluster)

Using API for

Account . Team_Cluster__c

This concept is only available in iCare. it is a way in in SpP to associate an account to a team (Sales team?)

Corresponding concept in CORE might be BU (to check)

Notes:

-Team cluster refers to the sales team in Solvay that handles an account. It is a way to associate an account to a sales team in solvay. Each sales team handles a specific (market) like automotive. battery, etc.  One account might be purchasing from various teams. in that case, team cluster is the one with the biggest sale.  → that makes the Market cluster different from team cluster. 

COPA03

The Gsheet below is used for this field as well 

technical name: GBU Segm. (Sold-to)_[C_CUSTSAL__0CUST_GRP2]

Customer_Sales_Area_Customer_group_2__Name_

GBU customer segmentation shows what GBUs are related to an account. There is one GBU segmentation per account for a GBU 

It refers to Solvay group level of segmentation for customer. Depends on the service level a customer receives from Solvay, it can be classified as KA, or standard, etc. 

The same customer segmentation can be applied at GBU level (below) 

Bus_Rank__Corp_

Group Segm. (Corp) (Name)_[C_SOLDID].[1C_CUSTGRC]

Special rule:

strategic ley account at group level are enforced to be strategic account for all GBU 

child account are following the parent account for GBU and group segmentation both (there are exceptions that can be specified by users)