Can users be prevented from creating "On The Fly" units of measure in Item Maintenance?

SUGGESTED

For example, we have "EA"  setup in our Units Of Measure Conversion Maintenance and the users should be selecting it from the UOM lookup but that doesn't always happen.

Over the years, inventory managers at different locations have entered items items as "each" in a UOM field or even typo'd a "ES" instead of "EA" in a couple of places.

Similar problems with cases, boxes, packs, pallets, etc...  inconsistent data entry.

It looks like other Sage products (MAS300, X3) seem to prevent this by including a security option for "Only Use Defined UOM" but that feature is not in Sage100.... or am I not looking in the right place? 

Thanks in advance for any help or suggestions!

  • 0

    At the moment, I think a table pre-validate event script on the unit of measure column is your only option.  You can get your own handle to "CI_UnitOfMeasure_svc" and use its Find method on the value the user entered and if Find does not return a 1 then the UOM is not on file.

  • 0 in reply to David Speck

    You probably also want to check CI_Item (using the child handle) to always accept the item's Standard and Sales UoM.

  • 0
    SUGGESTED

    You could always write a script and attach to field that reads what is entered and if it does not match a list then it does not accept the entry and tells the user they entered an incorrect UOM.

  • 0

    Create a User Defined Table with a key field that is 4 characters long.  Enter all of the values that are acceptable for that field into the UDT.  Then use the Advanced Field Settings option in UDF/UDT Maintenance to set the UOM fields on the CI Item Master table as requiring validation against that UDT. 

    This uses standard customization tools built into Sage 100 with no scripting or programming required.  Just note that anytime your users have a legit new UOM that needs to be used, you'll have to create it in the UDT before anyone can use it in an item...but it sounds like that's exactly what you're after. 

  • 0 in reply to jcl
    SUGGESTED

    Advanced field settings are very unforgiving.  Be absolutely sure you have all the required values entered into the UDT before you enable the validation or you might find that those fields will mysteriously become blank without warning.

    Also watch for things like miscellaneous items, charge codes, and comment lines (which won't have UoM, so you must allow blanks).

    Scripting allows more control, but AFS won't require scripting skills.