0017940: Payment Report: wrong subtotal amounts by status

Description

The Payment Report does not add up properly at subtotal level for the same status. In fact, the report does not differentiate between payments in and out for the same status.
After checking the corresponding wiki information (http://wiki.openbravo.com/wiki/Projects/PaymentReport/User_Documentation#Sub_Totals [^]) we have detected that there are the same status for both payments in and out. So, the report should differentiate the document type when there is a subtotal.

Steps To Reproduce

To reply the bug please follows the following steps in the example:
NOTE: the following example is already created in the client TEST and PRODUCTIVE environment version 2.50+MP28.
Create the following data:
• Payment Method to use: Write transfer (same configuration for payment in/out):
 Payment In Allowed: marked
 Execution Type: Manual
 Upon Reconciliation Use: Cleared Payment Account
• Business partner both: customer and vendor.
• Purchase Invoice - total amount: 150 €. Transaction and accounting date: 20-06-2011
• Sales Invoice – total amount: 200 € Transaction and accounting date: 20-06-2011
Once all these data have been registered into the system follow the following steps:
A. Financial Management || Receivables & Payables || Analysis Tools || Payment Report || Payment Report
1. Filter by:
 Organization: the regarding one
 Business partner: the created above.
 Cover to currency: the regarding to the invoices created
 Payment type: receivables and payables
 Ordering criteria: by date
2. Press button “Search” >> see attached the result:
3. Subtotal Awaiting Payment: once is a sales invoice (354,43 €) and the other is a purchase invoice (117,00 €). However, there is not possible to differentiate both. There should be a column to differentiate if it is a payment in or out. The subtotal for this status should be the subtraction but not the sum.
4. The same happens with other status like Subtotal Remittance in this example: as you can check in this example these remittance payments are AP Payments. Therefore, the subtotal should have to take into account the document type.

Proposed Solution

The subtotal should have to take into account the document type. The subtotal for an specific status should be the subtraction but not the sum base on the document type.

Finally, is the Grand Total amount should differentiate to amounts: payment in and payment out. This way, there final result should have sense.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

blocks

defect

0017797

closed

ioritzCia

Openbravo ERP

Payment Report: wrong subtotal amounts by status

Notes
(0038957) hgbot (developer) 2011-07-11 09:39	Repository: erp/mods/org.openbravo.financial.paymentreport Changeset: 1c15028d05489fdee15e59ecb4a509f31b6cf8c1 Author: Ioritz Cia <ioritz.cia <at> openbravo.com> Date: Fri Jul 08 14:48:26 2011 +0200 URL: http://code.openbravo.com/erp/mods/org.openbravo.financial.paymentreport/rev/1c15028d05489fdee15e59ecb4a509f31b6cf8c1 [^] Fixes issue 17940: Payment Report: wrong subtotal amounts by status. --- M src/org/openbravo/financial/paymentreport/erpCommon/ad_reports/PaymentReportDao.java ---

(0038997) dalsasua (reporter) 2011-07-11 18:27	Verified.

Issue History
Date Modified	Username	Field	Change
2011-07-08 14:13	ioritzCia	Type	defect => backport
2011-07-08 14:13	ioritzCia	fix_in_branch	=> 2.50
2011-07-11 09:39	hgbot	Checkin
2011-07-11 09:39	hgbot	Note Added: 0038957
2011-07-11 09:39	hgbot	Status	scheduled => resolved
2011-07-11 09:39	hgbot	Resolution	open => fixed
2011-07-11 09:39	hgbot	Fixed in SCM revision	=> http://code.openbravo.com/erp/mods/org.openbravo.financial.paymentreport/rev/1c15028d05489fdee15e59ecb4a509f31b6cf8c1 [^]
2011-07-11 09:58	dalsasua	Priority	immediate => high
2011-07-11 09:58	dalsasua	Severity	critical => major
2011-07-11 18:26	dalsasua	Project	Openbravo ERP => Modules
2011-07-11 18:27	dalsasua	Category	09. Financial management => Payment Report
2011-07-11 18:27	dalsasua	fix_in_branch	2.50 =>
2011-07-11 18:27	dalsasua	Note Added: 0038997
2011-07-11 18:27	dalsasua	Status	resolved => closed
2011-07-11 18:27	dalsasua	Fixed in Version	=> 1.1.3