IBM Support

IJ08742: INCORRECT TIMEZONE VALIDATION WHEN ENTERING LABOR ACTUALS IN MAXIMO ANYWHERE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When entering labor actuals in Maximo Anywhere on a device
    where there device time and the users profile are in a
    different timezone from the server, core Maximo sends back the
    following error when validating the start date and finish date
    
    BMXAA2569E - FINISH DATE AND TIME MUST BE LATER THAN STARTDATE
    AND TIME
    
    Steps to reproduce:
    
    1.   Set your server time to UTC and restart the Maximo JVM
    2.   Change your users default profile and device time to PST
    3.   Log in to Maximo Anywhere Work Execution select a work
    order in progress and enter labor actuals in the past.
    
    Start Date: 2018-08-15
    Start Time: 6:00 am
    Duration: 15 hours  (This must be set to a higher time to
    change the AM\PM flag)
    
    This should fill in the end date and end time to
    
    End Date: 2018-08-15
    End Time:  9:00pm
    
    4.  Turn on the OSLC logging and ensure the values are sent to
    core Maximo as seen.
    
    At this point Maximo should convert the time to UTC, however
    there is an issue in the conversion and validation which causes
    the end date to appear before the start date and display the
    following error.
    
    BMXAA2569E - FINISH DATE AND TIME MUST BE LATER THAN STARTDATE
    AND TIME
    
    This issue does not occur when the timezone is the same all the
    way through.
    
    
    Expected Results:
    
    For the transactions being sent to Maximo through the OSLC
    Framework to convert and validate timezones the same as core
    Maximo transactions
    
    Environment:
    
    Maximo 7.6.0.9
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * INCORRECT TIMEZONE VALIDATION WHEN ENTERING LABOR ACTUALS IN *
    * MAXIMO ANYWHERE                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.1.0 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ08742

  • Reported component name

    WORK ORDERS

  • Reported component ID

    5724R46WO

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-23

  • Closed date

    2018-08-23

  • Last modified date

    2018-08-23

  • 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

    WORK ORDERS

  • Fixed component ID

    5724R46WO

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Work Order Tracking

Software version: 760

Reference #: IJ08742

Modified date: 23 August 2018