Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0057830 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [Modules] Distribution Orders | minor | always | 2025-01-31 22:10 | 2025-02-20 14:09 | |||||||
Reporter | axelmercado | View Status | public | |||||||||
Assigned To | Sandrahuguet | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | scheduled | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Review Assigned To | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0057830: Problem with duplicity of lines when generating issue from “Issue Distribution Order”. | |||||||||||
Description | When we generate a DOI issue from the “Issue Distribution Order” window manually, for some reason a line is duplicated generating additional erroneous movements. | |||||||||||
Steps To Reproduce | Video with the steps in Livebuilds: https://drive.google.com/file/d/15VHOpF1JIXM7oHyQLUCp0Zx0E2NiBZBB/view?usp=sharing [^] | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ![]() | |||||||||||
![]() |
|
![]() |
|
(0175063) vmromanos (manager) 2025-02-03 14:22 |
I think you are not using the functionality properly. See documentation: https://wiki.openbravo.com/wiki/Projects/Distribution_Orders/User_Document#Issue_Distribution_Order [^] Usually you just want to create the header, populate the DO and In Transit bin fields, and press the Generate Issue button, which will automatically create the lines with the available stock. I don't understand what you are trying to do in the video and what you pretend the Generate Issue button to perform if you create manual lines with a new bin different from the In-Transit bin at the header. |
(0175780) mtaal (manager) 2025-02-17 20:15 edited on: 2025-02-18 11:02 |
After further email discussion the issue showed to be reproducable in livebuilds (see attached document). FYI, in theory the process works like this: 1. It iterates over the DOi lines declared in the Issue DO header. 2. If there is a previous Issue DO line linked to the DOi line and the product is the same as in the DOi line, it doesn't try to calculate anything. 3. Otherwise, it creates as many Issue DO lines as necessary to deliver the correspondent DOi line. 4. If there is an overissue bin declared, it goes to negative if necessary using this bin only if the line hasn't been added manually by the user. It showed it didn't work, see attached file for reproduction steps in livebuilds |
(0175972) hgbot (developer) 2025-02-20 13:07 |
Merge Request created: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/mods/org.openbravo.distributionorder/-/merge_requests/92 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2025-01-31 22:10 | axelmercado | New Issue | |
2025-01-31 22:10 | axelmercado | Assigned To | => Triage Omni WMS |
2025-02-03 14:22 | vmromanos | Note Added: 0175063 | |
2025-02-03 14:22 | vmromanos | Status | new => feedback |
2025-02-03 15:10 | axelmercado | Note Added: 0175064 | |
2025-02-03 15:10 | axelmercado | Status | feedback => new |
2025-02-17 20:15 | mtaal | File Added: 57830-livebuilds-reproduction.pdf | |
2025-02-17 20:15 | mtaal | Note Added: 0175780 | |
2025-02-17 21:20 | axelmercado | Note Deleted: 0175064 | |
2025-02-18 10:55 | mtaal | Assigned To | Triage Omni WMS => Sandrahuguet |
2025-02-18 11:02 | mtaal | Note Edited: 0175780 | View Revisions |
2025-02-20 13:07 | hgbot | Note Added: 0175972 | |
2025-02-20 14:09 | Sandrahuguet | Status | new => scheduled |
Copyright © 2000 - 2009 MantisBT Group |