Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0052633 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Order Preparation | major | always | 2023-05-31 23:34 | 2023-06-19 07:50 | |||
Reporter | Leosbanis | View Status | public | |||||
Assigned To | Retail | |||||||
Priority | high | Resolution | no change required | Fixed in Version | ||||
Status | closed | 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 | RR20Q1.3 | SCM revision | ||||||
Review Assigned To | marvintm | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0052633: When a sale is made and a customer is attached, the "updated" field of that customer is modified. | |||||||
Description | This happens when we close Picking (ClosePicking.java), at one point in this process the C_INVOICE_POST procedure is called and one of the extension points that is executed within it is: org.openbravo.advpaymentmngt/src-db/database/model/functions/APRM_GEN_PAYMENTSCHEDULE_INV.xml which was modified in the commit: https://gitlab.com/openbravo/customers/BUT/pi-20Q1/-/commit/6d57b0cfcf785bce95615708dd1f81e555886455 [^] Which causes the "Updated" field of the Business Partner to be updated to the current date. Happens also in our product last version (pi) | |||||||
Steps To Reproduce | 1- Login to the WebPOS. 2- Create a Sales Order. 3- Set delivery method other than "Pick and Carry" and delivery date after the current date. 4- Assign a Business Partner to the Order. 5- Pay the order. 6- Using the "Open receipt" option, open the created order. 7- Select the option "Prepare current ticket" and prepare the sales order. 8- Select the option "Picking" and search the created picking by the order document number. 9- Close the picking by following the steps in the popup. 10- Go to the "Business Partner" window of the backend and verify that the "Updated" column has been changed to the current date and time. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0151286) marvintm (manager) 2023-06-19 07:50 |
AFAICS, the behavior is correct. The function was modifying the credit used of the customer, and as with the rest of the records in Openbravo, if an entity is being changed, its updated column should also be updated. So I believe the current behavior should be preserved, and in this case the customer updated column should be modified. |
Issue History | |||
Date Modified | Username | Field | Change |
2023-05-31 23:34 | Leosbanis | New Issue | |
2023-05-31 23:34 | Leosbanis | Assigned To | => Retail |
2023-05-31 23:34 | Leosbanis | Triggers an Emergency Pack | => No |
2023-06-01 16:28 | kchoperena | Description Updated | View Revisions |
2023-06-19 07:50 | marvintm | Review Assigned To | => marvintm |
2023-06-19 07:50 | marvintm | Note Added: 0151286 | |
2023-06-19 07:50 | marvintm | Status | new => closed |
2023-06-19 07:50 | marvintm | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |