Openbravo Issue Tracking System - Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0055504 | Modules | Advanced Warehouse Operations | public | 2024-05-17 00:08 | 2024-06-13 19:48 |
|
| Reporter | axelmercado | |
| Assigned To | mtaal | |
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | approved |
| Regression date | |
| Regression introduced by commit | |
| Regression level | |
| Review Assigned To | |
| Support ticket | 97172 |
| OBNetwork customer | OBPS |
| Regression introduced in release | |
|
| Summary | 0055504: Error - Organization change in warehouse operations |
| Description | When we have a warehouse operation of a product belonging to the parent organization (for example US), if we make movements corresponding to a child organization (US East Coast or US West Coast, the operation should not change organization, it should continue to belong to the parent organization. |
| Steps To Reproduce | 1- In backoffice, create a Purchase Order with a parent organization (For example US).
2-In AWO receive the PO created before.
3-Check the warehouse operations, a new one has been created for the received product and the parent organization.
4- Perform any movement, it can be a put-away to another slot, move to another child warehouse or a picking of a SO from a sale of a child organization. Any action causes the warehouse operation in question to change organization which we believe is incorrect. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0057398 | | closed | AtulOpenbravo | Incorrect Organization set in Storage Detail |
|
| Attached Files |  2024-06-04_19-51.png (160,535) 2024-06-04 19:51
https://issues.openbravo.com/file_download.php?file_id=19875&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-05-17 00:08 | axelmercado | New Issue | |
| 2024-05-17 00:08 | axelmercado | Assigned To | => Triage Omni WMS |
| 2024-05-17 00:08 | axelmercado | OBNetwork customer | => No |
| 2024-06-03 11:38 | mtaal | Note Added: 0165461 | |
| 2024-06-03 11:38 | mtaal | Type | defect => design defect |
| 2024-06-03 21:38 | axelmercado | Support ticket | => 97172 |
| 2024-06-03 21:38 | axelmercado | OBNetwork customer | No => OBPS |
| 2024-06-04 19:50 | mtaal | Note Added: 0165574 | |
| 2024-06-04 19:51 | mtaal | File Added: 2024-06-04_19-51.png | |
| 2024-06-07 10:59 | mtaal | Status | new => feedback |
| 2024-06-07 11:02 | mtaal | Status | feedback => new |
| 2024-06-13 11:49 | mtaal | Assigned To | Triage Omni WMS => mtaal |
| 2024-06-13 11:51 | hgbot | Merge Request Status | => open |
| 2024-06-13 11:51 | hgbot | Note Added: 0165904 | |
| 2024-06-13 11:53 | mtaal | Note Added: 0165905 | |
| 2024-06-13 19:48 | hgbot | Merge Request Status | open => approved |
| 2024-06-13 19:48 | hgbot | Resolution | open => fixed |
| 2024-06-13 19:48 | hgbot | Status | new => closed |
| 2024-06-13 19:48 | hgbot | Note Added: 0165923 | |
| 2024-06-13 19:48 | hgbot | Note Added: 0165924 | |
| 2024-12-10 05:59 | AtulOpenbravo | Relationship added | related to 0057398 |
|
Notes |
|
|
(0165461)
|
|
mtaal
|
|
2024-06-03 11:38
|
|
|
after discussing with Victor seems at most a design defect |
|
|
|
(0165574)
|
|
mtaal
|
|
2024-06-04 19:50
|
|
After further discussion:
- the organization field in the warehouse operation is currently the same as the ad_org_id of the storage detail
- however the way the storage detail ad_org_id is computed is not well defined and it should not be used directly
- instead the organization of the warehouse (of the storage detail should be used)
as we can understand that it can give confusion we propose to make the following change to the warehouse operations window:
- make the organization field the same value as the warehouse organization
- the consequence is that the organization filter will automatically filter out unwanted warehouse operations in that window and therefore prevent confusion
See the screenshot attached to this jira for how this will look like. |
|
|
|
(0165904)
|
|
hgbot
|
|
2024-06-13 11:51
|
|
|
|
|
(0165905)
|
|
mtaal
|
|
2024-06-13 11:53
|
|
Test plan:
before the fix:
- login with Openbravo, goto warehouse operations window, show the warehouse-organization and organization columns in the grid --> check that they can have different values.
after the change:
- login with Openbravo, goto warehouse operations window, show the warehouse-organization and organization columns in the grid --> check that they have the same values.
- make the warehouse operations window available for AWO_US_W
- login as AWO_US_W, goto warehouse operations check that the window shows only records of the west organization |
|
|
|
(0165923)
|
|
hgbot
|
|
2024-06-13 19:48
|
|
|
|
|
(0165924)
|
|
hgbot
|
|
2024-06-13 19:48
|
|
|