| Requirements | Description | Comment | Existing source in transparency dashboard | Technical name in transparency source (mainly BW)→ table name and attribute name | SF source (comments from Dina) | Delivery | Frequency update | Data Ocean Source Table Name | Target Model Entity | Attribute Name in Data Ocean |
|---|---|---|---|---|---|---|---|---|---|---|
| Market | COPA03 | [4CPCOPA03-TGB2_C_GBR4] GBR: Corporate Enduser (Ship-To)_W\Attributes\[C_GBR2] GBR End-Use (Market) | ||||||||
| End use | It is unique per combination of customer ship to and material | First priority for Leo | COPA03 | SF for spp SELECT End_Use__c,Material_Group__c,Sap_Code__c as Sold_to FROM End_Use__c for other GBUs it is coming from BW (COPA03) [4CPCOPA03-TGB2_C_GBR4] GBR: Corporate Enduser (Ship-To)_W Note: Market, Application, and Segment are the attributes of this table in COPA03 | A table in icare that holds end use for the combination of customer and product. End use is related with "market segment" in icare. (there is no market segment concept in CORE) It is not the case is CORE. In core there is a relationship between application, segment, end use, and market. However there is no info for users about the end use per product and customer combination. The table in CORE is SLV_MARKET_SEGMENT_C that holds the end use but there is no relation of the info in this table with product and customer. For market segmentation, there is a field type that can be market, segment, application and end use. If the user specifies the end use, the application should be specified for the end use. Accordingly for segment and subsequently market. There is a hierarchy with end use, application, market | |||||
| Application | End use, application, market and segment are related in SF | COPA03 | [4CPCOPA03-TGB2_C_GBR4] GBR: Corporate Enduser (Ship-To)_W\Attributes\[C_GBR1] GBR End-Use (Application) | |||||||
| Enterprise segment | No relation with other concepts | [C_GBR21__C_ENTSEG] | ||||||||
| Segment | End use, application, market and segment are related in SF | [4CPCOPA03-TGB2_C_GBR4] GBR: Corporate Enduser (Ship-To)_W\Attributes\[C_GBR3] GBR End-Use (Segment) | ||||||||
| 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. | The GBU customer segment is unique per combination of GBU and customer Taking the master data from SF if it is consistent it is good enough | COPA03 Get the data from the BW query use the mapping file below to clean the values of the field retrieved from COPA The Gsheet below is used for mapping Color coding to be considered (to discuss this later) | technical name: GBU Segm. (Sold-to)_[C_CUSTSAL__0CUST_GRP2] Customer_Sales_Area_Customer_group_2__Name_ | In CORE, the table name is GBU_CUSTOMER_SEGMENTATION GBU customer segmentation table shows what GBUs are related to an account. There is one GBU segmentation per account for a GBU Important note from Dina: GBU customer segmentation master data is in COPA07. The data in SF is being populated from BW. In case of any doubt of the records in SF, the reference is BW. | |||||
| Market cluster | Only spp | A table in salesforce linked to the end use where other fields can be used (only in icare) | SELECT Label as End_use, Market_Cluster__c, SPPSegment__c as Investor_Market_group, BDTeam__c as BDM FROM End_Use_Maping__mdt | |||||||
| BDM | Only spp | |||||||||
| Investor market group | Only spp |
Overview
Content Tools
Tasks