Introduction

The BlueWorx application, BlueWorx Admin Application and BlueWorx Inspection Viewer have all been translated from English into a number of languages/. This article explains how this works.


CONTENTS

Translated Languages

The following languages are available

  • French
  • German
  • Hungarian [Unicode] 
  • Indonesian
  • Italian
  • Portuguese
  • Simplified Chinese [Unicode]
  • Spanish
  • Swedish
  • Russian [Unicode]

Prior to release SP5 the translations were for the BlueWorx applications only and do not include SAP configuration and master data values. As of SP5 BlueWorx now includes the translation of SAP Config and Master Data and BlueWorx Config.

BlueWorx accessed using German language (DE).

What data is translated?

Translation of SAP Master Data is delivered across the application, including the following:

  • Equipment - IE02 - EQUI
  • Functional Location - IL02 - FL
  • Characteristic - CT04 - CABN
  • Characteristic Value Description - CT04 - CAWN
  • Material Master - MM02 - MAT
  • Assembly Materials - MM02 - MASM
  • BOM Materials - CS02 and MM02 - BMAT
  • Work Center Descriptions
  • BOM Items - BMSP
  • Technical Object Long Text - Dynamic at sync
  • Measurement Points - MPNT
  • Catalog Groups - QPGR
  • Catalog Codes - QPCD
  • DMS Documents - DDMS
  • Order Types - T003O > T003P
  • Priorities - T350 > T003P 
  • Control Key - T430 - T430P
  • Maintenance Activity Type - T353I > T535I_T
  • Notification Type - TQ80 > TQ80_T
  • Technical Objects - T370K > T370K_T
  • ABC Indicator - T370C > T370C_T
  • Functional Location Category - T370F > T370F_T
  • Equipment Category - T370T > T370U
  • Activity Type - T353I > T3531_T
  • Notification Types - TQ80 TQ80_T
  • Operating Condition Text
  • Unit of Measure
  • Catalog Code Groups - QPGR > QPGT
  • Catalog Codes - TQ15 > TQ15T
  • Catalog Profiles - T352B - T352B_T
  • Characteristic Groups - TCMG > TCMGT
  • Measurement Point Categories

What content is not translated?

While the Admin Maps sub-application is translated the content you maintain for Maps, Layers, etc is not. This is because of the complexity with dealing with map data in multiple languages. If you have different language requirements then you can maintain duplicate entries, in all areas, for map services, layers, etc in your required language/s, include these in Map Profiles, and assign to users in their BlueWorx profile/s.

For some elements, you need to have SAP language packs installed in order to get translated values. Mainly this related to:

  • SAP BAPI updates operate in the SAP logon language of the user
  • Background jobs, like Inspection Updates, will operate in the SAP logon language of the batch job SAP user account
  • SAP config area and settings like expression descriptions which come from SAP domain values 

Impact on layout

Our development language is English. That means that the styling of the application is performed using English length words. Our observation is that English, as compared with many of the other languages we support, is relatively compact in terms of the number of characters used. As a consequence some forms and list may have title over runs due to increased texts lengths.

Some SAP Events don't trigger Update Events

There are some language related events in SAP whose maintenance does not trigger SAP change events. Examples include but are not limited to things like Order Long Text, Characteristic allowed values. In these cases the translations but not come to BlueWorx without master data refresh in SAP.

Language Files and Unicode

Zag will provide, in all the applications, all available translations for the non-Unicode languages. We will also provide a single upload file for all these non-Unicode languages and then separate upload files for the Unicode languages. Customers must upload any Unicode language packs that they intend to use. The reason Zag doesn't include the Unicode languages in the application is because some prospective customers have not yet moved to a SAP Unicode version.

We've done our best but can't guarantee it's all correct!

We engaged professional translators to for the majority of our translations. To date we have translated over 3500 unique words and phrases related to over 73,000 application fields and over 5,000 technical elements. As we add new controls we maintain new values but may miss some depending on the release sequence or get the translation wrong. If you have suggested corrections that you'd like to see driven back into the BlueWorx product then please raise a support call via this site. Otherwise you can correct your version on each release import.

BlueWorx Administration - default language

To use different languages the administrator must maintain the languages in use and which one is the default language. The default language is used where values in the specified language are not maintained in SAP or the BlueWorx application. 

Add the languages you intend to use, marking one as your default language. The chosen default language necessarily must be installed in the SAP system as a language pack. Technically you don't need to have the SAP language packs installed to use it as a non-default language however, as previously described, the SAP configuration data, as some master data, requires these in order to maintain the data.

BlueWorx Administration - other administration settings

Other admin options, base upon these Master Language value settings are then available. These are documented separately in their respective area.

Translation of BlueWorx Administration Application

BlueWorx Administration screen elements are maintained in selected languages. As of SP5 there is the ability to maintain BlueWorx configuration and Inspection values in other languages. However configuration values for settings are maintained in the assigned Default language. So if the Default language is English and you logon to the Admin applications in Spanish you will see the field elements in Spanish but the main values for things like Status' in English. You can then maintain the translations in the other configured languages.


For example - master language English (EN), user logon language Spanish (ES):


Translation values:

User access of their language

There are a variety of ways in which to dictate the language.

SAP PID Value

The SAP logon language can be set using the SAP PID value DYL in SAP transaction SU01 or users own settings via SAP GUI Menu > System > User Profile > Own Data [transaction SU3]. The PID value is DYL

In this example the users language is being set to Italian.

Neptune Application Logon

If you have maintained the setting for the web application launchpad in Neptune Admin, then you can select the logon language on application login. If you don't allow this setting this it uses the SAP PID value maintained for the user and as discussed above.


Important Limitations 

  • Neptune Software as standard, as of July 2019, only allow you to select languages maintained as languages packs in SAP. Zag has raised this limitation Neptune Software and they have committed to resolving this by allowing the selection of all (SAP supported) languages in a later release.
  • Neptune Software as standard, as of July 2019, only allow access to one language per mobile device/ application. This means that the language for the apps used is that of the first user to log on after after an application update in SAP. Zag has raised this bug with Neptune Software and they have committed to resolving it in a later release.

Browser

Add the logon language to the browser string - i.e: https://yoursystem/neptune/webapp/?launchpad=DESKTOP_MENU&sap-client=100&sap-language=DE for German.


Note for Testers: The browser works using cookies which means that if you open multiple sessions, using different language parameters, then the cookie will be set to the last logon and interchanges back to SAP will use that language and not the URL display language. This is standard SAP/ browser behavior.

Neptune Launchpad Language Settings

If you're using multiple languages then consider maintaining translations when you set up your Neptune Launchpad.

TranslationsUI Configuration

To maintain translations within the application see Translations UI

Neptune Designer - Translations

We have used the standard Neptune Application Designer functionality to support the BlueWorx, BlueWorx Admin and BlueWorx Inspection viewer app translations. This is available via the Neptune Designer Translation tab. Change must be done on the core BlueWorx application for Zag supplied content or in your extension application for customer content.

Neptune Designer - Old Screen

This is the designer screen in the older Neptune releases. Entries must be manually maintained although there is the ability to export to xls, maintain and then 'cut and paste' back into the designer. 

Neptune Designer - New Screen

This is the designer screen of later Neptune releases. It has the ability to export and import translations. Zag will provide translation files for import using this functionality.