Hi everyone,

 

I am currently working on a data migration scenario in IBM Maximo Manage where the source data is in Dutch, and I am trying to validate multi-language (ML) behavior.

 

Here are the steps I followed:

 

1. Base language is set to English, and Dutch is enabled as an additional language.

2. In Database Configuration:

 

   * Added language tables for JOBPLAN (L_JOBPLAN) and JOBTASK (L_JOBTASK)

   * Enabled MLSUPPORTED and MLINUSE for DESCRIPTION fields

   * Performed Database Configuration

3. Logged in with English profile and created a Job Plan and Job Task with English description and long description.

4. Changed profile language to Dutch, logged out and back in.

5. Verified that UI labels changed to Dutch.

6. Opened the same Job Plan/Task, but the description still shows English instead of blank or Dutch.

 

My understanding was that for ML-enabled fields:

 

* If no translation exists, either the field should be blank OR allow entering Dutch value separately.

 

However, in my case, the English value is still shown.

 

Questions:

 

* Is this expected behavior that Maximo falls back to base language if no translation exists?

* How can I confirm that ML values are being stored in language tables (L_JOBPLAN / L_JOBTASK)?

* Is there any additional configuration required for Job Plan / Job Task ML support?

 

Any guidance or best practices for handling multi-language data migration (especially Dutch → English scenarios) would be helpful.

 

Thanks in advance!
Sidhan

------------------------------
Abdul Sidhan P
------------------------------

------------------------------
Abdul Sidhan P
------------------------------

Hi Sidhan,

what you experience is by design. The base language value is always used when secondary language value is missing. The secondary language value gets saved only when you actively change on the UI base language value.

If you happen to work with secondary language session and you create a record which is language enabled then still secondary language value gets saved and base language gets populated with ~null~.
So the general practice is that all language enabled attributes should be created using base language session if they are to be viewed in base language or any other secondary language (as you may enable several more).

------------------------------
Andrzej Więcław
Maximo Technical SME
Naviam
Wrocław, Poland

If this post was helpful, please click the Like button to let others know.
------------------------------

Hi Sidhan,

Andrzej is correct.

I wrote an article on this using the example of Job Plan Tasks in 2019, it is still valid today - https://maximosecrets.com/2019/06/06/maximo-languages-and-language-tables/

For those who want to see language being applied on an item's description where it is being generated in multiple languages using Classification and Specification description generation then you might find this article of interest - https://maximosecrets.com/2020/08/20/item-classifications-generating-descriptions-in-multiple-languages/

Hope you find either useful.

Regards - Andrew

------------------------------
Andrew Jeffery
Maximo SME
Naviam
Barnstaple, Devon, UK
+44 (0)777 1847873
------------------------------

1. If a base language user enters a description, all other language users will see that value.

2. If a non-base language user (e.g., Dutch) enters a description, it is stored in the database for that language only, and base language users will not see it

If the language on your profile is now set to Dutch(NL) and you edit the above record and enter a description in Dutch (e.g. 'Noodreparatie aan leidingen') and save the record, this should create an entry in the Language tables

You can find more information on this here - https://www.ibm.com/docs/en/masv-and-l/cd?topic=deploy-language-support#concept_bdb_13b_54b__multi_lang__title__1

------------------------------
Best regards,
Aiman Ansari
Solution Architect
Naviam (formerly ZNAPZ)
------------------------------