Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0012225 | Openbravo ERP | 02. Master data management | public | 2010-02-11 11:20 | 2010-05-18 12:12 |
|
| Reporter | networkb | |
| Assigned To | harikrishnan | |
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.50MP11 | |
| Target Version | 2.50MP17 | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0012225: Error when copying accounting configuration from BP group |
| Description | In BP category > Accounting, it is possible to define multiple combinations for Accounting Schema, status, etc.
However, if same accounting schema and status is used, an error is shown:
c_bp_customer_acct_bpartner_un constraint fails.
Revising this constraint, is BP + Acct. Schema + Status.
The problem comes from C_BPartner_trg, first query returns duplicated records (Cur_Default)
Note: in order to reproduce this bug, it is really important to have fixed this bug:
https://issues.openbravo.com/view.php?id=11526 [^]
|
| Steps To Reproduce | Go to General Setup > Enterprise > Organization.
Search * Organization.
Go to Org Schema tab.
Create a new record, and select Smallbazzar accounting schema.
Go to Master Data Management > Business Partner Setup > Business Partner Category.
Create a new one.
Go to Accounting tab.
Create a new record, for * organization and Smallbazaar accounting schema.
Select accounts (any) with * organization.
Select an status.
Create other record, for * organization and Smallbazaar accounting schema.
Select diferent accounts with * organization.
Select other status.
Create another record, for * organization and Smallbazaar accounting schema.
Select diferent accounts with * organization.
Select another status.
Go to Master Data Management > Business Partner. Create a new one, and select the previous BP category.
Save it. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0011526 | 2.50MP11 | closed | vinothbabu | A BP only inherits one accounting of its BP category | | related to | defect | 0012588 | 2.50MP14 | closed | rajagopal | If the same accounting schema is assigend for more than one org, a vendor is created with many entries on the accounting tab | | related to | defect | 0013636 | 2.50MP19 | closed | adrianromero | If the same accounting schema is assigned for more than one org, a vendor is created with many entries on the accounting tab |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2010-02-11 11:20 | networkb | New Issue | |
| 2010-02-11 11:20 | networkb | Assigned To | => adrianromero |
| 2010-02-23 09:19 | networkb | Note Added: 0024723 | |
| 2010-02-23 09:19 | networkb | Status | new => feedback |
| 2010-02-24 18:06 | networkb | Note Added: 0024796 | |
| 2010-02-24 18:06 | networkb | Status | feedback => new |
| 2010-02-24 18:06 | networkb | Proposed Solution updated | |
| 2010-02-25 10:49 | adrianromero | Note Added: 0024809 | |
| 2010-02-25 10:52 | adrianromero | Status | new => scheduled |
| 2010-02-25 10:52 | adrianromero | fix_in_branch | => pi |
| 2010-03-08 16:05 | jpabloae | Target Version | 2.50MP14 => 2.50MP15 |
| 2010-04-07 18:23 | adrianromero | Note Added: 0025957 | |
| 2010-04-13 10:32 | networkb | fix_in_branch | pi => |
| 2010-04-13 10:32 | networkb | Description Updated | bug_revision_view_page.php?rev_id=229#r229 |
| 2010-04-13 10:32 | networkb | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=231#r231 |
| 2010-04-14 15:43 | dmitry_mezentsev | Note Added: 0026189 | |
| 2010-04-14 17:13 | adrianromero | Relationship added | related to 0011526 |
| 2010-04-22 06:22 | harikrishnan | Assigned To | adrianromero => harikrishnan |
| 2010-04-22 06:22 | hgbot | Checkin | |
| 2010-04-22 06:22 | hgbot | Note Added: 0026554 | |
| 2010-04-22 06:22 | hgbot | Status | scheduled => resolved |
| 2010-04-22 06:22 | hgbot | Resolution | open => fixed |
| 2010-04-22 06:22 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/ff1c64d7f68b5d987c47baa8f0e67f173ce5bcd4 [^] |
| 2010-04-22 06:43 | harikrishnan | Note Added: 0026557 | |
| 2010-04-22 11:25 | dmitry_mezentsev | Note Added: 0026562 | |
| 2010-04-22 11:57 | adrianromero | Relationship added | related to 0012588 |
| 2010-04-22 12:01 | adrianromero | Note Added: 0026567 | |
| 2010-04-22 12:01 | adrianromero | Note Edited: 0026567 | bug_revision_view_page.php?bugnote_id=0026567#r258 |
| 2010-04-22 12:11 | dmitry_mezentsev | Note Added: 0026568 | |
| 2010-04-22 16:15 | dmitry_mezentsev | Note Added: 0026580 | |
| 2010-05-03 17:00 | sureshbabu | Note Added: 0026878 | |
| 2010-05-03 17:00 | sureshbabu | Status | resolved => closed |
| 2010-05-04 00:00 | anonymous | sf_bug_id | 0 => 2996190 |
| 2010-05-14 15:27 | hudsonbot | Checkin | |
| 2010-05-14 15:27 | hudsonbot | Note Added: 0027265 | |
| 2010-05-18 12:12 | gorka_gil | Target Version | 2.50MP15 => 2.50MP17 |
| 2010-06-14 16:04 | adrianromero | Relationship added | related to 0013636 |
|
Notes |
|
|
|
|
Pending feedback from NPE |
|
|
|
|
When posting, only Account Schema is taken into account, so it does not make sense to define diferent combinations with same Accounting schema and diferent organization.
It should be avoided. |
|
|
|
|
|
The solution in this case is to add the same constraint of the table c_bp_customer_acct in the table c_bp_category. |
|
|
|
|
The previous proposed solution is not correct
The problem is that it is possible to define same configuration (Acct Schema + Status) for * and other Organization. But this should not be possible because of the constraint c_bp_customer_acct_bpartner_un .
It should be reviewed why this constraint does not work as expected. |
|
|
|
|
Adrian,
Could you please in-line with this issue have a look at the 11526?
It is marked as Closed but I failed to complete this flow. In my case only one accounting configuration was created for a BP which has several accounting records in BP Category.
I would like this issue to be checked course fix of current one does not make sense without 11526.
Thanks. |
|
|
|
(0026554)
|
|
hgbot
|
|
2010-04-22 06:22
|
|
|
|
|
|
Steps to test:
*Follow the steps to reproduce of these issues 11526,12588.
Reason for the fix
*A condition is added to avoid the insert of similar data where their is constraint in these 2 tables. |
|
|
|
|
Hari,
Above in the protocol I asked to review previous issue - 11526. I followed the steps described in it in live.builds postgresql and the result was not coping 2 Accounting configurations I created to BP.
You can have a look at Vendor BP Category there and BP - DM Category Test.
Thanks. |
|
|
|
|
The problem here is that the fix for issue 12588 reverted the changes reverted the fix done in 1152. But now with the fix provided by Hari all issues related should be fixed.
Hari, could you confirm that?
|
|
|
|
|
|
Thanks, Adrian. We had a chat with Hari and he confirmed that. |
|
|
|
|
|
My tests went well. Thanks. |
|
|
|
|
|
|
|
|
|