How to manage UOM flexibility for generic items before item master redesign?

We are working with a large number of generic items that were initially created in the Item Master without the proper Unit of Measure (UOM) defined for specific purchasing contexts.

As a result, users are forced to manually change the UOM during the creation of requisitions or purchase orders, which leads to errors, rework, and inconsistencies between documents.

While a catalog cleansing and item redesign is already planned, we would like to know:

• Is there a recommended interim solution (Quick Win) in Oracle Fusion to enforce or suggest the correct UOM per context or purchase type?
• Could Smart Forms or