Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0051076ModulesSelf-Replenishment for WMSpublic2022-12-06 20:522023-01-30 16:31
Reporteraxelmercado 
Assigned Toignacio_deandres 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.50 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customer
Regression introduced in release
Summary0051076: A wrong configuration of a replenishment bin break the entire replenmishment run
DescriptionWhen the replenishment background process is executed and one product among several has the bin group deleted or misconfigured, the process continues and finishes without showing any error message, so the warehouse for which the replenishment task has not been performed never learns of this error until the created tasks are corroborated.


Expected behavior:
- Process should immediately stop and return a clear error message for the user in other to fix the problem
- Alternatively the process could continue with the remaining products and at the end show a error messages with all the products with errors
Steps To ReproduceIn the warehouse definition window, replenishment tab, make sure you have multiple bins configured to be replenished and set the mins accordingly so that replenishment tasks should be generated.
1. run "Internal Area Self-Replenishment" or "External Area Self-Replenishment" background process and see that replenishment tasks have been generated successfully
2. remove the generated tasks
3. find 2-3 of the lines in the replenishment bin for which a replenishment was generated and go to the locator of these lines
4. change the configuration of the locator and remove the storage bin group (in other words screw up the configuration)
5. the replenishment algorithm will now fail when trying to replenish to these bins because the storage bin group is null
6. after this error the process stops completely
7. a message will be put into the log, but the process request will say success
Proposed SolutionExpected behavior: Process should immediately stop and return a clear error message for the user in other to fix the problem
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-12-06 20:52axelmercadoNew Issue
2022-12-06 20:52axelmercadoAssigned To => Triage Omni WMS
2022-12-15 11:02vmromanosNote Added: 0144734
2022-12-15 11:25vmromanosAssigned ToTriage Omni WMS => Triage Platform Base
2022-12-15 14:53axelmercadoProposed Solution updated
2022-12-20 11:32alostaleAssigned ToTriage Platform Base => Triage Platform Conn
2023-01-09 10:45adrianromeroAssigned ToTriage Platform Conn => ignacio_deandres
2023-01-09 10:45adrianromeroStatusnew => scheduled
2023-01-18 14:35axelmercadoCategoryAdvanced Warehouse Operations => Self-Replenishment for WMS
2023-01-19 14:39vmromanosNote Added: 0145644
2023-01-19 14:39vmromanosAssigned Toignacio_deandres => axelmercado
2023-01-19 14:39vmromanosStatusscheduled => feedback
2023-01-26 10:55gorkaionAssigned Toaxelmercado => Triage Omni WMS
2023-01-26 10:55gorkaionStatusfeedback => new
2023-01-26 10:55gorkaionDescription Updatedbug_revision_view_page.php?rev_id=25454#r25454
2023-01-26 10:55gorkaionSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=25456#r25456
2023-01-30 15:45hgbotNote Added: 0146038
2023-01-30 16:16vmromanosStatusnew => scheduled
2023-01-30 16:16vmromanosAssigned ToTriage Omni WMS => ignacio_deandres
2023-01-30 16:31hgbotNote Added: 0146040
2023-01-30 16:31hgbotResolutionopen => fixed
2023-01-30 16:31hgbotStatusscheduled => closed
2023-01-30 16:31hgbotNote Added: 0146041

Notes
(0144734)
vmromanos   
2022-12-15 11:02   
Expected behavior: Process should immediately stop and return a clear error message for the user in other to fix the problem
(0145644)
vmromanos   
2023-01-19 14:39   
Make sure this is reproducible in a standard environment, and if so add the right steps to reproduce it in a standard environment
(0146038)
hgbot   
2023-01-30 15:45   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.warehouse.advancedwarehouseoperations.selfreplenishment/-/merge_requests/9 [^]
(0146040)
hgbot   
2023-01-30 16:31   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.warehouse.advancedwarehouseoperations.selfreplenishment/-/merge_requests/9 [^]
(0146041)
hgbot   
2023-01-30 16:31   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.warehouse.advancedwarehouseoperations.selfreplenishment [^]
Changeset: fd99fb630d76e8de1ab368f3a11b4a5bec3d199e
Author: Ignacio De Andres <ignacio.deandres@openbravo.com>
Date: 30-01-2023 16:12:53
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.warehouse.advancedwarehouseoperations.selfreplenishment/-/commit/fd99fb630d76e8de1ab368f3a11b4a5bec3d199e [^]

Fixes ISSUE-51076: now when a warehouse does not have a storage bin group configured and a process is requested it will throw an exception and mark the process status as Error

---
M src/org/openbravo/warehouse/advancedwarehouseoperations/selfreplenishment/ad_process/GenerateSelfReplenishment.java
---