IBM Support

Status changes and their importance.

Technical Blog Post


Abstract

Status changes and their importance.

Body

As any long time application user in Maximo knows, status changes can be unforgiving at times. Change a record to a status that causes it to go into history too soon and it's problems. Status changes in Maximo always tend to call huge amounts of logic to be executed when a  change happens and reverting back is not always that easy. For instance, when a work order is changed to closed from approved, the logic called is huge. Checks are done against the inventory table, PO tables, Labor tables just to mention a few. A historied record can not be brought back to be used at a later point, some can be edited. Application's such as work order tracking feature a Edit History Work Order option allowing for some editing to be done when in a closed status. Make the same mistake in the purchase order application and you will have even more problems. Closed PO can not be edited and you have no ability to revise the record either. A great way to avoid issues with changing a record status to a history status too soon is to use more synonym values of the statuses that are not as restrictive. If you find that there are still things you would like to limit when using the synonym value add a data restriction to help with this. I think you would agree setting this up ahead of time is much easier than manipulating status of records via the back end. So set up a few synonym values as needed let the record move through these values until your certain they are no longer needed. Once confirmed as no longer needed, then change the status to its needed closed status. I think you agree, “An ounce of prevention is worth a pound of cure.” Benjamin Franklin.

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

UID

ibm11132977