Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005884Openbravo ERP09. Financial managementpublic2008-11-09 19:292008-12-15 15:29
Reportergalderromo 
Assigned Todalsasua 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS20OS VersionGentoo 2.6.24
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0005884: Spanish bank rule 34: Does not manage business partner bank accounts properly
DescriptionWhen a business partner has more than a bank account registered on the application, and the user creates a payment 34 bank rule, the generated file includes as payment per registered bank account.

It doesn't matter if the banks are active or not.
Steps To ReproduceRegister a business partner with 3 bank accounts.
Register a purchase invoice to this business partner.
Create an Spanish Cuaderno34 an include the debt payment from the previous invoice.
Process the remittance.
Generate the file.
Check you are paying 3 times the same person.
Proposed SolutionCheck the business partner has only an active bank account.
Throw an error if more than one bank is registered for any business partner on the remittance and do not generate the file.
Specify which business partners creates the exception.
The user will make sure a single bank account is activated for this business partner.
Make sure, the generated file, just includes a line per each activated bank account.
Additional Information
TagsNo tags attached.
Relationships
duplicate of backport 0005797 closed vmromanos CreateFile creates several lines for each remittance line 
blocks defect 0005880 closed dalsasua Spanish bank rule 34: Does not manage business partner bank accounts properly 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-11-09 19:29psarobeNew Issue
2008-11-09 19:29psarobeAssigned To => dalsasua
2008-11-09 19:29psarobeStatusnew => scheduled
2008-11-27 17:37dalsasuaProjectOpenbravo ERP => Localization Pack: Spain
2008-11-27 17:41jpabloaeProjectLocalization Pack: Spain => Openbravo ERP
2008-11-30 18:09galderromoNote Added: 0010827
2008-12-02 11:01dalsasuaNote Added: 0010870
2008-12-02 11:01dalsasuaStatusscheduled => feedback
2008-12-02 23:27galderromoNote Added: 0010918
2008-12-15 15:28dalsasuaNote Added: 0011372
2008-12-15 15:29dalsasuaRegression testing => No
2008-12-15 15:29dalsasuaRelationship addedduplicate of 0005797
2008-12-15 15:29dalsasuaStatusfeedback => closed
2008-12-15 15:29dalsasuaDuplicate ID0 => 5797
2008-12-15 15:29dalsasuaResolutionopen => duplicate

Notes
(0010827)
galderromo   
2008-11-30 18:09   
The process should also check the fields have the correct length. For example, check the postal code has 5 characters. Otherwise, the file won't be created correctly.
(0010870)
dalsasua   
2008-12-02 11:01   
Hi Galder,

Does this solution fit your needs: https://issues.openbravo.com/view.php?id=5797 [^] ?

Regards.
(0010918)
galderromo   
2008-12-02 23:27   
It does fit if:
- Makes sure the length of each field is what should be.
- Throws an exception when a business partner on the remittance has no bank account.
- Throws and exception when a business partner on the remittance has more than an active bank account.
(0011372)
dalsasua   
2008-12-15 15:28   
QA asks me to close the bug, confirming that was fixed at the same time than the backport 0005797.