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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0020294
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 09. Financial managementmajoralways2012-04-17 20:452015-05-13 17:08
ReportervmromanosView Statuspublic 
Assigned ToTriage Omni OMS 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_12
OS VersionDebian 5.0Database version8.3.8Ant version1.7.0
Product VersionSCM revision 
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
Summary

0020294: Updating Organization in Accounting Schema window

DescriptionWhen updating the Organization in the header of the Accounting Schema window, this change is not propagated to the window tabs creating wrong data in the database.

Example:
1. Run an Initial Org setup. Create org A with accounting
2. Run an Initial Org setup. Create org B with accounting
3. Go to Accounting Schema window.
4. Select A acct. schema and change its organization to B
5. See records in Accounting Schema Tables tab belong to A. (you should query the database, or display the organization field for this tab in the Application Dictionary)
Steps To Reproduce1. Run an Initial Org setup. Create org A with accounting
2. Run an Initial Org setup. Create org B with accounting
3. Go to Accounting Schema window.
4. Select A acct. schema and change its organization to B
5. See records in Accounting Schema Tables tab belong to A. (you should query the database, or display the organization field for this tab in the Application Dictionary)
Proposed SolutionTwo possible solutions to be discussed:
1. Don't allow to modify organization field in the header
2. Propagate the change to the rest of the tabs in that window. Check whether this acct. schema is already use in the Org. Schema tab (Organization window) and this change makes sense for that configuration
TagsMIR-Reviewed
Attached Filesdiff file icon bug_20294.diff [^] (40,252 bytes) 2015-05-13 17:08 [Show Content]

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0020254 closededuardo_Argal Multi accounting schema is not working properly in some circunstances 

-  Notes
(0048891)
naiaramartinez (viewer)
2012-05-23 17:47

 Go to Accounting Schema window. Select one record.
Go to all its child's tab. Create new record. Notice that you can't see/modify organization field. By default selected organization is parent organization, so child always have parent's organization.

Test Plan (build validation)
   
    Before applying the fix you need to have incorrect records in 'Account Schema Element', 'Account Schema Tables', 'Process', 'General Ledger' and 'Defaults' tabs. Those tabs are child tabs of Accounting Schema.
    So, go to database and insert an incorrect record in C_AcctSchema_Table, C_AcctSchema_Table_DocType, C_AcctSchema_Process, C_AcctSchema_GL and C_AcctSchema_Default. You need to insert a diferent organization than its c_AcctSchema's organization.
    Apply the fix.
    Run ant smartbuild -Dlocal=no.
    The compilation should fail (the record that you inserted and two records that were incorrect for QA client).
    Go to application as client admin role.
    Browse to the wrong records. You need to correct those incorrect record in the database (because in the application you can't modify the organization).
    After correcting them, run ant smartbuild -Dlocal=no again.
    The complication should go fine.
(0077403)
naiaramartinez (viewer)
2015-05-13 17:07

 I attach a solution made in 2012, but I don't know if it still will work or not.
The main problem here, is that Openbravo allows you to have headers with one organization and children with different organization. For example:
  * Go to 'General Ledger Configuration' (this window is the same as Account schema. The window was renamed)
  * create a record with 'Region norte' organization
  * Go to 'dimension' tab and create one record
  * Go to header again, and modify organization to 'Region Sur'.
  * Do a select in the bbdd, and notice that the organzation of the record created in dimesion tab, is still 'Region Norte'

- Issue History
Date Modified Username Field Change
2012-04-17 20:45 vmromanos New Issue
2012-04-17 20:45 vmromanos Assigned To => vmromanos
2012-04-17 20:45 vmromanos Modules => Core
2012-04-17 20:45 vmromanos OBNetwork customer => No
2012-04-17 20:45 vmromanos Relationship added related to 0020254
2012-04-19 18:43 mirurita Tag Attached: MIR-Reviewed
2012-05-10 12:12 gorka_gil Assigned To vmromanos => mirurita
2012-05-22 17:25 naiaramartinez Assigned To mirurita => naiaramartinez
2012-05-22 17:26 naiaramartinez Status new => scheduled
2012-05-22 17:26 naiaramartinez fix_in_branch => pi
2012-05-23 17:47 naiaramartinez Note Added: 0048891
2015-05-13 16:58 naiaramartinez Assigned To naiaramartinez => Triage Finance
2015-05-13 17:07 naiaramartinez Note Added: 0077403
2015-05-13 17:08 naiaramartinez File Added: bug_20294.diff

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker