Maximo Open Forum

 View Only
Expand all | Collapse all

Regular hours is sometimes getting updated to 0 and sometimes blank labor transaction records are coming into Maximo

  • 1.  Regular hours is sometimes getting updated to 0 and sometimes blank labor transaction records are coming into Maximo

    Posted 11-25-2020 01:26
    Dear All,

    We have been observing the issue of regular hours coming as 0 in Maximo from Anywhere for PM and Meter PM type of work orders and sometimes there are no labor transactions that are captured in Maximo from Anywhere.The version is 7.6.3.1

    We have put a validation in Maximo Anywhere where the work order cant be completed without a work type transaction and the field staff are starting the timer and stopping the timer once they complete the physical work at site and there are non zero labor hours in anywhere but it is not syncing back to Maximo.We have been unable to find any pattern to detect this behavior and also unable to reproduce this scenario in the non prod environment and also no clue drawn from Mobile First or Device logs to ascertain how these anywhere labor transactions are being lost from coming back to Maximo.

    Any suggestions will be greatly appreciated.

    Best Regards,
    Mahadevan
    Tata Consultancy Services
    #Mobility

    ------------------------------
    Mahadevan Ramakrishnan
    Tata Consultancy Services
    ------------------------------


  • 2.  RE: Regular hours is sometimes getting updated to 0 and sometimes blank labor transaction records are coming into Maximo

    Posted 11-26-2020 03:47
    Dear,

    Kindly trace the below mentioned at Test Environment.

    1. Please ensure that you are using the Correct Version of Maximo Anywhere for (Work Execution)
    2. From GoogleApp/ios there should be a sync the Current Version of Maximo Anywhere (Work Execution)/ Try not to use the latest Update Version sometimes it differs with your Current Mobile First Environment and displaying some issues respectively
    3. Check the Validation Criteria: Did you Use Conditional Expression or else Automation Script
    4. If Conditional Expression then Kindly do check the Security Rights for these Technicians (Properly) - Global Restriction in terms of labor 
    5. If you applied the automation script then you have to check if it is in Attribute level or Object level. My opinion that use the automation script for Wrench Time Calculation. Basically you are calculating the Actual Wrench Time for Laborcode. 
    6. Check the Timer (Start & Stop) Attributes used in Automation Script
    7. Check the GET/Post Method for OSLC 
    8. https://www.ibm.com/support/knowledgecenter/en/SSPJLC_7.6.3/com.ibm.si.mpl.doc/integration/t_import_resource_data.html


    Re Build the Application for MaximoAnywhere at Mobile First / Console and then Check hope this problem will be resolved

    BR
    Adnan Sheeraz
    Ora-Tech

    ------------------------------
    Adnan Sheeraz
    Ora-Tech
    ------------------------------



  • 3.  RE: Regular hours is sometimes getting updated to 0 and sometimes blank labor transaction records are coming into Maximo

    Posted 11-27-2020 00:22
    On the regular hours being captured as 0, are they possibly entering labor manually by hand? If I remember correctly, when manually recording labor transactions (not using the timer functionality), the hours are not calculated when you enter start date/start time finish date/finish time fields. That allows you to potentially enter 0 hours for a labor transaction if you don't adjust it yourself. 

    As for the work order can't be completed without a labor transaction (I assume that's what you meant instead of work type), there is an issue where Anywhere will send status change prior to the labor transaction (IJ26018: ANYWHERE IS NOT SYNCHRONIZING LABOR TRANSACTION BEFORE COMPLETING WORK ORDERS (ibm.com)). Assuming you are throwing an error on the Maximo side, that would prevent it from synchronizing properly. The fact that you're not seeing any errors on the record would be strange and might be an indicator of some deeper problem. Something we learned when we initially implemented Anywhere was that our web server was handling the various HTTP errors that Anywhere would throw and caused the JSON body that Anywhere expected to come back to be a HTML page so it wouldn't render the error messages. We had to change our web server configuration to allow the errors to passthrough so that the JSON response could be properly parsed by the app.

    ------------------------------
    Steven Shull
    Projetech
    ------------------------------