Openbravo Issue Tracking System - Modules
View Issue Details
0038052ModulesAdvanced Warehouse Operationspublic2018-03-06 11:492020-09-01 15:13
maarten1962 
dmiguelez 
urgentmajoralways
newopen 
5
 
 
0038052: Non-allocated Reservations, if existing, should be taken into account by Picking algorithms when creating tasks
When a sales order is created, a reservation is created as non-allocated. Note: Maybe there is a pref to change the rsrv. to alloc, but I consider this less relevant.
If a Rsrv exist for the order that is being picked, alloc or not alloc, it should be taken into account when creating the task.
Functionaly speaking, this is valid for all pickings: DO, WO, SO. I know that techically DO and WO use a different solution/table.
Create an order. Check that the rsrv is not alloc.
Then pick: the system will create a new rsrv, this time alloc.
Then try to issue. The system will give an error "There is a sales order line with more than one open reservation"
No tags attached.
has duplicate defect 0044804 closed inigo_lerga [AWO] - Order preparation gets duplicated if it already exists for so line 
diff proposal.diff (4,117) 2020-08-27 13:23
https://issues.openbravo.com/file_download.php?file_id=14903&type=bug
Issue History
2018-03-06 11:49maarten1962New Issue
2018-03-06 11:49maarten1962Assigned To => dmiguelez
2018-03-07 12:54vmromanosNote Added: 0103056
2018-03-07 12:54vmromanosTypedefect => design defect
2020-08-27 13:21dmiguelezNote Added: 0122388
2020-08-27 13:23dmiguelezFile Added: proposal.diff
2020-08-27 13:24dmiguelezNote Added: 0122389
2020-08-27 13:28dmiguelezRelationship addedhas duplicate 0044804
2020-09-01 15:13eugeniIssue Monitored: eugeni
2022-09-06 17:18caristuCategoryAdvance Warehouse Operations => Advanced Warehouse Operations

Notes
(0103056)
vmromanos   
2018-03-07 12:54   
Moved to design defect.

The current behavior is the expected one, and it's clearly documented at http://wiki.openbravo.com/wiki/Modules:Advanced_Warehouse_Operations#Determination_rules_of_the_From.2FTo [^]

"The sales order has predefined reservations (allocated) that point to a specific attribute/bin."


This proposal must be carefully studied to analyze its impact in the rest of the flows.
(0122388)
dmiguelez   
2020-08-27 13:21   
The proposed solution would be to implement:
1. Start the generation of the Tasks for the Picking SO
2. Check if there are non allocated reservations and temporarily delete them
3. Try to generate the Tasks
4. If it is not possible to generate the Tasks, revert the changes done to the reservations and set the context the same as it was at the beginning of the process
5. If the Tasks are correctly generated and the quantity reserved for the tasks is lower than the originally reserved quantity, create a non allocated reservation for the missing quantity so the total matches the originally reserved
(0122389)
dmiguelez   
2020-08-27 13:24   
A partial proposed solution has been attached as proposal.diff.
This code might be helpful while implementing the final solution.

It can not work as it is because it will fail in the case in which there is only 1 unit of stock of a particular product, in this case, the non allocated reservation does not allow to generate any tasks.

To implement the final solution, check the previous note in which the proposal implementation is explained