Customer related attribute requirements
| Target model dimension | Requirements | Description | Comment | Source in transparency | Technical name in transparency | SF source | Comment about SF |
|---|---|---|---|---|---|---|---|
| Customer | Customer ID | In SF known as account. An account can be sold-to or ship-to | |||||
| Customer | Parent ID | =Sold to ID | |||||
| Customer | Ship to ID | SAP code for customer to whom Solvay is shipping the products | 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 | There is no relation between the two in SF | |
| Customer | Sold to group | Only available in Leo's sheet | |||||
| Customer | Sold to ID | SAP code for customer to whom Solvay is selling the products | |||||
| Customer | Ship to KA ID | ||||||
| Customer | Final consignee ID | Only SpP related. | |||||
| Customer | Sales rep ID | In CORE, Sales Rep (CRS Customer Service Representative) and account manger master data available in ACCOUNT_TEAM_MEMBER → 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 CRS. In icare it is different. Related to sales area in SAP. | |||||
| Sales rep | Sales rep name | ||||||
| Sales rep | Sales rep email | ||||||
| Customer | Customer Short name | ||||||
| Customer | Customer Long name | ||||||
| Customer | Country | 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" | |||
| Customer | Zone | ||||||
| Customer | PRS code | In CORE, there is PRS=PF1 (PRS ID) , RCS = WP1 (RCS ID) . other ERP ID . Available in ACCOUNT table. | To avoid duplicate account, in SAP it happens that there are two accounts for one customer. In SF it doesn't happen so that there is no one to one from SF to SAP. (PRS ID history attribute handles old ones) | ||||
| Customer | RCS code | Refer to RCS code comment | |||||
| Customer | SAP code | Refer to RCS code comment | |||||
| Customer | SF code | ||||||
| Customer | Account manager | Refer to Sales rep ID comment | |||||
| Customer | Team cluster | 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) | |||||
| Market | GBU customer segment | A customer receiving different service levels could be classified as KA for one GBU and Standard for other. Exceptions: GSKA- they remain GSKA for all GBUs. | In CORE, the table name is GBU_CUSTOMER_SEGMENTATION . | GBU customer segmentation shows what GBUs are related to an account. | |||
| Customer ? | Group customer segment | 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) |