Openbravo Issue Tracking System - POS2
View Issue Details
0047605POS2Corepublic2021-08-24 18:222021-09-03 10:08
jmelin 
vmromanos 
urgentcriticalalways
closedduplicate 
5
 
TAP 
No
0047605: JIRA 2297 - Generation through overpayment and payment amount in BO
When generating a credit note with an overpayment, the payment plan/details are not comprehensive and doesn’t seem correct:

in payment plan : the received amount should be the received amount with the overpayment ?

in payment details : the credit note appear as a payment for the sales order ? or should be a negative amount ?

in payment details : the received amount shoud be the real amount received for each type ?

In BO, switch to role "White valley group admin"
- In "Organization" Vall Blanca Store set:
  - credit note expiration days =10
  - use credit note once = checked

- Create a new "Payment method" named "Credit note generation"

- Open "Touchpoint type" named "POS2SD VBS POS2 Terminal Type"
  - Add new payment method "Credit note generation" linked to the previous payment method
  - Modify "Voucher" method and check "Return overpayment as credit note"

- Create a financial account for vallblanca store and add the payment method "Credit note generation"

- Open "Touchpoint" named "VBS-2"
  - Add "Payment type" with search key "GCNV_payment.creditnote" and named "Credit note generation"


Connect to VBS-2
-Create a new sales order and add "Avalanche transceiver" qty=1

- Checkout and pay with "Voucher" for an amount of "300"


=> it generates a credit note of 149.50
but in the sales order
- we have two payment method 'credit note' and 'voucher'
- amount of each can't retrieve or are not understable
No tags attached.
duplicate of backport 0047102TAP closed vmromanos Cash up not correct while using Credit Notes feature 
blocks defect 0047586 closed vmromanos JIRA 2297 - Generation through overpayment and payment amount in BO 
Issue History
2021-08-30 11:02dmiguelezTypedefect => backport
2021-08-30 11:02dmiguelezTarget Version => TAP
2021-08-30 11:02dmiguelezStatusscheduled => acknowledged
2021-09-02 16:36vmromanosRelationship addedcaused by 0047102
2021-09-03 10:08vmromanosStatusacknowledged => scheduled
2021-09-03 10:08vmromanosAssigned ToRetail => vmromanos
2021-09-03 10:08vmromanosRelationship replacedduplicate of 0047102
2021-09-03 10:08vmromanosNote Added: 0131544
2021-09-03 10:08vmromanosStatusscheduled => closed
2021-09-03 10:08vmromanosResolutionopen => duplicate

Notes
(0131544)
vmromanos   
2021-09-03 10:08   
The issue has been fixed with 0047102