Void Shipment Guidelines (EPCIS v1.2)
See How To Use this Guide before interpreting the guidelines below.
Message Type: SOM_VOID_SHIPMENT
Info Exchange Display Name: Void Shipment

Data Element | Occurs Length |
Type | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
epcis:EPCISDocument | - |
1...1- | Required. EPCIS message root element. | |||||||
@schemaVersion | 0/* |
1...1Decimal | Required. The version of the EPCIS schema used to populate the EPCIS document elements. Must equal 1.2 .1 |
|||||||
@creationDate | 1/* |
1...1DateTime | Required. Date the message was created in YYYY-MM-DDTHH:MM:SS:mmZ format.2 | |||||||
EPCISHeader | - |
0...1- | Required.The XML file control header. | |||||||
sbdh:StandardBusinessDocumentHeader | - |
1...1- | Required. Business header information including EPCIS Header Version, Sender, and Receiver information, along with the document identification. | |||||||
sbdh:HeaderVersion | 0/* |
1...1String | Required.Version of the Standard Business Document Header (SBDH). The HeaderVersion must be set to 1.0 .3 |
|||||||
sbdh:Sender | - |
1...*- | Required. A unique identification key for the Sender party of the message, representing the organization that created the standard business document. The Sender element must be used only once with GS1 XML messages. | |||||||
sbdh:Identifier | 1/* |
1...1String |
Required. The value of the Identifier element may be a GLN, SGLN, or any other supported business party type.4 Send SGLN and all other party types with the GS1-conformant uri prefix, for example:
See the MDPartyTypeAttributes enumeration list for valid values. ![]() |
|||||||
@Authority | 1/* |
1...1String |
Required. The sender identifier type. The Authority was previously expected to be set to See the MDPartyTypeEnums enumeration list for valid values. |
|||||||
sbdh:ContactInformation | - |
0...*- | Required. Indicates a unique identification key for the direct Receiver party of the message, representing the organization that receives the standard business document. The Receiver element is used only once with GS1 XML messages. | |||||||
sbdh:Receiver | - |
1...*- |
Required. The value of the Identifier element may be a GLN, SGLN, or any other supported business party type.6 Send SGLN and all other party types with the GS1-conformant uri prefix, for example:
See the MDPartyTypeAttributes enumeration list for valid values. ![]() |
|||||||
sbdh:Identifier | 1/* |
1...1String |
Required. The receiver identifier type. The Authority was previously expected to be set to "GLN" for GS1 XML messages. An update made in December 2016 changed this to accept additional values.7 See the MDPartyTypeEnums enumeration list for valid values. |
|||||||
@Authority | 1/* |
1...1String | Required. Contains the identification group for the message. | |||||||
sbdh:ContactInformation | - |
0...*- | Required. Name of the document standard contained in the file or message. The standard value for this field is EPCglobal .8 |
|||||||
sbdh:DocumentIdentification | - |
1...1- | Required. Reflects the version of the document included. This is the complete version of the document itself and is different from the HeaderVersion as these are hard-coded values. The TypeVersion is set to 1.0 .9 |
|||||||
sbdh:Standard | 0/* |
1...1String | Required. Reference information that uniquely identifies this instance of the Standard Business Document between the Sender and the Receiver. This identifier confirms this document as being distinct from others.10 | |||||||
sbdh:TypeVersion | 0/* |
1...1String | Required. The document type. The Type value is set to "Events" for a void shipment event.11 | |||||||
sbdh:InstanceIdentifier | 1/* |
1...1String | Required. The date and time of the SBDH document's creation. GMT create date and time for the EPCIS message. The system expects the Z to be appended; however, if it is not included, the system assumes that the time is GMT and therefore appends the Z .12 |
|||||||
sbdh:Type | 0/* |
1...1String | Required. The document type. The Type value is set to "Events" for a take product sample event.13 | |||||||
sbdh:CreationDateAndTime | 0/* |
1...1DateTime | Required. EPCIS message root element. | |||||||
EPCISBody | - |
1...1- | Required. Contains all of the EPCIS events for this message. | |||||||
EventList | - |
1...1- | Required. Only one ObjectEvent will be present in the EventList for the Void Shipment message. | |||||||
choice | - |
1...*Choice | Required. Only ObjectEvent may be selected for EPCISBody | EventList. | |||||||
ObjectEvent | - |
1...*- |
Required. Choice 1 for EventList. Data = ObjectEvent for the Void Shipment message Events. EventList = ObjectEvent Void Shipment when all of the following is true:
|
|||||||
eventTime | 1/* |
1...1DateTime | Required. This field indicates the time stamp of date/time when the event occurred. Must include a time zone indicator as specified in Section 9.5 of [EPCIS1.0.1]. The system expects the "Z" to be appended; however if it is not included, the system assumes that the time is GMT and therefore appends the Z.14 | |||||||
recordTime | 0/* |
0...1DateTime | Not used. | |||||||
eventTimeZoneOffset | 1/* |
1...1String | Required. Time zone offset in effect at the time and place where the event occurred, consistent with what choice was made for eventTime. Per Section 7.2.8 of [EPCIS1.0.1].15 | |||||||
baseExtension | - |
1...1- | Not used. | |||||||
epcList | 1/* |
0...*String | Required. The EPCs of each item, case, and/or pallet commissioned. | |||||||
epc | 0/* |
1...1String | Required. The EPC identifier in EPC Pure Identity URI format. See EPC Pure Identifier Format Examples.16 | |||||||
action | 0/* |
0...1AnyURI | Required. The action value must equal OBSERVE .17 |
|||||||
bizStep | 0/* |
0...1AnyURI | Required. The bizStep value must equal urn:epcglobal:cbv:bizstep:void_shipping .18 |
|||||||
disposition | 0/* |
0...1AnyURI |
Required. The disposition value must equal |
|||||||
readPoint | - |
0...1- | This field identifies the location where the event occurred, i.e. the warehouse GLN location ID and storage location (e.g. shelf, bin), in URN format. | |||||||
id | 0/* |
1...1AnyURI | Required. The SGLN EPC of the location from where the event occurred. This may be a site-level SGLN, or a finer-grain location identifier.20 | |||||||
extension | - |
0...1- | Not used - GS1 Reserved. | |||||||
bizLocation | 1/* |
1...1AnyURI | Required. This value indicates the SGLN EPC of the location from where the event occurred. This may be a site-level SGLN, or a finer-grain location identifier. | |||||||
id | - |
0...1- | Required. The SGLN EPC of the location from where the event occurred. This may be a site-level SGLN, or a finer-grain location identifier.21 | |||||||
bizTransactionList | - |
0...1- | Required. Business documents required for void shipping message. Delivery document is mandatory. | |||||||
bizTransaction | 0/* |
1...*String |
Required. The business transaction identifiers for the Dispatch Advice (Advance Ship Notice) and/or Invoice and/or Purchase Order governing the shipment being voided, subject to Section 8.4.2 of [CBV1.0].22 The GLN that occurs after Delivery document (ASN) is mandatory but all document types are supported. |
|||||||
@type | 1/* |
1...1String |
Required. The transaction identifier type.. DESADV is the only biz transaction type that will be mapped. Valid value:23
Other types may be present in source file but if shipping document is missing an error will be thrown. |
|||||||
extension | – |
0…1- |
Indicates extension body for the shipping event. |
|||||||
sourceList | – |
0…1- |
Captures the sending business, location, and carrier parties for the delivery. Supports one of two functions:
|
|||||||
source | 0/* |
0…*String |
Captures the source party identifier for the sold from, ship from, or carrier parties. The party identifier in the source either:
Valid values:
![]() |
|||||||
@type | 0/* |
1…*String |
Conditionally required if source is populated. Captures the type of source party identifier. Valid values:
|
|||||||
destinationList | – |
0…1- |
Captures the receiving business or location parties and supports one of two functions:
|
|||||||
destination | 0/* |
0…*String |
Captures the destination party identifier for the sold to or ship to parties. Party identifier in destination either:
or
Valid values:
![]() |
|||||||
@type | 0/* |
1…*String |
Conditionally required if destination is populated. Captures the type of destination party identifier. Valid values:
|
|||||||
tl:locationId | - |
0...1- | Specifies identifier of facility/warehouse to scope the void shipping message for the delivery at the specified location.24 | |||||||
@type | - |
0...1- |
Required. Attribute that identifies location types.25 See the BusinessAndLocationId enumeration list for valid values. |
|||||||
tl:voidEventExtensions | - |
1...1- | Extensions used for Commission ObjectEvent. | |||||||
tl:deliveryDirection | 0/* |
0...1String | Required. Indicates whether the delivery is sent or received by the Partner. Determines if the message is for voiding a shipment or receipt. Valid values:
|
|||||||
tl:partnerId | 0/* |
1...1String | Conditionally required if delivery direction = Received . Partner ID for the delivery
document.26 |
|||||||
@type | 0/* |
1...1String |
Required. Partner identifier type.27 See the BusinessAndLocationId enumeration list for valid values. |
|||||||
tl:transactionDate | 1/* |
1...1Date | Required. User-specified date for Serialized Operations Manager Void message in XML date format YYYY-MM-DD.28 | |||||||
tl:orderCancelled | 0/* |
0...1Boolean |
Replaces CorrectShipment.
Tracks whether order is cancelled rather than intent to correct, aligning better
with future government reporting and ERP functionality. Default value is
|
|||||||
tl:changeReasonCode | 0/* |
1...1String |
Required. Code identifying reason for the void or correction.30 See the ReasonCodes enumeration list for valid values. |
|||||||
tl:reasonDescription | 0/* |
0...1String | Text description of reason code.31 |