[16.0][REF] account_cutoff_picking #268
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbaudoux
force-pushed
the
16.0-fix-mig-account_cutoff_picking
branch
2 times, most recently
from
6b3095a
to
6481959
Compare
Port PR OCA#73 to v16 and cleanup code
jbaudoux
force-pushed
the
16.0-fix-mig-account_cutoff_picking
branch
from
6481959
to
1155c48
Compare
|
Being replaced by #271 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Port and cleanup #73
cc @alexis-via @florian-dacosta @lmignon @rousseldenis
Instead of analyzing all pickings & invoices inside a given interval, only pickings and invoices generated after the cutoff date are analyzed, otherwise we rely on the SO/PO received/invoiced quantities. This allows to process a large amount of data in a reasonable amount of time. To decrease the amount of pickings & invoices to analyze a cron pre-generates the cutoff entries at the end of the period. Nevertheless, it is always possible to regenerate entries at any time (but the more pickings & invoices to analyze are, the more time it will take).
The limit in time in the past is then now disabled.
You can configure to disable accrual on closed orders.