| 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 | Naveen Comment/questions |
|---|---|---|---|---|---|---|---|
| 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. | |||||
| Material (name & code) | Material is a product packaged. It provides the lowest granularity level. One product can be packaged differently | Currently is used in COPA03 but to explore the right source | COPA03 C_MATNR2 | Material Name: Medium name → C_MATNR2 . TXTMD Material code→ C_MATNR2 . (technical name?) | |||
Material group/Product (both code & name) | Non packaged material | 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. Architect to decide how to design in data lake. ------ Suggested for data lake design to create 3 fields: Material Group for SP => C_MATNR2. [C_MAT_GRP] Material_Group Material group other GBUs => C_MATNR2. [C_PROD] Commercial product / Material Group 2- Material group: Material Group for SP => C_MATNR2. [C_MAT_GRP] Material_Group
| COPA03 | C_MATNR2. [C_MAT_GRP] Material_Group C_MATNR2. [C_PROD] Commercial product / Material Group | Merge of the two attributes in COPA03 in one field in the transparency dashboard Material Group for SP => C_MATNR2. [C_MAT_GRP] Material_Group Material group other GBUs => C_MATNR2. [C_PROD] Commercial product / Material Group | ||
| Product H4 | In the transparency dashboard, H4 and L4 has been merged in one field. H4 is for SpP and L4 for other GBUs. In various source tables, product/material are available in various hierarchies. We need to think how to model in the data lake to be manipulated/distinguished easily for various applications. Suggestion is to make hierarchy an attribute of the product in the target model design (no need to build a hierarchy in the data lake). For each hierarchy consider to have one attribute in the product dimension | COPA03 Gsheet 1qRE12ZhXjZI9Aq85CSeMDs2QuKA2NBvHngyzZ7qPRHs | The mapping file below is 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 | SF (ICARE) Product2 . Business_Unit__c | Product2 . Business_Unit__c | ||||
| GBU product family | One product (or material) belongs to a product family per GBU. | Currently in the transparency dashboard there are various rules based on the GBUs to populate this field. Using COPA03 for this field, the data has been populated at sales level where both product code and GBU are available to return the GBU product family. The challenge is that, there is one product/material sold by more than one GBU that might be given various GBU product family from one GBU to another . It makes it difficult to keep the GBU product family as an attribute of product dimension in the target model to be designed. Aligning between all the GBUs might be considered | COPA03 | If GBU = SP then Mapping based on PRODUCT_KEY (from icare) mapping is : input Product2 . Material_Group__c output Product2 . Family if either GBU= CS or TS AND SOURCE_SYSTEM_KEY= PF1_020 Prod_line3___P_hier [C_MATNR2__C_PRDHIER] Product Hier (LIP03) 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) | SF (iCare) Gsheet 1qRE12ZhXjZI9Aq85CSeMDs2QuKA2NBvHngyzZ7qPRHs | 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 | COPA03 | |||||
| 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_MATNR2] Material\Attributes\[C_LIP04] Product line 04 (not only to bring L4 but all layers L0,L1,..) | ||||
| GBU material group | To be decide later to add this field or not (Same as GBU product family) | ||||||
| Product line E2E | It is an attribute of material-> C_MATNR2 | [0CRM_PROD] Product Line (E2E) [0APO_PROD] Arche Type | Name in BW: Product Line (E2E) It is filtered by Arche_Type_Key<>'#' OR Product_Line__E2E__Key<>'#' (#means not assigned) | ||||
| Packaging type | It is an attribute of material-> C_MATNR2 | COPA03 | Material_Packaging_type__Medium_Name_ Found two attributes in C_MATNR2→ To ask Franck an Ayoub which one is correct [C_PACKAG] Packaging type [C_MATGR2] Packaging type | ||||
| Product hierarchy PIF | define? (somebody from logistic) | COPA03 | [0PROFIT_CTR__0PROD_HIER] 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 | [QVSBS_BW_QRY_CPCOPA03_0001] QV - BW P&L & Integrated Margin Query (CAR3) | [C_MATNR2]. [0UNIT_DIM] Unit | ||||
| Product brand | Only available in Leo (naming of the field should be discussed) | [QVSBS_BW_QRY_CPCOPA03_0001] QV - BW P&L & Integrated Margin Query (CAR3) | [4CPCOPA03-TGB2_C_GBR19] GBR: GBU Material Group (Ship-to) |
Overview
Content Tools
Tasks