RE: FW: Any interesting ideas?
Doug,
Though there may be reasons to do it in several reports (for example,
vocabulary overrides weren't that stable even in B7331) , I'd strongly
advise against it.
In B7331+ I can recommend the following:
Trivial solution:
For all users: set language preference
For report text: use vocabulary overrides (GH9011/P9220 for reports and
applications, P98306 for processing options)
For report data: use translation, where available (UDC, BU, Accounts,
AAIs...) Where translations tables are not there, use some fields in
standard tables. In most cases you can get away with it. Some JDEdwards
BSFNs accept language preference as parameter, if you do direct fetches -
you'll need to fetch accordingly. Don't forget to get default description if
translation is not available.
Less trivial solution: if your user needs to run reports in several
languages: insert a Processing Option with language
When you initialize the UBE, there's a system function, which can be used to
set the language preference (I don't remember the name). This function
sometimes does not work (for certain types of sections). In B7332 it was
better, but not yet absolute solution. But on the other hand it worked for
all reports we needed it in.
Data is retrieved in the same way as above, just use your processing option
instead of System Variable.
There are drawbacks if you are not XE - you can't use vocabulary overrides
to translate report name, and you can't translate report text variables
("Offset by document", which appears on the automatic entries in F0911
explanation/remark, is a good example). They (JDE) say that it is now
possible in XE. I still have not seen this in a report, so you can trust
JDEdwards or check yourself. There are a couple of other important
enhancements in XE to vocabulary overrides, so you may consider it (I don't
recommend it, because we, for example, will hold upgrade for a whiiile, for
a number of reasons)
And, for sure, you must deploy your changes to vocabulary overrides to
workstations with an update package (or simulate check-out).
A couple of hints for Vocabulary Overrides: If you have 0 in "Override"
column, description is not overridden and you are better off translating
Data Dictionary Item.
Vocabulary Overrides for version exist only if there are layout overrides
for the version.
Regards,
Vladimir Ponomarev