Project:
| View Revisions: Issue #39618 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0039618: Cash Up goes to Errors While Importing POS Data if the currency has more than 2 decimals and negative total | ||
| Revision | 2018-11-15 09:32 by ngarcia | ||
| Steps To Reproduce | In the backend: Configure a POS Terminal to be used with OMR (check that precision that will be used in POS is higher than 2) In the POS: Create a return of 0.009 Do the cash up Leave the amount to keep to 0 In the backend: Check a new Cash Up record is shown in Errors While Importing POS Data with the following error: current transaction is aborted, commands ignored until end of transaction block The log shows: ERROR org.hibernate.util.JDBCExceptionReporter - Batch entry 0 insert into FIN_Finacc_Transaction (AD_Client_ID, AD_Org_ID, Created, Createdby, Updated, Updatedby, Isactive, C_Currency_ID, Fin_Financial_Account_ID, Line, DateAcct, C_Glitem_ID, Status, Paymentamt, Depositamt, Processed, Processing, Posted, Trxtype, Statementdate, Description, CreatedByAlgorithm, EM_APRM_Modify, EM_Aprm_Processed, EM_Obpos_App_Cashup_ID, Fin_Finacc_Transaction_ID) values (...) was aborted. Call getNextException to see the cause. 40f8540e 2018-11-13 12:22:57,005 [ajp-bio-127.0.0.1-8009-exec-9835] ERROR org.hibernate.util.JDBCExceptionReporter - ERROR: new row for relation "fin_finacc_transaction" violates check constraint "fin_trans_amounts_chk" |
||
| Revision | 2018-11-15 09:26 by ngarcia | ||
| Steps To Reproduce | In the backend: Configure a POS Terminal to be used with OMR (check that precision that will be used in POS is higher than 2) In the POS: Create a return with more than 2 decimals Do the cash up Leave the amount to keep to 0 In the backend: Check a new Cash Up record is shown in Errors While Importing POS Data with the following error: current transaction is aborted, commands ignored until end of transaction block The log shows: ERROR org.hibernate.util.JDBCExceptionReporter - Batch entry 0 insert into FIN_Finacc_Transaction (AD_Client_ID, AD_Org_ID, Created, Createdby, Updated, Updatedby, Isactive, C_Currency_ID, Fin_Financial_Account_ID, Line, DateAcct, C_Glitem_ID, Status, Paymentamt, Depositamt, Processed, Processing, Posted, Trxtype, Statementdate, Description, CreatedByAlgorithm, EM_APRM_Modify, EM_Aprm_Processed, EM_Obpos_App_Cashup_ID, Fin_Finacc_Transaction_ID) values (...) was aborted. Call getNextException to see the cause. 40f8540e 2018-11-13 12:22:57,005 [ajp-bio-127.0.0.1-8009-exec-9835] ERROR org.hibernate.util.JDBCExceptionReporter - ERROR: new row for relation "fin_finacc_transaction" violates check constraint "fin_trans_amounts_chk" |
||
| Revision | 2018-11-14 15:59 by ngarcia | ||
| Steps To Reproduce | In the backend: Configure a POS Terminal to be used with OMR (check that precision that will be used in POS is higher than 2) In the POS: Create a return Do the cash up Leave the amount to keep to 0 In the backend: Check a new Cash Up record is shown in Errors While Importing POS Data with the following error: current transaction is aborted, commands ignored until end of transaction block The log shows: ERROR org.hibernate.util.JDBCExceptionReporter - Batch entry 0 insert into FIN_Finacc_Transaction (AD_Client_ID, AD_Org_ID, Created, Createdby, Updated, Updatedby, Isactive, C_Currency_ID, Fin_Financial_Account_ID, Line, DateAcct, C_Glitem_ID, Status, Paymentamt, Depositamt, Processed, Processing, Posted, Trxtype, Statementdate, Description, CreatedByAlgorithm, EM_APRM_Modify, EM_Aprm_Processed, EM_Obpos_App_Cashup_ID, Fin_Finacc_Transaction_ID) values (...) was aborted. Call getNextException to see the cause. 40f8540e 2018-11-13 12:22:57,005 [ajp-bio-127.0.0.1-8009-exec-9835] ERROR org.hibernate.util.JDBCExceptionReporter - ERROR: new row for relation "fin_finacc_transaction" violates check constraint "fin_trans_amounts_chk" |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |