IV78489: CANNOT SAVE A PLANNED LABOR RECORD IF IT USES A CREW TYPE INSTEAD OF A CRAFT WHEN UTILITIES IS INSTALLED.

APAR status

• Closed as program error.

Error description

• There is MaxVar named "CREWDURATION".  When its VarValue is set
  to "PLUSDCRW" you get errors trying to save a Planned Labor
  record that uses a Crew Type instead of a Craft.
  
  Set the VarValue to "DYNAMIC" and no more errors.
  But this would force them to set a different MaxVar value than
  they want to use which affects downstream functionality.
  
  It has been reported that it looks like this issue was
  introduced by the fix for APAR IV50149.
  
  The log shows the following messages:
  
  java.lang.NullPointerException
    at psdi.app.workorder.WPLabor.setDuration(WPLabor.java: 1227)
    at psdi.app.workorder.WPLabor.save(WPLabor.java:891)
  
  If someone looks at the code in the setDuration() method in the
  WPLabor.class, the bug should be pretty obvious.  There appears
  to be a copy/paste error at this point in the code.  The logic
  first checks if  AMCrew is populated and if so, it gets the
  AMCrew MBO and the related AMCrewLabPos MBOSet.  Otherwise, it
  check if AMCrewType is populated and if so it again tries to
  get the AMCrew MBO and related AMCrewLabPos MBOSet instead of
  the AMCrewT MBO and related AMCTCraft MBOSet.
  
  
  STEPS TO REPRODUCE:
  
  1. Using SQL Set the Maxvar "CREWDURATION"  to "PLUSDCRW".
  Commit the change and restart the Maximo Application Server.
  You may have to Insert this row.
  If it exists you can use this Update statemnent to set it to
  "PLUSDCRW":
  
     update Maxvars where varname = 'CREWDURATION' set
     varvalue = 'PLUSDCRW'
  
  2. Pick a Craft that has Labor associated such as LUB.   Check
  the CREW? checkbox so you can use it with Crews.   Save.
  3. Go To Admin - Resources - Crew Types and create a new Crew
  Type
  4. In the Required Crafts section click New Row
  5. For Position Leader pick LUB Firstclass.
  6. Click New Row again.   For Position Helper pick LUB
  Apprentice.
  7. Save
  8. Go To WOTrack
  9. Create a new WO with Duration = 5.
  10. On the Plans tab, in Planned Labor click on Select Crew Type
  11. Select the Crew Type you created above.
  12. Save
  
  
  CURRENT ERRONEOUS RESULT:
  
  When you try to Save you get this error:
  
     BMXAA4214E - An unknown error has occurred.
     Please contact your system administrator for assistance.
     Gather the logs from the <HOME> directory and determine
     where and why the error is thrown.
  
     null
  
  ENVIRONMENT (SYSTEM INFO):
  
  App Server IBM WebSphere Application Server 8.5.5.3
  
  Version IBM Maximo Asset Management 7.5.0.8 Build 201504071004
  DB Build V7508-00
  Tivoli's process automation engine 7.5.0.8 Build 20150401-2000
  DB BuildV7508-33
  IBM Maximo for Utilities 7.5.0.1-20150624-1038 Build
  20120710-0136
  DB Build V7501-14 HFDB Build HF7501-11
  IBM Maximo Asset Management Scheduler 7.5.2.0 Build
  20150401-2000 DB BuildV7520-181
  IBM Maximo Spatial Asset Management 7.5.0.1 Build 20120714-2208
  DB Build V7501-13
  IBM Maximo Calibration 7.5.0.0 Build 20150401-2000 DB Build
  V7501-03
  IBM TPAE Integration Framework 7.5.1.3 Build 20150403-1800 DB
  Build V7 513-02
  
  Server OS Linux 2.6.32-431.29.2.el6.x86_64
  
  Server DB Oracle 11.2
  

Local fix

• (none)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users using Work Order application in core Maximo with   *
  * Utilities installed.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CANNOT SAVE A PLANNED LABOR RECORD IF IT USES A CREW TYPE    *
  * INSTEAD OF A CRAFT WHEN UTILITIES IS INSTALLED.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply Release 7.5.0.10 of Base Services or request an        *
  * Interim Fix                                                  *
  ****************************************************************
  

Problem conclusion

• Null pointer was being thrown due to bad code.
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO SCHEDULE

• Fixed component ID

  5724R46SE

Applicable component levels

• R750 PSY

     UP