EPCIS Ruleset Descriptions

What is this Document? 

This document is meant to provide guidance on resolving errors and warnings provided by EPCIS Investigator found in EPCIS files. 

Resolutions will typically involve adding and modifying your Master Data in Onesan or having a new, corrected file be sent from its original source. 

You can filter for errors or warnings in this document by its Rule Number, Rule Message, or by its entire message found in EPCIS Investigator

Template

Message 1077: sscc cannot be aggregated to homogeneous case (sgtin)  

SSCC is not homogeneous with the case it is being aggregated to, case must stay homogenous  

Aggregate SSCC to its own case if needed 

 Message 1065: bizTransactionList should be omitted for aggregationEvent ([Item])   

BizTransactionList is found in aggregationEvent (packing) 

Generally, bizTransactionList includes PO and Shipment information 

<bizTransactionList> 

        <bizTransaction type="urn:epcglobal:cbv:btt:desadv">urn:epcglobal:cbv:bt:GLN:SHIPMENTID</bizTransaction> 

        <bizTransaction type="urn:epcglobal:cbv:btt:po">urn:epcglobal:cbv:bt:GLN:PO#                               </bizTransaction> 

</bizTransactionList> 

 Message 1067: action [Action] is invalid or not supported for bizstep:packing - expecting add.  

<action>ADD</action> - Commisioning/Packing 

<action>OBSERVE</action> - Shipping 

 Message 1061: eventTimeZoneOffset is a required element.  

Added after eventTime: <eventTimeZoneOffset>+00:00</eventTimeZoneOffset> 

 Message 1063: parentId is missing or invalid  

Required for childEPCs to be aggregated to parent. Aggregated to SSCC or sGTIN 

<parentID>urn:epc:id:sscc:SSCC</parentID>  

<parentID>urn:epc:id:sgtin:SSCC</parentID> 

 Message 1072: childEPC(s) in aggregationEvent were not commissioned ([Item])  

SGTINs that are aggregated were not commissioned 

Add commissioning event for childEPCs 

 Message 1075: childEPC(s) were declared as parentID after aggregationEvent eventTime. ([Key])  

After sGTIN(s) were commissioned, and then aggregated to a case, it was used as a parent for a bundle.  

Commissioning -> Aggregation (single into a bundle) -> Aggregation (into a case).   

 Message 1073S: parentID SSCC [parentId] found as a parentID in a prior aggregationEvent  

Attempted to have 2 aggregationEvents for 1 SSCC 

Move second group of childEPCs to first aggregationEvent  

 Message 1060: bizLocation is missing or invalid.  

<bizLocation> <id>urn:epc:id:sgln:SGLN</id> </bizLocation> 

 Message 1073G: parentID sGTIN [parentId] found as a parentID in a prior aggregationEvent  

ParentID sGTIN can be listed multiple times if aggregated that way however this error will need to be turned to a warning 

 Message 1069: parentID not found in prior commissioning event ([Item])  

SSCC or parent sGTIN was not commissioned before it was used as the parentID in an aggregationEvent 

LOCATION VOCABULARY

Message 1021: Vocabulary attribute name is required  

Company name is missing in VocabularyElement 

Ensure structure in vocab, and entity location’s name is in master data 

<attribute id="urn:epcglobal:cbv:mda#name" >COMPANY_NAME</attribute> 

 Message 1024: Vocabulary attribute state is required  

Company's State from address is missing in VocabularyElement 

Ensure structure in vocab, and entity location’s address is complete in master data 

<attribute id="urn:epcglobal:cbv:mda#state">COMPANY_STATE</attribute> 

 Message 1029: Vocabulary attribute countryCode is invalid, expecting standard two-letter abbreviation 

Ensure structure in vocab, and entity location’s address is complete in master data with a two letter code for Country Code 

<attribute id="urn:epcglobal:cbv:mda#countryCode">TWO_LETTER_CODE</attribute> 

 Message 1030: Vocabulary attribute countryCode is invalid, countryCode not identified  

Ensure structure in vocab, and entity location’s address is complete in master data with a two letter code for Country Code 

Available Alpha-2 (two letter code) can be found at https://www.iban.com/country-codes 

 Message 1025: Vocabulary attribute postalCode is required  

Company's postal code from address is missing in VocabularyElement 

Ensure structure in vocab, and entity location’s address is complete in master data 

<attribute id="urn:epcglobal:cbv:mda#postalCode">ZIP_CODE</attribute>  

 Message 1027: Vocabulary attribute state, expecting standard two-letter abbreviation.   

Ensure structure in vocab, and entity location’s address is complete in master data with a two letter code for State 

<attribute id="urn:epcglobal:cbv:mda#state">TWO_LETTER_CODE</attribute> 

 Message 1028: Vocabulary attribute state is invalid, state not identified  

Ensure structure in vocab, and entity location’s address is complete in master data with a two letter code for State 

Available two letter state abreviations can be found at https://www.faa.gov/air_traffic/publications/atpubs/cnt_html/appendix_a.html 

 Message 1022: Vocabulary attribute streetAddressOne is required  

Ensure structure in vocab, and entity location’s address is complete in master data with a street address 

<attribute id="urn:epcglobal:cbv:mda#streetAddressOne”>STREET_ADDRESS</attribute> 

 Message 1026: Vocabulary attribute countryCode is required  

Ensure structure in vocab, and entity location’s address is complete in master data 

<attribute id="urn:epcglobal:cbv:mda#countryCode">TWO_LETTER_CODE</attribute> 

 Message 1020: Vocabulary Element List Type is invalid - expecting urn:epc:id:sgln:CompanyPrefix.LocationReference.Extension  

The sGLN format within the vocabulary section does not match the above structure.

Message 1023: Vocabulary attribute city is required  

 Ensure structure in vocab, and entity location’s address is complete in master data 

<attribute id="urn:epcglobal:cbv:mda#city">CITY</attribute>

 OBJECT EVENT – SCHEMA

Message 1037: Event List Type cannot identify any aggregationEvent(s)  

No aggregation (packing) events found in file 

Should include aggregationEvent for packing items to bundle/case/pallet

<AggregationEvent> 

             <eventTime>YYYY-MM-DDTHH:MM:SS.MSZ </eventTime> 

            <eventTimeZoneOffset>-05:00 </eventTimeZoneOffset> 

            <parentId> urn:epc:id:sscc:SSCC </parentId> 

            <childEPCs> 

               <epc> urn:epc:id:sgtin:</epc> 

               <epc> urn:epc:id:sgtin:</epc> 

               <epc> urn:epc:id:sgtin:</epc> 

           </childEPCs> 

            <action> ADD </action> 

            <bizStep> urn:epcglobal:cbv:bizstep:packing </bizStep> 

            <disposition> urn:epcglobal:cbv:disp:in_progress </disposition> 

            <readPoint> 

               <id> urn:epc:id:sgln:SGLN</id> 

 </readPoint> 

            <bizLocation> 

               <id> urn:epc:id:sgln:SGLN</id> 

            </bizLocation> 

        </AggregationEvent> 

 Message 1043: disposition is missing or invalid  

Valid options are  

Commissioning 

urn:epcglobal:cbv:disp:active  

Aggregation 

urn:epcglobal:cbv:disp:in_progress 

Shipping 

urn:epcglobal:cbv:disp:in_transit 

Each ObjectEvent should have one  

Appears after bizStep, but before readPoint for any event. 

<bizStep> urn:epcglobal:cbv:bizstep:commissioning</bizStep> 

           <disposition> urn:epcglobal:cbv:disp:active</disposition> 

            <readPoint> 

                 <id> urn:epc:id:sgln:SGLN</id> 

            </readPoint> 

  Message 1042: bizStep is missing or invalid  

Add bizStep in following format:  

<bizStep>urn:epcglobal:cbv:bizstep:(packing, commissioning, etc)</bizStep> 

 Message 1036: Event List Type cannot identify any objectEvent(s).  

Could be general error. Ex} Missing items in order 

 Message 1038E: Custom extensions could cause errors and add to processing time. You should not include custom extensions for required master data attributes or product identifier(s) such as  

Not a GS1 extension in the header  

xmlns:epcis 

xmlns:gs1ushc 

xmlns:sbdh 

xmlns:cbvmda 

 Message 1035: Event List Type is missing or invalid - ObjectEvent, AggregationEvent and TransactionEvent are supported. 

Within the eventList, there are invalid tags, or no tags included. Only the above tags are supported in EPCIS 1.2  

 Message 1039: eventTimeZoneOffset is a required element  

EventTimeZoneOffset is missing within the EPCIS file 

Each eventTime should have an offset directly after the eventTime 

<eventTime> YYYY-MM-DDTHH:MM:SS.MSZ </eventTime> 

             <eventTimeZoneOffset> + or - HH:MM </eventTimeZoneOffset> 

 Message 1038: eventTime is a required element  

EventTime is missing within the EPCIS file 

eventTime should be included at the top of each event 

<eventTime> YYYY-MM-DDTHH:MM:SS.MSZ </eventTime> 

 Message 1041: action is missing or invalid  

Action is missing for ObjectEvent 

Action should be included after the epcList in all ObjectEvents 

Options below 

<action> ADD </action> - Commissioning 

<action> ADD </action> - Packing / Aggregation 

<action> OBSERVE</action> - Shipping 

 Message 1044: bizLocation is invalid, expecting URI format.  

This usually occurs when a GLN is sent in the bizLocation, when it expects the sGLN format 

<bizLocation> 

             <id> urn:epc:id:sgln:SGLN</id> 

</bizLocation> 

 Message 1049: bizLocation is a required element for a commissioning event  

BizLocation should be included in each commissioning event following the readPoint 

This denotes where the items were commissioned.  

<bizLocation> 

             <id> urn:epc:id:sgln:SGLN</id> 

</bizLocation> 

 Message 1045: bizTransactionList is invalid.  

General error in bizTransactionList format 

<bizTransactionList> 

               <bizTransaction 

 type="urn:epcglobal:cbv:btt:desadv">urn:epcglobal:cbv:bt:GLN:SHIPMENTID <bizTransaction> 

               <bizTransaction type="urn:epcglobal:cbv:btt:po">urn:epcglobal:cbv:bt:GLN:ORDERID</bizTransaction> 

            </bizTransactionList> 

Message 1200: Schema imports are invalid or not supported. [Warning Message] 

Using tags from a schema did not import or the schema referenced is invalid completely. To resolve this, verify that the schema you're using matches the required version for your system. Update the schema to the latest version if needed and ensure it adheres to the correct format. warnings are fine, you also can disregard it.

 EPC CLASS VOCABULARY

Message 1016V: Vocabulary attribute additionalTradeItemIdentification is > 80 characters 

Attribute is longer than 80 characters 

Generally is the NDC 

<attribute id="urn:epcglobal:cbv:mda#additionalTradeItemIdentification">NDC</attribute> 

 Message 1016: Vocabulary attribute additionalTradeItemIdentification is required   

Attribute is missing entirely  

<attribute id="urn:epcglobal:cbv:mda#additionalTradeItemIdentification">NDC</attribute> 

 Message 1008: Vocabulary List Schema is invalid  

General schema issue for vocab list 

Structure should be as follows 

For Item Vocab 

<Vocabulary type="urn:epcglobal:epcis:vtype:EPCClass" >  

<VocabularyElementList> 

<VocabularyElement id="urn:epc:idpat:sgtin:SGTIN >  

For Location Vocab 

<Vocabulary type="urn:epcglobal:epcis:vtype:Location >  

<VocabularyElementList> 

<VocabularyElement id="urn:epc:id:sgln:SGLN> 

 Message 1013: Vocabulary attribute dosageFormType is required  

Product vocab is missing an attribute 

<attribute> id="urn:epcglobal:cbv:mda#dosageFormType">DOSAGE TYPE</attribute> 

 Message 1012V: Vocabulary attribute regulatedProductName is > 500 chars  

Product vocab attribute is too long 

<attribute id="urn:epcglobal:cbv:mda#regulatedProductName"">DOSAGE TYPE</attribute> 

 Message 1009: Vocabulary Type is invalid - EPCClass type and Location type are required   

Type of Vocabulary element is invalid.  

Only available types are 

<Vocabulary type="urn:epcglobal:epcis:vtype:EPCClass"> 

<Vocabulary type="urn:epcglobal:epcis:vtype:Location"> 

 Message 1017: Vocabulary attribute additionalTradeItemIdentificationTypeCode, must be FDA_NDC_11.  

Attribute value is not FDA_NDC_11 

Only available option is 

<attribute id="urn:epcglobal:cbv:mda#additionalTradeItemIdentificationTypeCode">FDA_NDC_11</attribute> 

 Message 1015V: Vocabulary attribute netContentDescription is > 30 chars  

Attribute value is too long  

<attribute id="urn:epcglobal:cbv:mda#netContentDescription">1 </attribute> 

 Message 1015: Vocabulary attribute netContentDescription is required  

Attribute is missing or invalid 

<attribute id="urn:epcglobal:cbv:mda#netContentDescription">1 </attribute> 

 Message 1018: Vocabulary attribute additionalTradeItemIdentificationTypeCode is required  

Attribute is missing or invalid 

<attribute id="urn:epcglobal:cbv:mda#additionalTradeItemIdentificationTypeCode">FDA_NDC_11</attribute> 

 Message 1019: Vocabulary attribute dosageFormType is not a valid FDA dosage form.  

Attribute is not what is expected 

Ensure Dosage Form types are stored under Master Data -> Dosage 

Can view all available dosage form types here  

<attribute id="urn:epcglobal:cbv:mda#dosageFormType">INJECTION, POWDER </attribute> 

 Message 1011V: Vocabulary attribute manufacturerOfTradeItemPartyName is > 200 chars  

Attribute value is too long  

Should hold manufacturer’s name of the product  

<attribute id="urn:epcglobal:cbv:mda#manufacturerOfTradeItemPartyName">MANUFACTURER NAME </attribute> 

 Message 1011: Vocabulary attribute manufacturerOfTradeItemPartyName is required   

Attribute is missing or invalid 

<attribute id="urn:epcglobal:cbv:mda#manufacturerOfTradeItemPartyName"> MANUFACTURER NAME </attribute> 

 Message 1012: Vocabulary attribute regulatedProductName is required  

Attribute is missing or invalid 

<attribute id="urn:epcglobal:cbv:mda#regulatedProductName">PRODUCT NAME </attribute> 

 Message 1014V: Vocabulary attribute strengthDescription is > 30 chars  

Attribute value is too long 

<attribute id="urn:epcglobal:cbv:mda#strengthDescription">STRENGTH </attribute>

Message 1219: Structure of the document is invalid: item [ItemId] is registered in two different parents  

SGTIN or SSCC was packed twice to two different parents in the aggregationEvents.   

Item can be in only 1 packing event, to 1 parent.  

Remove sGTIN from the parent packing event that does not correlate with the physical package it was packed into 

 Message 1046: action [Action] is invalid or not supported for bizstep:commissioning - expecting add  

Action under bizstep:commissioning is something other than ADD 

Only option available is 

<action> ADD</action> 

          <bizStep> urn:epcglobal:cbv:bizstep:commissioning </bizStep> 

 Message 1221: The field ReadPoint has an incorrect format  

-Correct format:  

<readPoint>  

<id>urn:epc:id:sgln:SGLN</id>  

</readPoint> 

Message 1051: epc(s) not defined in the vocabulary element list for gtin ([code]) 

GTIN in <VocabularyElementList> has no epcs in the file 

Each GTIN in the <VocabularyElementList> needs to be used in the file 

Add the missing EPCs into the file 

 Message 1052: sgtin identified in multiple commissioning events  

An sGTIN or item is found in more than one commissioning event 

Items can only be commissioned one time 

Remove sGTIN from second commissioning event 

 Message 1053: sscc identified in multiple commissioning events  

An SSCC or pallet is found in more than one commissioning event 

SSCC or item can only be commissioned one time 

Remove SSCC from second commissioning event 

 Message 1047: disposition [Disposition] is invalid or not supported for bizstep:commissioning - expecting active  

Disposition for bizstep:commissioning is something other than active 

Only available option is 

<disposition> urn:epcglobal:cbv:disp:active </disposition> 

 Message 1040: epcList is missing or invalid.  

-Correct format: 

<epcList>  

<epc>urn:epc:id:sgtin:SGTIN</epc>  

</epcList> 

 Message 1050: bizTransactionList should be omitted from a commissioning event   

BizTransactionList is included in commissioning event 

Generally bizTransactionList is found at the end of the file to signify what order ID or shipment ID this order correlates with.  

Remove bizTransactionList from commissioning event  

 Message 1222: ilmd data missing  

-Correct format: 

<ilmd>  

<cbvmda:lotNumber>AU041445</cbvmda:lotNumber>  

<cbvmda:itemExpirationDate>2025-01-31</cbvmda:itemExpirationDate>  

</ilmd>

SHIPPING EVENT

Message 1087: source is in invalid format - expecting urn:epc:id:sgln:CompanyPrefix.LocationReference.Extension ([SGLN])  

Source within sourceList tag is in an invalid format  

Expected format below 

<sourceList> 

                  <source type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN </source> 

                  <source type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:SGLN</source> 

               </sourceList> 

 Message 1079: bizLocation should be omitted for bizstep:shipping  

BizLocation is generally for commissioning and aggregation events.  

BizLocation should be removed from the shipping  bizstep 

 Message 1098: epc(s) for epcList are invalid - epc(s) missing in aggregationEvent as parentId ([Item])  

The case or bundle sGTIN is missig from an aggregationEvent as a parent 

The AggregationEvent for this case or bundle should be added to the file 

    <AggregationEvent> 

           <eventTime>YYYY-MM-DDT16:37:03.413Z</eventTime> 

             <eventTimeZoneOffset>+08:00</eventTimeZoneOffset> 

             <parentID>urn:epc:id:sgtin:</parentID> 

            <childEPCs> 

                   <epc>urn:epc:id:sgtin:</epc> 

            </childEPCs> 

            <action>ADD</action> 

                 <bizStep>urn:epcglobal:cbv:bizstep:packing</bizStep> 

             <disposition>urn:epcglobal:cbv:disp:in_progress</disposition> 

            <readPoint> 

                   <id>urn:epc:id:sgln:</id> 

            </readPoint> 

            <bizLocation> 

                   <id>urn:epc:id:sgln:</id> 

            </bizLocation> 

       </AggregationEvent> 

 Message 1107: objectEvent for bizstep:shipping - bizTransaction contains more than one purchase order  

There is more than 1 PO for the bizTransaction 

Remove the multiple PO lines from the bizTransactionList 

<bizTransaction 

 type="urn:epcglobal:cbv:btt:po"> urn:epcglobal:cbv:bt:0860004013907:896449 </bizTransaction> 

 Message 1090: sourceList sGLN owning party or location not defined in the Location vocabulary ([SGLN])  

The Source Owning Party and Location in the sourceList were not defined in the location vocabulary section at the top of the file 

Add the missing sGLN information to the vocabulary section 

<VocabularyElement id="urn:epc:id:sgln:"> 

               <attribute id="urn:epcglobal:cbv:mda#name"> </attribute> 

               <attribute id="urn:epcglobal:cbv:mda#streetAddressOne"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#streetAddressTwo"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#city"> </attribute> 

               <attribute id="urn:epcglobal:cbv:mda#state"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#postalCode"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#countryCode"> </attribute> 

    </VocabularyElement> 

 Message 1082: sourceList is missing or invalid for objectEvent bizstep:shipping  

The sourceList for shipping ObjectEvent is missing or invalid 

Add the missing information to the shipping ObjectEvent 

<sourceList> 

           <source type="urn:epcglobal:cbv:sdt:owning_party"> urn:epc:id:sgln:</source> 

           <source type="urn:epcglobal:cbv:sdt:location"> urn:epc:id:sgln: </source> 

         </sourceList> 

 Message 1211: sourceList urn:epcglobal:cbv:sdt:location is a required type  

The source location for shipping ObjectEvent is missing or invalid 

Add the missing information to the shipping ObjectEvent

<sourceList> 

        <source type="urn:epcglobal:cbv:sdt:owning_party"> urn:epc:id:sgln </source> 

        <source type="urn:epcglobal:cbv:sdt:location"> urn:epc:id:sgln: </source> 

 </sourceList> 

 Message 1007: destination owning_party is invalid - expecting company headquarter sgln ([sGLN])   

The source owning party is not the headquarters location 

Ensure the location is added to your Master Data Entity Locations, and ensure the Type is HQ for their corporate level sGLN 

Reprocess the file, or request a new file after the master data has been validated 

 Message 1083: destinationList is missing or invalid for objectEvent bizstep:shipping   

The destinationList section is missing or incorrect. 

Add/update the missing section 

<destinationList> 

         <destination type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN</destination> 

            <destination type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:SGLN</destination> 

    </destinationList> 

 Message 1099: bizTransactionList was found in objectEvent and is invalid for bizstep shipping   

The destinationList section is missing or incorrect. 

Add/update the missing section 

<destinationList> 

         <destination type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN</destination> 

            <destination type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:SGLN</destination> 

    </destinationList> 

 Message 1105: bizTransaction urn:epcglobal:cbv:btt:po is in invalid format - expecting urn:epcglobal:cbv:bt:destinationOwnerGln:po.   

The PO section of the bizTransaction is incorrect. 

Update the incorrect PO section 

         <destination type="urn:epcglobal:cbv:btt:po"> urn:epcglobal:cbv:bt:DESTINATIONOWNERGLN:PO#</destination> 

 Message 1140: Serial numbers in the shipping event are not the outermost package of the shipment. Missing epc [Item].  

The items shipped during the shipping event are not the highest packaging level. 

This error is usually in tandem with error code 1096, if an SSCC is shipped during the shipping event. 

Add the commissioning event for the SSCC and reprocess file 

Ship the items at the bundle level 

 Message 1100: bizTransaction type is invalid, expecting urn:epcglobal:cbv:btt:po or urn:epcglobal:cbv:btt:inv  

The bizTransaction tags of the bizTransactionList section are incorrect. 

Update the incorrect bizTransaction tags 

         <bizTransaction type="urn:epcglobal:cbv:btt:po”>des urn:epcglobal:cbv:bt:DESTINATIONOWNERGLN:PO#/bizTransaction> 

      <bizTransaction type="urn:epcglobal:cbv:btt:desadv"> type="urn:epcglobal:cbv:btt:desadv">urn:epcglobal:cbv:bt:GLN:SHIPMENTID</bizTransaction> 

 Message 1216: destinationList owning party and location should use site-level sgln  

The sGLN sent in the destinationList is ending in something other than “.0” 

SGLN should be verified and updated in the MD then reprocessed or resent from supplier.  

 Message 1089: destination is in invalid format - expecting urn:epc:id:sgln:CompanyPrefix.LocationReference.Extension ([SGLN])  

Destination in either the location or owning party of the destinationList is incorrect. 

Update the value of the tags to match the above structure then reprocess or have file resent from supplier 

<destination type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln: COMPANYPREFIX.LOCATIONREFERENCE.EXTENSION </destination> 

 Message 1086: sourceList urn:epcglobal:cbv:sdt:owning_party is a required type  

The sourceList owning party line is missing 

Add the required line within the sourceList tags 

<source type="urn:epcglobal:cbv:sdt:owning_party"> urn:epc:id:sgln:SGLN </source> 

 Message 1086S: destinationList urn:epcglobal:cbv:sdt:owning_party is a required type  

The owning party line is missing within the destinationList 

Add the required line within the destinationList tags 

<destination type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN</destination> 

 Message 1084: source type is invalid - expecting urn:epcglobal:cbv:sdt:owning_party or urn:epcglobal:cbv:sdt:location  

The type of source under sourceList is incorrect or missing 

Add the missing lines or update the invalid lines then reprocess 

<source type="urn:epcglobal:cbv:sdt:owning_party"> urn:epc:id:sgln:SGLN </source>  <source type="urn:epcglobal:cbv:sdt:location"> urn:epc:id:sgln: SGLN</source> 

Message 1080: action [Action] is invalid or not supported for objectEvent bizstep:shipping - expecting observe.  

Action for shipping object event is invalid.  

The only valid action for shipping is OBSERVE 

Update the incorrect action to OBSERVE 

         <action>OBSERVE</action> 

        <bizStep> urn:epcglobal:cbv:bizstep:shipping</bizStep> 

 Message 1096: epc(s) for epcList are invalid - epc(s) prior commissioning event not found ([Item])  

The items listed in the errors are missing a commissioning event  

Add the missing epc(s) to the commissioning event and reprocess file or have the supplier resend the file  

 Message 1081: disposition [Disposition] is invalid or not supported for shipping, expecting in_transit  

Disposition for shipping object event is invalid.  

The only valid disposition for shipping is in_transit 

Update the incorrect action to in_transit 

<disposition> urn:epcglobal:cbv:disp:in_transit </disposition>sit 

 Message 1215: sourceList owning party and location should use site-level sgln   

The sGLN sent in the destinationList is ending in something other than “.0” 

SGLN should be verified and updated in the MD then reprocessed or resent from supplier. 

 Message 1093: destinationList sGLN owning party or location not defined in the Location vocabulary ([SGLN])  

The sGLN found in the destinationList was not previously defined in the Location Vocab 

Add the sGLNs from the destinationList to the Location Vocab and reprocess or have the file resent from the supplier 

<VocabularyElement id="urn:epc:id:sgln:SGLN"> 

                <attribute id="urn:epcglobal:cbv:mda#name"></attribute> 

                <attribute id="urn:epcglobal:cbv:mda#streetAddressOne"></attribute> 

                <attribute id="urn:epcglobal:cbv:mda#streetAddressTwo"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#city"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#state"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#postalCode"> </attribute> 

                <attribute id="urn:epcglobal:cbv:mda#countryCode"></attribute> 

              </VocabularyElement> 

 Message 1212: destinationList urn:epcglobal:cbv:sdt:location is a required type  

The location under destinationList is missing  

Add the missing location under destinationList and reprocess, or have the file resent from the supplier 

<destination type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:SGLN</destination>

EXTENSION FOR GS1 DSCSA TRANSACTION STATEMENT

Message 1034: legalNotice is missing or invalid, but not required  

Add the missing lines between the dscsaTransactionStatement tags 

       <gs1ushc:legalNotice> Seller has complied with each applicable subsection of FDCA Sec. 581(27)(A)-(G). </gs1ushc:legalNotice> 

 Message 1031: dscsaTransactionStatement is required in the document header  

Add the missing lines after the header vocab, but before the EPCISBody

<gs1ushc:dscsaTransactionStatement> 

       <gs1ushc:affirmTransactionStatement> true  </gs1ushc:affirmTransactionStatement> 

       <gs1ushc:legalNotice> Seller has complied with each applicable subsection of FDCA Sec. 581(27)(A)-(G). </gs1ushc:legalNotice> 

     </gs1ushc:dscsaTransactionStatement> 

 Message 1032: affirmTransactionStatement is required for dscsaTransactionStatement in the document header  

Add the missing lines between the dscsaTransactionStatement tags 

       <gs1ushc:affirmTransactionStatement> true  </gs1ushc:affirmTransactionStatement> 

 Message 1033: affirmTransactionStatement is false, shipment is not DSCSA compliant   

The affirmTransactionStatement needs to be true to be DSCSA compliant, meaning that the transaction does comply with the DSCSA 

Update the false affirmTransactionStatement to true 

<gs1ushc:affirmTransactionStatement> true   </gs1ushc:affirmTransactionStatement>

STANDARD BUSINESS DOCUMENT HEADER (SBDH)

Message 1203: Invalid SBDH, more than one receiver  

Only 1 sGLN can be listed as the SBDH receiver 

Update the SBDH receiver value to ensure there is only 1 sGLN  

 <sbdh:Receiver> 

        <sbdh:Identifier Authority="SGLN" > urn:epc:id:sgln:SGLN </sbdh:Identifier> 

     </sbdh:Receiver> 

 Message 1003S: Standard business document header - invalid sender identifier - expecting urn:epc:id:sgln:CompanyPrefix.LocationReference.Extension.  

The structure of the identifier under SBDH Sender is in an incorrect format 

Ensure the structure of the SBDH sender matches the below structure 

Reprocess or have the supplier resend the file 

<sbdh:Sender> 

        <sbdh:Identifier Authority="SGLN" > urn:epc:id:sgln:SGLN </sbdh:Identifier> 

     </sbdh:Sender> 

 Message 1204: InstanceIdentifier is invalid or missing  

The InstanceIdentifier is a required field  

Add or update the missing or invalid InstanceIdentifier  

<sbdh:InstanceIdentifier>UNIQUE_IDENTIFIER<sbdh:InstanceIdentifier> 

 Message 1201: Invalid structure - Standard business document header (SBDH) is missing from the EPCISHeader  

The structure of the file is incorrect  

The SBDH section is a required section of an EPCIS document 

Add/Update the missing or invalid section in the EPCIS header, matching the structure below 

<sbdh:StandardBusinessDocumentHeader> 

   <sbdh:HeaderVersion>1.0 </sbdh:HeaderVersion> 

   <sbdh:Sender> 

        <sbdh:Identifier Authority="SGLN" > urn:epc:id:sgln:SGLN</sbdh:Identifier> 

     </sbdh:Sender> 

   <sbdh:Receiver> 

        <sbdh:Identifier Authority="SGLN" > urn:epc:id:sgln:SGLN</sbdh:Identifier> 

    </sbdh:Receiver> 

     <sbdh:DocumentIdentification> 

        <sbdh:Standard>EPCGlobal </sbdh:Standard> 

        <sbdh:TypeVersion> 1.0</sbdh:TypeVersion> 

                          <sbdh:InstanceIdentifier>UNIQUE_IDENTIFIER<sbdh:InstanceIdentifier> 

        <sbdh:Type> Events</sbdh:Type> 

         <sbdh:CreationDateAndTime>YYYY-MM-DDTHH:MM:SS.MSZ</sbdh:CreationDateAndTime> 

       </sbdh:DocumentIdentification> 

     </sbdh:StandardBusinessDocumentHeader> 

 Message 1205: InstanceIdentifier [Identifier] has been processed at [Date] with id [OtherId]   

The instance identifier sent in the file was already processed 

This usually means we have received this file already and a duplicate has been sent 

If this is confirmed and validated as a new file, the supplier should resend the file with an updated instance identifier 

Ignore if confirmed file was already received 

 Message 1202: Invalid SBDH, more than one sender  

Only 1 sGLN can be listed as the SBDH sender 

Update the SBDH sender value to ensure there is only 1 sGLN  

 <sbdh:Sender> 

        <sbdh:Identifier Authority="SGLN" > urn:epc:id:sgln:SGLN</sbdh:Identifier> 

     </sbdh:Sender> 

 Message 1002: Standard business document header - invalid sender/receiver authority - expecting sGLN  

Error usually appears when a GLN or some other identifier is sent in the identifer sections of the SBDH.  

Verify the sGLN sent in he SBDH identifiers 

 <sbdh:Identifier Authority="SGLN">urn:epc:id:sgln:SGLN</sbdh:Identifier

GENERAL

Message 1300: Incorrect URN format [URN]  

General formatting error 

The URN included in the error message should point you to where the formatting issue is 

 Message 1135: Aggregation event(s) are missing or invalid from the EventList and are required. Aggregation events are defined as an aggregationEvent with bizStep packing.   

The file is missing aggregationEvents 

Add the aggregation events for the packing of items into higher packaging levels matching the format below  

     <AggregationEvent> 

        <eventTime> YYYY-MM-DDTHH:MM:SS.MSZ </eventTime> 

        <eventTimeZoneOffset> +00:00 </eventTimeZoneOffset> 

       <parentID> urn:epc:id:sscc:SSCC </parentID> 

        <childEPCs> 

              <epc> urn:epc:id:sgtin:SGTIN </epc> 

        </childEPCs> 

        <action> ADD</action> 

        <bizStep> urn:epcglobal:cbv:bizstep:packing </bizStep> 

        <disposition> urn:epcglobal:cbv:disp:in_progress </disposition> 

        <readPoint> 

              <id> urn:epc:id:sgln:SGLN </id> 

        </readPoint> 

        <bizLocation> 

              <id> urn:epc:id:sgln:SGLN </id> 

        </bizLocation> 

         </AggregationEvent> 

 Message 1136: Shipping event(s) are missing or invalid from the EventList and are required. Shipping events are defined as an objectEvent with bizStep shipping.  

The Shipping event in the file is either missing or invalid 

Add the missing shipping event matching the structure below, then reprocess or have the file resent from the supplier.  

<ObjectEvent> 

        <eventTime> 2023-11-21T14:46:07.174Z </eventTime> 

        <eventTimeZoneOffset> +00:00 </eventTimeZoneOffset> 

        <epcList> 

               <epc> urn:epc:id:sscc:SSCC</epc> 

        </epcList> 

        <action> OBSERVE </action> 

        <bizStep> urn:epcglobal:cbv:bizstep:shipping</bizStep> 

       <disposition> urn:epcglobal:cbv:disp:in_transit </disposition> 

       <readPoint> 

              <id> urn:epc:id:sgln:08600107146.0.0 </id> 

       </readPoint> 

       <bizTransactionList> 

          <bizTransaction type="urn:epcglobal:cbv:btt:po">urn:epcglobal:cbv:bt:GLN:PO# </bizTransaction> 

               <bizTransaction type="urn:epcglobal:cbv:btt:desadv">urn:epcglobal:cbv:bt:GLN:SHIPMENTID        </bizTransaction> 

       </bizTransactionList> 

       <extension> 

          <sourceList> 

            <source type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN     </source> 

                <source type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:SGLN     </source> 

          </sourceList> 

          <destinationList> 

                     <destination type="urn:epcglobal:cbv:sdt:owning_party">urn:epc:id:sgln:SGLN</destination> 

                     <destination type="urn:epcglobal:cbv:sdt:location">urn:epc:id:sgln:              </destination>  

         </destinationList> 

       </extension> 

</objectEvent> 

 Message 1134: Commissioning event(s) are missing or invalid from the EventList and are required. Commissioning events are defined as an objectEvent with bizStep commissioning 

The Commissioning event in the file is either missing or invalid 

Add the missing commissioning event matching the structure below, then reprocess or have the file resent from the supplier. 

<ObjectEvent> 

        <eventTime> 2023-11-21T14:46:07.174Z </eventTime> 

        <eventTimeZoneOffset> +00:00 </eventTimeZoneOffset> 

        <epcList> 

               <epc> urn:epc:id:sscc:SSCC</epc> 

        </epcList> 

        <action> ADD</action> 

       <bizStep> urn:epcglobal:cbv:bizstep:commissioning</bizStep> 

       <disposition> urn:epcglobal:cbv:disp:active</disposition> 

        <readPoint> 

              <id> urn:epc:id:sgln:SGLN</id> 

       </readPoint> 

    <bizLocation> 

                <id> urn:epc:id:sgln:SGLN</id> 

    </bizLocation> 

    <extension> 

<ilmd> 

     <cbvmda:itemExpirationDate>YYYY-MM-DD             

   </cbvmda:itemExpirationDate> 

   <cbvmda:lotNumber>LOTNUMBER</cbvmda:lotNumber> 

</ilmd> 

   </extension> 

</ObjectEvent> 

Dispensers can scan against data as part of their order receiving process. This can replace existing receipt methods such as stickering or manual verification once EPCIS data is fully complete. They are not absolutely required to scan against data, but as it becomes more complete, it is a useful way to verify the validity of every product they receive.