Maximo Open Forum

I'm doing some deep data scrubbing today, and noticed something strange.  Keep in mind this is still on 7.6.0.8; I'm hoping it's been corrected by now/MAS 9.x:

This is about WPITEM.ISSUETO.  Looking at it in Database Configuration, it is supposed to be SameAs LABOR.LABORCODE, and the Description mentions that it is for issuing to a Labor or Craft.

In Work Order Tracking --> Plans --> Materials, the field is configured with a Person lookup, not Labor.  And it accepts values for People, not Labor.

It just so happens that we have a small, single-site, single-org installation, and I've always done it so that for any given real person, their PERSON.PERSONID = LABOR.LABORCODE = MAXUSER.USERID .... but not every Person would have a Labor record and/or a User record.  So what I found here were a handful of records in the WPITEM table that have a value for WPITEM.ISSUETO that is a Person record, but that Person does not have a Labor record.

I think having ISSUETO go to a Person record makes more sense and gives greater flexibility.  So is this just some internal documentation that never got cleaned up since the Maximo v.6 (I think) introduction of People as a separate thing from Labor?  That is, IBM needs to change the Description and the SameAs for WPITEM.ISSUETO (and WPMATERIAL.ISSUETO) to PERSON.PERSONID?

It's still this way in MAS. I'd consider this a bug in the field documentation, though I don't think it's currently a known defect. I think you're spot on that it was based on V4 which only had a labor record and with the addition of PERSON, was never updated to account for it.