- 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”
Comment from Melissa:
I just had a meeting with David and Sarah to have an initial discussion on merging the contract database and the pricing dashboard.
The key information that users will want is "Contracted" (Y/N) and "Contract ID"
Today this information is available at the sold-to granularity and comes from CRM.
I think this would be great to incorporate this info in the customer master data as adding it directly to the dashboard will result in the same issue we see in aligning customer dimensions.
This is a topic for 2024 though so low prio but wanted to make sure we don't miss this in scoping out the data structure as we just discussed.