Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0013002
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 02. Master data managementmajoralways2010-04-15 10:152011-09-16 11:14
ReporterszimmermannView Statuspublic 
Assigned Tojonalegriaesarte 
PrioritynormalResolutionunable to reproduceFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionCommunity ApplianceDatabase version8.3.9Ant version1.7.1
Product Version2.50MP11SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0013002: Business-Partner Customer/Vendor-Accounts are created twice when adding a Business-Partner

DescriptionOnly one Account per accounting scheme schould be allowed.
It could happen, that the Trigger c_bpartner_trg finds more than 1 account in the cursor.
This is dangerous, because more than 1 Account leads to ssevere subsequent errors when making transactions with the Business Partner.
Steps To ReproduceCreate a Business Partner. With german accounting Scheme always 2 Accounts are created.
Proposed Solution1. Modify the unique Index c_bp_customer_acct_bpartner_un without status.Now It contains the status.
2. The field status seems not to be implemented consistantly in the system. Status has No Check-Constraint and can be null-That's dangerous, because the unique Index will not work on null-Columns.
2. Modify c_bpartner_trg: It sould only create one account per business Partner and accounting scheme as default.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0041007)
psarobe (manager)
2011-09-16 11:14

The status must be kept in 2.50 but in any case we are not able to reproduce. For 3.0 this issues does not apply (status are only for 2.50) so we encourage you to upgrade to 3.0

- Issue History
Date Modified Username Field Change
2010-04-15 10:15 szimmermann New Issue
2010-04-15 10:15 szimmermann Assigned To => adrianromero
2010-04-15 10:16 szimmermann Issue Monitored: szimmermann
2011-06-03 10:59 dalsasua Assigned To adrianromero => dalsasua
2011-07-20 18:12 dalsasua Assigned To dalsasua => jonalegriaesarte
2011-09-16 11:14 psarobe Note Added: 0041007
2011-09-16 11:14 psarobe Status new => closed
2011-09-16 11:14 psarobe Resolution open => unable to reproduce


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker