| Source | Technical name | BW query | |||
|---|---|---|---|---|---|
| Actual/Forecast | Dimension created to identify easily the data type | ||||
| BDM | to update | ||||
| Company code | Name of the legal entity | ||||
| Consolidated | |||||
| Document currency | Currency under which the transaction (sales invoice, purchase invoice) is set | [0DOC_CURRCY] Sales currency | QVSBS_BW_QRY_CPCOPA03_0001 | ||
| GBU Product family | Product level 3 | "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 L4 | Customize 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 | ||
| HPAM | SpP Only | QVSBS_BW_QRY_CPCOPA03_0001 | |||
| Incoterms | Part of the price. Precision of transfer reponsability between supplier and customer. Used at court in case of dispute | [C_INCOTRM] Incoterms_P | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_CPCOPC07_0001 | ||
| 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. | 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. | [C_PLANT] Plant | QVSBS_BW_QRY_CPCOPA03_0001 | ||
| Manufacturing plant | Last plant in the product production process | "PF1: [0PROFIT_CTR__0MATL_GRP_1] Industrial Origin WP1 : C_PLANT PF1: ORIGIN PLANT | QVSBS_BW_QRY_CPCOPA03_0001 QV_BW_QRY_CPCOPC04_0001 | ||
| Material | Product + 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 Code | SAP-code used to describe the product | ||||
| Mode of transport | Shipping Condition | QV_BW_QRY_CPCOPC07_0001 | |||
| Packaging type | Information on the packaging of the material | [C_MATNR2] Material\Attributes\[C_PACKAG] | QVSBS_BW_QRY_CPCOPA03_0001 | ||
| Plant type | The 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 | ||||
| Product | Material 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 code | SAP-code used to describe the product | ||||
| Product hierarchy | Product 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 line | Product classification | C_MATNR2] Material\Attributes\[C_LIP02] Product line 02 | QV_BW_QRY_CPCOPC04_0001 QV_BW_QRY_CPCOPC07_0001 | ||
| Source system | ERP 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:
- 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
- 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 )
- Contract database integration: We will also contact the contracts team to gather the information that we're missing (I will handle this and give you the details soon)
I have a meeting with the contract management team on Monday 22nd to clarify if we can use any of their data (for now we’re not sure we will be able to use any of it because they have already told me that their data is at Product sold to level, and we want it as material ship to level which is more granular).
Project Analyst - Contract management team (David Parian):
- Is a certain CPC (material and shipto in our case) contracted or not?
“Currently we can identify if a Sold-to x Product (H4 level) is under contract or not. I am not sure how well that translates to Ship-to x Material. If I am not mistaken, Material is on a more granular level than Product H4. Ship-to is also different from Sold-to with no 1:1 link between the two.”
- If there is a contract, the specific contract clauses (customer specific stock, formula pricing Y/N, Global vs. Local).
“We have two different "layers" in our database, a contract layer and a product layer.
On the contract layer we have different types of metadata that could be interesting from a AI prediction standpoint:
-Contract region(s) in scope
-Contract start/end date
-Contract formula Y/N
-Contract hardship Y/N
On the product layer:
- Estimated annual volume is present but it is not a mandatory field to fill in
- Product manufacturing site
- Maximum supply obligation
- Safety stock is present but it is not a mandatory field to fill in”