-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with planning operations confirmed in past #492
Comments
You have an example data to reproduce it? Or shall I create my own? |
I can provide you data, but you need to plan first, then shift dates of manufacturing orders to past and change status according to description in ticket I created. |
I have tagged a new patch release 6.20.1 with a correction for this issue. I'll also notify you by email when I have built the enterprise edition of the patch release. The windows executable you need will be part of that release. |
Hello,
![obrazek](https://user-images.githubusercontent.com/86603226/153146024-d45f8e37-bbde-41e8-9861-5e5c83404515.png)
as we discussed yesterday, we have problem with routing operations planned in past in case there is one of the suboperations confirmed.
If date of all operations is in past and status of one of the operations in routing is confirmed (others are proposed)
than after replanning, new operation is created,and the old one is disconnected from Demand. Date of all operations is shift to future.
![obrazek](https://user-images.githubusercontent.com/86603226/153146054-f958b2e2-2a4c-43a8-afb4-824c759ff26c.png)
In case all operations are in past, status of one of the suboperations is confirmed and routing operation is approved
![obrazek](https://user-images.githubusercontent.com/86603226/153153876-744bd7ed-b9dd-4e0b-8da1-4cc676b37d8a.png)
than after replanning are all operations disconnected from demand and they are planned again in future
![obrazek](https://user-images.githubusercontent.com/86603226/153153929-cb78731c-3a88-4fb1-947e-431ec4fd87dd.png)
The text was updated successfully, but these errors were encountered: