X-Sending-System
In order to identify and analyze from which system an EPCIS event was sent the service endpoint
supports a custom header X-sending-system.
The events and their sending system can be viewed on the Web UI - Raw Data Overview
1
2
3
4
5
6
7
8
9
10
(1)
POST /epcis/v1/events HTTP/1.1
(2)
Host: https://ttqs-pairing-backend-development.apps.de1.bosch-iot-cloud.com
Content-Type: application/xml
Authorization: APIKey ...mYXJ1dU9OakM3bUhlTmZnPT0=
(3)
X-sending-system: production-1
| 1 | http method, path and version |
| 2 | Standard http header |
| 3 | Custom http header to identify the sender system production-1 of the EPCIS events.
This value is visible on the Web UI - Raw Data Overview |
MES Pallet Number
In order to search and use the MES palette number within EPCIS events, these events are converted.
When packing the products onto the pallet, only the internal MES pallet number is available.
If the pallet SSCC is available from the SAP system, an EPCIS ObjectEvent is triggered which includes the
MES pallet number in the bizTransactionList.
This event does not represent a parentId - childId relationship.
Therefore this event cannot be searched for.
To enable a search for this kind of event, an artificial AggregationEvent is created that establishes the necessary parentId - childId relationship.
| Creating an artificial AggregationEvent to establish a parentId - childId relation leads to an AggregationEvent being displayed on the UI instead of an ObjectEvent! |