Open lambertciata opened 3 weeks ago
VolumetricWeight shouldn't make sense at Piece level as it is airline specific. It should be only on Shipment level. Check as well if it's requried on LineItem level as well, might impact where we need to put the Volumetric Weight
Here is a proposal to update the data model.
As discussed in 21Nov call:
In current ontology there seems to be a mistake on the way VolumetricWeight object is defined.
Object contains a property called
chargeableWeight
which is wrong or misplaced.As the Chargeable Weight is defined as the maximum between gross weight and volumetric weight, it need to be mentioned to avoid other stakeholders to implement the logic while viewing AWB data but it should not be in the VolumetricWeight object.
2 solutions: 1 - We deprecate VolumetricWeight object and move the
chargeableWeight
andconversionFactor
to Piece object. 2 - We removechargeableWeight
from VolumetricWeight object and move it to Piece object, we addvolumetricWeight
propery to VolumetricWeight object. In that case is VolumetricWeight a Value or just a double? Which unit does it have?In current messages, the value of the volumetric weight (volumes x conversion factor) is not present.