How to handle account code unit of measure mismatch.

Question

We have an estimate that is being loaded into Control. The estimate includes child-level items that share the same account code but have different units of measure. For example, pipe is measured in LF, while fittings are measured in EA. Both fall under the same account code, which is set up as LF. Apparently, when the estimate is loaded into Control, this creates an issue because the fittings have a UOM of EA, which does not match the account code, causing the import to be rejected. I assume this should be a relatively simple fix—perhaps we need to load a secondary UOM or make a similar adjustment. Any help or guidance would be appreciated. Thanks.

Robert.Delgado · Answer

Hello Greg,

Sorry for the delay getting back to you. I did some research and found that a mismatch between a cost item's Unit of Measure (UOM) and the account code it is assigned to is not a scenario that would prevent the import from completing. Based on our understanding of the product behavior, the import process does not validate or block records solely because the cost item UOM differs from the account code UOM.

To better understand what is occurring in your environment, I will be requesting some additional information directly from you. One possible cause we would like to investigate is whether all UOMs used in the Estimate are available in the Suite UOM Master Data Library. If a UOM referenced in the Estimate does not exist in the Suite master data, that could result in an import failure.

Greggory.Joyce · Answer

Thanks

Caleen Frisbie · Answer

Thanks for the post @Greggory.Joyce! Tagging in @Robert.Delgado who should be able to share a few thoughts.