[17.0][MIG] logistics_planning_invoicing: Migration to 17.0#2
Open
ChristianSantamaria wants to merge 12 commits into17.0from
Open
[17.0][MIG] logistics_planning_invoicing: Migration to 17.0#2ChristianSantamaria wants to merge 12 commits into17.0from
ChristianSantamaria wants to merge 12 commits into17.0from
Conversation
Links Logistics Planning with Invoicing
With this improvement, new tools for massive schedules mark as finished are added. And, when logistics_planning_mgmt_weight is installed, schedule inputs are not automatically marked as finished when a ticket (move) is selected, so massive marking schedules as finished becomes important.
…hods
Some onchange methods had write() calls within, that could lead to
unexpected results. In that cases we should use dot (".") notation or
update() calls.
Features added: * New Schedules Invoicing menu for Account users. * This menu shows both input and output invoiceable schedules. * For one (with a custom button) ore more schedules invoice action is available.
With this improvement, it's possible to duplicate those logistics plannings manually created. Some of the fields were reset anyway (like state, linked stock move, invoicing, etc). Parametrized multi duplication is allowed (selecting a certain number of schedules to be duplicated, with a custom limit that prevent a user error selecting "Duplicate" action when it wasn't intended to).
…voice line This improvement enables by default grouping selected logistics schedules to be invoiced in the same line if some of them shares the same values, making aggregation according price unit type expected behavior. Grouping criteria by: - product (replacing account, that is not available at this point) - analytic account - product unit of measure - price unit type - (OPT) price unit When aggregating, - If product unit of mesure is 'trip' => adding to price unit - If product unit of mesure is 'unit' => adding to price qty
…unt issues This commit fixes the following bugs: * When an invoice was duplicated, related schedules were also linked to the new invoice. A schedule cannot be linked to more than an invoice line. * When a draft invoice with linked schedules was deleted, every schedule was unlinked as well (ok), but the same didn't occur when a single invoice line was removed. Now, such check is made at invoice line level. * Invoice schedule count became wrong when lines with linked schedules were remove.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Standard migration to v17