[17.0] [MIG] stock_restrict_by_planned_consumed_date: Migration to 17.0 #1851
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
…ove line that is planned to consumed in different dates
alexandregaldeano
force-pushed
the
17.0-mig-stock_restrict_by_planned_consumed_date
branch
from
4f6de41 to
2b56eb4
Compare
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.
Migration to Odoo 17 of module in PR #1509
Based on #1850
In pickings, only reserves lots having an expiration date above the move's planned consumed date.
See example below where only the cheese burgers with an expiration date above the 2025-01-29 were reserved: