As discussed in WG- meeting there is a need for implementing a StatusReasonCode. The use of this information will be to be able to send information about why a package is rejected or accepted, when received it, in a structural way.
This structural change will be implemented at TransportHandlingUnit level
Actions l restrucutre:
[x] include StatusRasonCode and StatusReason
[x] remove DamageRemarks, the textual description element
We also discussed to make this change also at the package level, however, this is not possible according to today's UBL standard. this will then be reviewed after UBL 2.4 is released
As discussed in WG- meeting there is a need for implementing a StatusReasonCode. The use of this information will be to be able to send information about why a package is rejected or accepted, when received it, in a structural way.
This structural change will be implemented at TransportHandlingUnit level
Actions l restrucutre:
We also discussed to make this change also at the package level, however, this is not possible according to today's UBL standard. this will then be reviewed after UBL 2.4 is released