You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For all of the following message specifications, the folder EPCIS message examples contains illustrative examples.
EPCIS Events to express the loading and unloading of load carriers
Comments
Note: if there are tradable and non-tradable OR several quality levels in the course of an arriving/departing event, we need to generate several EPCIS events.
Rationale: these criteria entail different business processes/pallet values. Thus, we have to properly distinguish quantities pertaining to different qualities.
Dim
Data Element
V1
V2
Description
RTIs arrive at a given location
RTIs leave a given location
Event Type
ObjectEvent
ObjectEvent
eventID
EPCIS Event Hash ID
EPCIS Event Hash ID
action
OBSERVE
OBSERVE
When
eventTime
Timestamp of event
Timestamp of event
What
quantityList
_quantityElement
__epcClass
GRAI (without serial number) of RTI
GRAI (without serial number) of RTI
__quantity
Number of arrived RTIs
Number of departed RTIs
Where
readPoint
SGLN (without GLN extension) of RTI exchange location
SGLN (without GLN extension) of RTI exchange location
EPCIS Events to express a change of ownership (only applicable for open pool systems)
Dim
Data Element
V3
Description
RTIs change ownership from one to another organisation
Event Type
ObjectEvent
eventID
EPCIS Event Hash ID
action
OBSERVE
When
eventTime
Timestamp of event
What
quantityList
_quantityElement
__epcClass
GRAI (without serial number) of RTI
__quantity
Number of RTIs changing ownership
Why
bizStep
Accepting (CBV)
bizTransactionList
_bizTransactionIDtype:inv (CBV)
Invoice ID (URI, e.g. GDTI or GLN-based URI)
sourceList
_sourcetype:owning party (CBV)
PGLN of releasing exchange party
destinationList
_destinationtype:owning party (CBV)
PGLN of receiving exchange party
Other
b4l:qualityLevel
A, B, or C
EPCIS Error Declaration Events
Comments
The following illustrative example pertains to V1.
In case an ordinary arriving, departing or accepting event turns out to be erroneous in retrospect, exchange parties have the option to make use of the 'Error Declaration' Mechanism introduced as of EPCIS 1.2.
The Error Declaration (V4) as well as the Corrective Event (V5) SHOULD be captured in one request. The Error Declaration Event looks identical to the original (i.e. incorrect) event, except for the additional Error Declaration Element reversing its semantics. Further, it also accommodates a forward link to the Corrective Event.
For more information, see EPCIS v. 1.2, section 7.4.1.2.
EPCIS Event Hash ID
For populating the correctiveEventID/eventID field, we apply the EPCIS Event Hash ID as introduced in CBV 2.0
Amongst others, the advantage for B4L consists that the latter can (in conjunction with DiGSig) also be used for notarisation for EPCIS events.