| Target (Transparency) data model | Requirements | Descripting | Comment | Existing transparency source (Query in BW, table in SF or AP) | Technical name in the transparency source (BW, SAP, SF,..) | Transformations for transparency dashboard | SF source | SAP source | Comments |
|---|---|---|---|---|---|---|---|---|---|
| Product | material ID (target model) | Generated by Datalake by referring to C_MATNR2 Material is a product packaged. It provides the lowest granularity level. One product can be packaged differently that is identified with different material ID Important note: In various source tables, product/material are available in various hierarchy. To think how to model in data lake to be manipulated/distinguished easily for various applications. | C_MATNR2 C_MATCLS | ||||||
| Material name | Medium name | C_MATNR2 . TXTMD | |||||||
| Material code | It is finished product/material | To check the exact attribute technical name Currently is used in COPA03 but to explore the right source | Master data in BW COPA03 | C_MATNR2 | |||||
Material group/Product (both code & name) | Non packaged material | Depend on the sources such as PF1 and WP1 there are two attributes in the BW query which are not aligned There are two attributes in COPA03 that are merged in one field in the transparency dashboard. One refers to SpP and the other refers to other GBUs. To decide later how to design in data lake. ------ Currently it is only item 1 in transparency which is the merge of 2 and 3 Suggested for data lake design I would create 3 fields : Commercialized Product : SP => field Commercialed Product Other GBU => field Commercialed Product Material Group : SP => field Material . Material_Group Other GBU => field Commercialized Product 2- Material group (attribute of material) | C_MATNR2 C_PROD | ||||||
| Product H4 | in the dashboard H4 and L4 is merged. H4 is for SpP and L4 for other GBUs. To decide if it is two separate field in data lake. Somebody from SAP TO EXPLAIN HIRARCHIES There is a hierarchy in BW Suggested to be an attribute of the product (no need to build a hirarchy in the data lake) Suggested to have different field in the data lake | Only used for SPP 1qRE12ZhXjZI9Aq85CSeMDs2QuKA2NBvHngyzZ7qPRHs Using material group as an input to map, the output H4 | |||||||
| Business line | In transparency dashboard: It is coming from icare (it is only for SpP). there is no corresponding concept in CORE → it will be empty | Product2 . Business_Unit__c | Product2 . Business_Unit__c | ||||||
| GBU product family | Depending on GBU ( to be checked if there is one product for two GBU ) To be decide later to add this field or not Combination of product and GBU has one GBU product family | BW COPA 3 | If GBU = SP then Mapping based on PRODUCT_KEY (Note: icare is the source of the mapping) mapping is : input Product2 . Material_Group__c output Product2 . Family if either GBU CS or TS AND SOURCE_SYSTEM_KEY= PF1_020 if Prod_line3___P_hier Else Else if GBU is PA GBR__GBU_Material__Group__Ship_to_ Else Material_Product_Family_Code__Medium_Name_i | if GBU = SP then Mapping based on PRODUCT_KEY if either GBU CS or TS AND SOURCE_SYSTEM_KEY= PF1_020 Else if Prod_line3___P_hier Else if GBU is PA GBR__GBU_Material__Group__Ship_to_ Else Material_Product_Family_Code__Medium_Name_i | |||||
| HPAM | Product H4 and HPAM are both linked via material group using googlesheet made by transparency team | This info is not available in BW (H4 is available in iCare but HPAM is not available to the analyst knowledge) | 1qRE12ZhXjZI9Aq85CSeMDs2QuKA2NBvHngyzZ7qPRHs mapping only applies spp Using material group as an input to map, the output HPAM Exact same mapping product H4 | ||||||
| Product manager | to be asked later | ||||||||
| Product birth | it refers to the first time that the product has been produced | SF data table (to confirm icar or core or both) SF CORE CRM To ask from Gillm
| Calculation performed in transparency based on the year→ Franck to provide |
| |||||
| Product Line (0 to X) | Consider to bring all layers Hierarchy in SAP ERP (to check) | [C_MATNR2] Material\Attributes\[C_LIP04] Product line 04 C_LIP04 it refers to L4 , it suggests that there are L1, 2,.. | |||||||
| GBU material group | To be decide later to add this field or not (Same as GBU product family) | ||||||||
| Product line E2E | BW master data table for material attributes of C_MATNR2 It is an attribute of material | Name in BW: Product Line (E2E) It is filtered by Arche_Type_Key<>'#' OR Product_Line__E2E__Key<>'#' (#means not assigned) | Product_Line__E2E_ | ||||||
| Packaging type | It is an attribute of material | COPA03 | Material_Packaging_type__Medium_Name_ | ||||||
| Product hierarchy PIF | define? (somebody from logistic) | COPA03 | Product_Hierarchy_PIF_P | ||||||
| Product hierarchy | define? (somebody from logistic) It is an attribute of the Product L3 (to check in BW) | COPA03 | Prod_line3___P_hier_Key | ||||||
| Unite conversion rate | The current requirements in transparency dashboard is only to converting into VKG. Ongoing discussion in the requirements (to be discussed later) | P&L (BW or SF to be checked) | |||||||
| Unit | It is the attribute of the material | BW master data | |||||||
| Product brand | Only available in Leo (naming of the field should be discussed) | GBR__GBU_Material__Group__Ship_to_ |
Overview
Content Tools
Tasks