Skip to main content

Hello.

We have an issue on our DOP structure’s due dates.

In our example, a DOP header has a Start date at 27/05/2022 and, when the structure has the statut “created”, every lines of it has a Due date at the same date of 27/05/2022.

 

After that, we release the DOP structure .

In standard, the DOP order due dates of WINCH-T40 and B-MODULE-BOIS are 27/05/22.

 

However, in the shop order the required dates of these components are 02/06/22 because they are called on the second operation of the shop order

 

This impacts the dates of shop orders and purchase orders of components managed in DOP (or MRP/DOP)

This does not impact the dates of shop orders and purchase orders of components managed in MRP because the MRP component need is triggered by the shop order (however if the MRP component is below a SF component managed in DOP, as the SF date is wrong the component date is wrong).

 

Have you allready encounter this issue ? and have you a way to avoid it ?

Unfortunately this is a known limitation in DOP. The Due Date of a sub level DOP order is always planned to meet the parent DOP order Start Date even if it is not needed until a later operation on that order.

The reason for this limitation is that the operations on the DOP order are not scheduled with Start/Finish Times similar as shop order operations. (the start date of the operation is used to set the required date of the component) 

However, it would be a great enhancement if this was possible to do in the system, even if it would likely comes with a performance impact.

Please feel free to suggest this in the Idea section! 

Terms & ConditionsCookie settings