Void Shipment Errors (EPCIS v1.2)
The following errors may be encountered with the Serialized Operations Manager Void Shipment (EPCIS v1.2) message:
| Data Element | Error Message | Description |
|---|---|---|
| Class 1 | ||
| action | action OBSERVE is required for ObjectEvent void shipping !!! | The error occurs if the source does not equal OBSERVE. |
| bizStep | bizStep urn:epcglobal:cbv:bizstep:void_shipping is required for ObjectEvent void shipping !!! | The error occurs if the source does not equal urn:epcglobal:cbv:bizstep:void_shipping. |
| bizTransaction | Delivery document is required !!! | The error occurs if bizTransaction | @type does not equal urn:epcglobal:cbv:btt:desadv, or if source is empty or null. |
| Unable to parse data. bizTransaction must begin with urn:epcglobal:cbv:bt: !!! | The error occurs if the source does not begin with string urn:epcglobal:cbv:bt:. |
|
| disposition | Disposition urn:epcglobal:cbv:disp:in_progress is required for ObjectEvent void shipping !!! | The error occurs if the source does not equal urn:epcglobal:cbv:disp:in_progress. |
| ObjectEvent | At least one ObjectEvent for void shipment transaction is required !!! | The error occurs if the source input file does not include at least one ObjectEvent. |
| Only one ObjectEvent for the void shipment transaction is required !!! | The error occurs if more than one ObjectEvent is present. | |
| tl:changeReasonCode | Valid reason code is required !!! | The error occurs if the source is empty or null, or is not a valid value from the enumeration list. |
| tl:locationId | @type | Valid location identifier type is required !!! | The error occurs if the source is present, but there is no matching entry in the lookup file. |
| tl:partnerId | @type | Party type attribute is required when source partner Id is populated !!! | The error occurs if cmn:PartnerId is populated, but the source is empty or null. |
| Valid partner identifier type is required !!! | The error occurs if the source is present, but there is no matching entry in the lookup file. | |
| Class 2 | ||
| cmn:DeliveryNumber | Delivery [Delivery Number]: Shipment transaction for specified delivery number must be a sales shipment. Transfer shipment may not be voided. | The error occurs if the specified delivery number refers to a transfer shipment, not a sales shipment. |
| Delivery [Delivery Number]: Shipment transaction for specified delivery number has not been submitted. | The error occurs if the specified delivery number does not refer to a shipment in a submitted state. | |
| Delivery [Delivery Number]: The serial numbers for the specified deliver must be in a Commissioned - Shipped state. | The error occurs if the serial numbers are not in a Commissioned - Shipped state. | |
| Class 3 | ||
| The following is thrown for all Class 3 errors: “INTERNALERROR=Internal error from server [server details].” Please contact Support if this error is encountered. | ||
