Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0011095 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 09. Financial management | major | always | 2009-10-22 17:50 | 2011-10-28 12:57 | |||
Reporter | OlliJT | View Status | public | |||||
Assigned To | vmromanos | |||||||
Priority | high | Resolution | out of date | Fixed in Version | pi | |||
Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
Projection | none | ETA | none | Target Version | ||||
OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_11 | |||
OS Version | rPath Linux | Database version | 8.3.5 | Ant version | 1.7.1 | |||
Product Version | 2.40MP10 | 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 | 0011095: Error in handling write-offs when cancelling payments in settlement | |||||||
Description | If the write-off is left empty, processing of the settlement fails. Follow the steps. | |||||||
Steps To Reproduce | 1. Create a new settlement. 2. Open the pop-up window to select payments to cancel. 3. Select a payment and make the write-off field empty. 4. Create a corresponding payment in the created side. 5. Try to process the settlement. The last step fails because the write-off field of the canceled payment is empty, which is not taken into account by the procedure. | |||||||
Proposed Solution | Change in one row in the c_settlement_post function. Original: SELECT COALESCE(SUM(C_Currency_Round( C_Currency_Convert((Amount - WriteOffAmt), C_Currency_ID, v_Currency, v_Date, NULL, v_AD_Client_ID, v_AD_Org_ID), v_Currency, NULL)), 0), Fixed: SELECT COALESCE(SUM(C_Currency_Round( C_Currency_Convert((Amount - COALESCE(WriteOffAmt, 0)), C_Currency_ID, v_Currency, v_Date, NULL, v_AD_Client_ID, v_AD_Org_ID), v_Currency, NULL)), 0), | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0042224) dmitry_mezentsev (developer) 2011-10-28 12:57 |
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed. Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription. You can find more details about our Support policy in the following blog post http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^] |
Issue History | |||
Date Modified | Username | Field | Change |
2009-10-22 17:50 | OlliJT | New Issue | |
2009-10-22 17:50 | OlliJT | Assigned To | => rafaroda |
2009-10-22 18:27 | villind | Issue Monitored: villind | |
2009-10-23 06:53 | rafaroda | Assigned To | rafaroda => vmromanos |
2009-10-23 06:53 | rafaroda | Priority | normal => high |
2009-10-23 06:54 | rafaroda | Status | new => scheduled |
2009-10-23 06:54 | rafaroda | fix_in_branch | => pi |
2011-10-28 12:57 | dmitry_mezentsev | Note Added: 0042224 | |
2011-10-28 12:57 | dmitry_mezentsev | Status | scheduled => closed |
2011-10-28 12:57 | dmitry_mezentsev | Resolution | open => out of date |
2011-10-28 12:57 | dmitry_mezentsev | Fixed in Version | => pi |
Copyright © 2000 - 2009 MantisBT Group |