ddmrp icon indicating copy to clipboard operation
ddmrp copied to clipboard

[14.0][IMP] ddmrp: Refactoring of incomings calculation

Open BernatPForgeFlow opened this issue 1 year ago • 4 comments

Refactoring of incomings calculation

  1. Reformulate incoming quantities calculation Split incoming quantities between inside or outside DLT. Make it more heritable, to facilitate consideration of other data sources. Store all the incoming moves and rfqs to always show what was calculated the last time it was refreshed.

  2. Add customized Stock Moves view When checking incoming quantities or qualified demand moves, we will use a customized view that allows to redirect to the source document of that move.

Other changes:

  • A change is made to the DLT date limit calculation so that refreshing a buffer prior to 12:00:00 UCT, take into account DLT date limit supplies.
  • In the calculation of the arrival quantities, the case of receptions in more than one step is taken into account. In these cases there was the possibility of double counting the RFQ and the Stock Move of arrival.

BernatPForgeFlow avatar Aug 03 '23 07:08 BernatPForgeFlow

Hi @JordiBForgeFlow, @LoisRForgeFlow, some modules you are maintaining are being modified, check this out!

OCA-git-bot avatar Aug 03 '23 07:08 OCA-git-bot

Now that you are tackling this... Does this work fine with manufactured items? and if you have manufacturing in 3 steps?

@LoisRForgeFlow I have added 4 tests that check if it works for purchased and manufactured items with 1 or 3 step manufacturing.

BernatPForgeFlow avatar Sep 15 '23 14:09 BernatPForgeFlow

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[bot] avatar Mar 31 '24 12:03 github-actions[bot]

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[bot] avatar Sep 15 '24 12:09 github-actions[bot]