Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0048825 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Retail Modules] Web POS | major | always | 2022-03-17 14:16 | 2022-05-02 13:30 | |||||||
| Reporter | idiez | View Status | public | |||||||||
| Assigned To | rqueralta | |||||||||||
| 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 | pi | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | 2022-03-31 | |||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0048825: Directly affects the registration of the payment since the documents to be linked are not available | |||||||||||
| Description | The reported problem directly affects the payment record since the documents to be linked are not available. | |||||||||||
| Steps To Reproduce | Link of the videos :https://drive.google.com/drive/folders/18FAaqifUAx_h09TKxw6CLkM7kNKTQPqq?usp=sharing [^] 1.-From the POS a Pick&Carry product is sold. The total amount is paid. The order and invoice are generated. 2.- From the POS the sale is returned using the "Verified Return". A new product is added to the same ticket with the same price as the returned product and the delivery mode is set to "Pick up in store". 3.- From the POS I deliver the product through the option Issue Sales Order. The invoice for the new product is generated 4.- From the Backend I verify the registration of the Return and sale of the new product. It is observed that the payment plan of the return will NOT be continued. 5.- From the Backend in Payment Inn the registration of the payment for Amount 0 is initiated so that the invoice for the new product is paid (invoice in step 3). When you want to register the payment (for amount 0) the new invoice is available (step 3-VBS1FULLINV/0000003) but the invoice for the return is not available (step 2 - VBS1FULLINV/0000002). Result: The last invoice is paid from the payment record linking both vouchers (Step 2 - VBS1FULLINV/0000002 - Step 3 - VBS1FULLINV/0000003). | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0136882) marvintm (manager) 2022-05-02 13:30 edited on: 2022-05-02 13:31 |
This flow is quite complex, as it would require most probably refactoring the way we generate the payment plan for that specific flow, and then review how the invoices should be attached to that new payment plan. Therefore, I have changed it to design defect. One proposal from my side: - I would first start using customers properly configured (otherwise we don't support invoicing anyway, and it is clearly visible in the video that the invoicing process fails because the customer is missing Tax ID, if this is fixed invoicing in the Issue Sales Order will work, and there will be no need to generate the invoice in the backoffice) - Then, I would configure the Invoice Rule of the customer to "After order delivery". In this way, a single invoice will be generated, grouping both positive and negative line, and this invoice will already be paid. I think this proposal more accurately describes the real scenario that happened, and in this way the invoice will be generated without any need to pay anything (which also maps with the reality, as the customer actually did not pay anything when the second order was created). |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-03-17 14:16 | idiez | New Issue | |
| 2022-03-17 14:16 | idiez | Assigned To | => Retail |
| 2022-03-17 14:16 | idiez | Regression date | => 2022-03-31 |
| 2022-03-17 14:16 | idiez | Triggers an Emergency Pack | => No |
| 2022-03-27 21:00 | rqueralta | Assigned To | Retail => rqueralta |
| 2022-03-27 21:00 | rqueralta | Status | new => scheduled |
| 2022-05-02 13:30 | marvintm | Note Added: 0136882 | |
| 2022-05-02 13:30 | marvintm | Type | defect => design defect |
| 2022-05-02 13:31 | marvintm | Note Edited: 0136882 | View Revisions |
| 2022-05-02 13:31 | marvintm | Note Edited: 0136882 | View Revisions |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |