Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0052014 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
backport | [POS2] POS | minor | have not tried | 2023-03-30 09:51 | 2023-04-11 17:31 | |||
Reporter | mtaal | View Status | public | |||||
Assigned To | mtaal | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 23Q2 | |||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | 23Q2 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Merge Request Status | approved | |||||||
Review Assigned To | ||||||||
OBNetwork customer | No | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0052014: RM-5704: Pager when on order consolidation then lines should be combined irrespective of pickuppoint | |||||||
Description | When the system determines which lines to combine in a deliver control method (based on consolidation) then currently it will separate lines in different DCM if their pickup point is different. This also happens in case of order consolidation. For order consolidation this should not happen, it should combine lines with the same DCM. For non-order consolidation it does not need to use pickup point either as there the consolidation already forces separation in different dcm instances. https://openbravo.atlassian.net/browse/RM-5704 [^] | |||||||
Steps To Reproduce | Set order consolidation and different pickup points on lines and same DCM (pager), see that several pager calls are done. Only one should be done. | |||||||
Proposed Solution | Do not use pickuppoint to separate lines on different DCM instances. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
![]() |
||||||||
|
![]() |
|
(0148245) hgbot (developer) 2023-04-04 12:43 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1671 [^] |
(0148284) gracebathtub (viewer) 2023-04-05 09:02 |
Is there a similar column merge option possible? I have a question with https://thebackrooms2.com [^] |
(0148382) hgbot (developer) 2023-04-11 17:31 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1671 [^] |
(0148383) hgbot (developer) 2023-04-11 17:31 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^] Changeset: 5b61ea29ea9ffa0bff5dad09e694611ea188e532 Author: ruben.jimenez <ruben.jimenez@openbravo.com> Date: 11-04-2023 15:30:37 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/5b61ea29ea9ffa0bff5dad09e694611ea188e532 [^] Fixed ISSUE-52014: Do not separate DCM lines on the basis of pickup point --- M web-jspack/org.openbravo.pos2/src/core/pickupPoint/PickupHandler.js M web-jspack/org.openbravo.pos2/src/core/pickupPoint/__test__/PickupHandler.test.js --- |
![]() |
|||
Date Modified | Username | Field | Change |
2023-03-30 12:23 | nicola_uva | Type | defect => backport |
2023-03-30 12:23 | nicola_uva | Target Version | => 23Q2 |
2023-04-04 12:43 | hgbot | Merge Request Status | => open |
2023-04-04 12:43 | hgbot | Note Added: 0148245 | |
2023-04-05 09:02 | gracebathtub | Note Added: 0148284 | |
2023-04-11 17:30 | hgbot | Merge Request Status | open => approved |
2023-04-11 17:31 | hgbot | Note Added: 0148382 | |
2023-04-11 17:31 | hgbot | Resolution | open => fixed |
2023-04-11 17:31 | hgbot | Status | scheduled => closed |
2023-04-11 17:31 | hgbot | Fixed in Version | => 23Q2 |
2023-04-11 17:31 | hgbot | Note Added: 0148383 |
Copyright © 2000 - 2009 MantisBT Group |