Maximo Open Forum

 View Only
  • 1.  Work Order and Preventive Maintenance Error ("Has been updated by another user"

    Posted 4 days ago

    Hi all,

    Seeking your assistance to provide ideas or solutions on how to resolve this issue. Whenever I generate a work order from Preventive Maintenance or try to close a work order, I keep receiving the error message: "Has been updated by another user." Our Maximo version is 7.6.1.3

    Appreciate your help on this.


    #Administration
    #Assets
    #EverythingMaximo
    #Scheduling
    #Utilities
    #WorkManagement
    #Monitor

    ------------------------------
    Nor Herman Afandi
    ------------------------------


  • 2.  RE: Work Order and Preventive Maintenance Error ("Has been updated by another user"

    Posted 4 days ago

    I have seen the updated by another user error in various PM related bugs but can't think of a scenario off the top of my head when it occurs on the LOCATIONS object.

    Is this a PM record tied to the location (rather than an asset or route)? And is it schedule based or meter based? And is it all PMs for all locations or just this one specific location/PM?

    What I like to do to triage this scenario when you can reliably recreate it is to turn on sql logging to INFO for just the locations object. IE create a new child logger of LOCATION.LOCATIONS with its log level set to INFO.



    Save and apply settings. Then recreate the issue and disable the logging.

    What this does is help you understand how locations are being fetched along with what is being modified on the locations object. This can help you identify where the problem might be. It is possible, for example, that a custom automation script is updating the locations record on work order save and is using a different relationship to get the record. 

    I would recommend since you're on 7.6.1.3 (newer MAS versions have a system property to disable automation scripts) to turn on admin mode in a lower environment and try to recreate the issue. That can potentially eliminate or help confirm an automation script as the issue. It's not perfect because it does disable other things (such as publish channels) which could potentially lead to the issue. But is still helpful in trying to pinpoint. 



    ------------------------------
    Steven Shull
    Naviam
    ------------------------------