Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Question from prantasa on Feb 12 at 6:57 AM Hello,
We are using automatic finite scheduling with assembly orders. It generally works quite ok - user starts to create a sales order, SAP creates an assembly order, and due to configuration settings capacity check is automatically run. The user is presented a popup to show the results of capacity check, and if there is no available capacity on the selected dates the order will be rescheduled with finite scheduling. Then the production order end date is passed back to the sales order, which allows us to promise a specific delivery date for the customer.
However, there are sometimes cases when there are no available capacity within the planning period. These cases are usually due to some other incorrect orders which have reserved excessive capacity (in any case the reason does not matter - the problem occurs regardless of reason why there is no available capacity). If finite scheduling was not able to find any time slot with sufficient capacity then the popup shows the original date for the order and Capacity confirmed -checkbox is no checked => the order cannot be confirmed into the basic load.
The specific problem we have is that in these cases the production order should be rescheduled until the end of the planning period => we are using the finish date as the basis for availability promise to the customers. If there is no available capacity then the order should be scheduled to finish at the end of the planning period (say, e.g., three months). This would show to the sales person that there is some problem with capacity. We cannot rely on the sales person to notice one single missing checkbox... besides, they should not make the decision to overload the production plan.
So the question is: can I configure capacity levelling profiles in a way that finite scheduling would reschedule the order to the end of the planning period if there is no available capacity instead of leaving the original dates? Or are there other options to modify the system to behave in this way?
Quite specific question - I hope somebody has encountered this behaviour before and has found a solution. In any case I think that the SAP standard logic is not very well thought out in this case.
Regards,
- Pekka
| Reply to this email to post your response. __.____._ |   _.____.__ |
