0052615: When Confirm Stock Reservation is No in DO, Available Stock is not properly shown when there is reserved stock for product

Description

When Confirm Stock Reservation is No in DO, Available Stock is not properly shown when there is reserved stock for product

Steps To Reproduce

- Make sure there is product with stock and some reserved quantity. For eg: Chinese Plum in Food001 Storage Bin Available stock is 150 and reserved quantity is 10.
   To have reserved quantity as 10 do the below:
   - Create a DO OTF in Front End, set the Storage Bin as Food001
   - Add product Chinese Plum and set Confirmed Quantity as 10
   - Do not confirm the DO, go back to main menu.

- Create a DO in Back Office.
- Set DO OTF flag as Yes and Confirm Stock Reservation flag as No.
- Set Storage Bin as Food001, Add above product in the DO Line.
- Realize that Available Stock is set as 150.

Expected Available Stock value in the DO Line is 140.
https://openbravo.atlassian.net/browse/RM-6667 [^]

Proposed Solution

diff --git a/src/org/openbravo/warehouse/advancedwarehouseoperations/distributionorders/mobile/processors/DistributionOrderEventsProcessor.java b/src/org/openbravo/warehouse/advancedwarehouseoperations/distributionorders/mobile/processors/DistributionOrderEventsProcessor.java
index 48a3d70..6fba8c6 100644
--- a/src/org/openbravo/warehouse/advancedwarehouseoperations/distributionorders/mobile/processors/DistributionOrderEventsProcessor.java
+++ b/src/org/openbravo/warehouse/advancedwarehouseoperations/distributionorders/mobile/processors/DistributionOrderEventsProcessor.java
@@ -90,7 +90,7 @@ public class DistributionOrderEventsProcessor extends JSONProcessSimple {

           if (dol == null) {
             if (!docIsDOOTFConfirmStockReservation) {
- reservedQty = BigDecimal.ZERO;
+ reservedQty = storageDetail != null ? storageDetail.getReservedQty() : null;
             } else {
               reservedQty = storageDetail != null
                   ? storageDetail.getReservedQty().compareTo(BigDecimal.ZERO) > 0

Issue History
Date Modified	Username	Field	Change
2023-05-31 07:34	AtulOpenbravo	New Issue
2023-05-31 07:34	AtulOpenbravo	Assigned To	=> Triage Omni WMS
2023-05-31 07:35	AtulOpenbravo	Relationship added	related to 0052382
2023-05-31 07:45	AtulOpenbravo	Steps to Reproduce Updated	View Revisions
2023-05-31 07:48	AtulOpenbravo	Steps to Reproduce Updated	View Revisions
2023-05-31 07:52	AtulOpenbravo	Proposed Solution updated

Notes
There are no notes attached to this issue.