How is the field -Earliest Next Due Date (PM.ERLSTWOGENDATE)- calculated in Maximo Base Services?
PM.ERLSTWOGENDATE = Earliest next due date for a work order generated from this PM.
This is calculated from the PM tab in the PM application - 'Work Order Information' section
To set the Earliest next work order generation date, the code checks for:
Time Based (PM.nextdate and PM.extdate) and Meter Based Frequency
If it finds any of the above scenarios,namely PM.nextdate or PM.extdate or if its the 'Meter Based Frequency', then it gets the 'Estimated Meter Due Date'.
The calculation will find the earliest meter based due date taking in consideration all meters listed on the PM:
- ASSETMETER - lastreadingdate
- ASSETMETER - average
If no date can be generated for this PMMeter, null will be returned.
As this is a calculated field, this field is not to be found in a table as such.
It is a non-persistent attribute influenced by the above various factors as well as the other related calculated date fields.
This attribute can be found in the PM class under:
extended by psdi.mbo.Mbo
extended by psdi.mbo.StatefulMbo
extended by psdi.app.pm.PM
Note: Please keep in mind that if seasonal dates are involved, the calculation will be influenced accordingly.
For further information on some of the mentioned calculated fields, see also the following related DCF documents:
|Systems and Asset Management||Control Desk||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows||7.5, 7.5.1|
|Systems and Asset Management||Tivoli Asset Management for IT||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows||6.2.8, 7.1.1, 7.1.2, 7.5|
|Systems and Asset Management||Tivoli Change and Configuration Management Database||Not Applicable||AIX, Linux, Windows, Solaris, HP-UX||6.2.8, 7.1.1, 7.1.2, 7.5|
|Systems and Asset Management||Tivoli Service Request Manager||Not Applicable||AIX, Linux, Solaris, Windows 2003 server||6.2.8, 7.1, 7.1.2, 7.5|