Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0018328 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
backport | [Openbravo ERP] Z. Others | major | always | 2011-08-12 15:23 | 2011-08-24 11:53 | |||
Reporter | mirurita | View Status | public | |||||
Assigned To | mirurita | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | ||||
Status | closed | Fix in branch | 2.50 | Fixed in SCM revision | 8c201739ffa1 | |||
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 | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0018328: AlertsForWrongInvoices not taking in account VOID payment schedule details | |||||||
Description | After the new status included in payments (void), the sum of the payment schedule details don't have to match with the payment schedule amount. You can have the following scenario in which an invoice has been included in a payment and then this payment voided. The status in the database is the following: Invoice Payment Schedule = 100 Payment Schedule Detail = 100 Payment Schedule Detail = 100 (voided) That's why the new rule is: sum of the not voided payment schedule details have to match with the payment schedule amount. The alert (AlertsForWrongInvoices) included in APRM for detecting discrepancies must be updated to take in account voided payment schedule details. | |||||||
Steps To Reproduce | 1) Create invoice 1 (100€) 2) Pay completely invoice 1 with a payment method configured to be deferred (Awaiting Execution) 3) Void this payment 4) You will see the alert. | |||||||
Proposed Solution | Ignore voided payment schedule details in the alert query. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0040386) hgbot (developer) 2011-08-22 13:59 |
Repository: erp/pmods/org.openbravo.advpaymentmngt Changeset: 8c201739ffa1fabdd0c26b3bf2b2050fc73887bb Author: Mikel Irurita <mikel.irurita <at> openbravo.com> Date: Mon Aug 22 13:57:55 2011 +0200 URL: http://code.openbravo.com/erp/pmods/org.openbravo.advpaymentmngt/rev/8c201739ffa1fabdd0c26b3bf2b2050fc73887bb [^] Fixes issue 18328: AlertsForWrongInvoices not taking in account VOID payment schedule details --- M build/classes/org/openbravo/advpaymentmngt/modulescript/AlertsForWrongInvoices.class M build/classes/org/openbravo/advpaymentmngt/modulescript/AlertsForWrongInvoicesData.class M src-util/modulescript/src/org/openbravo/advpaymentmngt/modulescript/AlertsForWrongInvoices.java M src-util/modulescript/src/org/openbravo/advpaymentmngt/modulescript/AlertsForWrongInvoices_data.xsql M src-util/modulescript/src/src/org/openbravo/advpaymentmngt/modulescript/AlertsForWrongInvoicesData.java --- |
(0040478) psanjuan (manager) 2011-08-24 11:53 |
fixed and working |
Issue History | |||
Date Modified | Username | Field | Change |
2011-08-19 14:46 | mirurita | Type | defect => backport |
2011-08-19 14:46 | mirurita | fix_in_branch | => 2.50 |
2011-08-22 13:59 | hgbot | Checkin | |
2011-08-22 13:59 | hgbot | Note Added: 0040386 | |
2011-08-22 13:59 | hgbot | Status | scheduled => resolved |
2011-08-22 13:59 | hgbot | Resolution | open => fixed |
2011-08-22 13:59 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/pmods/org.openbravo.advpaymentmngt/rev/8c201739ffa1fabdd0c26b3bf2b2050fc73887bb [^] |
2011-08-24 11:53 | psanjuan | Note Added: 0040478 | |
2011-08-24 11:53 | psanjuan | Status | resolved => closed |
Copyright © 2000 - 2009 MantisBT Group |