IBM Support

Discard & Refresh, sometimes a refresh just isn't enough.

Technical Blog Post


Abstract

Discard & Refresh, sometimes a refresh just isn't enough.

Body

In life, sometimes we just have to get rid of something, a refresh just won't do. You ask them to stop leaving that shoe in that one place that is always in the way, do they, no. You freshen up, but they come back and leave the shoe in that same place once again. The answer, discard the shoe and then refresh, now there is no shoe to get in the way. Let's apply the same thinking to scheduler and the two options, refresh and discard and refresh. 

 

I was working with a customer on an issue they were having in the scheduler, they had 1 work order referenced on 2 different scheduler records, but each had a different start and end time. The customer was wondering how something like this could happen, well after some investigation we were able to figure out exactly how it happened in this case. I can't say this will be the case of all issues, but it's a great place to start when troubleshooting the issue. 

Here is my schedule information from the work order tab.

image

Here we can see the target start is listed as 6/6/16, starting at 9:00 AM and scheduled to finish on 6/8/16 AM. A new scheduler record is now created and the work order created earlier is added to schedule, we are now on the Gantt view tab. 

 

image

 

For some reason, a second new schedule is created for the same work order. We now have 2 scheduler records for the same work order. At this point, both will have the same information on the Gantt View tab.

 

image

The scheduler now starts to perform their work duties as needed and they change the start and end date of the work order to a new day and time. A save and commit was done, this in turn write back to the work order, if we check the work order, we can see the new dates now on the work order.

image

We will now have schedule 1 with one start time and end time for the work order, while schedule 2 will have different information. Schedule 1 shows:

 

image

 

 

Now check the other schedule, the start and time will not be the same as the 1st schedule.

 

image

For the schedules to have the same information on them, we have to use the discard and refresh option, the refresh option on its own will not update the record as needed. Using the refresh option will cause Maximo to look at the SKD tables, that will then cause Maximo to use the already loaded data in those tables. We require Maximo to look at the work order tables since a commit was done when we changed the dates and times on the 1st schedule. For this to happen, we must use the discard changes and refresh options, this will now have Maximo refresh the record and show the dates needed, now all the dates match between the 2 schedule records. 

 

 

image

 

 

 

 

 

 

 

 

 

 

 

 

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11131105