Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
stylenone

A unit of measure structure describes the relationship of eaches to boxes, boxes to cases, cases to pallets, and so on. First you would define the primary UOM which is the each SKU. Then you define each unit of measure in the structure using Item Units of Measure during the creation of the Basic Item Master Data record for the item.

...

Base SKU or primary SKU can be SKU A. The subsequent UOMs for the base SKU A can be A5(which is a pack of 5 items), box of 20 (which is a box of 20 items).

Constraints

...

  • There will be no restriction of mapping items to bin or in bin put-away. A single bin can have multiple UOM items. Ie. The same bin can have eaches as well and cartons as well. The system will not restrict this. If it's required then OPS will have to manage this.

  • Inventory exposure via API to Outer world will always be in eaches quantity.

  • Orders will come via API OR CSV will always be in eaches qty.

Note
  • A Virtual SKU cannot be marked as UOM and vice-versa.

  • The maximum allowed value for nextBreakableSkuQty is 200, i.e a maximum 200 units of the next breakable SKU can be present in a UOM unit.

  • UOM SKUs will not be supported in kitting workflow.

  • Perishable UOMs cannot be defined with Non-Perishable each SKU and vice-versa.

  • UOM and NextBreakableSKU cannot be uploaded in single UOM definition creation CSV.

  • Once the UOM definition is uploaded, it cannot be modified again.

Master Data setup and definitions 

...