Thanks Rohit,
This is very insightful. So I am deriving my CDP at CDP@PERPRODCUSTSPCODE level then aggregating it to the CDP@PERPRODCUST level. This handles my demand.
For supply planning, how do I convert the CDP@PERPRODCUST level when my CRATIO is defined at PERPRODCUSTLOC level and not at PERPRODCUSTSPCODELOC.
Do I follow the same approach as I did for Demand i.e. enter a calculation logic: DEPENDENTCUSTOMERDEMAND@PERPRODCUSTSPCODELOC = CRATIO@PERPRODCUSTSPCODELOC * CDP@PERPRODCUSTSPCODE
then DEPENDENTCUSTOMERDEMAND@PERPRODCUSTLOC = SUM ( DEPENDENTCUSTOMERDEMAND@PERPRODCUSTSPCODELOC)
Is it mandatory to define CRATIO@PERPRODCUSTLOC level only or can I do it at CRATIO@PERPRODCUSTSPCODELOC. As the Supply Planning algorithm can automatically compute my dependent customer demand , location demand etc. (using the SCM operators) , will this not create a conflict. How do I perform my supply planning considering the PROD-SPCODE combination.
Appreciate your thoughts in this regard.
Thanks,
Alok