Skip to content

Conversation

@DavidJForgeFlow
Copy link
Contributor

When computing the outgoing moves, it were taking all the pickings that weren't going to internal. An internal move from WH/Stock to VirtualLocations/Scrap will be taked with this method. Now it takes all the moves going from an internal location to customer or supplier. (Also the dropshipping moves).

@ForgeFlow

@codecov-commenter
Copy link

Codecov Report

Merging #426 (b6c3e7f) into 14.0 (fbb102d) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             14.0     #426   +/-   ##
=======================================
  Coverage   79.64%   79.64%           
=======================================
  Files         138      138           
  Lines        4570     4570           
  Branches      861      861           
=======================================
  Hits         3640     3640           
  Misses        723      723           
  Partials      207      207           
Impacted Files Coverage Δ
rma/models/rma_order_line.py 77.93% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fbb102d...b6c3e7f. Read the comment docs.

@DavidJForgeFlow DavidJForgeFlow changed the title [FIX] rma: outgoing moves and pickings [14.0][FIX] rma: outgoing moves and pickings Apr 4, 2023
@AaronHForgeFlow
Copy link
Contributor

@LoisRForgeFlow is this fine to you?

Copy link
Contributor

@LoisRForgeFlow LoisRForgeFlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale label Nov 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants