Maximo Open Forum

Expand all | Collapse all

Wrong timestamp on Audit enabled Maximo Object

  • 1.  Wrong timestamp on Audit enabled Maximo Object

    Posted 18 days ago

    Hi,

    we have a custom object defined in maximo with audit enabled on it and  we use it in workorder application on a new custom tab.

    one workorder can have more than one row of this new object something like related records.

    Lets say custom object as NEWOBJ and audit enabled as A_NEWOBJ.

    in Applictaion designer, changeby and changedate of NEWOBJ is mapped to eauditusername and eaudittimestamp of A_NEWOBJ.

    and in dbconfig a relationship is defined from NEWOBJ to A_NEWOBJ as

    newobjid=:newobjid and rowstamp=(select max(to_number(rowstamp)) from a_newobj where newobjid=:newobjid)

    But the eauditusername and timestamp of one newobj row is getting stamped to another newobj record which is giving a wrong impression that the person who did not make any changes on that newobj record is getting stamped as eauditusername on audit table .

    can anyone help me identify the issue or the approach ?



    #Administration

    ------------------------------
    Meghana Siriveli
    ------------------------------


  • 2.  RE: Wrong timestamp on Audit enabled Maximo Object

    Maximo Certified
    Posted 17 days ago
    I feel like I mostly understand what you're saying but I don't think I follow so I'm going to try and talk through it to see what I'm missing. 

    NEWOBJ is a child of WO (has a relationship from WO->NEWOBJ) and NEWOBJ has the out of the box Maximo e-audit configured. A custom relationship from NEWOBJ to A_NEWOBJ tries to retrieve the maximum e-audit entry for that record. 

    User A is on WO 1234. They enter a new record in the NEWOBJ table (NEWOBJID of 2000) which causes an entry to get added into the A_NEWOBJ audit table. Instead of the audit table record being recorded for NEWOBJID of 2000, it's being recorded as 1900 (a different NEWOBJ record). So when this user views 1900, it shows that they've modified 1900 but doesn't show that they modified 2000. 

    Is the above what you're seeing? If so, is it specifically other NEWOBJ records associated to the same WO or random?

    ------------------------------
    Steven Shull
    Projetech Inc.
    ------------------------------



  • 3.  RE: Wrong timestamp on Audit enabled Maximo Object

    Maximo Certified
    Posted 15 days ago
    Just like Steve , I too could not understand the issue properly.
    I think we would need for more explanation( screenshots would be better).
    Also, what do you mean by "in Applictaion designer, changeby and changedate of NEWOBJ is mapped to eauditusername and eaudittimestamp of A_NEWOBJ"? Could you please explain how did you achieve this mapping ( just curious to understand the configuration better) in Application designer?



    ------------------------------
    Biplab Choudhury
    Tata Consultancy Services
    ------------------------------