Scenario:
A new unit of measurement is required for handling materials.
Action:
The user defines a new UOM with code, name, and type.
Outcome:
The UOM is created and available for assignment to materials.
Scenario:
The description or naming convention of a UOM needs correction.
Action:
The user edits the UOM master record.
Outcome:
The updated details reflect across all dependent transactions.
Scenario:
The materials require different measurement categories.
Action:
The user assigns a UOM type such as Weight, Length, Volume, or Count.
Outcome:
The system enforces appropriate usage and validation.
Scenario:
The material requires a standard reference unit.
Action:
The user marks a UOM as the base unit.
Outcome:
All alternate UOMs convert back to the base UOM accurately.
Scenario:
The material is procured, stored, or issued in different units.
Action:
The user defines alternate UOMs linked to the base UOM.
Outcome:
Multiple units can be used without data inconsistency.
Scenario:
The material cannot be transacted without a valid unit.
Action:
The user assigns UOM to material master.
Outcome:
The material transactions follow defined measurement rules.
Scenario:
The certain UOMs should not be used for specific materials.
Action:
The system restricts UOM selection based on configuration.
Outcome:
An incorrect unit selection is prevented.
Scenario:
The user enters incorrect or mismatched quantities.
Action:
The system validates quantity and UOM compatibility.
Outcome:
The accurate and consistent data entry is enforced.
Scenario:
The UOM is required in Inventory, Purchase, Production, Sales, and MES.
Action:
The system shares UOM master across modules.
Outcome:
An uniform measurement handling across ERP/MES.