SAP Global Track and Trace

Event-to-Action Engine
Release 1802 – Delivery 2018.06a

CUSTOMER
Objectives

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

• Outline the purpose of the Event-to-Action Engine of SAP Global Track and Trace
• Understand how the different components of the Event-to-Action Engine work together
• Define and activate Rules for a specific GTT model
• Explain what kind of actions can be triggered when events are processed for a tracked
process instance

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

Overview
Overview: Event-to-Action Engine

• What is the Event-to-Action Engine?

It allows you to define Rules to automatically trigger actions if certain events are processed for a
tracked process instance

• Who is responsible for the Event-to-Action Engine?

Solution owners of SAP Global Track and Trace can define and deploy Rule Services for their
GTT models to enable "event to action" for the corresponding tracked processes.

• Why is the Event-to-Action Engine featured?

It improves the flexibility and efficiency of SAP Global Track and Trace.

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

Overview: Event-to-Action Engine

The following Rule Services can be deployed to a GTT model since 2018.05a:

Rule Service Name Action to Trigger

ActionUpdateTrackedProcess Updates the status properties or the header properties of a tracked

process instance.
ActionFLPnotification Sends SAP Fiori Launchpad (FLP) Notifications to specific users.
ActionCPIforwarding Forwards the tuple consisting of tracked process type and event to SAP
Cloud Platform Integration (CPI).
ActionUpdatePersonalDataRet Configures the residence period and retention period of users’ personal
entionDate data.
ActionUpdatePlannedEvent Updates the planned time for an event.

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

Overview: Event-to-Action Engine – Integrated Components

Business Data – tracked

process, events …

Metadata
Modeling app
SAP Cloud Platform
Integration (CPI）
GTT Event-
GTT Model Modelling Rule services
Management Activate to-Action Action
app Engine
CSN Models
Global Track and Trace app

GTT Model
Management
app

GTT Fiori Launchpad

Design time Run time

Note: URL to SAP CP Business Rules help: https://help.sap.com/viewer/product/BUSINESS_RULES/Cloud/en-US
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6
Sequence Diagram (Design Time)

Metadata Modeling GTT Model Management app

app
4
1 2 3
View
Deploy Update and Select a pre-defined rule Activate
rule
GTT re-deploy service. rules
details
Project GTT Project Define and save rules.

Generate GTT Metadata Service Generate rule/rule

Update service runtime
corresponding
rule project Fetch rule results
rule project
with Data data
with Data Store runtime
Objects
Objects results to GTT

GTT SAP CP Business Rules

CSN Model Rule Service Rule Service

Note: *Rule Services are by default activated

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 7
Example Use Cases
Example Use Case
Tracked Process “Delivery with delay event”

Create delivery in ERP

1 (delivery date = today + 3 days)

3
Defined rules for tracked
process delivery:
Report a event of type
IF (Event type = “DelayEvent”) “DelayEvent” (newDeliveryDate
and Activate SAP Global Track = today + 4 days)
( DelayEvent.newDeliveryDate and Trace
> TP.DeliveryDate )
THEN
{
• Update Delivery Status to
“Critical Delayed” 4
• Notify consignee with “Delay”
alert Consignee gets a notification that
} delivery 4711 is critical delayed
All deliveries with delivery status
“Critical Delayed” can be easily
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER selected with GTT app 9
 Design Time
Design Rules for “Delivery with delay event”
Solution Owner successfully deploys a
model with Metadata Modeling app in results In GTT Model Management app, model
SAP Web IDE is listed in model list.

Metadata
Modeling
app

GTT Model
Management
app

GTT Model
Management
app

1. Go to Metadata
Modeling app to
deploy / redeploy a
GTT project
Click on the model from list to see details.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 10
 Design Time
Design Rules for “Delivery with delay event”

Switch to ‘Rule Services’ tab, select a Define rules to selected rule

pre-defined rule service to define rules service and save the rule

Metadata
Modeling app

GTT Model
Management
app

GTT Model
Management
app

2. Go to GTT
Model
Management app
to define rules

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

 Design Time
Design Rules for “Delivery with delay event”

Solution Owner deploys Rule Service from GTT Model Management app

Metadata
Modeling app

GTT Model
Management
app

GTT Model
Management
app

3. Go to GTT Model
Management app to
activate Rules

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

Run Time
Event-to-Action Engine for “Delivery with delay event”

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

Example Use Case
Tracked Process “Update Planned Event”

1 Create a shipment in
ERP
3

Defined rules for tracked Report an event of

process shipment: type “Car Arrival”
IF (Event type = “CarArrival”) SAP Global Track
Activate
THEN and Trace
{
• Update planned departure
to new date/time
• Update planned arrival at
destination to new 4
date/time
} Consignee check planned
departure date and planned
arrival date from GTT

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

 Design Time
Design Rules for Update Planned Event

Select action: ActionUpdatePlannedEvent, then define rule: Event of type “Carrier Arrival” to
trigger update Planned Event action.

Metadata
Modeling app

GTT Model
Management
APP

GTT Model
Management • New timestamps and the processEventDirectoryIds have to be sent in via the triggering
APP
event

• If it is not necessary to have different planned business and technical timestamp, both can
be set to the same value.
• plannedBusinessTimeZone is used to determine the time zone in which the planned
business time is displayed on the UI
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15
Run Time
Event-to-Action Engine for “Update Planned Event”

Report event of type “Carrier Arrival” to

update planned event dates, then check from GTT

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

Example Use Case
Tracked Process “Shipment with departure event”

1 Create a shipment in
ERP
3

Defined rules for tracked Report an event of

process shipment: type “DepartureEvent”
IF (Event type = SAP Global Track
“DepartureEvent”) Activate
THEN
and Trace
{
• create Inbound delivery to
consignee
• Notify consignee of 4
departure event
} Consignee gets a notification
about shipment departure
Check inbound delivery in ERP

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

Design Time
Design Rules for CPI Forwarding / FLP Notification

Select action: ActionCPIforwarding, then define rule: Event Select action: ActionFLPNotification, then
of type “DepartureEvent” to trigger inbound delivery creation define rule: Event of type “DepartureEvent”
in ERP via CPI Forwarding to trigger FLP Notification

Metadata
Modeling app

GTT Model
Management
APP

GTT Model
Management
APP

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

Run Time
Event-to-Action Engine for “Shipment with departure event”
Send an event of type “DepartureEvent” to a shipment
tracked process Users defined in the Rule get notification on the Fiori Launchpad

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

Run Time
Event-to-Action Engine for “Shipment with departure event”
Details on CPI Forwarding – what is really sent out

SAP Cloud Integration SAP on-premise

SAP Global Track (HCI) (ERP/TM…)
and Trace
iFlow
GTT Convert JSON to
Event-to- requested format (field
Action
Engine mapping)

JSON file
(business data of tracked Call to RFC/Web Service in
process and triggering event) backend sytem via Cloud
is sent to CPIEndpoint Connector
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 20
Run Time
Event-to-Action Engine for “Shipment with departure event”

Inbound delivery is created upon event of type “DepartureEvent”

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

Summary

You should now be able to:

• Explain the purpose of the Event-to-Action Engine

• Describe how the components of the Event-to-Action Engine work together
• Define and activate Rules for a GTT model
• Outline what kind of actions can be triggered when events are processed for a tracked
process instance

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

© 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 distributors 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 affiliate 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 construed 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 document 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’ strategy 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 companies 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 functionality. 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 trademarks 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 companies.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.