Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0005856Openbravo ERP09. Financial managementpublic2008-11-06 14:132009-06-05 18:59
networkb 
dalsasua 
immediatemajoralways
closedfixed 
10
2.35MP7 
 
Core
No
0005856: G/L entry does not work with multiple Accounting Schema
If a new GL/entry is created selecting in the Header an Accounting Schema (it is supposed it exist more than one) is selected, in Lines tab, Account selector does not take into account the Accounting Schema selected in the Header.
1) Create a second accounting schema in 'Financial Management || Accounting || Setup || Accounting Schema'.
2) Add some elements to this new accounting schema in 'Account Schema Element' tab.
3) Go to 'General Setup || Client || Client' and select yours.
4) Inside 'Information' tab, tick 'Second Accounting Schema' check-box and select the recently created accounting schema.
5) Go to 'Financial Management || Accounting || Transactions || G/L Journal || Batch' and create a new record.
6) Move to 'Header' tab and create a new record, selecting the recently created accounting schema.
7) Go to 'Lines' tab and click on 'Accounting Combination' icon.

Notice that the account selector is not taking into account header's accounting schema since it is displaying client primary accounting schema's elements.
No tags attached.
depends on backport 0005857 closed dalsasua G/L entry does not work with multiple Accounting Schema 
depends on backport 0005858 closed dalsasua G/L entry does not work with multiple Accounting Schema 
Issue History
2008-11-06 14:13networkbNew Issue
2008-11-06 14:13networkbAssigned To => rafaroda
2008-11-06 14:13networkbsf_bug_id0 => 2229542
2008-11-06 14:13networkbRegression testing => No
2008-11-06 14:13networkbIssue Monitored: networkb
2008-11-06 15:21networkbOS5 => 10
2008-11-06 15:21networkbversion => 2.35MP7
2008-11-06 15:44rafarodaProposed Solution updated
2008-11-06 15:51rafarodaStatusnew => scheduled
2008-11-06 15:51rafarodaAssigned Torafaroda => dalsasua
2008-11-06 15:51rafarodafix_in_branch => trunk
2008-11-07 11:52svnbotCheckin
2008-11-07 11:52svnbotNote Added: 0010075
2008-11-07 11:52svnbotStatusscheduled => resolved
2008-11-07 11:52svnbotResolutionopen => fixed
2008-11-07 11:52svnbotsvn_revision => 9780
2008-12-16 16:58psarobeStatusresolved => new
2008-12-16 16:58psarobeResolutionfixed => open
2008-12-16 16:58psarobeStatusnew => scheduled
2008-12-17 10:41svnbotCheckin
2008-12-17 10:41svnbotNote Added: 0011470
2008-12-17 10:41svnbotStatusscheduled => resolved
2008-12-17 10:41svnbotResolutionopen => fixed
2008-12-17 10:41svnbotsvn_revision9780 => 11288
2008-12-22 18:15svnbotCheckin
2008-12-22 18:15svnbotNote Added: 0011677
2008-12-22 18:15svnbotsvn_revision11288 => 11506
2009-04-21 11:09psarobeStatusresolved => closed
2009-06-05 18:59DavidVNote Added: 0017052
2009-06-05 19:00DavidVIssue Monitored: DavidV

Notes
(0010075)
svnbot   
2008-11-07 11:52   
Repository: openbravo
Revision: 9780
Author: davidalsasua
Date: 2008-11-07 11:52:42 +0100 (Fri, 07 Nov 2008)

Fixes Bug 0005856: G/L entry does not work with multiple Accounting Schema

---
U trunk/src-db/database/sourcedata/AD_COLUMN.xml
---

https://dev.openbravo.com/websvn/openbravo/?rev=9780&sc=1 [^]
(0011470)
svnbot   
2008-12-17 10:41   
Repository: openbravo
Revision: 11288
Author: davidalsasua
Date: 2008-12-17 10:41:13 +0100 (Wed, 17 Dec 2008)

Fixes Bug 0005856: G/L entry does not work with multiple Accounting Schema

---
U trunk/src/org/openbravo/erpCommon/info/Account.java
U trunk/src/org/openbravo/erpCommon/info/Account_data.xsql
---

https://dev.openbravo.com/websvn/openbravo/?rev=11288&sc=1 [^]
(0011677)
svnbot   
2008-12-22 18:15   
Repository: openbravo
Revision: 11506
Author: davidalsasua
Date: 2008-12-22 18:15:52 +0100 (Mon, 22 Dec 2008)

Fixes Bug 0005856: G/L entry does not work with multiple Accounting Schema

---
U trunk/src/org/openbravo/erpCommon/info/Account.java
---

https://dev.openbravo.com/websvn/openbravo/?rev=11506&sc=1 [^]
(0017052)
DavidV   
2009-06-05 18:59   
May I ask what is the satus of this issue?
It was put to pi on 21.12.2008.
Now, it is closed, but it is not in production (2.50 MP1).

I experience the same problem in 2.50 MP1 ...

Thank you
David