Violation of relationship between operations in the same planned order when a block is inserted on a resource

[Former Member]

Gurus,

Whenever a resource downtime is maintained through transaction code /SAPAPO/RES01 the operation in that resource gets shifted to a future time/date. However the subsequent operations in the same planned order loaded on other resources do not get shifted resulting in violation of the inter-operation relationships. That means, the subsequent operations start before the finish of the previous operation which got shifted because of the insertion of the block.

   The relationships between the operations in the same order do not get violated if any one of them is rescheduled manually or through heuristic. But this functionality is missing when the operation is moved by putting downtime on the resource. How we can avoid this violation of relationships when we block the resources?

Thanks in advance!

Snigdho

[Former Member · Accepted solution]

This is a standard functionality. Closing the thread.