Requirement & Availability dates mismatch: Block plnd resources

[andy_yeri]

Hi Experts,

Looking to see if there is a standard way to the below issue -

On the image above, you can see -

• The last planned order created with an Availability date of 09/05/2015, is our Block Planned resource.
• The products above this planned order can obviously only be made after it's Available Date/time.
• Question: Should standard SAP recalculate the date under the Available Date column & reset 'em per the transit time & the planned order duration at each level? i.e. - the one highlighted in YELLOW with an availability date of 09/19/2015 should be reset to 09/05/2015, as its Planned ord duration is only 5 mins (in our case).
• Justification: When we measure ontime performance, it is measured @ the last but one product level, so it always gets projected as being made ontime while we really make it way early.

Any suggestions?

[andy_yeri]

I'll add another screen print, to explain how the system resets the Requirement Dates as well, when the Block is unavailable @ the requested date/time -

In this case, the Sales Order requirement date was 09/01/15. We've a 2nd sched line added, coz the system had to reschedule the order. What's unclear is why the system would influence the Requirement Date (underlined in RED) & synch it up with the Available Date/Time. I would expect the Requirement Dates to be stand alone, coz they are what they are.

[m_manimaran]

Hi Andy Yeri,

In my experience, if there is enough capacity available to pull in the operations in, then the optimizer, will and should move the requirement date of the header order, based on the availability of the component order.

In your case, since you are using block planning, is there any constraint to move the header order in?

Regards,

Manimaran M.

[andy_yeri]

Hi Manimaran,

We do not use Optimizer. Secondly, from a scheduling stand point, I do not understand why should there be a need to reset/change the Requirement Date/time? The requirement date/time comes from the Sales Order (lets assume this to be a Sales Order driven planning, for now) & per backward scheduling, the dates on the subsequent BOM levels are set while the system carries out detailed scheduling.

On the scenario with the 1st screen print, my question is - "in the mill environment, where we make the Rolled product immediately after making the core/Jumbo, it becomes imperative to keep the availability dates connected". In other words, the making of the Rolled product & the core/Jumbo cannot be detached.

On the scenario with the 2nd screen print, my question is - Why should the system come back to adjust the requirement dates. These should be left to by themselves.. Availability dates can change per the available capacity, but, unless there is a rescheduling on the Sales Order, the requirement dates must not be touched.

Hope that puts it into context

Thanks.

[m_manimaran]

Hi Andy,

In the context view, whatever the Requirement date displayed at the sales order line only is the requirement date of the sales order. Meaning, when you move the requirement date in sales order directly or using BOP, this is the only date that will change.

The lower level requirement dates are - dates at which the planned order requires the component to start the planned order. These dates can be changed by scheduling.

I understand the need for keeping component order and header order closer to each other. However, if they are processed in different resources and there are different operations involved, there is always a chance to see the gap between availability of the component and requirement date of the header.

If you have to keep them close enough, I think, we have to consider the availability situation of the resources.

Which is the constrained resource in your case - component production resource or header resource or both?

If it is both, then it is difficult to achieve your requirement.

Please let me know more details about your scheduling process.

Regards,

Manimaran M.

[andy_yeri]

Hi Manimaran,

While establising the Requirement Dates, the system starts with the SO date (MAD) & backward schedules to get the dates for the Component orders. In the process, it is supposed to consider the Operation/s duration for Planned Orders & the transit time for the STR's.

On the other hand, Availability is a totally different calculation by itself, dependent on when SLOTs or BUCKETS of free capacity become available.

In our case, the component production resource is constrained. i.e. it is the one that is bucket managed.

Thanks for your responses.