on 11-04-2013 5:48 PM
Hi,
We have a requirement to propagate the priority from finished good planned orders to semi-finished good orders. Can sombedy please explain how heuristic SAP_PP_012 can be used for this purpose? Is it executed as a heuristic run step or should it be called from an MRP heuristic like SAP_MRP_001? We are in a make-to-stock environment.
Any suggestion is highly appreciated!
Regards,
Peter
Dear Peter,
since you have to propagate the priority from Sales Orders down to Manufacturing / Procurement Orders; you have to execute SAP_PP_012 from a service heuristic that triggers SAP_PP012 in order of Low Level Code.
This service heu is /SAPAPO/HEUR_MRP_PLANNING that launches Other Heu = SAP_PP_012
Best Regards,
Gaimpiero
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
I am sure you must have read the theory behind this heuristic. Read the info in help.sap or in the SPRO.
to use it in system, first your demand should be prioritized
e.g.
1. SO's with priorities.
2. Product masters in various plants with priority (SNP2 tab page) e.g. FG product in 100 plant is required urgent (priority) than same product at location 200. 100 being location serving critical customer... etc.
Once you have these priorities and due to any case the supply is constrain/change in planning.. then you would like to prioritize the receipt based on the demand. you can use this Heuristic.
what it does already mentioned in the documentations (pasting below)
"
Use
Changing or creating receipts or requirements automatically leads to th
system carrying out dynamic pegging, which enables it to reassign the
receipts to the requirements. After this, receipt and requirement
elements with different order priorities can be linked via a pegging
relationship.
With this algorithm (function module /SAPAPO/HEU_PRIO_CHANGE) you can
adjust the priorities of receipt elements to suit the priorities of the
assigned requirements elements.
Procedure
For every receipt element the algorithm determines the requirements
elements to which the receipt element is assigned via a pegging
relationship. The algorithm then determines the highest order priority
(the lowest numerical priority value) of the assigned requirements
elements and assigns this order priority to the receipt element.
Parameter in location master that the system does not take into account
Planning time fence."
Hope this help.
Thanks
Pravin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Peter,
In general receipts & requirement have a dynamic pegging relation. With this algorithm we can adjust the priorities of supplies to suit the priorities of demand.
For every receipt element the algorithm determines the requirements elements to which the receipt element is assigned via a pegging relationship. The algorithm then determines the highest order priority (the lowest numerical priority value) of the assigned requirements elements and assigns this order priority to the receipt element.
Run it as a heuristic step.
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
4 | |
3 | |
2 | |
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.