Hi Calin
The current behavior is that the quantity represents strict duplicates of an item (typically a non-serialized and non-configurable item such as battery, headset, etc.).
Units of measure are not appropriate here.
What would be your use case (in the communications services world) for having a quantity that is not a strict number? If there is such a case, it could be handled for the specific case (product specification) by defining appropriate characteristics to model this quantity.
Adding
@Ludovic Robert for additional comment
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Sep 01, 2020 10:58
From: Calin Mates
Subject: Unit of measure for order items
Hi,
In a ProductOrderItem resource (part of a ProductOrder) there is a quantity (integer) that identifies the quantity of the ordered item. In case of ordering physical items in general it would be nice to have the unit of measure for the order item (such as kg/ pieces etc). Do you have any plan of including the unit of measure at the order item level?
Many thanks,
Calin
------------------------------
Calin Mates
Aplication Architect
IBM Corporation
------------------------------