on 10-19-2012 11:27 AM
Dear all,
I have some trouble with component's requirement date during production order conversion.
Component's requirement date at planned order are changed during production order conversion.
Is it standard system behavior?
the behavior is as following:
Planned order 10001, Ord.start 2012/11/19, Ord. finish 2012/12/03
Component Offset LT Req.date Qty
1. CompA 10 2012/12/03 1Pc ⇒based on scheduling calculation, the requirement date should be 2012/12/04 (2012/11/23 is holiday). Since finish date of the planned ord is 2012/12/03, the system automatically adjust it to 2012/12/03.
2. CompB 0 2012/11//19 1Pc
3. CompC -10 2012/11/05 1Pc
When we convert this planned ord to prod.ord. the requirement date of CompA becomes 2012/12/04.
Prod. ord 20001, basic date start 2012/11/19, finish 2012/12/03
Component Req.date Qty
1. CompA 2012/12/04 1Pc ⇒ the requirement date is changed.
2. CompB 2012/11//19 1Pc
3. CompC 2012/11/05 1Pc
Guess is you have maintained your I/H production time for your assembly material as 9 days.
Because only in such a case, say with forward scheduling and run for basic dates scheduling, the start date will be 19/11 and end date will be 3/12 (taking into account the holiday on 23/11 as specified by you).
The lead time maintained in the BOM for 10 days(workdays) will calculate the dep reqmt date as 4/12 but order finish date will decide the upper limit for the dependent requirement and so the 3/12 date will be proposed for the dep reqmt.
(Curious.Do you still see the reqt date of Component C as 5/11 or is it also 19/11)
Your scheduling setting looks like 'Do not adjust basic dates'. In such a case when your Basic order finish date of 3/12 should be earlier than the Production finish date (which is evident from your Prod order 20001) when you try to convert the planned order into a production order and will be with a 64 exception message. Because of this the system can now push the dep reqmt to the next date ie 4/12 during conversion into a production order which looks like standard system behaviour.
If and only if the 9 day setting for I/H pdn is true in your case try changing it to 10 days and update on the observations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear UK SAPPP,
Thanks for your response. I just noticed that my explanation was insufficient.
I/H production time = 30 days
Adjust scheduling = do not adjust basic dates, dep. req. to order start
Scheduling type = backward
After MRP execution, the basic dates for planned order 10001 are as following.
Start date : 2012/11/19, finish date : 2013/01/03
Component Offset LT Req.date Qty
1. CompA 10 2012/12/04 1Pc
2. CompB 0 2012/11//19 1Pc
3. CompC -10 2012/11/05 1Pc
(If we convert it to prod. ord., we will have reservations with exactly the same date as dependent requirement dates above, CompA on 2012/12/04, so on)
Prod. planner checks the proposed order before convert it to prod. ord. In some case,
he will bring the production forward and adjust the finish date, for example set the finish date to 2012/12/03. The dependent requirement date are adjusted automatically, CompA to 2012/12/03, CompC still 2012/11/05.
But then when we convert the planned ord. to prod. ord., the reservation date for CompA
is changed back to 2012/12/04. We would like to have the reservation for the component with the same date on dependent requirement.
Please let me know, if you have any idea to solve it.
Hi, Based on your screenshots could replicate the issue and thoroughly understood it.
Read through SAP note 386279 which specifies the probable system behaviour:
(Positive)Lead-time offset:
Lead time (negative number of days in the lead-time offset field of the BOM
item):
the start date of the first operation or
In your case the moment you delete the LT offset for the +10 days cpt, you will see that the dep.reqmt correspond to the Order basic start date again.
Results in your screenshots corresponds to what is mentioned in this note. Anyways please update on this issue, after you hear back from SAP/OSS.
Dear UK SAPP,
Thanks for the note. It's very helpful.
About the limitation of requirement date, does it mean that the requirement date for unscheduled planned order is limited to order finish date, but for scheduled planned order, the order finish date won't be considered in requirement date calculation?
Since production order is scheduled by lead time scheduling, it means that the reservation of material won't be limited to order finish date. That's why we will have the same result if we schedule the planned order first before convert it to production order.
I'll update this thread if there is any response from SAP/OSS.
Thank a lot.
Dear UK SAPPP,
I've already got the confirmation from SAP.
As stated on the note you shared, an unscheduled planned order, the requirements date of a component can be moved at the most to the order finish date of the order. So the requirements date of a component won't fall after the order finish date. This logic is not implemented to the scheduled planned order. For scheduled planned order, the requirements date of a component may fall after the order finish date. Since production order is scheduled based on lead-time scheduling, it means it shares the same logic with scheduled planned order, so for production order, the requirement date of component won't be adjusted to order finish date, even if it falls behind.
It is standard system behaviour.
Thanks for your cooperation.
Best regards,
Suwandi
Dear Suwandi,
I encounter same problem as you. Have you solved the problem?
Can you share the solution?
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your quick response.
As you said, the material reservation shows the same date as dependent requirement date on planned order. But, the dependent requirement date for CompA(in my test system, it is SU-T321-1) becomes 2012/12/19. Component requirement date falls after order finish date.
Are there anyway, so that dependent requirement is limited to order finish (the component requirement doesn't fall after order finish date)?
Regards
I did the test as you mentioned.
1. Create new planned order and save it.
> finish: 2013/01/21, start: 2012/12/05
> Requirement date for SU-T321-1 : 2012/12/19
2. Change the planned order.
> finish, New: 2013/01/21, old: 2012/12/17
> Requirement date for SU-T321-1: 2012/12/17
3. Run scheduling
> Requirement date for SU-T321-1: 2012/12/19
-> requirement date is updated and falls after order finish date
4. Convert to Prod. ord.
> Start: 2012/12/05, finish: 2012/12/17
Component requirement date
1. SU-T321-1 2012/12/19
2. SU-T321-2 2012/12/05
3. SU-T321-3 2012/11/21
-> exactly as planned order, but the requirement for SU-T321-1 falls after order finish date.
Dear,
I hope you have run the MRP with Lead time scheduling.
Now compare the parameter of scheduling of your planned and production order type in OPU5 and OPU3 for Adjust dates.
If in OPU3 you defined Adjust dates = Do not Adjust Basic Dates, Dep Req to Order Start. You will have the same date.
Read the F1 help on this field to get an idea in details.
Regards,
R.Brahmankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Brahmankar,
Thanks for your reply.
I've tried a couple times, but it doesn't work.
The requirement date of the component is different in production order.
The date is change during production order conversion.
By the way, we are not using Lead time scheduling.
We run MRP with basic date scheduling.
I tried to run MRP with lead time scheduling, but the result is still the same, the requirement date is changed.
Suwandi,
If you want to have the dates always be the same, you MUST at a minimum use lead time scheduling during MRP. In addition, you must also set your scheduling parameters the same for your planned orders as you have for your production orders. OPU5 and OPU3.
You must also use the same routing and BOM for both Planned orders and Production orders (this is normal).
Best Regards,
DB49
DB49,
Thanks for your reply.
I've set the same parameter for adjust scheduling dates at OPU5 and OPU3
The lead-time offset that I mentioned above is not operation lead-time offset. So I thing that I don't need to run MRP with lead time scheduling. By the way, I ran MRP using lead time scheduling a couple times, but the result is still the same that the component requirement date will be changed during convertion.
And because the production orders is created by converting planned order, the routing and BOM are the same.
Regards,
Suwandi
Suwandi,
The lead-time offset that I mentioned above is not operation lead-time offset. So I thing that I don't need to run MRP with lead time scheduling.
I don't know what this means. Dependent requirements of 'non-lead-time scheduled' planned orders is a function of the BOM and the inhouse production time. Dependent requirements of Production orders are not a function of these factors. These dates (planned and production) will only be the same by coincidence.
Many stars must be in alignment to consistently have the same dates of dependent requirements between planned and production.
You actually have to analyze how the dates of the planned orders were achieved. Then, you have to analyze how the dates of the production orders were achieved. Then, you have to compare the two.
Best Regards,
DB49
User | Count |
---|---|
95 | |
11 | |
9 | |
5 | |
3 | |
3 | |
3 | |
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.