Maximo Open Forum

 Creation Dates for PMs, Assets and Job Plans

  • Administration
Glen Holt's profile image
Glen Holt posted 09-24-2025 13:33

I'm getting a request to create reports displaying the initial creation dates for our active Assets, PMs, and Job Plans. I'm not seeing
this option in related database attributes. Does anyone have any suggestions?

Thanks!

sun kim's profile image
sun kim

https://www.ibm.com/support/pages/setting-field-defaults

I haven't tested it myself, but couldn't create a new datetime field called CREATEDDATE and in the default value put &SYSDATE&?

This will default a field with the current system date/time

Since you're alterting the table, you'd need to take the system down while doing the DBCONFIG each object you touch.

gail smith's profile image
gail smith

If you have audit turned on for those 3 modules, you can find it there.  If you don't have audit tables enabled, then I would use the status change tables.  Won't show you create date, but will show you when it was first approved/activated, which I think is more relevant than when it was created anyway.  Then turn on the audit tables to make life easier going forward.  

Craig Kokay's profile image
Craig Kokay

Hi Glen,

As Gail said, eAudit would make this easy; however, let's examine what is present.

Assets

When you create an asset and save, a record is added to the Asset Move History table (ASSETTRANS).  This represents the initial creation date is where there is no Transaction Type.

Job Plans

Each time the JP has a status change, there is a corresponding entry in the Job Plan Status History table (PLUSCJPSTATUS).  Therefore, the oldest date with a status of DRAFT is the initial creation date.

PM

Now for the fun one.  There is no similar table for the PM as for the other two; however, by default, the PM object is eAudit enabled...and guess what, so does the Asset object.  Therefore, all you need to do is create MAXRELATIONSHIP to find the oldest entry.

So, one thing to take away is that eAudit is very valuable and maybe enabled a bit more; however, that has to be taken in the context that it will add rows and, therefore, require more disk space.  There have been a lot of times when the value of eAudit outweighs the additional cost.  I would counsel that where you do have eAudit enabled that you ensure that you have enabled ALL of the attributes that you want to be recorded in the audit table.  

I hope that answers your question.