I found out that translation manager doesn’t let you translate UNX’s in SAP BI 4.0 suite. (They just don’t show when you try to import one from the tool)
Am I correct or am I missing something? And Why?
Tiny 
(BOB member since 2004-11-10)
crapy the crap crap crap!
1.6 About translating universes from the information design tool
Universes generated by the information design tool are not directly translated. Translation management
tool can independently translate the data foundations or business layers created by the information
design tool. These resources can be located on local information design tool projects or on shared
information design tool projects stored in the CMS repository.
Once these resources are translated, use the information design tool to republish the universe that will
contain these translations.
source: http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_translation_management_tool_en.pdf
Tiny (BOB member since 2004-11-10)
well… I’ll have to revise my earlier findings:
It’s not that bad… but I preferred the way it was with normal *.unv’s
Translating universe metadata
Before you begin, the universe you want to translate must be created in the source language, and published to a repository or local folder.
This procedure presents the recommended way to translate the data foundation and business layer metadata for universes created in the information design tool. For details on the procedures in the translation management tool, see the Translation Management Tool User Guide.
In the information design tool, create a local project if you do not already have one.
When creating the project, note the file path to the directory where the project files are saved in the file system. The default root directory for all projects is workspace.
Retrieve the universe into the local project.
The information design tool saves the .dfx and .blx files in the local project. These files correspond to the data foundation and business layer definitions. These are the files that are used as the source for the translations.
Note: For OLAP universes, only a .blx file is saved.
In the translation management tool, translate the data foundation metadata (for relational universes):
a. Import the .dfx file from project folder in the local file system.
b. Translate the metadata.
c. Export the translated content to the local file system.
For details on these workflows, see the Translation Management Tool User Guide.
Follow the same procedure as in previous step to translate the .blx file.
In the information design tool, to see the translations:
a. In the application language preferences, select translated language as the Preferred Viewing Language. Exit and restart the information design tool for the language change to take effect.
b. Open the business layer by double-clicking it in the Local Projects View. You can see the translated metadata in the Query Panel. To open the Query Panel, select the Queries pane and click Insert Query.
Re-publish the business layer so that translations are available to universe users.
For universes published to a repository, you can open the Query Panel on the published universe by right-clicking the universe the Repository Resources View and selecting Run Query.
source: IDT HELP files
Tiny (BOB member since 2004-11-10)
It looks like I can translate the object name in the business layer via Translation Manager.
After changing the viewing language the translated object name also appear in the query panel. In the report it self, the original objectnames are shown.
Any idea what’s wrong ?
RuudCalis (BOB member since 2006-10-05)
Which exact patch level are you on?
Current is: SAP BI BusObjects 4.0 SP4 Patch 3, I believe.
Andreas 
(BOB member since 2002-06-20)
The issue is related tot 4.0.4
Does this help ?
RuudCalis (BOB member since 2006-10-05)
Translating a .unv works as expected. Any help is much appreciated.
Regards
Ruud
RuudCalis (BOB member since 2006-10-05)