A) shared by Leo 

Historical

MonthIncotermsSource SystemMaterial CodeShip-To CodeGroup of ActivityCountry (Ship-To)Country (Sold-To)GBU RegionEnd Use: refers to a market to be used (related to ship to and product. it comes from invoice Qquery  from BW. Better from SF . it is related to the custumer via an extra table GBU Product FamilyEnterprise Segment= related to customer and product together. From BW transaction level. Market= hierarchy between end use, enterprise & GBU segment, market  → to discuss seperately GBU Customer SegmentGroup Customer SegmentProduct NameProduct CodeProduct Brand NameSales (€)Unit Price (€/KG)Volumes (KG)Last Invoice Price (€/KG)

Forecast

GBUMonthIncotermsSource SystemMaterial NameMaterial CodeShip-To NameShip-To CodeSold-To NameSold-To CodeSold-To GroupShipping PlantManufacturing Plant, there is another type of plant to be explored Group of ActivityCountry (Ship-To)Country (Sold-To)GBU RegionEnd UseGBU Product FamilyEnterprise SegmentMarketGBU Customer SegmentGroup Customer SegmentProduct NameProduct CodeProduct Brand NameFcst Sales [Est Act] (€)Fcst Volume [Est Act] (KG)Fcst Unit Price [Est Act] (€/KG)Last Invoice Price (€/KG)A) shared by leo
BW P&L
ICM/Sales Order
QV: QVSBS_BW_QRY_CPCOPA03_0001
BW P&L

Integrated Unit cost
QVSBS_QRY_MVCOPA06_0001
BW (Global Sales)

Order Book
QVSD_BW_QRY_MVSDSO41_SD004
BW (Global Sales) - Review

Budget & BFR
QV_BW_QRY_MVSDSO61_0001
Manufacturing Variable Costs
QV_BW_QRY_CPCOPC04_0001
Sales Forecast Revenue QV_BW_QRY_CPCOPC07_0001


a) Transparency dashboard



Type SourceTechnical name BW queryFrequency Transformations/rulesCommentsProduct dimension (yes/no)User stories
Actual/ForecastDimension created to identify easily the data type
Made in transparency dashboard






BDMto update








Company codeName of the legal entity








Consolidated









Document currencyCurrency under which the transaction (sales invoice, purchase invoice) is set

[0DOC_CURRCY] Sales currency QVSBS_BW_QRY_CPCOPA03_0001




GBU Product familyProduct level 3
BW"Default: [C_MATNR2] Material\Attributes\[C_FMPRD] Product Family Code Exceptions Soda Ash and Fibras [C_MATNR2__C_PRDHIER] Product Hier (LIP3) Aroma, Silica and Special Chem [C_GBR18__C_GBR19] GBR GBU Mat Group Peroxides: PF1: [C_MATPNT2__C_PRODPIF] Cheops PIF (Missing- not possible) WP1: [C_MATNR2] Material\Attributes\[C_LIP02] Product line 02 Novecare and Technology Solution: WP1: Default PF1:[C_MATNR2__C_PRDHIER] Product Hier (LIP3)"QV_BW_QRY_MVSDSO61_0001




H4/Prod L4Customize dimension using SpP product H4 and Others GBUs product line 4

[C_MATNR2] Material\Attributes\[C_LIP04] Product line 04 QVSBS_BW_QRY_CPCOPA03_0001




HPAMSpP Only


 QVSBS_BW_QRY_CPCOPA03_0001




IncotermsPart of the price. Precision of transfer reponsability between supplier and customer. Used at court in case of disputeTransaction

[C_INCOTRM] Incoterms_P


 QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_CPCOPC07_0001






Logistics Logistics Organizational Unit representing the place where either materials are produced or goods and services provided.

Identification of production and non production plants.

Use in CO - PF1:

Organizational Cost Centers standard hierarchy
Profit Centers standard hierarchy
Cost Object Hierarchy (first 2 levels in the structure)
Materials: To identify the ones relevant for costing and to be updated during the Project (Accounting / Costing views).
Material Ledger activation (customizing).

Use in CATS - PF1:

Physical “allocation” of the person.

PF1[C_PLANT] Plant QVSBS_BW_QRY_CPCOPA03_0001




Manufacturing plantLast plant in the product production process

"PF1: [0PROFIT_CTR__0MATL_GRP_1] Industrial Origin
WP1:[4CPCOPA03-MAP2_PRPLANT] Production Plant (Material Plant)"

WP1 : C_PLANT PF1: ORIGIN PLANT

 QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_CPCOPC04_0001






MaterialProduct + packaging

[C_MATNR2] Material


 QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_MVSDSO61_0001

QV_BW_QRY_CPCOPC04_0001

QV_BW_QRY_CPCOPC07_0001






Material CodeSAP-code used to describe the product








Mode of transportShipping Condition


QV_BW_QRY_CPCOPC07_0001




Packaging typeInformation on the packaging of the material

[C_MATNR2] Material\Attributes\[C_PACKAG] QVSBS_BW_QRY_CPCOPA03_0001




Plant typeThe plant type leads to a specific customizing in SAP.

In WP1, there are 5 plant types :

PROD = Production plant
NDIR = Direct Trading : shipment from third party suppliers to customer (Order Type TAS will be used for this type of plant)
NDEP = Warehouse : physical Solvay stock location to store purchased materials from Solvay or 1/3 party supplier or Solvay produced materials
NDC = Customer consignment warehouse: stock held at customer address (purchased or produced materials)
SSTT = Sub contracting









ProductMaterial group aggregation
Can be Commercial Product / Material Group / Product Group, depending on the GBU.


[C_MATNR2__C_PROD] Commercial Product / Material Group

[C_MATNR2__C_PROD] Comm. prd / Material

"[C_PROD] Comm. Prd/Material group if empty => [C_MATNR2__C_PROD] "

C_PROD



 QVSBS_BW_QRY_CPCOPA03_0001

QVSD_BW_QRY_MVSDSO41_SD004

QV_BW_QRY_CPCOPC04_0001

QV_BW_QRY_CPCOPC07_0001






Product codeSAP-code used to describe the product








Product hierarchyProduct LIP03

[C_MATNR2__C_PRDHIER] Product Hier (LIP03)

"[C_PRDHIER] Product Hier (LIP3) if empty => [C_MATNR2__CPRDHIER]"

0PROD_HIER

 QVSBS_BW_QRY_CPCOPA03_0001

QV_BW_QRY_CPCOPC04_0001

QV_BW_QRY_CPCOPC07_0001






Product lineProduct classification

C_MATNR2] Material\Attributes\[C_LIP02] Product line 02

QV_BW_QRY_CPCOPC04_0001

QV_BW_QRY_CPCOPC07_0001






Source systemERP in scope (PF1, WP1 or non ERP data)

[[0LOGSYS] Source System


 QVSBS_BW_QRY_CPCOPA03_0001

QVSD_BW_QRY_MVSDSO41_SD004

QV_BW_QRY_CPCOPC04_0001

QV_BW_QRY_CPCOPC07_0001






Enterprise Segment


GBR_Enterprise_segment_W QVSBS_BW_QRY_CPCOPA03_0001








Price optimization team for Novecare

Inputs from Salesforce, PIM and contract


Intro: We are feeding the Algorithm with transaction data from the pricing dashboard, but that input doesn't include all the information we need. There are some price drivers and some product characteristics that will come from Saleforce, PIM and the contract database. We will need support to extract that data from the source and feed it into the Algorithm.


We will need the following:


  1. Saleforce Integration: Stockholding strategy (Made to order vs Made to stock)


PO’s (Nestor) input:

“Stock Holding strategy is a parameter defined per material/shipping plant and it comes to salesforce via interface to SAP in a daily refresh. We also store it when we create a price (a quote line item).“


The name of the objects and their tables are: 

In Material/Shipping plant object - SLV48_Stock_Holding_Strategy__c 

You can explore it in salesforce with this simple query: 


select id, SLV48_Stock_Holding_Strategy__c from Manufacturing_Plant__c

where RecordTypeId ='01208000000sm7gAAA'


In Quote Line Item - SLV49_Stock_Holding_Strategy__c 

You can explore it in salesforce with this simple query: 


select id, SLV49_Stock_Holding_Strategy__c from SLV44_ONE_Quote_Line_Item__c 


  1. PIM data Integration: Help in the integration of product characteristics data from the PIM (system used to store product information at Novecare - Leo Baussand will provide the exact names of the fields needed, I think Leo spoke to Youness about this PIM data already, so he might be familiar already) - the owner of the PIM is Jeanchristophe Pham in case there are any technical questions.


Leo Baussand-ext: kindly paste the name of the fields that you identified in Jeanchristophe’s extract that we would like to feed into the algorithm


Any technical support you can contact chandan.p-ext@solvay.com 

Enhancements/feature request  you can reach out Jessica.Ternier@solvay.com (back up Luis.dias@solvay.com

Jean-Christophe Thuan - Jessica Ternier


BOM: