on 06-09-2015 8:28 PM
Hi,
I have a situation where some planned orders that are firmed & within our planning time fence are being rescheduled by MRP.
That reschedule is done in Forward Scheduling, with a schedule start time exactly at the time MRP was ran.
For example, on our last MRP Run at 13:00:00 today:
I am currently not able to reproduce at all by myself, I'm not sure what the initial state of the planned order is when this happens.
When I try to reproduce, the best I get is a Forward Scheduling on 2015-06-09 at 00:00:00 ( so current day, but time in the past).
Here is the result I have on my test on a planned order that was confirmed on 2015-08-08.
The MFBF confirmation creates forward scheduling, but basic dates didn't move.
After MRP Run on 2015-06-09 at 15:25:00.
Any ideas what is causing the difference ?
Hi Experts,
Here is my current status on the issue of firm planned orders being rescheduled and basic dates being adjusted even though my OPU5 settings say otherwise. This happens on partially confirmed (reduced) planned orders in Repetitive Manufacturing.
Now I'm guessing this is all standard and normal way of processing dates in the past for MRP. However, my requirement was for the basic dates to stay to their initial positions in all case to simplify the follow up of the plan. It seems that I need to plan without production dates (MF50 with basic dates in the selection screen settings).
Anyone has an opinion on my conlcusions ? Other ideas ?
Thanks for all your help,
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Thanks all for your comments.
With the help of a colleague, we were able to find the pattern.
This brings me to 2 questions:
Thanks all !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, in my current testing, I'm still not happy with how MRP deals with my basic dates.
I'm in a particular situation where my routing is always 24h in scheduling no matter what the quantity is. This means that when we do a MFBF confirmation, the scheduled dates are changed automatically with the forward scheduling.
Please see this Thread on the subject :
My goal remains for basic dates to stay to there initial state even after a partial confirmation. However, I can't make it work. I've changed my planned order scheduling parameters to this:
Still MRP will change my basic dates in some cases.
I have 2 different behaviors on planned orders that are partially confirmed based on the field Sched.by prod.dates (PLAF-PRSCH).
Planned Order 1 - Does not have a value in PLAF-PRSCH.
Before MRP:
After MRP:
Planed Order 2 - Has value "X" in PLAF-PRSCH (because it was changed in MF50 with setting Production Dates).
Before MRP:
After MRP:
So when field PLAF-PRSCH is populated and the finish date/time is in the past, MRP triggers forward scheduling from the time it is run. And it adjust my Basic Dates even though my configuration is set to not adjust them !
If the field PLAF-PRSCH is empty, the MRP planning seems to use the basic dates to plan, I'm pretty sure the reason why they don't change is simply because my scheduling parameters allow for 1 day in the past and the planned order is schedule as far back in the past i can.
All of this on 2 firm planned orders.
My goal is really for basic dates to stop moving.
Thanks.
Hi Marc,
If you work with Re-explode BOM, check in t.code OMIW what is the parameter for explosion date?
I would change the planning mode to 1 - adapt.
In your first post you have mentioned Forward Scheduling. In this case why in OPU5 is backward?
Also check at Plant level the parameters for Re-scheduling (tolerance value forward and for displacement).
Thanks, Marius
Hi Marius,
Yes your are correct, I have thought about changing it to Adapt Planning, but I was trying to limit impact on current processes for other plants. This is still a potential option, will test a little with it.
My title might be misleading a bit, I meant that MRP when it cannot go far enough in the past to satisfy the demand, will switch automatically to Forward Scheduling. Even though I'm in backward.
My Re-Scheduling tolerances are set to 0, but that is suppose to create exception messages, not trigger rescheduling.
To me the issue is still everything that has value PLAF-PRSCH set to 'X' and has a finish scheduled date / time in the pass is directly forward scheduled by MRP, regardless if my scheduling parameters could allow for rescheduling in the pass (1 day). And the fact that the basic dates don't want to stay put.
Hi Marc,
I think that you need to change the MRP behavior with
Here are few threads to check:
http://scn.sap.com/thread/3494308
http://scn.sap.com/thread/3744160
http://scn.sap.com/thread/2150526
Thanks, Marius
MRP ran again at 1 PM.
To me this is link to my Repetitive Manufacturing confirmations that reduce and reschedule my orders without changing my basic dates.
For example, before my MRP Run, one planned order had these dates:
(last MFBF confirmation on 2015.06.10 at 07:35:52)
Bsc start | Basic fin. | SchedStart | Start Time | Sched.Fin. | Finish tme |
2015-06-10 | 2015-06-10 | 2015-06-10 | 7:35:52 | 2015-06-11 | 7:35:52 |
After the MRP, the dates are now (MRP changed the Basic Finish Date).
Bsc start | Basic fin. | SchedStart | Start Time | Sched.Fin. | Finish tme |
2015-06-10 | 2015-06-11 | 2015-06-10 | 7:35:52 | 2015-06-11 | 7:35:52 |
To me MRP should not change a firm planned order.
Another example, before my MRP Run, one planned order had these dates:
Bsc start | Basic fin. | SchedStart | Start Time | Sched.Fin. | Finish tme |
2015-06-09 | 2015-06-10 | 2015-06-09 | 12:01:01 | 2015-06-10 | 12:01:01 |
After the MRP, the dates are now (MRP changed both the basic dates and scheduled dates and did forward scheduling starting at the exact time it ran).
Bsc start | Basic fin. | SchedStart | Start Time | Sched.Fin. | Finish tme |
2015-06-10 | 2015-06-11 | 2015-06-10 | 13:00:55 | 2015-06-11 | 13:00:55 |
As I said, this seems to happen only on planned orders that were reduced by MFBF and rescheduled at the same time. But this does not happen systematically, some planned orders are not rescheduled by MRP.
I'm really at a lost here as to what is causing this on firm planned orders.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To add to this, out of 27103 planned orders in my Production System, only 53 are affected by this.
It seems that only firm PE planned orders with production version assigned are affected. And not all of them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also,
I'm currently testing in my QA and I changed the Scheduling Parameters of my planned orders to not adjust basic dates, Also note that I allow for scheduling to happen one day in the past and that all orders take exactly 1 day of scheduling no matter what the quantity is:
Still, my MRP run gave me the same results, some orders now have a scheduled start at the time of the MRP Run, and basic dates were adjusted:
Also, my Planned order settings allow basic dates in the past:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
In the planning run, the basic dates of the planned orders are determined via the in-house production time from the material master. The order finish date which is determined by the planning run displays the requirements date of the material.
The in-house production time in the material master should be maintained so that no adjustment of the order finish date is required.
This is the case if a scheduling type with forward scheduling has been set in the scheduling parameters (Transaction OPU5) or scheduling has been changed to a today scheduling in order to avoid production dates in the past.
You should generally use scheduling types with backward scheduling for planned orders.
Please refer 46237 - Consulting: determination of the order dates
Best Regards,
R.Brahmankar
Hi,
@Kiran Kumar - Both example are firmed orders. I know the basic dates are ok, my question is more towards the Scehduled Dates, when my MRP runs, some orders get a scheduled start at the exact second they were changed by MRP. However, when I try to reproduce, the best I can get is forward scheduling with a scheduled start date on today's date, but a scheduled start time in the past (00:00:00).
@R.Brahmankar - Yes I have read this note, and I understand that my MRP runs my Lead Time scheduling in Forward scheduling because some dates are in the past. However, same question, why do I get a schedule start time at the exact second they were changed by MRP in one case and a start at 00:00:00 in the second case. Also, why are my basic dates not adjusted in both cases ?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marc,
Your question is confusing.In your initial order which is highlighted in MD04 there is no issue with dates because end date is on 10th June and and GR processing time is 1 day so available date is 11th June which correctly showing in MD04 and moreover it would not get changed with MRP run unless any manual changes.
In your second example where you were tried to reproduce I am not sure whether it a firmed order or not because I don't see any firming indicator in your snap shots.
BR
KK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.