Maximo Open Forum

 View Only
  • 1.  Maximo Audit tables - Mobile

    Posted 08-09-2021 13:29
    Hi All,

    We would like to know what is the best approach to track real time date in EAUDITTIMESTAMP column when we are updating any work order or asset using mobile (custom mobile solution)

    For  example technician completed a work order in mobile when he is in offline and synced the data after 3 hours when he is online so how we can record actual date and time in EAUDITTIMESTAMP  column ( A_WORKORDER table) for that transaction  ?

    #Maximo #MaximoMobile #oslc #RESTAPI


    Thanks,
     Ajay

    ​​​​
    #Integrations
    #Mobility

    ------------------------------
    Ajay Kotapati
    BEUMER GROUP
    ------------------------------


  • 2.  RE: Maximo Audit tables - Mobile

    Posted 08-11-2021 16:06
    I'm really not sure there's a good way to accomplish it. The request is logical but the intent of e-audit is to record when it actually occurred in Maximo. Certain fields in Maximo (changedate) for example can be provided during the API request and stored with a different date/time than when recorded but e-audit wasn't really intended to be modified. This data gets SQL inserted into the table and is done in the core MboSet class. You can't simply extend this class without extending everything else that extends it (which is way more than you'd ever want to do) and you wouldn't want to replace the MboSet class with your own custom version (as that'd be a nightmare to maintain). If you only cared about WO you could extend that class and provide your own eAuditMbo method but I'm not sure I'd really want to replicate that logic even. 

    I'd either create your own version of e-audit for the customer (recording only the stuff you care about in another MBO, with the dates that you care about) or utilize a separate date field that you track as part of e-audit. I wouldn't use changedate because that will change too often and will fill the audit table with noise, especially on WO. And I'd let the customer know the advantage to this is when you're trying to troubleshoot issues, it's extremely helpful to know when it really made it to Maximo as that's what matters. If the user recorded actuals and the e-audit showed that the actuals came in before it was approved, that causes a lot of confusion to people down the road. So I think leaving a proper e-audittimestamp is helpful as I've had to triage a lot of "why did this happen this way" and having dates you can depend on makes it a lot easier to reverse engineer what happened.

    ------------------------------
    Steven Shull
    IBM
    ------------------------------



  • 3.  RE: Maximo Audit tables - Mobile

    Posted 08-23-2021 06:17
    Hi Steven,

    Thank you for the detailed information.

    We are planning to use some custom date field for mobile data audit.

    Thanks,
      Ajay


    ------------------------------
    Ajay Kotapati
    BEUMER GROUP
    ------------------------------