Troubleshooting
Problem
When a new schedule is created with a set of work orders and saved, the Gantt view shows the work order as modified (description in italic blue prefixed with the * character) though no changes were made to the schedule.
Environment
Tivoli's process automation engine 7.5.0.5 family.
Resolving The Problem
This is working as designed. Lets review the behaviour.
When creating a new schedule, while it may seem as it is not "modified", it will almost always be modified. The reason is that when the schedule data is populated, in many cases the STARTTIME and ENDTIME fields are null. Later when the schedule is 'loaded', those START and END times are calculated, and the data becomes "modified" and "uncommitted". The first time this happens, the data is actually updated in SKDACTIVITY with the START/END times, and the record is flagged as UNCOMMITTED, so that the next time the project is loaded, it knows the data was modified.
This is working as expected, although, it may be somewhat confusing. You can see it happening, if you create a new query on a fresh database. Then in Scheduler, after a save (but before going into the Gantt), look at the data in SKDACTIVITY, specifically the STARTTIME and ENDTIME fields. They will most likely be null. Then go into the GANTT, and requery the SKDACTIVITY table. Now we see the STARTTIME and ENDTIME fields have values (ie, it's been modified).
The concept of a "modified" work order or assignment is not limited to just a manual modification, it could be cases like this where missing data is populated/fixed.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21688557