Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002377Openbravo ERP09. Financial managementpublic2007-12-17 13:322008-12-17 11:09
Reporterpjuvara 
Assigned Tormorley 
PrioritynormalSeveritymajorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionpiFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0002377: Accounting report do not honor account translations
DescriptionPROBLEM DESCRIPTION
===================
The Account Elements support multiple languages. It is therefore possible to associate multiple translations to the account name and description.
For example:
 Account No: 70000
In Spanish: Ventas de mercaderías
In English: Sales revenue

It appears that all the accounting reports pick the name and description from the main table rather than from the translation table and therefore always show the account name in the base language.

ENVIRONMENT
===========
Openbravo 2.35 Community Edition

HOW TO REPRODUCE
================
1) Define a translation for an account element
2) When you manually enter a GL Journal you can see the translated value
3) When you run a report, you can still see the base language.
Steps To Reproduce
Proposed Solution
Additional Information
Tagstranslation
Relationships
related to design defect 0019365 new dmiguelez There should be an ability to reference Chart of Accounts module data from other modules 
blocks feature request 0004058 acknowledged rmorley Translation management 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-13 19:48psarobeSeverityminor => major
2008-06-13 19:48psarobeDescription Updated
2008-06-13 19:51psarobeStatusnew => scheduled
2008-06-13 19:58cromeroTarget Version => 2.40
2008-06-17 11:42pjuvaraAssigned Todalsasua => pheenan
2008-06-17 11:42pjuvaraTypedefect => feature request
2008-06-17 11:42pjuvaraFixed in Version2.40 =>
2008-06-17 11:42pjuvaraTarget Version2.40 => 2.50
2008-06-19 09:22pjuvaraStatusscheduled => feedback
2008-06-19 09:22pjuvaraStatusfeedback => new
2008-06-19 09:22pjuvaraStatusnew => acknowledged
2008-06-19 09:24pjuvaraRelationship addedblocks 0004058
2008-06-24 18:29pjuvaraTarget Version2.50 =>
2008-06-25 08:54pheenanTag Attached: translation
2008-09-24 15:57rafarodaAssigned Topheenan => rafaroda
2008-09-24 15:57rafarodaStatusacknowledged => scheduled
2008-09-24 15:57rafarodaTarget Version => 2.50
2008-11-03 13:48pjuvaraTarget Version2.50 => 2.60
2008-11-10 14:25rafarodaAssigned Torafaroda => pjuvara
2008-11-21 16:45pjuvaraStatusscheduled => acknowledged
2008-11-21 17:05pjuvaraTarget Version2.60 => trunk
2008-12-17 11:09pjuvaraAssigned Topjuvara => rmorley
2011-12-26 18:04dmitry_mezentsevRelationship addedrelated to 0019365

Notes
(0005966)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1852265 [^]
(0002813)
cromero   
2008-06-03 19:18   
(edited on: 2008-06-12 09:23)
Logged In: YES
user_id=1500614
Originator: NO

It is not useful to translate accounting elements, because account names are linked to accounting issues of the country, and translate may not be possible.
(0002814)
pjuvara   
2008-06-03 19:45   
(edited on: 2008-06-12 09:23)
Logged In: YES
user_id=1871571
Originator: YES

REOPENING.

I disagree. A corporate chart of accounts might consolidate across different countries and different languages and need to support multiple language translations.

The product is designed to support this feature: If you go to Financial Managment > Setup > Account Tree, you can see that Element Values have Translations.

Why don't we honor this?