on 01-30-2013 6:54 PM
Hello Everybody
How can i create a scenario in the SNP 1 tab of Prod/Locn Master to tell the Deployment Optimizer to 1st consider the Sales orders & then the Forecast.
Regards
Rachel
Hi Rachel,
If your business requirement is to treat customer requirements (i.e. sales orders) with higher priority than the forecast, you can simply maintain the deployment optimizier profile and assign priority 1 to customer requirement, 2 to corrected demand forecast, 3 to demand forecast, and 4 to safety stock. This will influence the optimizer solve to treat the demands based on their types and specified priorities. It's more or less a static assignment of priorities.
However, your requirement is to assign (temporal) priorities dynamically, then you need to maintain the penalty cost groups, quantity profiles, etc. You can also have categorize your priorities based on customer using consumption groups. Pl check the following thread for details.
http://scn.sap.com/thread/3165395
Thanks,
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rajesh- Thanks for the info. I will try to configure this scenario.
However Can you tell me, how can i test this scenario:
In my mind: I have a Product at the DC & the Plant location, with tlanes & other MD in place.
Sales orders created n CIFed across to the APO system, Forecast release has happened - shall i go ahead n run the SNP heuristics & then the Deployment- If yes then how will i know that the system has given the priority to the Sales orders over the Forecast?
Hi Rachel,
Pl consider the following scenario.
Assumption:
Context:
You have a sales order for a product@DC1 for 800 CS with required delivery date as 2/15/2013 and a forecast for the same product@DC2 for 800 CS with required date as 2/15/2013. If you execute SNP network heuristic it will create distribution demand at the plant for 1600 CS on 2/14/2013 and receipt element (with in-house production, a planned order) will be created on 2/14/2013.
With this context, consider reducing the planned order (receipt element) quantity to 1000 CS.
Expected Result:
Since there is limited supply, the deployment optimizer needs to allocate 800CS to sales order @ DC1 first and remaining 200CS@DC2 to the forecast order.
Thanks,
Rajesh
Rachel,
Since costs are not considered, the 'automatic cost generation' flag should not be selected. Then, the property 'Strict Prioritization' needs to be selected (as you shown in the screenshot). With respect to safety stock, you can choose it to be treated as customer demand or forecast demand. The other parameters are better to leave with defaults for a simple proof of concept.
Thanks,
Rajesh
Hi Rachel,
SNP (heuristics or optimizer) does not create fixed pegging relationships like CTM. However, you can have dynamic pegging relationships that can be seen in the product view (similar to CTM).
The test scenario given in the earlier post might be a good test along with checking pegging structures (high light the generated planned order in elements tab and click the context button to see pegging structures to know how the planned order quantity distributed to sales order and forecast).
Thanks,
Rajesh
User | Count |
---|---|
12 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.