About This Module

Duration: 75 Minutes
Module Knowledge

Monitoring Transportation Events

Configuring SAP Event Management (SAP TM) for Transportation Visibility

Target Audience

Application Consultant

End User

Super / Key / Power User

About This Topic

In this lesson, you learn how to monitor transportation events with SAP Event
Management.
Estimated time to complete this topic: 40 Minutes
Objective(s)

Monitor transportation events with SAP Event Management

Nowadays, supply chains are global and complex. End-to-end supply chain
visibility is one of the key factors in efficient supply chain operation and
control. SAP Event Management is the only application needed to provide this
visibility, since it is available to all partners, including customers. SAP Event
Management can also work with multiple SAP and non-SAP applications.
As companies expand their suite of IT products to handle more complex
scenarios, they often have to add systems to their ERP environment. This
makes it difficult for business users and management to gain a complete view
of end-to-end processes and monitor potential service issues. Therefore, it is
imperative to have a tool that can incorporate information from several
systems and provide insight into how order fulfillment is progressing.
SAP Event Management makes processes, assets, and performance visible
across the entire supply chain. Extensive tracking and tracing functions allow
process monitoring, automated exception resolution, proactive alerting, as
well as extensive reporting in a single solution.
The event management system is designed to work with several SAP ERP
instances, if necessary. It can communicate with SAP CRM, where sales
orders may be received, and this communication is processed back to the
customer to support order fulfillment. SAP Advanced Planning and
Optimization (APO) may be responsible for creating the replenishment plan.
SAP ERP or SAP Manufacturing Execution (ME) may be responsible for
communication and tracking progress on the shop floor. SAP EWM (Extended

Warehouse Management) may be responsible for the picking and packing as

part of the logistics execution.

Event Management in SAP TM

SAP Event Management offers visibility processes to monitor transportation
execution in connection with SAP TM. The transportation execution visibility
processes enable users in roles such as transportation dispatcher, shipper, or
ordering party, to track and monitor planned events or to report an actual
event. Tracking and tracing is provided for the following business document
types in SAP TM:

Freight unit

Freight order

Freight booking

Transportation unit

Resource

Instruction execution for standard operating procedures

In each case, the goal is to manage by exception, reduce time to action, and
spend less time fire-fighting.

Monitor, notify, analyze, and adjust - these are the four cornerstones of SAP
Event Management, and they contribute to providing an adaptive solution. The
monitoring process collects data from the various source systems.
Notifications can be set up to be triggered, with alerts sent to the parties
responsible if a process deviates from its anticipated course. Based on the
alerts, the appropriate parties can then simulate adjustments and make any
necessary changes. Finally, in relation to analytics, SAP Event Management
can be tied into the SAP NetWeaver BW environment to support
transportation management reviews.

SAP Event Management is capable of processing several different types of

events. Within a given process, you have events that you expect to happen,
and events that actually happen. Typically, you want to compare the actual
event against what you expected, as follows:

Regular Event
The first type of event is an event that you expect to happen within a
particular time frame, and it happens as expected. This is a regular event.

Overdue Event
This is an event that you expect to happen within a particular time frame,
and it happens outside the expected time frame. An overdue event can
cause a subsequent event to be rescheduled, or it could just be recorded
as an overdue event.

Unexpected Event
The third type of event is one that is unexpected. This could be a truck that
breaking down or a malfunction in a piece of equipment; something that
could potentially have an effect on subsequent events, causing something
to be rescheduled or another action to be taken. An unexpected event
could trigger an alert or another type of notification.

Unreported Event

In this case, you expect an event to occur within a particular time frame,
but for whatever reason, it is not reported. It is possible that something still
needs to happen following this event, so you could set a time limit that
sends a message or triggers something to happen when the event is
unreported for a certain time period.

The event management tool has the following features.

Event Management Tool Features

Event Management monitoring tools provide:
1. Expected events are coming from the application system, in this case SAP
TM. The expected events are the activities planned in SAP TM planning.
2. The reported events are the events that are reported from the real-world
operations.
3. Based on received events from operations or unreported events, the rules
in SAP Event Management are triggered to respond to real-world activities
happening in operations or execution.
4. Via SAP TM screens or the SAP Event Management Web front-end,
expected and real events are made visible to user and target groups like
(internal) customers, planners, and people in operations. This visibility is
given from a transport order, or on the demand-side via Freight Unit
Tracking & Tracing and Monitoring and for the operations-side, via Freight
Orders and Bookings Tracking & Tracing and Monitoring.
SAP Event Management can point out critical situations within your supply
chain in good time, by comparing expected events with the actual events, and
can then, for example, actively notify those persons involved.

An expected event is an event that can be defined before the corresponding

business process has begun and that describes the normal flow of the
business process.
In the context of SAP TM integration, expected events are activities planned in
SAP TM.
Expected events include:

Cargo receipt

Onboard confirmation

Proof of delivery

The expected events are compared to actual events (also known as reported
events).
Reported events include:

Unloading truck

Late departure

Accident

No POD sent

The transportation execution visibility process enables users and target

groups like (internal) customers, planners, and people in operations to monitor
events or to report an actual event via SAP TM screens or the SAP Event
Management web interface.

Transportation Execution Visibility Process

SAP Event Management offers visibility processes to monitor transportation
execution in connection with SAP TM. Tracking and tracing is provided for the
following business document types in SAP TM:

Freight units

Freight orders

Freight bookings

Transportation unit

Resources

Instruction execution for standard operating procedures

Transportation operations is an area in which transparency is crucial,

especially in those cases where lengthy transportation times have to be
considered, such as when shipping overseas. To ensure customer
satisfaction, it is more important than ever to keep full control of what is going
on, even if parts of the business process may run outside your companys
sphere of influence.
Visibility processes for transportation management offer preconfigured, out-ofthe box content for transportation operations, supporting you in tracking
relevant activities within and beyond the confines of your company. You can
monitor different processes and business documents, such as freight units,
freight orders, and freight bookings. Depending on your role, you can choose
different layouts for the user interface, such as shipper and consignee, which
result in a comprehensive and easy to understand view of transportation
operations.
The figure depicts a realistic scenario in which SAP TM and SAP Event
Management can be integrated to monitor an end-to-end international order.
In the first step of the process, the order is created in SAP ERP and sent to
SAP TM. At this point, a freight unit is created and scheduling can begin.
SAP TM provides the basis for tracking and tracing in SAP EM. In SAP TM,
freight units, orders and bookings create the event handlers, and the planned
activities in SAP TM are the expected events that SAP EM monitors.
For real-world awareness and proactive monitoring, SAP TM relies on SAP
EM. Actual events that occur during execution are reported in SAP EM.

The reporting of events can happen in SAP TM and sent to SAP EM and vice
versa.

The figure shows a typical scenario in which the SAP EM and SAP TM
systems are updated to accurately reflect the real world progress of a freight
order.

Due to the alert system, the planning team does not have to watch over every
order. They can spend most of their time managing exceptions.

Alerts
During the loading process, SAP ERP or SAP EWM may send a signal
(notification) that there is a delay in the loading process. This can trigger an
alert. The transportation planner may have to make adjustments to the
schedule to ensure that the container makes it to the ship on time. Once the
ship has left the departure port, GPS updates may indicate that the ship has
not reached its midway point. This could be due to weather or mechanical
issues. The customer service agent can be notified and can contact the
customer to inform them of anticipated delays.

Here you can see both expected and unexpected events. The expected
events are planned activities in SAP TM. For example, when loading begins
for a freight unit, SAP TM reports to SAP EM that this event has occurred.
Unexpected events are events that are not planned for example delays,
damaged packaging material, and cancellations. Unexpected events can also
be reported from SAP TM.

SAP TM Notifier is an app that provides event report functionality to Androidbased mobile devices. It enables you to display a list of open and assigned
freight orders along with their details, for example, the stops for a freight order
and freight units that are assigned to the stops. You can also report the
delivery status.
Additional features include the ability to display the map indicating the exact
location of the freight order or freight unit in real-time (from the latest reported
events). Each stop has a list of predefined events that you can use to report
the status of your delivery, for example, start loading or finish loading. In
addition to the predefined events, you can send a delay notification for an
event.

With the SAP TM Notifier App, you can display freight order details and report
the status of your delivery using predefined events on your mobile device.
Mobile devices provide planning information for the driver, and execution
information back to the planner from the driver.
Mobile tracking enables users by being able to do the following:

Display open freight orders that are valid within a certain time frame

Display details of a freight order

Display details of a stop

Display freight units for a stop

Display events for a stop

Display information about a freight order on a map

Confirm an event for a stop after completing the corresponding activity

Report a delay for an event

Mobile Tracking And Tracing

Use Case

1. Get the relevant freight orders

2. Review the tour data

3. Show data on the map
4. Report potential problems or delays
5. Execute part of the freight order or the whole freight order and report back
the execution
Technical Requirements

SAP Transportation Management Release 8.0

SAP Event Management Release 7.1, Enhancement Package 1, SP05

SAP NetWeaver Release 7.02

SAP NetWeaver Gateway 2.0 Support Package 2

Sybase Unwired Platform 2.1

Summary
You should now be able to:

Monitor transportation events with SAP Event Management

About This Topic

In this lesson, you learn how to configure the settings to enable visibility to
transportation events with SAP EM.
Estimated time to complete this topic: 35 Minutes
Objective(s)

Configure settings to enable visibility to transportation events with SAP EM

In SAP TM, an application interface (AI) to SAP Event Management (SAP EM)
configuration is required so that data is transferred from the SAP TM to SAP
EM. Examples of configuration objects include function modules (codes) and
extractors required to interface the data between the two systems.
SAP TM must be configured so that programs (or extractors) can extract data
(for example, expected events) from SAP TM and send the data via the
application interface to SAP EM.
To utilize the SAP EM features, configuration is also required in SAP EM. This
may include visibility settings using the web UI or SAP GUI. Additionally, roles
and role assignment to users should be set up to enable access to visibility
scenarios.
In SAP EM, BAPIs are used to integrate with SAP TM and other non-SAP
systems, via SAP PI or other methods.
The BAPIs are:

/SAPTRX/BAPI_EH_POST - for creation of event handlers

/SAPTRX/BAPI_EH_ADDEVENTMSG_02 - for reporting events

Integration Tools between SAP TM and SAP EM

SAP TM is different from other SAP solutions (for example SAP ERP) in how
it interfaces with the application interface. In SAP ERP, this interface is
triggered by BAdIs when a business document is saved. SAP TM uses the
Post-Processing Framework (PPF) for this. The PPF is also used for printing
and interfaces to SAP ERP and SAP GTS.
Therefore, before the integration can start, you need to check if this EM
Interface is enabled in the PPF.
In Customizing for Cross- Application Components, choose Reusable Objects
and Functions for BOPF Environment PPF Adapter for Output
Management Maintain Output Management Adapter Settings.

Non-TM systems use IDoc and Web Services to integrate with SAP EM.

In this section, we look at the configuration settings for event types and event
handlers.
In the integration between SAP TM and SAP EM, two different interfaces and
functions are used.
1. Creation and update of the Event handler with all expected events and
other critical fields such as parameter and tracking IDs.
2. Sending or reporting of events from the TM system, for example loading or
unloading events from freight unit or freight order.
To be able to create event handlers in SAP TM, you must configure the
Application Object Types (AOTs). From the AOTs, the extractors are created.
These extractors send the data to SAP EM and create EM event handlers.
Application Object Types contain the following:

Expected events, with planned dates and times

Tracking IDs that uniquely identify the trackable object or business

document, for example, a freight order

Info and system parameters that contain information on the object

The extractors contain:

A freight order

A freight booking

A freight unit

A transportation unit

Other objects

An event handler represents a business document (for example, freight order,

freight unit, or transportation unit) or a business process (for example, within a
Transportation Execution) that is relevant to tracking or monitoring functions.
SAP EM creates an event handler for each object. The event handler contains
all the information necessary to track this application object. It contains this
information in a form that is independent of its origin, so that SAP EM can
map and track business processes in a uniform way.
The event handler information makes it possible to enable the monitoring of
events that are reported to SAP EM for an application object, and to check if
the actual events occur in line with the expected events. In SAP TM, Event
Types are used to send or report events to SAP EM.

Events
Basic Fields in an Event

An event contains the following basic fields:

Date

Time

Time zone

Tracking ID

Tracking code

Event code

All these fields are configured or coded in the event types.

To monitor SAP TM Execution events, you can use the visibility scenarios
from the freight order, freight booking, resource, or freight unit in the standard.
This means that the application object types (AOTs) and the event type
configuration are already available and only need to be activated. You also
need to assign the application (in this case SAP TM) to the SAP EM system.

To use the visibility scenarios for transportation execution in SAP EM, you will
need to ensure that the following prerequisites are fulfilled:
1. An RFC destination between SAP TM and EM in transaction SM59 is
created.
2. All services belowdefault_host/sap/bc/webdynpro/saptrx/ in
transaction SICF for the SAP EM web interface to work.
3. Business functionSCM_EM_TMCONTENT01 is activated in SAP EM.

Visibility Process Configuration

Configuration in SAP TM

Once the prerequisites are fulfilled, you can perform the following
configuration in SAP TM:
1. Define SAP EM.
2. Define used business process types, application object types, and event
type.
a. Assign SAP EM to the application object types.
b. Mark the event management relevance for the application object.
c. Assign SAP EM to all required events types.
d. Mark the event management relevance for all required events types.
3. Activate the application object types.
Configuration in SAP EM

Perform the following steps in SAP EM:

1. Define an application system.
2. Assign a parameter profile to the mapping area.
3. Assign user profiles to users or a role.

Settings in SAP Transportation Management

Define the System Configuration
In SAP TM, define the system configuration as follows:
1. Define Logical System for SAP Event Management

In Customizing for Integration with Other SAP Components, chooseEvent

Management Interface Define System Configuration Define Logical System.
2. Define RFC Destination to SAP Event Management
In Customizing for Integration with Other SAP Components, chooseEvent
Management Interface Define System Configuration Define RFC Connection to
SAP EM
3. Define SAP Event Management System
In Customizing for Integration with Other SAP Components, chooseEvent
Management Interface Define System Configuration Define RFC Connection to
SAP EM.

The RFC connection to the SAP Event Management system and the definition
of the logical system serve as base definitions for connecting to SAP EM.

SAP delivers a predefined application object type with the relevant functions
and extractors. The application object type determines the SAP EM relevance
of objects and processes in SAP TM. To define the application object type, in
Customizing for Integration with Other SAP Components, chooseEvent
Management Interface Define Application Interface Define Used Bus.
Proc. Types, Appl. Obj. Types, and Evt Types.

Define the Application Object Type

SAP delivers a predefined application object type with the relevant functions
and extractors. The application object type determines the SAP EM relevance
of objects and processes in SAP TM. To define the application object type, in
Customizing for Integration with Other SAP Components, choose Event
Management Interface Define Application Interface Define Used Bus.
Proc. Types, Appl. Obj. Types, and Evt Types.

SAP delivers a predefined event type with the relevant functions and
extractors. The event type determines whether the change to an SAP TM
object requires an event to be sent to the relevant event handler in SAP EM.

To track the execution status of a freight order or freight unit, the Execution
Tracking Relevance field in the freight order type and in the freight unit type
must be set to Execution Tracking with External Event
Management.

Set Freight Unit Types and Freight Order Types for SAP EM
Integration
To track the execution status of a freight order or freight unit, the Execution
Tracking Relevance field in the freight order type and in the freight unit type
must be set to Execution Tracking with External Event
Management . You can define the freight order in Customizing for SAP
Transportation Management. Choose Transportation Management Freight
Order Management Freight Order Define Freight Order Types.
You can define the freight unit in Customizing for SAP Transportation
Management. ChooseTransportation Management Planning Freight
Unit Define Freight Unit Types.

The RFC connection to the SAP Event Management system and the definition
of the logical system serve as base definitions for connecting to SAP EM.

Parameter Mapping

The mapping profile is used to unify parameters when data is coming from
SAP TM and to determine event handler types. To define the parameter
mapping, in Customizing for Event Management, choose Event
Management Event
Handlers
and
Event
Handler
Data Parameters Define Parameter Mapping.

To Configure Integration Between Freight Orders and Event

Management
Steps

1. View the Event Manager Definition for the TM logical system

ZMTCLNT800.
a. In Customizing for SAP TM, choose Integration with Other SAP
Components Event Management Interface Define Application
Interface Define SAP EM.
b. In the Information dialog box, choose Continue.
c. In the Display View SAP Event Manager Definitions: Overview screen,
look for the row with ZMTCLNT800 in the Dest. field.
d. Here you will see the various event manager definitions.
Field

Value

Event
Manager

Name or identification of an Event Manager

EM Log.
System

The logical System ID of Event Manager

SAP EM
Version

SAP Event Manager release used

Local

Do not select the checkbox

Dest.

Enter the standard name of an RFC destination. If the receiver is an SAP

system, the name of the instance in the SAP system is displayed. (For
example ZMTCLNT800)

Sync.

Select checkbox if the communication to the Event Manager occurs

synchronously for all BAPIs. Deselect this checkbox to improve
performance. Select this checkbox for test purposes only. In a productive
environment, it is recommended to use asynchronous communication.

e. Exit the function.

2. View the business process type settings in SAP TM.
a. In Customizing for SAP TM, choose Integration with Other SAP
Components Event Management Interface Define Application
Interface Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt
Types.

b. On the Change View Define Used Business Process Types:

Overview screen, select the row for a business process type. (For
example, TMS_TOR).
c. In the Dialog Structure screen area, choose Define Application Object
Types.
d. On the Change View Define Application Object Types:
Overview screen, select an application object type (For example,
ODT30_T0).
e. Choose

(Details).

f. On the Change View Define Application Object Types: Details screen,

in the Event Manager field, ensure that the name of the Event
Manager is entered. (For example, EM_TM_800).
g. Ensure the EM Relevance of Appl. Obj. checkbox is checked.
3. View the event types.
a. In the Dialog Structure, choose Define Event Types.
b. In the Change View Define Event Types: Overview screen, select an
event type. (For example ODT_20_Scheduled).
c. Choose

(Details).

d. In the Change View Define Event Types: Details screen, on

the General Data tab page, in the Event Managerfield, ensure that
the Event Manager name is entered. (For example, EM_TM_800).
e. Ensure the EM Relevance of Appl. Obj. checkbox is selected.
f. Return to Customizing.
4. Enable event management tracking in SAP TM for freight order.
a. In Customizing for SAP TM, choose SAP Transportation
Management Transportation Management Freight Order
Management Freight Order Define Freight Order Types.
b. Choose a freight order type.
c. Choose

(Details).

d. On the Change View Freight Order Types: Details screen, in

the Execution Settings screen area, in theExecution Track Relev. field,
choose Execution Tracking with External Event Management.

e. If you select the Immediate Processing checkbox, the life cycle status is
automatically set to In Process when a freight order is created.
f. The Propagate Execution Info setting indicates whether an event that is
reported for a freight order is to be propagated to the predecessor
freight units.
g. If severe execution checks are activated, the system only allows you to
perform cargo management related activities on the freight order
interface if the handling execution status of the related items is set to a
value that allows such activities.
h. In the Event Management Settings section, in the Application Object
Type field, select an application object type for freight orders. (For
example, ODT30_T0).
i. In the Last Exp. Event field, select the last expected event, for example,
POD (Proof of Delivery). If this event is reported from the destination
stop of a freight order, the freight order is finished from an execution
perspective and the system changes the execution status of the freight
order to Executed.
j. Save and exit the function.
5. Enable settings for event tracking in SAP EM.
a. In Customizing for SAP TM, choose Event Management General
Settings in SAP Event Management Define Application System.
b. In the Information dialog box, choose Continue.
c. In the Display View "Application System Definition": Overview, in the
logical System field, you enter the name of the system that is integrated
with SAP EM. (For example TM_00_800).
d. Save and exit the function.
6. Enable Settings for the event handlers in SAP EM system.
a. In Customizing for SAP TM, choose Event Management Event
Handlers and Event Handler Data.
b. Maintain additional settings for Event Handlers, Expected Events and
Parameters. For more information, refer to the guide Integration of SAP
TM and SAP Event Management.

Summary
You should now be able to:

Configure settings to enable visibility to transportation events with SAP EM