Could not convert item code UofM

Error text similar to: Could not convert item code UofM: ‘(Actual item code)’ from ‘(Some unit of measure or an empty string)’ to a BASEUOM for the in-progress transaction for (some transaction name, options are Adjustment, Site Transfer From, Site Transfer To, Receiving, Order Fulfillment, Issue Inventory, Assembly, and Connected Sales).

As part of our feature to keep the quantities we have being used in other transactions, we need to convert all In Progress, Pending, or Failed transactions down to the base unit of measure so we can display the correct available quantity to the user.  If we find a unit of measure that we cannot convert to the base unit of measure, we display this error message.

This is an error that occurs on the handheld’s software during validation of the quantities available for the transaction you are attempting to work on and is indicative of a problem within the PanatrackerGP database, not GP, regardless of where it originated (see possible causes below).  This error is NOT caused by the transaction you are trying to process. It is caused by an older existing In Progress, Pending, or Failed transaction in the Portal.

To fix this issue:

1. Go the Panatracker portal
2. Open the transaction list that is marked in the error
   1. Adjustment – Check both Remove Adjustment and Add Adjustment
   2. Site Transfer From and Site Transfer To – Check Site Transfer
   3. Other transactions match up exactly in the portal
3. Click the Filter icon next to the column header “Status” and filter the transaction by Failed and click Filter.
4. Only the Failed transactions should be displayed at this point. You’ll need to see if any of these have the item code displayed in the error message with the unit of measure in the error message.
5. Once you find it, you will need to either Discard or Edit and fix the transaction to have a correct unit of measure.
6. Repeat the process in 3 through 5 with statuses Pending and InProgress until you find the offending transaction.
7. Once you fix the transaction, try what you were doing again to verify that it is working properly.

Causes of this problem:

• If you changed a unit of measure schedule (removed or changed spelling on a conversion).
• If we migrated your data, this could be left over from your migration. (Usually from the above issue)
• If the user did something strange on the handheld and was somehow able to submit an inappropriate unit of measure.  We have checks for this in place, but sometimes users do something we don’t expect.  The best way to avoid this is for the user to hit the enter key after entering data or scanning into fields.