MWO does not understand Inventory part barcode. 

Inventory Part barcode takes a full set of keys for some inventory (part no, serial, revision, WDR, project activity etc) and relabels it with a unique ID (just a number).  The Inventory Part Barcode you print out is a barcode of that number, let’s say it’s “1234”.

This entity is not included in MWO.  Therefore you can scan “1234” in MWO, but it doesn’t know what that means.  It will look for a part number “1234” or a work task “1234” depending which screen you’re on, but it will not look for an Inventory Part Barcode record.

You could though edit the layout of the Inventory Part Barcode report so that it has the actual part number in a separate barcode.  Then you could scan that using MWO.

So basically, you just have to produce a barcode of the part number.

Tanks, Paul.  I am VERY familiar with the standard IFS bar code functionality and how it relates to the inventory part.  But this seems like another example of design incompatibility between function within the software.  As an aside, I have, in many years of implementation, had clients who did NOT use our bar code logic and labels but designed and implemented their own.

Suffice it to way, we will probably do the same with the customer in question.

I’m not sure how often the ifs inventory part barcode is actually used inside Applications and its clients. But in wadaco it is possible to use it in most places where we work with the part stock keys. If you want to build a customization that uses that barcode it should be very simple, just need a field to scan it the BARCODE_ID to and then some logic that will fetch the different values from that particular BARCODE_ID using the server package for InventoryPartBarcode.