SAP Global Track and Trace

Object Tracking - EPCIS

Early Knowledge Transfer
Release 1802 – Delivery 2018.06a

CUSTOMER

1
Objectives

After completing this learning module, you will be able to:

• Outline the purpose of the Object tracking with EPCIS in SAP Global Track and Trace
• Learn how to create model for EPCIS event tracking in Metadata modeling App
• Understand how EPCIS Capture service works
• Understand how EPCIS Query service works
• Know how objects tracked with EPCIS Events are displayed in Global Track and Trace App

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2

2
Overview

3
 Use Cases for Object Tracking
Asset Tracking
• China Unicom
• US hospital track
medical asset
Predicament
visibility Inventory
▪ Auto - JIT supply
▪ T-Mobile track
Process Tracking Object Tracking customer returned
mobile device
EPCIS
Production • Source: ERP system ▪ Source: Data capture application (AII)
visibility • Data Type: Transaction Data (PO, ▪ Data Type: Viability Event Data (Pack, Parcel Tracking
SO, Delivery, Shipment) Pick, Transport...) ▪ Postal
• Granularity: Document level ▪ Granularity: Instance level (serial number, ▪ Express
• Data Size: GB batch/lot)
▪ Data Size: TB ~ PB
Anti-Counterfeiting
Fulfillment ▪ Pharmaceutical
visibility ▪ Tobacco
▪ Wine

Transportation Food Freshness

visibility Recall

Retail Healthcare T&L Foodservice Technical

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 4

EPCIS is a GS1 standard that enables trading partners to share event

throughout the supply chain

4
What is EPCIS?

Electronic Product Code Information Services (EPCIS) is a global GS1 Standard for creating
and sharing visibility event data, both within and across enterprises, to enable users to gain a
shared view of physical or digital objects within a relevant business context.

Query Event cross repositories Query Event

Repository
Repository Repository Repository
Event Event
Event Event
Event

Logistics Service
Manufacturer Distribution Center Retailor
Provider

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 5

5
Basic Elements of EPCIS Event

“What” (Object)
• SGTIN (GTIN+ Serial number) “Why”
• LGTIN (GTIN+ Batch/Lot number) • Business Step  Event
• SSCC • Packing
• Staging_outbound
• …... • Arriving
• Loading
• Departing
• Transporting
• Unloading
• Accepting (PoD)
“When”
• Date/Time • Disposition  Status
• In_Progress
• Time zone offset • In_transit
• Damaged
• Returned
• Stolen
• Recalled
• Expired
“Where” • Active/inactive
• Read point : GLN • Business Transaction Type
• Business location : GLN • Desadv – Dispatch advice (ASN)
• PO – purchase order
• Source and Destination

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6

6
 Example of EPCIS Aggregation Event

Trade Item <AggregationEvent>

GTIN-13: 6901028075015 <eventTime>2018-03-15T10:00:00.000+09:00</eventTime>
EPC: urn.epc.id.sgtin.69010280.07501.BB0001 <eventTimeZoneOffset>+09:00</eventTimeZoneOffset>
<parentID>urn:epc:id:sgtin:69010280.07501.BB0001</parentID>
<childEPCs>
<epc>urn:epc:id:sgtin:69010280.07576.AA0001</epc>
<epc>urn:epc:id:sgtin:69010280.07576.AA0002</epc>
<epc>urn:epc:id:sgtin:69010280.07576.AA0003</epc>
<epc>urn:epc:id:sgtin:69010280.07576.AA0004</epc>
Serial No: BB0001 <epc>urn:epc:id:sgtin:69010280.07576.AA0005</epc>
Bundling </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:0614141.00000.100</id>
</readPoint>
S/N: AA0001 S/N: AA0002 S/N: AA0003 S/N: AA0004 S/N: AA0005 <bizLocation>
Trade Item <id>urn:epc:id:sgln:0614141.00000.0</id>
</bizLocation>
GTIN-13: 6901028075763
</AggregationEvent>
EPC: urn.epc.id.sgtin.69010280.07576.AA0001

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 7

7
Core EPCIS Service interfaces

EPCIS Accessing Application

Deliver Result (XML)

SOAP/HTTP
Send query message
EPCIS
Method HTTP Body Description
EPCIS Query Interface System /Operation
Query Request Capture Input data: Store a standard EPCIS document that
Filter, Sort, Limit HTTP.POST EPCIS Document includes a set of event data and master
data.

Event Repository Poll SOAP message Immediately return a set of event data or
SOAP/HTTP • SimpleEventQuery master data matched with the given query.

Validation / Conversion

EPCIS Capture Interface

HTTP.POST

Data Capture Application

Create EPCIS Document (XML)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 8

8
Create GTT Model for EPCIS

9
Create Model for EPCIS event tracking

Procedure to create a EPCIS

Model:
1. Choose File New Project from Template .
The Template Selection page appears.
2. In the Category list, choose SAP Global
Track and Trace and then choose Next.
3. Type a Project Name for your GTT
project.
4. Choose Next. The Project Customization
page appears.
5. Choose Standard or Simple mode.
6. Type Namespace and Version, choose
Template as EPCIS and type Description.
Then choose Next or Finish.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 10

10
Create Model for EPCIS event tracking

An EPCIS model contains:

• One EPCIS tracked object entry

• Three EPCIS event entities:
• Object event
• Aggregation event
• Transaction event

• EPICS Events are mapped to the events

modeled here and customer cannot
extend these at this point in time.

• Right now, SAP Global Track and Trace

supports above three event types.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 11

11
Create Model for EPCIS event tracking
After EPCIS Model is ready, activate the model.
Solution owner can view and manage model in GTT Model Management App.
Once related business role is assigned properly, business users can check EPCIS related tracked objects in Global Track and
Trace App.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 12

12
EPCIS Capture Service

13
Core Capture Operation – Technical Validation

Capture Interface SHALL NOT accept invalid document.

• Well-formedness check (Correct syntax with XML 1.0)
• XML documents must have a root element
• XML elements must have a closing tag
• XML tags are case sensitive
• XML elements must be properly nested
• XML attribute values must be quoted
• Validation
• Must conforms to XML schema for EPCglobal-epcis.xsd
• Support Tenant-specific validation
• Reject invalid EPCIS event

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 14

14
Example of call capture service with Postman
EPCIS capture service endpoint:
• https://<server address>[:port]/epcis/v1/capture/event

Return Code 200 means the EPCIS event is successfully stored in GTT.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15

15
Handling Failure

1. XML is not well-formed or invalid.

2. Not authorized to perform capture operation
3. Size limitation of EPCIS XML file: Less than 4MB

Golden Rule: Accept all EPCIS Events in one EPCIS Document or reject all

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 16

16
EPCIS Query Service

17
Supported parameters for SimpleEventQuery
Parameter Name Meanings
eventType ObjectEvent, AggregationEvent, QuantityEvent, TransactionEvent, or TransformationEvent

GE_eventTime eventTime greater than or equal to the specified value

LT_eventTime eventTime less than the specified value

GE_recordTime recordTime greater than or equal to the specified value

LT_recordTime recordTime less than the specified value

EQ_action ADD, OBSERVE, or DELETE , if not, the implementation SHALL raise a QueryParameterException

EQ_bizStep (a) have a non-null bizStep field; and where (b) the value of the bizStep field matches one of the specified values.

EQ_disposition Equal to specified value

EQ_readPoint Equal to specified value

EQ_bizLocation Equal to specified value

EQ_bizTransaction_type Equal to specified value

EQ_source_type Equal to specified value

EQ_destination_type Equal to specified value

MATCH_epc

MATCH_parentID

MATCH_anyEPC

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 18

18
Supported parameters for SimpleEventQuery

Parameter Name Meanings

EQ_eventID eventID field is equal to specified value

orderBy The value of this parameter SHALL be one of: eventTime, recordTime

orderDirection The value of this parameter must be one of ASC (for ascending order) or DESC (for descending order); if not, the
implementation SHALL raise a QueryParameterException.

If omitted, defaults to DESC.

eventCountLimit If specified, the results will only include the first N events that match the other criteria, where N is the value of this
parameter.
maxEventCount If specified, at most this many events will be included in the query result. If the query would otherwise return more than
this number of events, a QueryTooLargeException SHALL be raised instead of a normal query result.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 19

19
Example of call query service with Postman
EPCIS query service endpoint:
• https://<server address>[:port]/epcis/v1/query

Response XML
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:QueryResults xmlns:ns3="urn:epcglobal:epcis-query:xsd:1"
xmlns:ns4="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" xmlns:ns5="urn:epcglobal:epcis:xsd:1">
Request XML <queryName>SimpleEventQuery</queryName>
<?xml version="1.0" encoding="UTF-8"?> <resultsBody>
<EventList>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body> <ns3:TransactionEvent>
<eventTime>2018-05-29T01:00:16.000+01:00</eventTime>
<eqpcisq:Poll xmlns:eqpcisq="urn:epcglobal:epcis-query:xsd:1">
<recordTime>2018-05-30T07:42:45.945+01:00</recordTime>
<queryName>SimpleEventQuery</queryName>
<params> <eventTimeZoneOffset>+01:00</eventTimeZoneOffset>
<bizTransactionList>
<param>
<name>EQ_disposition</name> <bizTransaction type="urn:epcglobal:cbv:btt:inv">urn:epc:id:gdti:0356781.02010.0000003091</bizTransaction>
<bizTransaction type="urn:epcglobal:cbv:btt:bol"/>
<value type="urn:String">
<bizTransaction type="urn:epcglobal:cbv:btt:desadv">urn:epc:id:gdti:0111111.02005.000002578</bizTransaction>
<string>urn:epcglobal:cbv:disp:sellable_not_accessible</string>
</value> <bizTransaction type="urn:epcglobal:cbv:btt:pedigree">urn:epc:id:gdti:0222222.02005.000006891</bizTransaction>
<bizTransaction type="urn:epcglobal:cbv:btt:po">urn:epc:id:gdti:0333333.02010.0000001256</bizTransaction>
</param>
<param> <bizTransaction type="urn:epcglobal:cbv:btt:poc">urn:epc:id:gdti:0444444.02010.0000001256</bizTransaction>
<bizTransaction type="urn:epcglobal:cbv:btt:prodorder">urn:epc:id:gdti:0555555.02005.000001981</bizTransaction>
<name>EQ_bizTransaction_urn:epcglobal:cbv:btt:inv</name>
<bizTransaction type="urn:epcglobal:cbv:btt:recadv">urn:epc:id:gdti:0666666.02005.000002567</bizTransaction>
<value type="urn:String">
<string>urn:epc:id:gdti:0356781.02010.0000003091</string> <bizTransaction type="urn:epcglobal:cbv:btt:rma">urn:epc:id:gdti:0777777.02005.000002167</bizTransaction>
</bizTransactionList>
</value>
</param> <parentID>urn.epc.id.sgtin.69010280.10528.LC00Z</parentID>
<epcList>
<param>
<epc>urn.epc.id.sgtin.69010280.10528.LC000</epc>
<name>GE_recordTime</name>
<value type="urn:DateTime"> </epcList>
<action>ADD</action>
<datetime>2018-05-28T01:11:43.615+01:00</datetime>
</value> <bizStep>urn:epcglobal:cbv:bizstep:storing</bizStep>
<disposition>urn:epcglobal:cbv:disp:sellable_not_accessible</disposition>
</param>
<readPoint>
<param>
<name>orderBy</name> <id>urn:epc:id:sgln:0012345.11111.400</id>
</readPoint>
<value type="urn:String">
<string>recordTime</string> <bizLocation>
<id>urn:epc:id:sgln:0012345.11111.0</id>
</value>
</bizLocation>
</param>
<extension>
<quantityList/>
<param>
<name>eventCountLimit</name> <sourceList/>
<destinationList/>
<value type="urn:Int">
</extension>
<int>2</int>
</value> </ns3:TransactionEvent>
</EventList>
</param>
</params> </resultsBody>
</ns3:QueryResults>
</eqpcisq:Poll>
</SOAP-ENV:Body>
</soapenv:Body>
</soapenv:Envelope> </SOAP-ENV:Envelope>

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 20

20
Global Track and Trace App

21
Search EPCIS event
Use input EPC ID, or business step or disposition, read point, business location or event time to search all the
satisfied EPCIS data should be listed below.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 22

22
Display head of EPC object

▪ Business step
▪ Disposition
▪ Read Point & Business Location
▪ Event Time

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 23

23
Display packaging hierarchy

Packaging hierarchy shows the

current relationship of parent event
and child event.

List all the events list which deal with the same EPC ID in different event time.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 24

24
Display EPCIS event details
Below is the detail event info page after clicking the event in the previous main EPCIS page.

Shows the current event’s Parent ID, and business

step, disposition and read point.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 25

25
Summary

You should now be able to:

• Outline the purpose of the Object tracking with EPCIS in SAP Global Track and Trace
• Model EPCIS event in Metadata Modeling App
• Send EPCIS event to capture service
• Query EPCIS event via query service
• Track objects and packaging hierarchy in Global Track and Trace App.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 26

26
© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distr ibutors contain proprietary software components
of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affil iate company products and services are those that are
set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be constr ued as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated compani es at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionalit y. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

27