Change workorder tasks to use a different autonumber value

If you generate workorders from PM’s that have a lot of job tasks, you may have noticed that the parent workorder numbers are not in order or sequential. It may seem like the workorder numbers are skipping when they shouldn’t be, but in fact, what’s happening is this. When a PM, that has job tasks associated with it, is generated into a workorder, those individual tasks use up workorder autonumber keys. So if your job plan has 30 tasks, it will use 30 workorder autonumber keys and I think this is unnecessary. If you have a lot of PM’s, this number can get high pretty quickly. I think the workorder autonumber should be used only for that purpose. So here is how you setup different autonumber keys for workorder tasks so that you don’t use all the autonumber values.

This text is available for purchase but you need to login or register first. Please Login here.
About Chon Neth

I am a Senior Software Engineer at InterPro Solutions, LLC located in Wakefield, MA.

  • ec3

    Hey Chon,

    I followed your instructions however when you go to site level and create a new row, it only allows you to choose a value from a lookup. We cannot create a WOACTIVTYNUM because of this restriction. We then went into the autokey table,added a new row, and applied that new autonum to the db object. That didn’t seem to work either. Not sure if we are using a different version of Maximo because at the site level we can only choose a lookup.

    Thanks Chon

    • http://interprosoft.com Chon

      I have rewritten the tutorial so that it works. Please try again and let me know…

  • Ernie

    Works like charm. Thanks again Chon.

  • Epsita

    I have a requirement to set different autonumbering sequence for different cloned applications of views created from Work Order table.Does it seem feasible?

    • http://interprosoft.com Chon

      Not sure