Stories already created:
Pending Questions:
- Are Products in Core always exclusively GBU specific? ie, the quoting tool being developed will only use Products where GBU = Novecare? Yes
- Are the Novecare GBU products used by any other GBU? No
- Is the Active/Inactive value of Products currently being used? Yes
- What is the "Generic Product" checkbox supposed to represent?
- Used to allow linking Opps to Products that do not really represent a "sellable" product - for interim stages of the Quoting/Selling process
- Exclude these Generic Products from the Quoting Process...
- Are Level lookups filtered by Level? No
- Are Level lookups filtered by GBU (only a GBU level 4 can be parent of a GBU level 5) No
Draft Data Model
Product
What Products need to be "quotable" - Level 5 only
Data Issues:
There are currently 15 554 Novecare Level 5 Active Products in Core Production environment. According to Julien, it should be around 3500 Products- data cleanup required and confirmation of SAP integration to check why SF has almost 5X more Active Products in this GBU than it should.
Product Name - as is
Product Owner
“Product Manager” - new lookup to User object required
Manufacturing Plant - MFP-{00000000}
Confirm that Utilities records in Core where Type = Plant and Involved GBU includes Novecare - correspond to the needed Solvay Manufacturing Plants for Novecare
- what specific data from the Manufacturing Plant is required for the purposes of calculating Quote prices?
- Country / Region
Duplicate Rule required to prevent same Level 5 Product of being linked twice to the same Utility (Plant)
Shipping Plant
ie, Warehouses - this is only relevant to calculate the Logistics and Duties variable Costs
what are these? does this mean that the Manufacturing Plant can be different than the Shipping Plant for a specific customer Order, and as such affecting the prices (which would in turn need to be reflected in the Quote sent to the Customer via SF?)
- what specific data from the Shipping Plant is required for the purposes of calculating Quote prices?
Price floor
- Defined on a per Product/Plant basis (same product coming from 2 different plants can have 2 different values on Price Floor)
- Currency per UOM (EUR/KG)
- Price Floor is a fixed value that is calculated based on:
- Product Level 5 + Manufacturing Plant
- only depends on Product - no relation to Market or Region nor Logistics and Duties
Price Floor will be inputted in SF directly per Product Level 5 combination with Manufacturing Plant
Variable Manufacturing Costs
- Will be captured in Manufacturing Plant custom junction object
- Format = Value + Currency + Product UOM
- One number field to capture Value
- Currency will be standard field
- Product UOM will be a formula field retrieving UOM from Product in Manufacturing Plant object
Order Fulfillment (MTO/MTS)
Picklist field with values:
- Pending Julien input on values
Product Levels 1/2/3
Already existent in the Product object
Product Status
Defined by Active TRUE/FALSE checkbox on Product object
Potential to implement later something similar to the Product Availability of iCare.
Product Code
Already exists in Product
MDG Code
Already exists in Product
Customer
Ship To - how will this affect pricing in Quotes?
Incoterms - how will this affect pricing in Quotes?
Region
As a Global picklist value set
Price Policy Versus Price Floor
Pricing Policy - computation that starts from Margin Policy (captured at Product Level 4 - varies according to Region, Market and Product); Marketing Directors will be maintaining the Margin Policy
- plus Variable Manufacturing Costs (depends only on Product)
- plus Duties and Logistics Costs (depends on Customer location and Incoterms)
Price Floor
- it is a fixed value that is calculated based on:
- Product Level 5 + Manufacturing Plant
- only depends on Product - no relation to Market or Region nor Logistics and Duties
Price Floor will be inputted in SF directly per Product Level 5
Minimum Order Value
currency field (same as the Currency standard field) - pending further details from Julien - depends on Customer segment - does not need to be captured on RMP
Region and Market Pricing - RMP-{00000000}
Product is meant to be Public Read Only - sharing rules TBD later
Formula field for RMP Is Active? - If TODAY > Valid From and < Valid To
Questions:
Minimum Data requirements:
Will all Products always have Pricing for all 4 Regions (APAC/EMEA/NAM/LAM)? No
Will all Products always have the 6 Markets (Agro/Coatings/HPC/IPS/Amines/Not Assigned)? No
Limits on data:
A Level 5 cannot gave 2 RMPs for same combination of Region and Market (ie, 2 RMPs for APAC/Agro)? Duplicate Rule required
- Currency - standard field
- Lead Time (days) - Number - curve ball by Julien on
- lead times at Novecare are Product Level 4 x Plant - options presented by Julien:
1. Load max lead time across plants at PL 4
2. Load lead times in Junction object (PL5 x plant)
3. Create new junction object PL4 x Plant
- lead times at Novecare are Product Level 4 x Plant - options presented by Julien:
- Valid From
- Valid To
Validation Rules Required
- Valid To Date cannot be < Valid From
- Valid From cannot be in the past on Creation only
- Valid To cannot be more than 5 years from Today - both on creation and Edit
Volume Brackets - VBR-{00000000}
- Region and Market Pricing (MD)
- From (Volume) - number (16,2)
- To (Volume) - number (16,2)
- Margin Policy value - number
- formula field to show as Margin Policy (RMP.Currency + Margin Policy Value + RMP.Product.Unit of Measure)
- RMD Approval % - Percent number
- Marketing Director Approval % - Percent number
Questions:
Prevent overlaps on From/To VBRs under the same RMP.
Never allow any VBR to be smaller than 0,01