Hi Danny,
I concur with Maycon; however, we keep forgetting to ask the question about the process used to reach the issue you are experiencing.
There are three ways of having the FNLT populated on the work order:
- From a PM that generated the work order
- From someone manually entering the FNLT datetime
- From someone applying a JP, but only after someone has entered the Target Finish Date. This is assuming that someone has entered the Finish Constraint on the JP.
So, what process was being used? Let's walk down the path using your keyword "generated". This will lead me down the path that the work order came via a PM.
Now, for the FNLT to be set by a PM that either needs to come from:
- the Finish Constraint on the PM
- the Finish Constraint on the JP
In all cases, the Finish Constraint is in the format of HH:MM; thus, as you indicated, 24:00, which will apply 24 hours to the Target Finish Date (TARGCOMPDATE), if it is populated.
The PM sets the Target Finish Date based on the Target Start Date (in effect, the PM's next due date or forecast date, depending on whether you have a forecast set) and the Target Start Time+ duration (which can come from the JP or the PM)).
For example, the next due date is 01 August 2026 at 08:15, duration is 10 hours, which gives a Target Finish Date of 01 August 2026 at 18:15. You have then assigned 24:00 hours as the Finish Constraint, giving a FNLT of 02 August 2026 at 18:15.
This leads me to what Maycon also said, which is that this FNTL has nothing to do with the Reported Date...though there is one more way of setting the FNLT field, but it's an outlining case.
Scenario: SLA
I set up an SLA with a resolution of 24:00 hrs. I create a new work order and apply the SLA after entering all the data except for the JP. This then defines the Target Finish Date to be 24:00 after the reported date. Then I apply the JP, which then sets the FNLT. As I mentioned, it's an unusual case that requires a very specific order of operations. Of course, this scenario also undermines the argument that the FNLT does not rely on the Reported Date.
Hope that helps.
------------------------------
Craig Kokay
Principal Consultant
COSOL
email:
craig.kokay@cosol.global#IBMChampion
------------------------------
Original Message:
Sent: 01-21-2026 11:56
From: Danny Richardson
Subject: Finish Constraint Offset of 24:00 not giving 24 hrs.
Problem: The Finish No Later than is defaulting to certain database time instead of giving the full Finish Constraint Offset from the Job Plan based upon the Reported Date and Time.
On the Job Plan the Finish Constraint Offset is 24:00 hrs.
I generated the work order and it did not give a full 24 hrs.
My thought is that since the work order was generated at 1/21/26 11:46am then the Finish No Later Than should be 1/22/26 11:46am, but the Finish No Later than seems to default to the database time. Our Database is in UTC so the Finish No Later than is 1/22/26 00:00. And the UI shows a date/time of 1/21/26 7:00 PM.
Is this a setting or just expected behavior for Maximo to default to a certain Finish No Later Than instead of implementing the exact 24 hrs offset?
Thank you
#Administration
#EndUser
#EverythingMaximo
#WorkManagement
------------------------------
Danny Richardson
Maximo Administrator Manager
Technimark LLC
------------------------------