Openbravo Issue Tracking System - Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0054974 | Modules | Advanced Warehouse Operations | public | 2024-03-15 23:57 | 2024-05-14 09:15 |
|
| Reporter | axelmercado | |
| Assigned To | ludmila_ursu | |
| Priority | high | Severity | major | Reproducibility | random |
| Status | feedback | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Regression date | |
| Regression introduced by commit | |
| Regression level | |
| Review Assigned To | |
| Support ticket | |
| OBNetwork customer | |
| Regression introduced in release | |
|
| Summary | 0054974: Task and Reception list duplicated caused by delta SAME flow in SMCP |
| Description | The SMCP client has been presenting a problem of duplicated task and receptions lists for some time. When a task contains the confirmed quantity less than the expected/issued quantity, a duplicate task is created as if the "Delta Same" button was selected in AWO, when the client does not contain such functionality.
We believe this is due to the following part of the code where the deltaResponse = OBAWO_Constants.DELTA_SAME:
private String getDeltaResponse(final OBAWOTask task) {
String deltaResponse = null;
if (task.getDeltaResponse() != null) {
deltaResponse = task.getDeltaResponse();
} else {
if (StringUtils.equals(OBAWO_Constants.DELTA_DIFFERENT,
task.getInventoryTransactionType().getDeltaResponse())) {
deltaResponse = OBAWO_Constants.DELTA_DIFFERENT;
} else {
deltaResponse = OBAWO_Constants.DELTA_SAME;
}
task.setDeltaResponse(deltaResponse);
}
return deltaResponse;
} |
| Steps To Reproduce | At AWO:
1- Select a DO that is available to receive.
2- Confirm some tasks completely and others partially or with quantity 0.
3- After having processed all the tasks of the DO, verify that the tasks received partially or with quantity 0, a new task has been created.
4- Check in BO the previous DO and verify that the tasks and the reception list are duplicated. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  image.png (15,442) 2024-03-18 18:45
https://issues.openbravo.com/file_download.php?file_id=19561&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-03-15 23:57 | axelmercado | New Issue | |
| 2024-03-15 23:57 | axelmercado | Assigned To | => Triage Omni WMS |
| 2024-03-18 09:24 | mtaal | Assigned To | Triage Omni WMS => ludmila_ursu |
| 2024-03-18 11:28 | aferraz | Status | new => feedback |
| 2024-03-18 12:00 | aferraz | Note Added: 0162265 | |
| 2024-03-18 18:45 | axelmercado | File Added: image.png | |
| 2024-03-18 18:45 | axelmercado | Note Added: 0162308 | |
| 2024-03-18 18:45 | axelmercado | Status | feedback => new |
| 2024-04-22 11:40 | mtaal | Status | new => feedback |
| 2024-05-14 09:15 | ludmila_ursu | Note Added: 0164535 | |
| 2024-05-14 14:53 | ludmila_ursu | Note Edited: 0164535 | bug_revision_view_page.php?bugnote_id=0164535#r27960 |
|
Notes |
|
|
|
|
Moved to feedback because we don't have enough information to reproduce the problem. |
|
|
|
|
As can be seen in the attached image, duplicate tasks come with the delta response = SAME field. The SMCP client does not have the SAME button flow, the user cannot set it. The only part of the code where this value is set is the one mentioned in the description, which details the behavior of the tasks received partially or with a value of 0.
The random reproducibility has been given because it is not an easy problem to reproduce, sometimes it happens and sometimes it doesn't, but the flow of steps to follow is the basic one: You have a DO to receive, you proceed to receive them and some tasks are received partially, nothing else (this in the client environment). |
|
|
|
(0164535)
|
|
ludmila_ursu
|
2024-05-14 09:15
(edited on: 2024-05-14 14:53) |
|
Extra logs present in production since 24/04. Informed Romain about the added logs, they can continue with the analysis
|
|