IJ51165: THE LONG DESCRIPTION TEXT IS SHOWING IN THE DB, BUT MISSING FROM THE UI FOR MIGRATED OBJECTS WITH MULTIPLE LONG DESCRIPTIONS

APAR status

• Closed as program error.

Error description

• Problem description:
  
  When migrating an object (e.g. Workorder) that has multiple Long
  Descriptions and has content only in the first long descriptions
  and not the last, and the HASLD flag is set to 0 and the
  existing long descriptions for the other fields are not shown,
  they are correctly written to the database but just not shown in
  UI.
  
  Steps to reproduce:
  
  1.    Create a new package definition: Test 07
  2.    Leave everything as default and in the Migration Groups
  table, enter a new Migration Group via Detail menu > Go to
  Migration Groups
  3.    Create a new migration group Test 06
  4.    In the Migration Objects for TEST 06, create a new Object
  Structure via Detail menu > Go to Object Structures
  5.    Create an Object Structure TEST_WO_06 and assign it the
  WORKORDER object in the Source Object for TEST_WO_06 table
  6.    In More Actions, click on Exclude/Include fields and
  uncheck the flag for the HASLD attribute
  7.    Go to Work Order application and create a new Work Order
  TEST 06
  8.    Leave the Work Order Long Description empty
  (WORKORDER.DESCRIPTION_LONGDESCRIPTION), but enter something in
  the long description of the Priority Justification
  (WORKORDER.JUSTIFYPRIORITY_LONGDESCRIPTION)
  9.    Go back to Migration Manager application and in the
  Migration Groups, click on the Set Where Clause of the TEST 06
  Migration group
  10. Approve the package and go to the Distribution tab, select
  Target name as drive C, Type FILE, Database URL C:\
  11. On the Package tab, click Create > Click Yes  on the System
  message dialog (BMXAA6136W - You have user-defined migration
  objects in this package definition.) > Click Continue
  
  12. Download the package as zip file
  13. Upload the zip file on the target environment and deploy it
  14. Check the WO that was migrated (TEST 06) and check the long
  description of the Priority Justification
  (WORKORDER.JUSTIFYPRIORITY_LONGDESCRIPTION)
  
  
  Current results: The text is missing (it shows in the backend).
  
  Expected results: The long description text should show.
  
  
  If the WO record has only JUSTIFYPRIORITY_LONGDESCRIPTION,
  although the JUSTIFYPRIORITY_LONGDESCRIPTION is copied to the
  target system, the HASLD flagged is migrated as FALSE, meaning
  the WO doesn't know there is a Long Desc data found in the DB,
  and nothing is displayed in the UI. But upon checking the DB,
  the Long Description data is showing in the LONGDESCRIPTION
  table.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * THE LONG DESCRIPTION TEXT IS SHOWING IN THE DB, BUT MISSING  *
  * FROM THE UI FOR MIGRATED OBJECTS WITH MULTIPLE LONG          *
  * DESCRIPTIONS                                                 *
  ****************************************************************
  

Problem conclusion

• A fix for this APAR will be included in a future release.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels