Skip to content
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

Dummy order on a past date #61

Closed
MicheleZak opened this issue Nov 22, 2019 · 5 comments
Closed

Dummy order on a past date #61

MicheleZak opened this issue Nov 22, 2019 · 5 comments

Comments

@MicheleZak
Copy link

Hello,

The strategy you suggest ( to schedule orders with a date different than the current one ) fails when setting an order with a date previous than the current one. You can see this behaviour in the image attached.

It's ok if the algorithm does not create all the past orders, I'm fine with that, but I would like then that the order being created keep the step range. It is being created on the current date instead.

Could you check?
Thanks

Screenshot_2019-11-22 Maintenance Orders - Odoo

@wowas18
Copy link
Contributor

wowas18 commented Nov 25, 2019

Can you explain more detail what issue you try to resolve?
As I see from your example you has one order in past and you overtime required period. When you plan new orders you wish execute it at present or future. Why you need plan new order in past? I don't understand :(

@MicheleZak
Copy link
Author

MicheleZak commented Nov 25, 2019

I'll explain to you with an example.

I want to schedule orders each 30 days, but I want the first one to be 40 days ago.
The orders that would fall in the past can be skipped, I'm only interested in keeping the correct step computation.
Taking that into account, I should get an order in 20 days when replanning, instead I get one in 30 days.

The image regard that very example.
The day was the november 22nd and I had a previous order on the 15th of october.
The procedure should have created an order on the 14th of december, not on the 22nd, because of the 30 days rule's interval and because, otherwise, the order should have been created on the november 14th, and that's a day in the past ( I don't care of the past orders ), so it would have jumped to the next one, but keeping the correct steps, on december 14th.

@wowas18
Copy link
Contributor

wowas18 commented Nov 26, 2019

Just take first order (22 december), move manually it to 14 december and confirm it. After confirm it will not changed with next replan.

@MicheleZak
Copy link
Author

That was only an example.
I should not take care of the computations that the software should take care of - what if the first order was 12 months ago?
This behaviour is not consistent at all. I understand that you consider the need of a missing order to still be executed, but most of the enterprises I know of want to track orders in the past too (even if they never happened!): they are needed for fiscal and statistical purposes.

@wowas18
Copy link
Contributor

wowas18 commented Dec 2, 2019

Because you can't clear define and describe business case that need support, I close this issue.

@wowas18 wowas18 closed this as completed Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants