You are on page 1of 294

SAP Event Management 9.

CUSTOMER
Document Version: 1.0 - November 2012
Copyright
© Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC


No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,
Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,
BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,
Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are
trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

(C) SAP AG 2
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and
other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of
Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group 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.

(C) SAP AG 3
Icons in Body Text
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help  General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.

Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen
titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

(C) SAP AG 4
Table of Contents
SAP Event Management ........................................................................................................... 9
SAP Event Management ...................................................................................................... 10
Disclaimer ......................................................................................................................... 11
SAP Event Management Infrastructure ............................................................................ 12
Scenario and Solution Settings..................................................................................... 15
Application Integration .................................................................................................. 16
Application Object ..................................................................................................... 18
Business Process Type ......................................................................................... 21
Application Object Type......................................................................................... 23
Application Object Type Determination ................................................................. 24
Main Object Table and Master Table for Application Objects ............................... 26
Event in the Application System ............................................................................... 28
Event Type ............................................................................................................ 29
Event Type Determination ..................................................................................... 30
Main Object Table and Master Table for Events ................................................... 32
Application Interface .................................................................................................. 33
Data Transfer from the Application System........................................................... 35
Input Help for Defining Parameters ..................................................... 39
Event Handler ............................................................................................................... 43
Event Handler Type .................................................................................................. 45
Event Handler Set ..................................................................................................... 46
Event Handler Set Profile .......................................................................................... 47
Event Consolidation Profile ....................................................................................... 50
Parameters ................................................................................................................ 51
Event Handler Extension Table ............................................................................. 55
Creation of Event Handlers ....................................................................................... 56
Creation of Event Handler Hierarchies ..................................................................... 61
Event Handler Updating ............................................................................................ 63
Event Handler/Event Handler Set Deactivation/Activation ....................................... 66
Query IDs .................................................................................................................. 69
Status Attribute .......................................................................................................... 70
Event ............................................................................................................................. 71
Tracking ID ................................................................................................................ 74
Expected Event ......................................................................................................... 77
Expected Event Update Via Event Message ........................................................ 79
Expected Event Monitor ............................................................................................ 81
Parameter Selection for Expected Event Monitor ................................................. 82
Event Reporting ........................................................................................................ 85

(C) SAP AG 5
Event Message ...................................................................................................... 88
Internal Event Code and External Event Code .................................... 90
Inbound Event Message Processing..................................................... 95
Extended Check to and Preprocessing of Event Messages .................. 96
Event Message Processing ................................................................... 97
Adding Attachments to Event Messages ............................................. 99
Using Event Message Parameters ...................................................... 102
Buffered Event Message Processing .................................................. 103
Individual Event Reporting .................................................................................. 104
Expected Event Reporting ................................................................................... 105
Reactions to and Actions for Events ....................................................................... 107
Rule Set ............................................................................................................... 112
Rule Condition ................................................................................... 115
Evaluation in the Rule Set.................................................................. 116
Rule Set Display ................................................................................ 120
Simulating Processes in the SAP Application System and SAP EM 122
Connection to the Alert Framework ..................................................................... 124
Direct Access to Detailed Information .............................................. 126
Connection to SAP Business Workflow............................................................... 128
Authorizations and Filters ........................................................................................... 130
Authorizations for Changing Data and Sending Event Messages .......................... 133
User Interface ............................................................................................................. 135
Web Interface .......................................................................................................... 136
Modes of Access of the Web Interface................................................................ 138
Logging On to the Web Interface with SSO ...................................... 139
Setting Up A Direct Link User .......................................................... 140
Parameter Display (Web Interface) ..................................................................... 141
Visualization Using Geographical Maps .............................................................. 142
Printable Version for Tables on a Web Page ...................................................... 143
Use of the Event Handler Hierarchy .................................................................... 144
Drilldown in the Web Interface ............................................................................ 145
Frequently Asked Questions (FAQ) .................................................................... 147
General Information ........................................................................... 148
Navigation to the Web Interface ........................................................ 149
Administration Screen ....................................................................... 150
Search Panel ....................................................................................... 151
Navigation and Sorting of Tables ...................................................... 153
Search Result Panel............................................................................ 154
Sending of Event Messages (Fast Entry) ........................................... 155
Sending of Event Messages for Multiple Tracked Objects or Processes
............................................................................................................ 156
Sending of Event Messages ............................................................... 157
Settings ............................................................................................... 158
Details of Tracked Objects and Processes ......................................... 159
Monitoring and Evaluating Processes ........................................................................ 160

(C) SAP AG 6
Use of the Event Handler List ................................................................................. 161
Defining Search Criteria ...................................................................................... 162
Use of the Event Handler Overview .................................................................... 164
Use of Event Handler Details .............................................................................. 165
Settings for EH Overview Screen and EH Details Screen .................................. 168
Application Log ........................................................................................................ 169
Reports for Internal Monitoring and Evaluation of Processes ................................. 170
List of Event Handlers with a Specific Status Attribute ....................................... 172
Last Reported Event List ..................................................................................... 173
Event Handler Set Browser ................................................................................. 175
Event Message Processing Error List ................................................................. 176
Event Message Processing Status List ............................................................... 178
Expected Event Overdue List .............................................................................. 180
Connection to the Computing Center Management System .................................. 181
Connection to SAP NetWeaver Business Intelligence ............................................ 183
Connection to the SCM Alert Monitor ..................................................................... 187
Connection to the Document Flow .......................................................................... 191
Creation and Updating of a Network ................................................................... 193
Displaying a Network ........................................................................................... 195
Deletion of a Network .......................................................................................... 197
Logging with Change Documents ........................................................................... 198
Simulating Processes in the SAP Application System and SAP EM ...................... 200
Overview of Activities Delivered ................................................................................. 202
Activity List Structure ............................................................................................... 203
Activity List .............................................................................................................. 204
Supply Chain Coordination ............................................................................................. 214
Uses of Supply Chain Event Management ................................................................. 217
Use in Procurement ................................................................................................ 218
Use in Manufacturing .............................................................................................. 220
Use in Order Fulfillment .......................................................................................... 222
Use in Asset Management ...................................................................................... 223
Processes in Supply Chain Event Management ........................................................ 225
SAP Event Management User .................................................................................... 230
Administration ................................................................................................................. 231
Consistency Checks for SAP EM Customizing .......................................................... 232
Processing Control ..................................................................................................... 234
Locked Event Handler or Event Handler Set Processing ....................................... 235
Roles for SAP Event Management ............................................................................. 236
SAP EM Administrator for the Application System ................................................. 237
SAP Event Management Administrator .................................................................. 238

(C) SAP AG 7
SAP Event Management User ................................................................................ 239
Data Archiving ............................................................................................................ 241
Archiving with Archive Development Kit (ADK) ....................................................... 242
Archiving in SAP Event Management ..................................................................... 244
Archiving Event Handlers (SCM-EM) .................................................................. 246
Archiving Event Messages (SCM-EM) ................................................................ 248
Archiving Event Handler Sets (SCM-EM)............................................................ 250
Data Archiving for High Data Volumes ................................................................ 252
Archiving Sequence Event Handler and Event Message ................... 254
Archiving Sequence Event Message and Event Handler ................... 256
Overview of Possible Statuses of an Event Handler .......................... 258
Archiving Event Handlers (SCM-EM) .............................................. 260
Archiving Event Messages (SCM-EM) ............................................. 262
Variant Settings for Writing (SCM-EM)................................................................ 264
System Installation and Integration ................................................................................ 266
Connection of SAP Systems....................................................................................... 268
Connection Using SAP Basis Plug-In ..................................................................... 269
SAP Basis Plug-In ............................................................................................... 270
Connection Using SAP R/3 Plug-In ........................................................................ 271
Connection of Business Objects ............................................................................. 272
Business Application Programming Interface in SAP EM ................................... 275
Connection of External Systems ................................................................................ 276
Integration with SAP NetWeaver Process Integration ................................................ 277
Enterprise Services for SAP Event Management ....................................................... 279
Interfaces in SAP Event Management ........................................................................ 280
Visibility Processes ......................................................................................................... 287
Business Functions in SAP Event Management ............................................................ 289
Business Functions in SAP Event Management ........................................................ 290
EM, Archiving and Web Interface Improvements ................................................... 291
EM, Visibility Proc. for External Transportation Mgmt System ............................... 292
Business Functions in SAP Object Event Repository ................................................ 293
OER, Performance-Optimized PTA and Cold Chain .............................................. 294

(C) SAP AG 8
SAP Event Management
Product Information
Product SAP Event Management

Release 9.0

 SAP enhancement package 5 (or higher) for SAP


Based On ERP 6.0

 SAP enhancement package 1 SAP NetWeaver 7.3

The BI Content release depends on the type of BI Content


you want to use for SAP Event Management, as follows:

 If you want to use the new or enhanced BI Content,


you can use any of the following:

BI Content 7.06 SP04, 7.36 SP02, 7.46 SP02

BI Content 7.07, 7.37, 7.47


BI Content
Release  If you do not want to use the new or enhanced BI
Content, you can use any of the following:

BI Content 7.04, 7.05, 7.35

The old BI Content is still available in the new or


enhanced BI Content..

Documentation
November 2012
Published

See SAP Note 1769112 for corrections that are made after the documentation has been
delivered.

For information about SAP NetWeaver, cross-application business functions of the SAP
Business Suite, and processes and tools for enterprise applications, see the following:

 SAP NetWeaver Library [External]

 Processes and Tools for Enterprise Applications [External]

 SAP Library SAP Business Suite SAP Business Suite – Cross-Business


Functions SAP Business Suite – Cross-Application Business Functions

(C) SAP AG 9
SAP Event Management
SAP Event Management allows companies to manage processes, inventories, assets, and
partners by exception rather than monitoring processes that are running smoothly. It is able to
recognize and react to unplanned events in the supply chain, to provide a single point of
access for collaborative processes, and to measure business partners' performance.

SAP Event Management 9.0 is an add on of SAP Enhancement Package 1 for SAP
NetWeaver 7.3. This means that it can be deployed on any application system with the
release level 7.31. The restriction to specific deployment options as described for former SAP
Event Management releases no longer applies.

Typically SAP Event Management can be used stand alone, in connection with SAP ERP,
SAP Transportation Management, or as part of SAP Supply Chain Management Server.

For more information about SAP Event Management, see:

 SAP Event Management Infrastructure

 Supply Chain Coordination

(C) SAP AG 10
Disclaimer
If you use SAP Event Management (SAP EM), you must have licensed SAP EM
appropriately. For more information, see SAP Note 1122317.

(C) SAP AG 11
SAP Event Management Infrastructure
Purpose
SAP Event Management allows you to track goods movements and to query the process
status of the movement flows, for example, at any time.
SAP Event Management enables you to coordinate your planning and activities with your
partners by exchanging information across systems.
You can specify reactions to critical situations. For example, SAP Event Management can
send a warning as an e-mail, or trigger processes in other systems.

Introductory Notes
To map your processes that are relevant to supply chain event management (SCEM-relevant)
in SAP Event Management, set up the appropriate Customizing.

Integration
SAP Event Management can work in principle with all SAP components and non-SAP
components, for example SAP ERP or SAP NetWeaver Business Intelligence.
The scope of integration varies depending on the SAP Event Management release and the
individual SAP application component release that you use. For more information about
installing and integrating SAP Event Management, see SAP Service Marketplace at
http://service.sap.com/SCM  SAP Supply Chain Management  Technology
 Installation and Upgrade overview.
SAP Event Management is also integrated into the SAP object event repository landscape.
For more information, see SAP Library for SAP solutions for auto-ID and item serialization on
SAP Help Portal at http://help.sap.com.

Features
SAP Event Management can link, update, and evaluate the event messages with the
application data from the supply chain network.
It enables you to:
 Monitor, measure, and evaluate business processes:
 SAP Event Management automatically monitors event that occur and those that
have not been reported.
For example:
 Goods issue
 Purchase order transfer
 Production end
 Unreported proof of delivery
 SAP Event Management can automatically transfer data to a data warehouse
system. This system uses key figures to create performance data for the quality
of execution and notification.
 Employ checking processes and notify persons responsible to control events:
 SAP Event Management checks the SCEM-relevant objects as soon as the
application system saves them.

(C) SAP AG 12
 SAP Event Management can automatically inform the decision maker when
action is required in critical situations (for example, automatic re-scheduling of
the subsequent process step when a delay has occurred).
 Exchange and query information between partners, for example, via e-mail or Internet

Data Transfer to SAP Event Management


SAP Event Management receives data from various external data sources, for example:
 Service providers
 Global positioning systems
 Scanners for wagon and container labels
 On-board computers in vehicles
 Service suppliers
You can send data in the following formats:
 Electronic Data Interchange (EDI)
An EDI converter prepares the EDI data entry to be converted into IDoc format for the
SAP Event Management BAPI interface.
 IDoc
You can use a separate IDoc for creating event handlers and one for sending event
messages.
 eXtensible Markup Language (XML)
You make the setting in SAP Event Management to determine whether the SCEM-relevant
data is sent directly from a data source to a recipient or whether it is first sent to a service
provider. The service provider processes the raw data and sends it to the end recipient in a
standard format.

SAP Event Management Interfaces


To receive SCEM-relevant data from those involved in the supply chain and to report the
results of event processing, SAP Event Management uses the following interfaces:
 An interface to exchange data with the application system
This interface allows SAP Event Management to receive SCEM-relevant data from the
application system and to confirm information itself (for example, updating a status or
sending overdue event messages).
For connections to an SAP system, SAP delivers an application interface in the
application system. For connections to external systems, a standardized interface
exists in SAP Event Management.
 An interface to connect internal and external systems and devices to SAP Event
Management, which send event messages and queries to SAP Event Management.
For example, you can work with a Web browser or with a Personal Digital Assistant
(PDA).
 An interface to transfer data to a data warehouse system
This interface allows SAP Event Management to send its information to a data
warehouse system such as SAP NetWeaver Business Intelligence for evaluation
purposes, for example, to check whether standards have been fulfilled and to check the
quality of the execution.

(C) SAP AG 13
The following figure provides an overview of the interfaces and participants with which SAP
Event Management communicates:

Status Query
For example:
External
• Mobile Devices
SAP Component
Systems
• Internet Services
• Business Systems
Application
Interface

BAPI, XML,
EDI, IDoc

Event Reporter
For example: SAP Event SAP NetWeaver
Business
• Mobile Devices Management Intelligence
• Internet Services BAPI RFC
• Technical Systems EDI/IDoc
XML

See also:
 Connection of SAP Systems [Page 268]
 Connection of External Systems [Page 276]
 Interfaces in SAP Event Management [Page 280]

(C) SAP AG 14
Scenario and Solution Settings
Use
This function allows you to use scenarios [External] and solutions [External] in the application
system and in SAP Event Management (SAP EM). It simplifies and improves your
Customizing procedure in the application system and in SAP EM.
This function hides entries (for example, parameters, event handler type, or activities) that are
not relevant to supply chain event management Customizing on the application system side
and SAP EM Customizing. On the system interface of both the application system and SAP
EM, you only see those entries for the scenario or solution that you work with.
You assign all scenarios that belong to an SAP business area to a solution. A scenario can be
assigned to several solutions (one-to-N relationship). A solution can contain various groups of
scenarios.

You assign the scenarios production pallet tracking and vehicle order planning
to the automotive solution, to specify that these scenarios can be used with the
SAP industry solution SAP for Automotive, for example.

Prerequisites
You must be assigned to one or more scenarios that you want to configure, or must assign
yourself to them. This assignment restricts the number of entries for Customizing.
If you are not assigned to a scenario, the system displays all Customizing entries.
You assign a user to all existing scenarios by either entering an asterisk (*) or by not entering
any value.
For more information about assigning users to scenarios, see the Implementation Guide
(IMG) for Event Management  Solutions and Scenarios  Assign Users to Scenarios.

Example
You assign yourself to a fulfillment visibility process, for example, and only receive
parameters for Customizing in the application system and SAP EM that are appropriate to
tracking deliveries in an LTL shipment.

Solution
Scenario
Automotive Tracking vehicle orders
Tracking automotive production
Supplier replenishment
Production Replenishment within production
Oil and Gas Tracking shipment containers

(C) SAP AG 15
Application Integration
Purpose
To define the objects and processes that SAP Event Management (SAP EM) is to track, you
define the supply chain event management relevance (SCEM relevance) of individual
application objects [Page 18] (see also Application Object Type [Page 23]). You also define
which data the application system is to transfer to SAP EM for these objects (see also Data
Transfer from the Application System [Page 35]). This might be parameters, expected events,
or tracking IDs, for example. You report events for an object or process to SAP EM or the
system does this. To do this, you define the SCEM relevance of the individual events in the
application system (see also Event Type [Page 29]). SAP EM processes the events reported
for the relevant event handler(s).

Prerequisites
You have set up Customizing for SAP EM in the application system. You have made the
following settings, for example:
 To create a physical connection between the application system and SAP EM, you
have defined the RFC connection from the application system to SAP EM.
 You have set up the logical system between the application system and SAP EM.
 You have specified one or more SAP EMs in the application system.
 You have specified the business process types [Page 21] in the application system.
 You have defined the application object types and event types in the application
system.
 You have specified the conditions for SCEM relevance in the application system and
assigned them to the application object types and event types.
 You have defined the function modules for extracting the following:
 Parameters
 Expected events
 Tracking IDs
 Query IDs
 Event types
 Actual events
For all the Customizing settings, see the Implementation Guide (IMG) for the application
system under Integration with SAP Components  Interface to Event Management.

(C) SAP AG 16
Process
...

1. You create or change a document in the application system and save it.
Documents or parts of documents are assigned to a business process type in a fixed
way. In this way, the business process type is known to the system.
2. The application system executes the following for application objects and events:
Application Objects Events
 The system checks its list of application  The system checks its list of event types that
object types that belong to the business belong to the business process type.
process type.
 If the system finds event types that fit, it
 If the system finds application object types checks the conditions that have been defined
that fit, it checks the conditions that have for the respective event types. These
been defined for the respective application conditions specify the SCEM relevance of an
object types. These conditions specify the event.
SCEM relevance of an application object.
 If it does not find an appropriate event type, it
 If it does not find an appropriate application writes a message to the application log and
object type, it writes a message to the terminates the transaction.
application log and terminates the
transaction.
 The system notifies SAP EM of each  The system notifies SAP EM of each event
application object for which the condition is for which the condition is fulfilled.
fulfilled.
3. SAP EM creates an event handler for each application object or updates it (see also
Event Handler Creation [Page 56], Event Handler Updating [Page 63]). SAP EM also
creates a change document [Page 198] belonging to the event handler, as required.
4. SAP EM sends the event to each event handler in accordance with the assignment of
the tracking ID and processes this event (see also Event Message Processing [Page
97]).
5. The extractors specified in the application object type transfer the SCEM-relevant data
from the application objects and events to SAP EM.

Result
The system has executed the following:
 Checked the SCEM relevance of your document or parts of it
 Created one or more event handlers in SAP EM, if possible
 Sent the event message belonging to the event to SAP EM, if possible

(C) SAP AG 17
Application Object
Definition
An object in the application system that maps a complex process or part of a process that is
relevant to supply chain event management (SCEM-relevant). You or a system can report
events to an application object.
Examples of application objects (AOs):
 A procurement process
 A container shipment
 A leased pallet

Use
You use application objects to specify the objects and processes for which you want to
determine supply chain event management relevance (SCEM relevance) (Application Object
Type Determination [Page 24]).
The application system sends the SCEM-relevant data from these objects and processes to
SAP Event Management [External] (SAP EM).
By determining the application objects, you specify the level of detail of the SCEM-relevant
objects and processes. An application object can map not only an entire business object in
the application system, but also parts of objects. You can also map cross-business-object
processes in conjunction with event types.

You map an entire procurement process. On the other hand, you can also
specify that the individual pallets belonging to the supplier are SCEM-relevant
objects.
In procurement, you define the purchase order item as the application object
type. You define the delivery, invoice, and Financial Accounting as event types.
You have an SCEM-relevant application object, Purchase Order Item. In this
case, the corresponding event handler represents the entire follow-on process
and not just the purchase order item. This means that you can also send events
from other business objects to this event handler.
The following relationships can exist between an object from the application system (business
object) and the application object:
 A one-to-one relationship (for example, you track an entire truck)
 A one-to-N relationship (for example, you track the individual packages in a truck as
part of an SCEM-relevant process)

(C) SAP AG 18
The following figure provides an overview of the relationships between business objects and
application objects:

11 Railroad Shipment 1:1


JPk-5-43 JPk-5-43

Wagon 1 = AO1 DB DB Wagon 2 = AO2

22 LTL Shipment 1:N


Delivery 1 = AO1

LTL Shipment

Delivery 2 = AO2

Choice
Choice of
of application
application object
object depends
depends onon the
the individual’s
individual’s point
point of
of view
view
 For
 For example,
example, service
service provider reliability 
provider reliability  AO
AO == shipment
shipment
 For
 For example,
example, customer service 
customer service  AOAO == delivery
delivery

AO Application Object
LTL Partial Load

As a result of determining, changing, or saving an SCEM-relevant application object in the


application system, SAP EM creates an event handler [Page 43] that represents this
application object (one-to-one relationship).
When you delete an application object in the application system, SAP EM marks the
corresponding event handler(s) as deleted, but does not physically delete them from the
database.
To track an entire business process and its sub-processes, you can create an event handler
for each sub-process. You join these event handlers together in an event handler set [Page
46]. You can track a fulfillment process with its sales order, delivery, and shipment, for
example.

(C) SAP AG 19
The following figure provides an overview of the relationship between the application object
and the event handler:

Application System

Application Object

 BPT (Shipment)
 AOT (LTL Delivery)
 AO ID

 Application System ID
Event Management
1:1
Event Handler Header
 GUID Unique ID
 AS
Reference Back to
 AOT
Application Object
 AO ID

 ...
AS Application System  BPT
AOT Application Object Type  Tracking IDs
AO ID Application Object ID  Event Handler Type
BPT Business Process Type (in accordance with rule set, profiles, ...)
LTL Partial Load

(C) SAP AG 20
Business Process Type
Definition
The business process type is a classification of business objects or business processes in the
application system for which you want to manage events in SAP Event Management.

Use
You need the business process type to determine the business objects, business processes,
and relevant changes (events [Page 28]) that are relevant to supply chain event management
(SCEM-relevant) (see also Application Object Type Determination [Page 24], Event Type
Determination [Page 30]). You assign a business process type to each business object in the
application system.
The system needs the business process type as the main criteria for assigning an application
object type to an event handler type. In this way, it can create event handlers [Page 56] and
update them. For example, the system needs the business process type to find the
corresponding event handler for incoming event messages. If the business process type,
which the application system transfers to SAP Event Management for an SCEM-relevant
object, matches any of those saved in the event handler, SAP Event Management processes
the event message and updates the event handler.
SAP delivers a selection of business process types with SAP Event Management. You can
also define your own business process types in Customizing in the application system and in
SAP Event Management.

We recommend that you use a remote call to compare all business process
types for processing in SAP Event Management with all those in the application
system. The business process type is the only parameter that is found in both
systems. SAP Event Management uses this parameter to find the event handler
type [Page 45] and creates an event handler if the business process type is the
same.

Example
Examples of business process types include:
 A sales order
 A purchasing transaction
 A manufacturing order
 A shipment
 A delivery

(C) SAP AG 21
The following figure gives you an example of the link between the business process type and
the business object:

Application System

Business
Business Object:
Object: Business
Business Process
Process Type:
Type:
Sales
Sales Order
Order Sales
Sales Order
Order

Business
Business Object
Object 1:
1: Business
Business Object
Object 2:
2: Business Object 3:
Purchase
Purchase Order
Order Inbound
Inbound Delivery
Delivery Shipment

Container

Business
Business Process
Process Type:
Type:
Shipment
Shipment

In this example, there are four business objects, two of which you have defined as being
SCEM-relevant:
 You track the business process for processing a sales order. You consider the sales
order as a whole. You have assigned the business process type Sales Order to it.
 You track the container that transports the goods. You have assigned the business
process type Shipment to the shipment, since the handling unit container belongs to
the shipment.

(C) SAP AG 22
Application Object Type
Definition
A classification of the application object by defining a condition. You can define multiple
application object types for a business process type [Page 21].

Use
You use the application object type to determine the supply chain event management
relevance (SCEM relevance) of objects or processes in the application system. You
determine the SCEM relevance by using a condition that you define in the application system
and that you assign to an application object type. SAP Event Management (SAP EM) only
processes the incoming event messages [Page 88] for objects or processes that fulfill this
condition.
You use the application object type to determine the tracking IDs [Page 74] that identify
objects. In this way, either you or a system can send internal or external messages to this
object and SAP EM can execute the SCEM process.
You can use the application object type to determine the control, info, and system
parameters. SAP EM needs these for information and query purposes and to check the
SCEM process (see also, Monitoring and Evaluating Processes [External]).
The application system writes the application object type and the application object ID into a
status table. Together with the name of the application system, they provide a unique
reference between the application object and event handler. The system uses this reference
to refer to the business object and its business process type. An n-to-one relationship exists
with the business process types in the application system.

Example
Examples of application object types include:
 A standard purchase order
 A delivery
 A handling unit of a particular type on a particular route as part of a shipment (for
example, a railroad wagon)
 A railroad shipment with dangerous goods
 A handling unit as part of a delivery (for example, 20” container on Atlantic route)
 A grouped goods shipment to the East coast of the US

(C) SAP AG 23
Application Object Type Determination
Use
This function uses a classification of the application object based on a condition or function
that you define in Customizing.
The system uses the application object type (AOT) together with the application object ID (AO
ID) and the name of the application system to define the unique reference between
application object and event handler. The system uses this reference to refer to the business
object in the application system. The application system writes the application object type and
the application object ID into a status table.

Integration
This function is part of the process for creating event handlers [Page 56].

Prerequisites
 You have defined application object types and their supply chain event management
relevance (SCEM relevance) in Customizing.
 You have assigned the application object type to a business process type [Page 21] in
Customizing.
 You have specified the condition or function in Customizing whose evaluation is used
by the system to determine the application object type and thereby SCEM relevance.
 You have specified the main object table, and, if required, the master table, in
Customizing for determining the application object type.

Features
By determining the application object type, you can create the relationship between your
business processes and the application object type. Multiple application object types can
represent a single business process type.
The application interface provides the function with the following information about the
application object type:
...

 Whether the application object type is active or inactive


You can deactivate the application object type for test purposes. As a result however,
the application object type is no longer available.
 The condition or function to determine the SCEM relevance of this application object
type
 The extractors to set up the different parameters from the parameter containers that the
system uses with this application object type
 The definition of the parameters for the reference and help function in SAP Event
Management (SAP EM) that the system uses with this application object type (see
Input Help for Defining Parameters [Page 39]).
 The SAP EM system that creates the corresponding event handler
 How the application interface processes errors (that is, process terminated for the
application object to be processed, or for all application objects with this AOT, or the
entire operation terminated)

(C) SAP AG 24
The function provides the application interface with the following information about the
application object:
...
...

 Whether this is a relevant application object belonging to a business object


 The business object tables that represent the application object (main object table and
master table [Page 26])
 The application object ID

Example
In this example, you can use four application object types to represent your shipment process
SH. These track not only the packaging (application object type 1 UPS package), but also
the means of transportation (application object type 2 container, application object type
3 wagon), and the business process itself (application object type 4 LTL shipment).

Application System

BPT e.g. "SH" for Shipment

UPS Package = AOT1

1:N Container = AOT2

Wagon = AOT3

LTL Shipment = AOT4

AOT Application Object Type


BPT Business Process Type
LTL Partial Load

(C) SAP AG 25
Main Object Table and Master Table for
Application Objects
Definition
The main object table and, in some cases, the master table specify where the data used to
evaluate whether an object is relevant to supply chain event management is located. The
main object table represents the application object. The master table represents additional
information about the application object.

Use
You need the information from the main object table and the master table to define the
condition for determining the application object type [Page 23] in the application system.
You can define tracking IDs [Page 74] in the extractor from the main object table and the
master table.
To define the main object table and the master table, you execute the following:
 You define which application tables are available for a business process type in the
application system (transaction /SAPTRX/ASC0TO).
 In the application system you assign a main object table and, if required, a master table
from these available application tables to the relevant application object type
(transaction /SAPTRX/ASC0AO). The system displays all the application tables that
you have assigned to the relevant business process type in the input help.

(C) SAP AG 26
Example
The following table provides example uses of main object tables and master tables:
Example Main Object Table Master Table Tracking IDs and Assigned Delivered
Query Options for Business With
SAP Event Process Type
Management
You are SHIPMENT_ITEM_N SHIPMENT_HEA Several tracking IDs: ESC_SHIPMT Fulfillment
tracking one EW DER_NEW visibility
or more (provides one or (provides the  Delivery process
deliveries in more delivery shipment number) number
a shipment. numbers for the  Shipment
shipment) number
You are only SHIPMENT_HEADE ---- A tracking ID: ESC_SHIPMT Fulfillment
tracking a R_NEW visibility
shipment. (provides the  Shipment process
shipment number) number

You are PURCHASE_ITEM_ PURCHASE_OR Several tracking IDs: ESC_PURORD Procureme


tracking one NEW DER_HEADER_ nt visibility
or more (provides the NEW  Purchase process
purchase purchase order (provides one or order number
order items number) more purchase  Purchase
in a order items) order item
purchase
order.
You are INSPLOT_NEW ---- A tracking ID: EPL_INSPLOT Quality
tracking an (provides the control
inspection inspection lot  Inspection lot visibility
lot. number) number process

(C) SAP AG 27
Event in the Application System
Definition
An event is an incident that has occurred.
For examples of events, see Event [Page 71].

Use
You use events in the application system to define whether changes to application objects or
processes are relevant to supply chain event management (SCEM-relevant).
The application system sends the SCEM-relevant data for these events to SAP Event
Management (SAP EM).
The application system can create multiple events at the same time for a change to an
application object. SAP EM can also process multiple events in the event handlers.

You use two different events for a delivery process to report the following for an
event handler:
 The completeness of a delivery
 A change to the delivery date of a delivery item

For information about using events in SAP EM, see Event [Page 71].

(C) SAP AG 28
Event Type
Definition
A classification of the event [Page 28] by defining a condition. You can define multiple event
types for a business process type [Page 21].

Use
You use the event type to determine the supply chain event management relevance (SCEM
relevance) of events in the application system. You determine the SCEM relevance by using
a condition that you define in the application system and that you assign to an event type.
SAP Event Management only processes these events using the relevant event handlers.
You use the event type to determine the tracking IDs [Page 74] that allow you to identify event
handlers in SAP Event Management. In this way, either you or a system can send internal or
external messages to the application object and SAP Event Management can execute the
SCEM process.
You can use the event type to determine the information that the application system gives to
the event handler in SAP Event Management with the message. In this way, SAP Event
Management can process the event correctly (see also Event Reporting [Page 85]).

Example
Examples of event types include:
 The completion of a delivery
 A change to the delivery date of a delivery item
 A change to the delivery date of a delivery item if this date differs by more than three
days from the original delivery date
 The change in the delivery status from Picked to Goods Issue Posted
 A reported quantity for a delivery item in goods receipt that deviates from the tolerance
limit for the requested quantity of the corresponding purchase order item

(C) SAP AG 29
Event Type Determination
Use
This function uses a classification of the event based on a condition or function that you
define in Customizing.
You enable the application system to use the event type [Page 29] together with the tracking
ID to assign the event to the event handler or event handlers in SAP Event Management
(SAP EM).

Integration
This function is part of the process for reporting events [Page 85].

Prerequisites
 You have defined event types and their supply chain event management relevance
(SCEM relevance) in Customizing.
 You have assigned the event type to a business process type [Page 21] in
Customizing.
 You have specified the condition or function in Customizing whose evaluation is used
by the application system to determine the event type and thereby SCEM relevance.
 You have specified the main object table [Page 32], and, if required, the master table
[Page 32], in Customizing for determining the event type.
If you want to define SCEM relevance conditions for document changes, you can also
specify the main object table, and, if required, the master table, with the data record
before the data is saved.

Features
By determining the event type, you can create the relationship between your business
processes and the event type. Multiple event types can represent a business process type.
The application interface provides the function with the following information about the event
type:
 Whether the event type is active or inactive
You can deactivate the event type for test purposes. As a result however, the
application object type is no longer available.
 The condition to determine the SCEM relevance of this event type
 The extractors for the event data that the application system is to send to the event
handlers
 The SAP EM system that creates the corresponding event handler
The application interface provides the function with the following information about the
application object:
 Whether this is a relevant event belonging to a business object
 The business object tables that represent the event (main object and master table)
 The tracking ID [Page 74]
The tracking ID is part of the event data and is determined by the extractor.

(C) SAP AG 30
Example
The delivery generates five different events. The application system sends these to the
corresponding event handler in SAP EM. The application system determines the event
handler using the tracking ID specified in the extractor.
You save the following with the events:
 The completion of a delivery
 A change to the delivery date of a delivery item
 A change to the delivery date of a delivery item if this date differs by more than three
days from the original delivery date
 The change in the delivery status from Picked to Goods Issue Posted
 A reported quantity for a delivery item in goods receipt that deviates from the tolerance
limit for the requested quantity of the corresponding purchase order item

(C) SAP AG 31
Main Object Table and Master Table for Events
Definition
The main object table and the master table specify where the data used to evaluate whether
an object is relevant to supply chain event management is located. The main object table
represents the event. The master table represents additional information about the event.
Both tables with the data record before the current data save also specify the state that the
business object had before its current state.

Use
You need the information from the main object table and the master table to define the
condition for determining the event type in the application system.
You can define tracking IDs [Page 74] in the extractor from the main object table and the
master table.

Example
For example, you want to track a handling unit only for overseas shipments. To do this you
need, on the one hand, information from the main object table (handling unit) to determine the
tracking ID. On the other hand, you also need additional information from the shipment (for
example, the route) to process events in the event handler, for example, if the route was
changed. You define a condition that queries the change in status from Loading Begin to
Loaded. The condition uses the main object table with the data record before the current data
save to determine the old status Loading Begin and it uses the main object table to
determine the new status Loaded.

(C) SAP AG 32
Application Interface
Use
You need the application interface to SAP Event Management (SAP EM) to:
 Establish the technical connection between the application system and SAP EM
 Define the supply chain event management relevance (SCEM relevance) of objects or
processes
 Establish the data transfer from the application system [Page 35] to SAP EM
The following data is transferred from the application system to SAP EM:
 Expected events
 Parameters
 Indicators
The application system contains programs (extractors) that extract data (for example,
expected events) from the application system. The system uses the application interface to
send this data to SAP EM.
The application interface calls the Business Application Programming Interfaces [Page 275]
(BAPIs) in SAP EM.

(C) SAP AG 33
Application Interface Customizing
You define the following in Customizing for the application interface to SAP EM:
 To define the system configuration:
 The RFC connection to SAP EM
 Defined the logical system
 To define the application interface:
 The SAP EM system
 The business process types
 The used business process types, application object types, and event types that
are relevant to supply chain event management
 The SAP EM interface functions
 The SAP EM relevance conditions

For more information about application interface Customizing, see the


Implementation Guide (IMG) for the ERP system under Integration with Other
SAP Components  Interface to Event Management.

Example
The following figure provides an example of a system landscape for the application interface.

Customizing

Application SAP
Application SAP Event
Event
BAPI

Interface
Interface
Management
Management
SAP
SAP R/3
R/3 Plug-In
Plug-In

SAP
SAP Basis
Basis Plug-In
Plug-In

SAP
SAP R/3
R/3

The SAP Basis Plug-In [Page 269] that contains the application interface as of SAP Basis
Plug-In 2002.1, is an add-on that you can install on a Web Application Server or SAP product
with SAP Basis 6.20 or higher.
To communicate with SAP EM, the application interface for SAP EM uses Business
Application Programming Interfaces (BAPIs).
The application interface is also part of the SAP R/3 Plug-In for all SAP R/3 releases as of
4.0B.

(C) SAP AG 34
Data Transfer from the Application System
Purpose
You use this process to:
 Specify the parameter containers for SAP Event Management (SAP EM) in the
application system (AS) that it fills with data from the table containers
 Trigger the transfer of parameter containers to SAP EM
 Obtain an input help for mapping parameters [External] in SAP EM
 Save events [Page 28] that have occurred for business objects in the application
system in the relevant event handlers in SAP EM

Prerequisites
You have completed the following on the application side:
 Defined the logical system
 Specified the application objects [Page 18] that are relevant to supply chain event
management (SCEM-relevant)
 Specified the Active mode for the business process type for your SCEM-relevant
application objects and events
 Assigned function modules to extractors in Customizing for the application system
 Assigned the extractors to application object types and event types in Customizing for
the application system
 Specified the corresponding SAP EM(s) for the application system
 The parameters in SAP EM

Process
...
...

1. The process begins when you create or change a document in the application system.

For example, you have completed the following in Customizing for the
application system:
 Specified extractors A and B for creating the info parameter list.
You assign function module XYZ to extractor A and function module
XY5 to extractor B.
 Assigned extractor A to application object type AOT1 and extractor B to
application object type AOT2
You create an application object AO1 for application object type AOT1
You create an event EV1 for event type EVT1.

As of PI Basis 2006.1, you can define a Customizing for the extractors and work
with table-based extraction.

(C) SAP AG 35
2. The application system determines the application object types. It automatically creates
the parameters (parameter list, milestones, query IDs, and tracking IDs) in the
individual extractors that are assigned to the application object types. The application
system also generates the event data that belongs to this event type.

For example, the system creates an info parameter list with the AS info
parameters P1 and P9 for application object AO1. The system also creates the
event data for event EV1.

If you have set the mode of the business process type for your SCEM-relevant
application objects to Maintenance, the system continues to create an input help
for defining parameters [Page 39].
You use business object keys as a back link from SAP EM to the application system.

A shipment consists of two deliveries and two handling units. It is not sufficient
for you to know the main object table with its technical key as a back link to the
object in the application system. The back link using the business object key
allows you to assign a business object in a unique way.
3. The application system transfers the following data to SAP EM using the definition for
parameter mapping and the parameter dictionary that you have defined:
 The parameter list
 The milestones
 The query IDs
 The tracking IDs
 The event data

You have specified in Customizing for SAP EM that SAP EM is to perform the
following mapping for application system AS1 and application object type
AOT1:
 AS info parameter P1 onto SAP EM info parameter X5
 AS info parameter P9 onto SAP EM info parameter X3
4. SAP EM transfers the data to the event handler that belongs to the application object.

For example, the SAP EM info parameters X5 and Z3 and the event EV1 are
transferred to event handler EH1.

(C) SAP AG 36
The following figure provides you with a simplified overview of the standard case for
transferring application data from the application system to SAP EM:

Application System SAP Event Management

Determining
Determining Extractors
Extractors
Extractor
Extractor A
A with
with Function
Function Module
Module XYZ
XYZ
Extractor
Extractor B with Function Module XY5
B with Function Module XY5

Assigning
Assigning Extractors
Extractors to
to AOT
AOT
Extractor
Extractor A
A to
to AOT1
AOT1
Extractor
Extractor B
B to
to AOT2
AOT2

Create
Create Shipment
Shipment Document
Document

Call Application
Interface

Determining
Determining Application
Application Object
Object Type
Type (AOT)
(AOT)
(/SAPTRX/ASC0AO)
(/SAPTRX/ASC0AO)

Result:
Result:
Application
Application object
object type
type AOT1
AOT1 is
is found.
found.

Setting for “BPT


Setting for “BPT Maintenance”
Maintenance” == “Active”
“Active” ==
Create/Update
Create/Update EH
EH

Creating Transfer Parameter


Parameter Mapping
Mapping
Creating Parameter
Parameter Containers
Containers Using
Using the
the
Individual
Individual Extractors
Extractors Parameter
Containers Control
Control Parameters
Parameters KP5
KP5 -> -> KX5
KX5
-- Control Control
Control Parameters
Parameters KP9
KP9 -> -> KX9
KX9
Control Parameters
Parameters KP5,
KP5, KP9
KP9
-- Info Info
Info Parameters
Parameters P1
P1 -> -> X5
X5
Info Parameters
Parameters P1,
P1, P9
P9
Info
Info Parameters
Parameters P9
P9 -> -> Z3
Z3
-- Tracking
Tracking ID
ID 123
123
Tracking
Tracking ID
ID 123
123 -> 123
-> 123
-- Expected
Expected Events
Events Expected
Expected Events
Events .... ->
-> ...
...

Create
Create Event
Event Handler
Handler EH1
EH1

-- Control
Control Parameters
Parameters KX5,
KX5, KX9
KX9
-- Info
Info Parameters
Parameters X5,
X5, Z3
Z3
-- Tracking
Tracking ID
ID 123
123
-- Expected
Expected Events
Events

(C) SAP AG 37
Result
The application system has transferred the following data for an application object and event
that you have defined as being SCEM-relevant to SAP EM:
 The parameter list
 The milestones
 The query IDs
 The tracking IDs
 The business object keys
At the same time the application system has created an event for this application object and
has also transferred this data to SAP EM.
SAP EM has written all the data into the relevant event handler (parameter data in
accordance with the relevant definition for parameter mapping).

(C) SAP AG 38
Input Help for Defining Parameters
Purpose
The system provides you with an input help for defining parameters in SAP Event
Management (SAP EM). This gives you a quicker overview of the application system (AS)
parameters that you can use for defining parameters in SAP EM.

Prerequisites
You have completed the following on the application side:
 Defined the logical system
 Specified the application objects that are relevant to supply chain event management
(SCEM-relevant)
 Specified Maintenance mode for the business process type for your SCEM-relevant
application objects
 Assigned function modules to extractors in Customizing for the application system
 Assigned the extractors to application object types in Customizing for the application
system
 Specified the corresponding SAP EM(s) for the application system
 Specified the parameters [External] in SAP EM

Process Flow
...
...

1. The process begins when you create or change a document (application object of a
specific application object type) in the application system.

For example, you have completed the following in Customizing for the
application system:
 Specified extractor A for creating the info parameter list. You assign
extractor A to function module XYZ.
 Assigned extractor A to the application object type AOT1.
 Created a shipment document SHD that belongs to application object
type AOT1.
The application system creates an application object AO1 for application
object type AOT1.
2. The application system determines the application object types.

If you have set the mode of the business process type for your SCEM-relevant
application objects to Active, the system continues to extract application data
[Page 35] from the application system and transfer it to SAP EM.
The application system automatically creates a parameter list. The system stores the
parameter list in a Customizing table. SAP EM displays the parameter list to you as an
input help when you define parameter mapping. You can specify a description for the
parameters.

(C) SAP AG 39
For example, the system creates an info parameter list with the AS info
parameters P1 and P9 for application object AO1. You specify a description for
the info parameters.
The following figure shows you the simplified automatic creation of the input help. You can
also create the input help manually in the transaction for defining SAP EM interface functions
(/SAPTRX/ASC0TF).

(C) SAP AG 40
Application System

Determining
Determining Extractors
Extractors
Extractor
Extractor A
A with
with function
function module
module XYZ
XYZ
Extractor
Extractor B
B with
with function
function module
module XY5
XY5

Assigning
Assigning Extractors
Extractors to
to AOT
AOT
Extractor
Extractor A
A to
to AOT1
AOT1
Extractor
Extractor B
B to
to AOT2
AOT2

Create
Create Shipment
Shipment Document
Document

Call Application
Interface

Determining
Determining Application
Application Object
Object Type
Type (AOT)
(AOT)
(/SAPTRX/ASC0AO)
(/SAPTRX/ASC0AO)

Result:
Result:
Application
Application object
object type
type AOT1
AOT1 is
is found.
found.

Setting for “BPT


Setting for “BPT Maintenance”
Maintenance” ==
“Maintenance”
“Maintenance” == Write
Write table
table

Creating
Creating Parameter
Parameter Containers
Containers Using
Using
Individual
Individual Extractors
Extractors

-- Control
Control parameters
parameters KP5,
KP5, KP9
KP9
-- Info
Info parameters
parameters P1,
P1, P9
P9
-- Tracking
Tracking ID
ID 123
123
-- Expected
Expected events
events

Customizing
Customizing Table
Table with:
with:

-- Control
Control parameters
parameters KP5,
KP5, KP9
KP9
that
that are
are assigned
assigned to
to the
the extractor
extractor for
for control
control
parameters
parameters
-- Info
Info parameters
parameters P1,
P1, P9
P9
that
that are
are assigned
assigned to
to the
the extractor
extractor for
for info
info
parameters
parameters
-- Expected
Expected events
events that
that are
are assigned
assigned toto the
the
extractor
extractor for
for
expected
expected events
events Filling
Filling the
the Customizing
Customizing Table
Table

Control
Control parameter
parameter KP5
KP5 == <short
<short text>
text>
Control
Control parameter
parameter KP9
KP9 == <short
<short text>
text> Enter
Enter your
your own
own <short
<short
Info text>
text> for
for each
each one.
one.
Info parameter
parameter P1
P1 == <short
<short text>
text>
Info
Info parameter
parameter P9
P9 == <short
<short text>
text>
Exp.
Exp. event
event == <short
<short text>
text>

(C) SAP AG 41
Simple Example Use for the Input Help
...

1. You want to create a parameter mapping profile (transaction /SAPTRX/TSC0PDM) and


want to use the input help for entering application system info parameters to do this.
2. This info parameter mapping profile is to be valid for application system XYZ and
application object type AOT1.
3. You have SAP EM display the input help for the info parameters. To do this, SAP EM
asks the application system for the input help belonging to application object type
AOT1.
4. The application system checks whether or not application object type AOT1 exists:
 If it does exist, the application system transfers the input help to SAP EM.
SAP EM displays the input help for entering application system info parameters.
 If it does not exist, the application system does not transfer an input help to SAP
EM.
SAP EM does not display an input help for entering application system info
parameters.
The following figure shows you a simplified overview of using the input help:

Application System SAP Event Management

Check if “AOT 1” exists.


If “YES” = read contents of assigned table
into SAP EM input help.

Application
Application system
system == XYZ
XYZ RFC
Application Mapping
Mapping Profile
Profile with
with Input
Input Help
Help
Application object
object type
type == AOT1
AOT1

Prerequisite
Prerequisite
The
The application
application system
system and
and application
application
object
object type
type must
must be
be specified
specified in
in SAP
SAP
Event
Event Management.
Management.

Application
Application system
system == XYZ
XYZ
Application
Application object
object type
type == AOT1
AOT1

Extractor
Extractor assigned
assigned to
to AOT1
AOT1

P1
P1 == Route
Route Customizing
Customizing for
for Parameter
Parameter Mapping
Mapping
P9
P9 == Loading
Loading status
status
AS
AS Parameters
Parameters SAP
SAP EM
EM Parameters
Parameters

Selection
Selection using
using P1
P1 == Route
Route
input
input help
help P9
P9 == Loading
Loading status
status

Key
AOT Application object type
Input Help
AS Application system
RFC Remote Function Call P1 = Route
SAP EM SAP Event Management P9 = Loading status

(C) SAP AG 42
Event Handler
Definition
An event handler represents a business process (for example, within a supply chain network)
or a business object (for example, a purchase order, shipment, or production order) that is
relevant to supply chain event management (SCEM-relevant). SAP Event Management (SAP
EM) tracks this business process or business object.
An event handler contains expected, reported, or unexpected events and attributes to identify
and track the related business processes.

Use
Application objects [Page 18] map business objects in the application system for the SCEM-
relevant process. A business process can consist of one or more application objects. SAP EM
creates just one event handler for each SCEM-relevant application object. Several event
handlers can map a related business process.
The event handler contains all the information necessary to track just this one 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 process 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. Examples of information are:
 Identifiers that are used in event messages (for example, container number, the service
provider’s own shipment number, sales order number, and serial number)
 Events that SAP EM either expects or requires for an application object (for example,
arrival at place of destination or proof of delivery)
 Information about the origin, destination, and interim stops
 Route and carrier information
 Shipment container number
 Weight, size, type, and temperature

Structure
The event handler determines the following:
 The expected events [Page 77] belonging to the application object
 An excerpt from the original data and master data (for example, business partners,
locations, materials)
 The identifiers for internal and external reference
 The parameters [External]
 The status
 The rules
The user defines the expected events and rules in SAP EM. This information is required for
monitoring event message processing [Page 97].

Integration
If you save an application object in the application system and the corresponding application
object type is SCEM-relevant, SAP EM creates an event handler.

(C) SAP AG 43
The application object ID together with the application object type and the business process
type serve as a reference between the event handler in SAP EM and the corresponding
application object in the application system.

(C) SAP AG 44
Event Handler Type
Definition
The event handler type is the definition of the business process or the business objects that
an event handler [Page 43] represents.
It is an SAP Event Management (SAP EM) control parameter that applies the rule set and
expected event profile to control the processing of event handlers, and that contains the
expected events.
The following are examples of event handler types:
 A purchase order for a supplier
 A manufacturing order for a plant
 A sea container for a shipment

Use
You can use the event handler type to specify the following:
 The way in which the system creates and updates an event handler
 The rule set [Page 112] for an event handler for processing event messages
 The profile settings for the following profiles:
 The expected event profile [Page 77]
 The status attribute profile
 The authorization profile for querying event handler data
 How data for an event handler is transferred to SAP NetWeaver Business Intelligence
 The activation for writing change documents [Page 198]
 The activation of the application log and the degree of detail of the logging
 The possibility to hide the historical data for expected events, measurement data, or
status attributes to improve performance
The event handler type is dependent on the application object’s parameters and is
determined using conditions and a mapping function.

(C) SAP AG 45
Event Handler Set
A group of event handlers that logically belong together and that map a certain process within
the supply chain.

The event handler set forms a link between these related event handlers. SAP Event
Management displays the event handler to the Web interface user (see User Interfaces [Page
135]) in accordance with Customizing, for example, for queries. For more information, see
Customizing for SAP Event Management under Event Messages, Status Queries, and Web
Interface Web Interface Define Web Interface Transactions .

Example
1. You track a sea shipment that consists of three legs:

o Two preliminary legs on the road during which your forwarding agent
transports your deliveries to the departure harbor

o A main leg during which your forwarding agent continues with the
transportation of your deliveries by sea

o A subsequent leg on the road during which your forwarding agent transports
your deliveries from the destination harbor to the relevant recipient

On the SAP Easy Access screen, choose Event Management Monitoring and
Lists Event Handler Set Browser or choose transaction /SAPTRX/EH_SET.

2. You specify the two SAP ERP delivery numbers as the tracking IDs and therefore as
the search criteria, and you start the search.

3. The system displays the results list (see Use of the Event Handler List [Page 161])
with the same number of event handlers as you have deliveries in your transportation
chain. Each event handler set consists of three event handlers: One for the
preliminary legs, one for the main leg, and one for the subsequent leg. The event
handler list shows you the events for each of these legs, for example, departure and
arrival times.

The list shows you the same information that the customer can see using the Web
interface. SAP Event Management does not show the user the information for details
for which he or she does not have authorization. You define this using the settings in
the filter concept.

For more information about the settings in the filter concept, see Customizing for
SAP Event Management under Authorizations and Filters.

(C) SAP AG 46
Event Handler Set Profile
Definition
Specifies the relations between event handlers that SAP Event Management (SAP EM) uses
to group these event handlers in an event handler set [Page 46].

Prerequisites
You have defined event handler types [Page 45].

Use
You use event handler set profiles to define the event handler set relations [External]. An
event handler set relation consists of an event handler set relation type [External] and an
event handler set relation code [External]. SAP EM uses the event handler set relation types
to group the event handlers and then to display them as a group for subsequent search
queries.
You can assign the following to the event handler set profile, as required:
 A filter profile
 A status attribute profile
 An event consolidation profile
 A status icon schema

Integration
You assign the event handler set profile to at least one event handler type [Page 45], so that
SAP EM can create event handler sets.
You assign multiple event handler set profiles to an event handler type, if an event handler
belongs to multiple business processes.

Structure
An event handler set profile consists of the following:
 A filter profile
It determines the data that SAP EM displays to the user when he or she selects event
handler sets in the Web interface. The following figure shows the relation between
authorization profiles, filter profiles, and event handler set profiles:

(C) SAP AG 47
EH
EH 11 EH
EH 22 EH
EH 33 EH
EH 44 EH
EH 55

Filtering Using Authorization Profile


(User-Specific)

EH
EH 11 EH
EH 22 EH
EH 44

Filtering Using Filter Profile


(User-Specific)

EH
EH 11 EH
EH 44

EH
EH Set
Set 11
Individual
Individual tables,
tables, fields,
fields, and/or
and/or rows
rows hidden
hidden for
for EH
EH 11 and
and EH
EH 44

Filtering Using Event Handler Set Profile


(Dependent on EH Type)

Individual
Individual tables,
tables, fields,
fields, and/or
and/or rows
rows hidden
hidden for
for EH
EH set
set 11

EH Event Handler EH Set Event Handler Set EH Type Event Handler Type

During a search request in the Web interface, the user-specific authorization profile
filters a subset from all the event handlers found. In turn, the user-specific filter profile
forms a subset from that subset. You can hide individual tables, fields, or rows for event
handlers in an event handler set. Depending on the event handler type, the event
handler set profile hides individual tables, fields, or rows for an event handler set.

For more information, see Authorizations and Filters [External].


 A status attribute profile
It determines the overall status for all the event handlers in a set.
 An event consolidation profile [Page 50]
This profile determines the order in which SAP EM displays the events for the event
handler set that it has consolidated to the user.
 A status icon schema
It determines the predefined status icons that SAP EM uses to display an event status
or an event handler set status in the Web interface.
 Event handler set relations with their event handler set relation types and event handler
set relation codes

(C) SAP AG 48
 The event handler set relation type specifies the type of relation between event
handlers within a set. You can form the set using control parameters [External],
tracking ID [Page 74] code sets, or query ID [Page 69] code sets.
 If the event handler set relation code (control parameter name, name of the
tracking ID code set, name of the query ID code set) is identical, SAP EM
creates an event handler set.
 You use the assignment of the event handler set relation code to the event
handler set relation type to specify the condition, so that SAP EM groups event
handlers (for example, event handler set relation code Control Parameter
and the corresponding parameter name Business Process Type).

For more information about defining event handler set profiles, see the
Implementation Guide (IMG) for SAP Event Management under Event Handlers
and Event Handler Data  Event Handlers  Define Event Handler Set
Profiles.

Example
...

1. You create an event handler set profile.


You have specified control parameter as the event handler set relation code and
business process type as the event handler set relation type in the event handler set
profile.
2. You assign the event handler set profile to event handler type LTL Shipment.
3. You use the Web interface to start a search query to SAP EM.
Preconfigure the Web interface for search queries about event handler sets
appropriately.
4. SAP EM checks the conditions that you have defined for assigning event handler type
LTL Shipment to the event handler set. SAP EM uses the relation type business
process type to search for the event handlers that correspond to your query.
5. A consolidated list is displayed containing all event handlers that correspond to your
query.

(C) SAP AG 49
Event Consolidation Profile
Use
You use event consolidation profiles to determine the order in which SAP Event Management
(SAP EM) sorts and displays the events for the event handlers of a set (see Event Handler
Set [Page 46]) on the consolidated page of the Web interface.
You can specify the sort order using the following criteria:
 The fields from the event handler header
 The event handler type
If you use both options together, SAP EM first sorts the events according to the fields from the
event handler header table and then according to the event handler types.
If you do not use an event consolidation profile, SAP EM sorts the events in descending order
by the date and time when SAP EM created the event handler.

Activities
In the Implementation Guide (IMG) for Event Management, choose Event Handlers and Event
Handler Data  Event Handlers  Define Event Consolidation Profiles.

(C) SAP AG 50
Parameters
Parameters are variables of objects and processes that are relevant to supply chain event
management (SCEM-relevant). The parameters contain the information from the application
system about an application object. They are defined and stored in SAP Event Management
in the form of control, info, and system parameters. This means that you can use SAP Event
Management independently of an application system.

In addition, you can also set values for rule processing parameters while processing a rule
set. You can use these rule processing parameters to transfer values from one task to the
next task in the rule.

Control, Info, and System Parameters


You use control, info, and system parameters in SAP Event Management in the rule set for
processing search or information queries.

To select the control and info parameters in SAP Event Management Customizing, you create
a parameter list for control and info parameters in the application system.

SAP Event Management stores information from the application system in the following
parameter types:

 Control parameters

You use control parameters, together with system parameters, to specify the event
handler type and the characteristics for an event handler.

 Info parameters

You use info parameters for all additional information that you want to transfer to the
event handlers in SAP Event Management for display purposes. If you have
permitted the use of info parameters for condition processing, you can use them for
processing in the rule set. To do this, set the corresponding indicator within an info
parameter.

 System parameters

These are all the control parameters that the application system transfers to the
corresponding fields in the event handler extension table, for example, the service
provider ID or the destination ID.

You need the parameters for the following:

 Control parameters to define and to check the process steps in SAP Event
Management, for example, the service provider name, document type, or material
type.

 Info parameters for information and query purposes, for example, location.

 System parameters to specify the field values for typical search queries to SAP Event
Management.

System parameters are therefore a special type of control parameter from the
application system that use database indexing to enable you to make quicker search
queries.

(C) SAP AG 51
For a transportation process, you define the country of origin and the destination
country, the name of the carrier, the mode, and the departure date as system
parameters.

 Control and info parameters to make your queries about SCEM-relevant information
to SAP Event Management and to transfer the SCEM-relevant information to a data
warehouse system.

Rule Processing Parameters


In SAP Event Management, you use rule processing parameters to transfer values from one
task to another task in a rule. You use an activity to set the value of a rule processing
parameter. You can access this value using an activity within a rule or using a rule condition.

You have both read and write access to rule processing parameters during rule set
processing.

Specify Parameters in the Application System


Choose the transaction for defining SAP Event Management interface functions in the
application system to specify a parameter list for control and info parameters. You get these
parameters as a selection list when defining expected events and control parameters in
Customizing for SAP Event Management. For more information, see Customizing for SAP
Event Management in the application system under Event Management Interface Define
Application Interface .

Specify Parameters in SAP Event Management


In SAP Event Management, choose the transaction for defining control, info, and rule
processing parameters and the transaction for defining system parameters.

For more information about defining parameters, see Customizing for SAP Event
Management under Event Handlers and Event Handler Data Parameters .

Structure
Info and Control Parameters
Info parameters consist of either text for information and query purposes or organizational
data for transferring data to a data warehouse. SAP Event Management saves the
information in a string format with a maximum length of 255 characters.

Control parameters save selected information in a string format with a maximum length of 60
characters.

We deliver control and info parameters. You can, however, create your own.

SAP Event Management saves control and info parameters as different data records in a data
container that has the following structure:

 Parameter name

 Index

 Parameter value (string)

 Length

 Original data type

(C) SAP AG 52
System Parameters
SAP Event Management saves system parameters in their own database fields in the event
handler extension table in Customizing. You can define your own system parameters using
this extension table and you can then change the value, if necessary, using activity method
Updating Field Value in Header Extension Table (HDR_EXT_VALUE_UPDATE).

You store the field values for your typical search queries as a record in the event handler
database table in Customizing, and set up a targeted index for these fields.

Rule Processing Parameters


SAP Event Management saves rule processing parameters as different data records in a data
container that has the following structure:

 Parameter name

 Parameter value (string)

 Length

 Original data type

Integration
The interface between the application system and SAP Event Management uses a mapping
process to transfer the parameters from the application system to SAP Event Management
(see Data Transfer from the Application System).

SAP Event Management uses parameters to change event handlers, for example (see Event
Handler Updating).

The Web interface displays parameters and other event handler data.

For more information, see Parameter Display (Web Interface (Web Dynpro ABAP) and
(Classic)) [Page 142].

Example
Control Parameters

Name Index Value

Service Provider ABC

Mode TRUCK

Priority HIGH

Material Class FROZEN GOODS

Info Parameters

Name Index Value

Color BLUE

(C) SAP AG 53
Country USA

Driver Jim Miller

Material 1 Corn Flakes

Material 2 Chocolate Corn Flakes

Sales Organization 1000

System Parameters in the Event Handler Extension Table

Name Index Value

Departure Country ABC

Destination Country FRG

Forwarding Agent SMITH

Mode ROAD

Departure Date 01.01.01

(C) SAP AG 54
Event Handler Extension Table
Definition
An additional table in which you can define your own fields that you can then use for search
and report queries.
The extension table is found in the event handler header data. System parameters are
mapped from the application system to the fields in the extension table. (See also:
Parameters [External]  Structure section.)

Use
The user can use the fields in the extension table as additional options for search and report
queries about event handlers. For more information about adding additional data from the
extension table as selection criteria in the event handler list, see Defining Search Criteria
[External].

Fields in the extension table must not contain numeric domains. Only use
character-type data types for the domains.
For more information, see the Implementation Guide (IMG) for SAP Event Management under
Event Management  Event Handlers and Event Handler Data  Event Handlers  Define
Extensions to Event Handler Header.

(C) SAP AG 55
Creation of Event Handlers
Use
You use event handlers to track and evaluate objects or processes that you have determined
as being relevant to supply chain event management.
Event handlers are created in SAP Event Management in various ways:
 The application interface creates event handlers for application objects.
 Sending an event message creates an event handler.
 The application system calls a Business Application Programming Interface (BAPI).
This triggers the creation of an event handler in SAP Event Management.
To check how event messages are processed for an event handler, the system requires the
expected events and the rule set that belong to the event handler, as defined in Customizing
in SAP Event Management.

If you test functions in SAP Event Management purely for test purposes and do
not want to set up a corresponding application system, you can use transaction
/SAP/TRX/EH_CREATE.
For more information about manually creating event handlers for test purposes,
see SAP Service Marketplace at http://service.sap.com/scm 
Supply Chain Event Management  Detailed Information.

Integration
Depending on the objects that you want to track and the partners who are involved, you can
create different event handlers using the application interface.

For example, you can specify the expected events according to the quality of the
supplier. The event handler for an unreliable supplier has a more extensive list
of expected events that must be reported than the event handler for a reliable
supplier (see also Event Message Processing [Page 97]).

(C) SAP AG 56
Communicating Data to Create Event Handlers
The following data is transferred from the application system to SAP Event Management via
the application interface to create an event handler:
 Main identification of the application object (application system, application object type,
and application object ID)
 Parameter record:
 Control parameters
 Tracking IDs
 Info parameters
 Expected events
 Query IDs
 Measurement data

Prerequisites
 You have specified the following in the application system:
 The application object types [Page 23]
 The condition for determining the application object type [Page 24]
 The function for determining expected events [Page 77]
 The control, system, and info parameters (see Parameters [External])
 You have defined the following in SAP Event Management:
 The event handler types [Page 45]
 The condition for determining the event handler type
 The expected event profile
 The parameter profile
 The status attribute profile
 The rule set [Page 112]
 You have set up Customizing for the application interface and have installed the
corresponding visibility process in the application system or have defined your own
process. The visibility process allows you to connect to your business objects in the
application system.
 You have set up the RFC connections that create the link between the application
system and SAP Event Management.
 You have defined the following for creating an event handler using an event message:
 The criteria
 The plug-in function modules
For more information about defining criteria and plug-in function modules, see
Customizing for SAP Event Management under Event Messages, Status Queries, and
Web Interface  Define Criteria for Event Message Processing.

Activities
The event handler creation process begins as soon as you save a document in the
application system.

(C) SAP AG 57
The steps for creating an event handler are shared between the application system and SAP
Event Management.
...

1. You save your document in the application system.


2. The application system executes the following:
...

a. It extracts the data container of the business object so that SAP Event
Management can create an event handler with the corresponding event handler
type.
b. It determines which SAP Event Management system is responsible for the
application object type. (An application system can work with several SAP Event
Management systems simultaneously.)
c. It specifies the business process type (BPT) of the business object.
d. It retrieves the application object types for the BPT from the application system
and determines if they are relevant to supply chain event management (SCEM-
relevant).
e. It creates control parameters for all application objects that are SCEM-relevant.
f. It checks whether SAP Event Management can create one or more event
handlers.
3. SAP Event Management executes the following:
...

a. It standardizes the control parameters that have been sent from the application
system so that it can process them.
b. It checks if suitable event handlers already exist.
If it does not find any suitable event handlers, it continues to execute the checks
for generating an event handler.
If it finds a suitable event handler, it uses this and updates the event handler.
c. It checks if it can generate the event handler.
d. It sends the result of the check to the application system.
4. The application system continues to process the confirmed application objects.
5. The application system then executes the following:
...

a. It collects all data from the parameter containers (control and info parameters,
expected events, tracking IDs, query IDs, business object keys).
b. It sends the marker for sending the collected data to SAP Event Management.
(The application system does not send the data until it continues with the saving
process. See also: step 5e)
c. It marks open communication processes for a status update in the status table.
(The application system does not update the status until it continues with the
saving process. See also: step 5e)
d. It flags the application log for an update. (The application system does not
update the application log until it continues with the saving process. See step
5e)
e. It returns to saving the business object. All actions that have been marked for
execution are completed in the application system.
6. At the same time, SAP Event Management determines the event handler type and
creates an event handler with the relevant expected events and status attributes. To do
so, SAP Event Management executes the following:
 It standardizes the data from the application system parameter containers (see
step 5a) so that it can process it.
 It calls the activities for updating processes.

(C) SAP AG 58
 It sends the confirmation for completed transactions to the application system.

(C) SAP AG 59
Creating an Event Handler Using an Event Message
 The event handler creation process begins as soon as you send an event message to
SAP Event Management. For this to occur, the event message must meet the
predefined criteria.
 The plug-in function module creates an event handler and SAP Event Management
processes the event message.
You specify the following data in the event message so that the plug-in function module can
create the event handler:
 The application system
 The application object type
 The control parameters
 The info parameters
 The tracking IDs
 The milestone data for the expected events from the event message

(C) SAP AG 60
Creation of Event Handler Hierarchies
Purpose
SAP Event Management (SAP EM) saves the hierarchical relationship between event
handlers as an event handler hierarchy that consists of a higher-level event handler and the
corresponding lower-level event handlers. The Web interface (Web Dynpro ABAP) [Page 136]
displays this information. For example, if you have two event handlers, one for a shipment
and one for a handling unit (HU) within this shipment, these two event handlers can have a
hierarchical relationship to one another. SAP EM archives the hierarchical information
together with the archiving object /SAPTRX/A0 Event Handlers [Page 246] and the archiving
object SAPTRX_A2 Event Handler Sets [External].

Prerequisites
You have created your own event handler within the hierarchy that you want to track. You
have also set up the entire Customizing for SAP EM. For more information about displaying
event handler hierarchies, see the Implementation Guide (IMG) for SAP EM under Event
Management  Event Messages, Status Queries, and Web Interface  Web Interface 
Configure Fields for User Profiles or Define User Profiles.

Process
...

1. The process begins when you create the required event handlers.

You want to track shipment SHIP0001 that contains HU HU02 and HU


HU03. You need a higher-level event handler for the event handler hierarchy. In
this example, it is the event handler EH_SHIP0001 for shipment
SHIP0001. You also need two lower-level event handlers for the two HUs:
 Event handler EH_HU02 with the tracking ID HU02 for HU HU02
 Event handler EH_HU03 with the tracking ID HU03 for HU HU03
When the shipment is created in ERP, you must have defined in Customizing for SAP
EM that SAP EM is to create the event handler EH_SHIP0001 with tracking ID
SHIP0001 for the shipment.
2. You send an event message to SAP EM with a further reference table for the higher-
level event handler. You specify in this reference table how SAP EM can determine the
lower-level event handlers for the higher-level event handler.

Since HUs HU02 and HU03 are assigned to shipment SHIP0001, you make
sure that the event handlers EH_HU02 and EH_HU03 are updated in SAP
EM. You also send an event message for shipment SHIP0001 that contains
the following information:
 The tracking ID SHIP0001 for the event handler EH_SHIP0001 in
the event message header
 A further reference table for the shipment
The further reference table contains the further reference IDs HU01 and HU02 so
that SAP EM can determine the lower-level event handlers EH_HU02 and
EH_HU03. For more information about setting data in a further reference table,
see the documentation for activity method ADD_EH_TO_PROCESS (CO
/SAPTRX/CL_EH_EVENT_MSG_MODEL ACT_ADD_EHS_TO_PROCESS).

(C) SAP AG 61
3. In accordance with your Customizing, SAP EM applies the activity method
EH_HIERARCHIE_UPDATE Update Event Handler Hierarchy Table in combination
with the following activity methods:
 ADD_EHS_TO_PROCESS Add Additional Related Event Handler GUIDs from
Further Reference Data
 EH_GUID_SET Retain Event Handler GUID Currently Being Processed
In this way, SAP EM creates the event handler hierarchy between the higher-level
event handler and the lower-level event handlers. For more information, see the activity
documentation (CO /SAPTRX/CL_EH_EVENT_MSG_MODEL
ACT_UPDATE_EH_HIERARCHY).

SAP EM creates the hierarchical relationship between the shipment and the
HUs on the basis of the information that you specified in the reference table in
the event message.
4. You log on to the Web interface and search for your shipment SHIP0001.
5. SAP EM displays the higher-level event handler EH_SHIP0001 with the lower-level
event handlers EH_HU02 and EH_HU03 in accordance with your Customizing for the
Web interface.

For an example of how you can use an event handler hierarchy, see SAP Help
Portal at http://help.sap.com  SAP Business Suite  SAP Auto-ID
Infrastructure  SAP Solutions for RFID  SAP Object Event Repository 
Supported Processes  Product Tracking and Authentication.

(C) SAP AG 62
Event Handler Updating
Purpose
By updating event handler data, the system can check how event messages are processed
for an event handler. To do this, the system needs the expected events that belong to an
event handler and the rule set in accordance with the Customizing settings made in SAP
Event Management.
You use current event handler data to track and evaluate objects or processes that you have
determined to be relevant to supply chain event management.

Prerequisites
 You have specified the following in the application system:
 The application object types [Page 23]
 The condition for determining the application object type [Page 24]
 The function for determining expected events [Page 77]
 The control, system, and info parameters (see Parameters [External])
To do so, in Customizing, choose Integration with SAP Components  Interface to
Event Management.
 You have defined the following in SAP Event Management:
 The event handler types [Page 45]
To do so, in Customizing for SAP Event Management, choose Event Handlers
and Event Handler Data  Event Handlers  Define Event Handler Types.
 The condition for determining the event handler type
To do so, in Customizing for SAP Event Management, choose Event Handlers
and Event Handler Data  Event Handlers  Define Conditions for Event
Handler Types and Event Handler Sets.
 The expected event profile
To do so, in Customizing for SAP Event Management, choose Event Handlers
and Event Handler Data  Expected Events  Define Profiles for Expected
Events.
 The parameter profile
To do so, in Customizing for SAP Event Management, choose Event Handlers
and Event Handler Data  Parameters  Define Parameter Mapping.
 The status attribute profile
To do so, in Customizing for SAP Event Management, choose Event Handlers
and Event Handler Data  Status  Define Status Attribute Profiles.
 The rule set [Page 112]
To do so, in Customizing for SAP Event Management, choose Reactions to
Event Messages  Define Rule Sets.
 You have set up Customizing for the application interface and have installed the
corresponding visibility process in the application system or have defined your own
process. The visibility process allows you to connect to your business objects in the
application system.

(C) SAP AG 63
For more information, see SAP Service Marketplace at
http://service.sap.com/scm  Supply Chain Event Management 
Visibility Processes  Generic Configuration Guide.
 You have configured the RFC connections between the application system and SAP
Event Management.
To do this, execute the following:
 In Customizing for the application system, choose Integration with SAP
Components  Interface to Event Management  Define System Configuration
 Define RFC Connection to SAP EM.
 In Customizing for SAP Event Management, choose General Settings in SAP
Event Management  Define RFC Connection to Application System.
 If you want to log changes to data relevant to event handlers, you have defined the
relevant indicator with the corresponding level of detail. For more information, see
Customizing for SAP Event Management under Event Handlers and Event Handler
Data  Event Handlers  Define Event Handler Types.

Process
The steps for updating an event handler are shared between the application system and SAP
Event Management, as for creating [Page 56] event handlers.
...

1. You save your document in the application system.


2. The application system executes the following:
...

a. It extracts the data container for the business object so that SAP Event
Management can use the application object ID to check if an event handler with
the corresponding event handler type can be found.
b. It determines which SAP Event Management system is responsible for the
application object type. (An application system can work with several SAP Event
Management systems simultaneously.)
c. It specifies the business process type (BPT) of the business object.
d. It retrieves the application object types for the BPT from the application system
and determines whether they are relevant to supply chain event management.
e. It creates control parameters for all application objects that are SCEM-relevant.
3. The application system checks if the event handler has the correct status for the
application object, that is, it has not been set to inactive (for example, for testing
purposes).
4. SAP Event Management executes the following:
...

a. It standardizes the control parameters that have been sent from the application
system into a view that it can process.
b. It checks if suitable event handlers already exist.
If it does not find any suitable event handlers, it continues to execute the checks
for generating an event handler.
If it finds a suitable event handler, it uses this and updates the event handler.
c. It sends the result of the check to the application system.
5. The application system continues to process the confirmed application objects.

(C) SAP AG 64
6. The application system then executes the following:
...

a. It collects all the data from the parameter containers. This includes:
 Expected events
 Control parameters
 Info parameters
 Tracking IDs
 Query IDs
 Business object keys
 Event data
 Application object IDs
 Queue names
You can define in the application system that SAP Event Management is to
delete the control parameters, info parameters, query IDs, or tracking IDs that
belong to a relevant application object.
b. It sends the marker for sending the collected data to SAP Event Management.
When the application system continues with the saving process, it sends the
data; see also step 6e.
c. It marks open communication processes for a status update in the status table.
When the application system continues with the saving process, it performs the
status update; see also step 6e.
d. It flags the application log for an update.
When the application system continues with the saving process, it updates the
application log; see also step 6e.
e. It returns to saving the business object. All actions that have been marked for
execution are completed in the application system.
7. At the same time, SAP Event Management determines the event handler type and
updates the event handler with the relevant expected events and status attributes. SAP
Event Management also standardizes the data from the parameter containers in the
application system into a view that it can process. Then it calls the activities for
updating the process and sends the confirmation of the completed transactions to the
application system.
If necessary, SAP Event Management deletes any control parameters, info parameters,
query IDs, or tracking IDs that belong to a relevant application object.
If you have activated logging with change documents [Page 198] and use activities in
the rule set that change data relevant to change documents, SAP Event Management
updates the corresponding change documents.

(C) SAP AG 65
Event Handler/Event Handler Set
Deactivation/Activation
Use
You use this function to deactivate event handlers or event handler sets whose tracking
process has been completed for the time being.

You want to track your deliveries. You define an activity to deactivate an event
handler in the rule set for SAP Event Management (SAP EM). As soon as your
delivery arrives at your customer, SAP EM deactivates the relevant event
handler.

Prerequisites
You have defined the following in SAP EM:
 The event handler types [Page 45]
 The condition for determining the event handler type
 The event handler set profile, if required
 The expected event profile
 The parameter profile
 The status attribute profile
 The rule set [Page 112]

(C) SAP AG 66
Automatic Deactivation and Activation of Event
Handlers or Event Handler Sets
You have specified in the rule set the method or function module for deactivating and
activating event handlers or event handler sets. SAP delivers methods or function modules for
activities [Page 204].

When the last expected event is reported for an event handler, the deactivation
of this event handler is triggered, for example. To do this, you define an
appropriate rule in the rule set that calls the method for deactivating event
handlers. You specify the reporting of the last expected event as a rule
condition.

When the system executes the method or function module for an event handler
that belongs to several event handler sets, it deactivates or activates these sets
and all event handlers belonging to the sets.

(C) SAP AG 67
Manual Deactivation and Activation of Event Handlers

You have the authorization to manually deactivate and activate event handlers.
...
...

1. Select the event handler to be deactivated or activated from the event handler list
[External].
2. The event handler overview appears and you display the detailed event handler header
data.
3. You select the Header Data tab page.
4. If the system does not display this tab page, choose EH Display Configuration and
configure the event handler data display so that the system displays the Header Data
tab page.
5. You choose Display  Change.
6. The system displays the event handler information that you are authorized to change in
change mode.
7. You activate or deactivate the event handler using the corresponding checkbox field in
the Status frame.
8. You save your setting.

(C) SAP AG 68
Query IDs
Definition
An additional identification to the tracking ID [Page 74] that you can also use to address an
event handler so that you can send queries to SAP Event Management (SAP EM).
Examples of query IDs are a sales order number or a purchase order number.

Use
In Customizing for the application system you specify query IDs so that you can use
information that you know as search criteria when you make queries to SAP EM.
SAP EM uses the query ID to find the event handler that matches your search query.

For example, you have defined the sales order number and the delivery number
as query IDs in Customizing for the application system. The customer only
knows the sales order number, whereas the sales representative knows the
sales order number and the delivery number. Both parties can query the event
handler status in the Internet using the sales order number, for example.

(C) SAP AG 69
Status Attribute
Description of the current status of an event handler or event handler set. The status attribute
consists of a name and one or more values. You define a status attribute Fill Status with
status attribute values Empty/Half-Full/Full.

When creating an event handler or event handler set, SAP Event Management uses the
default value for the status of the object or process relevant to supply chain event
management together with the expected events and parameters. You specify the default
value in Customizing for SAP Event Management.

When you send actual data on the status of an event handler or event handler set to SAP
Event Management in an event message, SAP Event Management checks the condition from
the rule set of the event handler or event handler set. If you have defined an activity in the
rule set for updating statuses, the evaluation of the condition may trigger this activity,
depending on the result. SAP Event Management updates the status attribute.

You can assign an icon to each status attribute in Customizing for SAP Event Management
under Event Handlers and Event Handler Data Statuses Define Status Attributes .
You can also define the sequence in which the Web interface displays the status attributes in
Customizing for SAP Event Management under Event Handlers and Event Handler Data
Statuses Define Status Attributes .

The status or the icon provides you with a quick overview of the relevant event handler or
event handler set when you make queries to SAP Event Management. You can also use the
status as a search criterion for event handlers.

For more information about status attribute Customizing, see Customizing for Event
Management under Event Handlers and Event Handler Data Statuses .

You classify the status attribute values in status attribute types that are either the YES/NO
type or the Status Attribute Value type.

A status attribute type specifies, for example, the status Shipment On Time as YES/NO or
the status of a vehicle as Loaded/Empty or as Delayed/Deviated from Route/Damaged.

For more information about defining status attribute types, see Customizing for SAP
Event Management under Event Handlers and Event Handler Data Statuses
Define Status Attributes .

You group one or more status attribute types in a status attribute profile, which you assign to
an event handler type.

For more information about defining status attribute profiles, see Customizing for SAP
Event Management under Event Handlers and Event Handler Data Statuses
Define Status Attribute Profiles .

(C) SAP AG 70
Event
Definition
An event is an incident that has occurred.
Examples of events include:
 Production start
 Delivery at the customer
 Delayed arrival of a truck
 Damage to a delivery

Use
 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.
 You can use SAP Event Management to make your supply chain measurable. When
processing event messages SAP Event Management checks if expected events [Page
77] have been met, and applies qualitycharacteristics for execution and reporting
habits.
 You update the status of the business process that you are monitoring in SAP Event
Management so that it can send current information (for example, about the production
level) in response to queries (see Event Reporting [Page 85]).
 You use events in the application system to define whether changes to application
objects or processes are relevant to supply chain event management (SCEM-relevant).

For more information about using events in the application system, see Event in
the Application System [Page 28].

(C) SAP AG 71
Event Categories
You can assign events to three different categories that allow you to monitor and evaluate the
supply chain:
 Regular event
The event occurs within the expected time (for example, the punctual arrival of
materials).
 Overdue event
The event does not occur within the expected time (for example, the late arrival of a
service provider).
 Unexpected event
The event occurs, but it was not planned (for example, traffic jam, production stop,
change of route for a service provider).
The following figure provides an overview of the three event categories and the life
cycle of an event handler:

Actual Event Event 1 Event 2 Event 3

Logistics Object

Expected Event Event 1 Event 2

Regular Overdue Unexpected


Event Event Event

Time

(C) SAP AG 72
Event Reporting
When reporting events you differentiate between:
 Events that have been reported
(regular, premature, delayed, and unexpected)
 Events that have not been reported (overdue)
Until the planned end time is reached, no information about whether the actual event
has occurred is available for unreported events.
The following are possible reporting combinations for the event and the event message:
 Event message
 Regular (event reported)
 Regular (event occurred)
 Premature/delayed (event occurred)
 Premature/delayed (event reported)
 Regular (event occurred)
 Premature/delayed (event occurred)
 No event message
 On schedule (in order according to time schedule) and not expected
(unexpected event has not yet occurred)
 On schedule (in order according to time schedule), but expected (event and
event message)
 Overdue (as far as is known, the event has not yet occurred, the event message
has not yet been sent)
You can send actual events to SAP Event Management in the following ways:
 You enter the data directly in the application system (for example, document
processing).
 You enter the data manually in SAP Event Management.
 You enter the data externally and report in the Internet or using EDI, for example.
Planned events are reported to SAP Event Management or determined in the following ways:
 The application system sends the data to SAP Event Management.
 SAP Event Management determines the data itself.

For example, you define the time for an expected shipment start to be two hours
after loading end.
 External partners report the data.

For example, a tender is sent to a service provider who cannot complete the
order for the required time, but instead for a later time. Since the service
provider has the appropriate authorization, he or she can overwrite the expected
events that are defined in SAP Event Management with the new data.

(C) SAP AG 73
Tracking ID
Definition
An identification with which to address an event handler [Page 43] so that an external or
internal message can be sent to it.

Examples of tracking IDs are a container number or a shipment number.

Use
 SAP Event Management (SAP EM) uses the tracking ID (together with the tracking ID
code set) to identify event handlers. In this way, you can send external or internal
messages to this object.
SAP EM uses tracking IDs and tracking ID code sets to find the corresponding event
handler(s). The combination of the tracking ID and tracking ID code set does not have
to be unique.
The tracking ID code set allows you to classify the tracking IDs.

For example, it is possible to have both a pallet with tracking ID 1234 and a
container with tracking ID 1234. However, you assign the pallet to the tracking
ID code set PAL for pallet and the container to tracking ID code set CON for
container. Each object has its own event handler.

There are two deliveries for a shipment, for example, and each delivery has its
own event handler in SAP EM. Both have the same tracking ID (for example,
shipment number 1234) and the same tracking ID code set (for example, HU40).
SAP EM processes an event message that is sent to this tracking ID and
tracking ID code set for both event handlers.
 When events are reported, SAP EM uses the tracking ID that is provided in the event
message to find the corresponding event handler.
The application system determines the tracking IDs.

If you define the function for the tracking ID in the application object type, you
define the different tracking IDs for this application object type.
 You use tracking IDs as search criteria when making queries in SAP EM.

For example, you can specify the tracking ID or the tracking ID code set as
search criteria when searching for the last reported events or for the status of
event messages (see Reports for Internal Monitoring and Evaluation of
Processes [Page 170]).

(C) SAP AG 74
Examples
Multiple tracking IDs linked to one event handler
...

1. You report an event.


 You report an event as a carrier using the shipment number.
 You report an event as a sales representative using the sales order number.
 You report an event as a production employee using the manufacturing order
number.
2. SAP EM finds the appropriate event handler using the combination of tracking ID and
tracking ID code set.
The following figure shows the connection between several tracking IDs belonging to one
event handler:

Tracking IDs
Reporter:
Reporter: Carrier
Carrier Reporter:
Reporter: Sales
Sales Employ.
Employ. Reporter:
Reporter: Prod.
Prod. Employ.
Employ.
Tracking
Tracking ID
ID CS:
CS: CR
CR Tracking
Tracking ID
ID CS:
CS: SE
SE Tracking
Tracking ID
ID CS:
CS: PE
PE
Tracking
Tracking ID:
ID: 18725
18725 Tracking
Tracking ID:
ID: 700147
700147 Tracking
Tracking ID:
ID: 4819
4819

Means of Communicating Event


Message
For Example:
 EDI
 XML
Event Handler  Internet
Tracking
Tracking ID
ID Code
Code Set
Set Tracking
Tracking ID
ID
CR
CR 18725
18725 Tracking ID code set is sent by
SE 700147 the message reporter, for
SE 700147
example, CR, SE, or PE.
PE
PE 4819
4819

Tracking ID CS: Tracking ID Code Set


CR: Carrier
SE: Sales Employee
PE: Production Employee

(C) SAP AG 75
Multiple tracking IDs linked to different event handlers
...
...

1. You report events for a pallet, a manufacturing order, and a shipment order for three
different event handlers. These event handlers have the same tracking ID but different
tracking ID code sets.
2. SAP EM can only find the event handler that matches the event message by using the
tracking ID code set.
The following figure shows the connection between multiple tracking IDs belonging to different
event handlers:

Tracking IDs
Event
Event 11 Event
Event 22 Event
Event 33
Reporter:
Reporter: Carrier
Carrier Reporter:
Reporter: Sales
Sales Employ.
Employ. Reporter:
Reporter: Trsp.
Trsp. Employ.
Employ.
Tracking
Tracking ID
ID CS:
CS: PAL
PAL Tracking
Tracking ID
ID CS:
CS: MO
MO Tracking
Tracking ID
ID CS:
CS: SO
SO
Tracking ID:
Tracking ID: 4711
4711 Tracking ID:
Tracking ID: 4711
4711 Tracking ID:
Tracking ID: 4711
4711

Event Handler
Tracking
Tracking ID
ID Code
Code Set
Set PAL
PAL Tracking
Tracking ID
ID Code
Code Set
Set MO
MO Tracking
Tracking ID
ID Code
Code Set
Set SO
SO
Tracking
Tracking ID
ID 4711
4711 Tracking
Tracking ID
ID 4711
4711 Tracking
Tracking ID
ID 4711
4711

Tracking ID CS: Tracking ID Code Set


PAL: Pallet
Sales Employ.: Sales Employee
MO: Manufacturing Order
Trsp. Employ,: Transportation Employee
SO: Shipment Order

(C) SAP AG 76
Expected Event
Definition
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.

Examples of expected events are the expected arrival time of a service provider
or the expected time of an order confirmation or confirmation of a quality check.

Use
 SAP Event Management needs expected events to be defined to monitor overdue or
unreported events.
 You can use expected events that have been defined and then fulfilled as quality
criteria, for example, service provider punctuality or quality assurance.
In Customizing for SAP Event Management, you define an expected event profile. You
define the list of expected events in this profile. You also use this to specify the
database fields relevant to SAP Event Management.
The profiles allow SAP Event Management to automatically create expected events for
an event handler [Page 43].

Structure
An expected event contains the following:
Content of an Expected Event
Location type
Location ID
Partner type
Partner ID
Data code set
Data code ID
Date
Time
You can define functions for the following checks, as required:
 Check for location code set and location code ID
 Check for partner code set and partner code ID
 Check for data code set and data code ID
 Check for transferring data for location data, partner data, or other corresponding data
You can also define the following:
 The date and time with tolerances, if required
 Additional dates and times for your own purposes, for example, for adhering to base
plans, if required
 Multiple expected events as a profile group within the expected event profile so that
SAP Event Management creates recurring expected events multiple times

(C) SAP AG 77
Integration
The following options are available for reporting data for the list of expected events to SAP
Event Management:
...
...

1. You send the data for an expected event:


 From the application system
 Externally from an external system
2. SAP Event Management determines the data for an expected event itself.

You specify in SAP Event Management that your partner is to report the
shipment end. You also specify that the date for proof of delivery by the
customer is to automatically be set for two days after shipment end has been
reported. In this case, SAP Event Management automatically calculates the time
for the expected event Proof of Delivery by Customer after the service provider
has reported the shipment end.

(C) SAP AG 78
Expected Event Update Via Event Message
Use
By sending an event message to SAP Event Management (SAP EM), you can trigger an
update of the expected event list (delete, add, and update events).
SAP EM updates the following expected event data:
 The estimated deadlines (for example, expected transportation time, estimated arrival
time at location)
 The next expected events (for example, new location or new partner)
 The deadlines for the next expected events (for example, new date or new time)

Prerequisites
You have defined an activity, EVM_EE_UPDATE, with which to update expected event data.
For more information about defining SAP Event Management activities, see the
Implementation Guide (IMG) for Event Management  General Settings in SAP Event
Management  Functions, Conditions, and Activities in SAP Event Management  Define
Activities for SAP Event Management.
You have defined the following in Customizing:
 An expected event profile
 Internal and, optionally, external event codes for the expected events
 Location code sets, if required
 Location code IDs, if required
 Partner code sets, if required
 Partner code IDs, if required

Features
 The following are keys for the update of the expected event list:
 The event counter
 The event action
 The external event code, if you have defined it
 The internal event code, if you have not defined an external one
 The following data, if you have defined it:
 The location code set
 The location code ID
 The partner code set
 The partner code ID

If you want to use the attribute for the estimated time (STATT) to update the
data and to calculate the earliest and latest events and the earliest and latest
event messages, define your own activity by copying activity EVM_EE_UPDATE
and changing it correspondingly.

(C) SAP AG 79
If you create an expected event using a BAPI, the requirement type of this
expected event is set to Not required.
 You can also update the expected event list independently of reported events.
 You can update the data for your additional time categories.

For more information, see the relevant activity description.


In the Implementation Guide (IMG) for Event Management, choose Reactions to
Event Messages  Define Rule Sets. Choose Activity Methods in the dialog
structure and select the EVM_EE_UPDATE method. Choose Display Function
Module Documentation.

(C) SAP AG 80
Expected Event Monitor
Use
This report checks the expected events of an active event handler for overdue messages and
triggers activities where necessary.

Prerequisites
If you want to use the process for seasonal procurement, you must have set the Seasonal
Procurement indicator.
See also: Parameter Selection for Expected Event Monitor [Page 82].

Features
You can start this program as a background process. SAP Event Management (SAP EM)
uses the expected event [Page 77] monitor to recognize overdue expected events. You can
define activities, for example, sending an e-mail, to react to these overdue events.
When you use the seasonal procurement process, you can use the selection fields specific to
seasonal procurement.
SAP EM processes overdue expected events belonging to the seasonal procurement process
in a different way from other overdue events. In the case of overdue expected events
belonging to the seasonal procurement process, SAP EM works on event handlers and not on
individual expected events. SAP EM bundles the expected events. When you select an
overdue expected event for an event handler belonging to the seasonal procurement process,
SAP EM reads all the expected events for this event handler. At the same time, SAP EM
determines internally in one step and with reference to the time index for the report selection
which expected events for the event handler will be overdue in this report run. SAP EM
determines from these expected events the which one is valid and which has the highest
internal priority.

SAP delivers activities [Page 204] for the expected event monitor (for example,
for comparing two fields or activating an event handler set).

(C) SAP AG 81
Parameter Selection for Expected Event Monitor
Use
You can set selection parameters for the report that checks the expected events of an active
event handler for overdue expected events.

Prerequisites
If you want to activate extra selection options for seasonal procurement in addition to the
default selection parameters for seasonal procurement, you have executed the following:
 You have created an entry and set the Seasonal Procurement indicator in Customizing
for SAP Event Management (SAP EM). You set the indicator in the Implementation
Guide (IMG) for SAP EM under General Settings in SAP Event Management 
Activate Seasonal Procurement Process or in transaction /SAPTRX/TSC0FASH.
 You have set the parameter value X for GET/SET parameter /SAPTRX/EE_MON_SEL
(Display Monitor Fields).
If you want to use the unspecific selection parameters, that is, those that are not specific to
seasonal procurement, you have set the parameter value X for GET/SET parameter
/SAPTRX/EE_MON_SEL (Display Monitor Fields).

(C) SAP AG 82
Selection Parameters for Seasonal Procurement
In the standard system, you have the following selection options for seasonal procurement:
 Check for Old qRFC
 Lines per Package w/o Split
 Package per Order

When SAP EM processes qRFCs, it executes automatic activities, as required.


Here it can be the case that a direct data backflow takes place from the SAP
system to SAP EM. This backflow can result in changes to the expected events
for event handlers. These changes have a direct effect on the selection of
overdue expected events in this report.
You can activate additional selection options for seasonal procurement by executing the
relevant Customizing and setting the relevant value for the GET/SET parameter. You then get
the following radio buttons under Old Monitor Entries:
 Process Old Monitor Entries
 Do Not Process Old Monitor Entries
 Delete Old Monitor Entries

(C) SAP AG 83
Fields Not Specific to Seasonal Procurement
You can use the following unspecific selection options:
 Selection Criteria for Monitor Function
 From date
 To date
 Package size - monitor selection
 Location Parameters
 Location code set
 Location ID 1
 Location ID 2
 Internal event code

For more information about the report and the possible selection parameters,
see the report documentation for report /SAPTRX/EE_MONITOR.

(C) SAP AG 84
Event Reporting
Purpose
By reporting events you can:
 Forward information in a timely way to all partners involved in the business process
 Check if planned or agreed deadlines have been met, and if so how
 Document the business process

Prerequisites
 You have defined the business process types [Page 21] and event handler types [Page
45] in Customizing.
 You have defined an expected event [Page 77]profile in Customizing for each event
handler type.
 You have defined a rule set [Page 112] in Customizing for each event handler type to
check event messages.
 You have checked if a means already exists to report events, or if an appropriate
interface must be implemented.

You have an existing EDI system and an EDI converter that can send IDocs, for
example.
 You have defined the internal event codes in Customizing.
If your partners use external event code sets and event codes, you can define the way
in which SAP Event Management (SAP EM) maps the external events codes onto
internal ones.

Process
...

1. You (as an employee, service provider or partner, for example) report an event to SAP
EM.
2. You specify the external event code [Page 90] consisting of an event code set and an
event code ID.
3. You specify the tracking ID [Page 74].
4. SAP EM receives the event message and prepares it for additional processing (for
example, checks the validity of the event message).

(C) SAP AG 85
The following figure provides an overview of the standard process flow:

SAP Event Management

Update Event
Message Database

Send
Event Message

Optional: Process Event


Create EH Message in
Send Send SAP EM

For more information about the process flow in SAP EM, see Inbound Event Message
Processing [Page 95] and Event Message Processing [Page 97].

(C) SAP AG 86
Means of Communication for Reporting Events
You can use various means of communication to report events:
 Direct input in SAP EM
 Transfer from the application system
 Input in the Internet
 EDI
 XML
 Language recognition

Result
SAP EM receives the data. It processes this data and reacts in accordance with the activities
defined in the rule set (for example, sends an e-mail or updates the data in the shipment
document in the application system).

(C) SAP AG 87
Event Message
Definition
An event message is any form of information transfer from a data source to SAP Event
Management that involves information about current expected events [Page 77] or unplanned
incidents within the supply chain.

Use
You can use event messages to transfer information about changes to a business object
within the supply chain from an application system or from external sources to SAP Event
Management.
An event message can contain data for multiple events and multiple document references.
You can also send attachments (for example, a digital signature) with an event message to
SAP Event Management.

(C) SAP AG 88
Message Sources
You can send event messages from both internal and external data sources.
Examples of internal message sources are:
 Application objects that have reached a specific status
 Event handlers that generate an event message for another event handler
Examples of external message sources are:
 On-board computer
 Tracking service provider
 Service provider uses the Internet or an automatic scanner to directly enter event
message

Structure
The following table gives you an overview of the information that an event message can
contain:
Information Comment
Identifiers For example, a tracking ID that identifies the
objects that SAP Event Management is to track
Event The event that has occurred
Date For the event
Time For the event
Location For the event
Partner For the event
Measurement data For the event
Further Information For example, the transportation route
One or more document references, as
appropriate
One or more attachments, as appropriate
A Uniform Resource Locator (URL) for the For more information about using and defining
tracking service provider’s Web page a link to a tracking service provider’s URL, see
Customizing for SAP Event Management
under Event Messages, Status Queries, and
Web Interface  URL Templates for Tracking
ID Providers.

Example
You are expecting a delivery of car tires at 13:00. The service provider reports his departure
to SAP Event Management by on-board computer at 10:00. SAP Event Management sends
you an e-mail informing you that the carrier departed at 10:00 with your delivery.

(C) SAP AG 89
Internal Event Code and External Event Code
Definition
The event code is a joint term for the event code set and the event code ID. SAP Event
Management (SAP EM) differentiates between the internal event code and the external event
code.

(C) SAP AG 90
Internal Event Code
The internal event code displays the internal type of the event [Page 71] for an event
message [Page 88]. The internal event code makes it possible for SAP EM to display the
external event code in a standardized way.
You specify the internal event code in SAP EM.
An external event (for example, delivery arrival) is mapped onto an internal event code (for
example, PUAR).

(C) SAP AG 91
External Event Code
The external event code displays the event type for an event message.
You specify the external event code in SAP EM. It corresponds to the industry standard
codes, such as ANSI X12214 status code, RosettaNet, or CLM code.
The following figure provides an example:

External External External Event


Event Event Code
Code Set Code ID

Incomplete
ANSIX12 214 X12 1 X12 1 Delivery

EDIFACT EDI 1 EDI 1 Arrival

Use
The event codes identify the event that has occurred and that is to be updated in SAP EM.
SAP EM needs internal event codes to:
 Create a list of expected events for an event handler
 Find the corresponding expected event when an event message is sent and thereby
check the planned and actual data
You use external event codes so that your business partners can still use their event codes
(for example, EDI standard code).

(C) SAP AG 92
Mapping External Event Codes onto Internal Event
Codes
...

1. You send an event message with an external event code to SAP EM.
2. SAP EM maps the external event code onto the internal event code in accordance with
Customizing.
3. If you have defined internal event code groups, SAP EM assigns the internal event
code to the appropriate internal event code group.
The following figure provides an overview of mapping external event codes onto internal
event codes:

Event Message

4711 LOADING
LOADING 14:00

4711 X12 L ANSIX12 214

EDI 48 EDIFACT

Tracking ID External External


Event Event
Code Set Code ID

4711 X12 L
EDI 48
Tracking ID External Event Code

Mapping Process for


External Event Codes in
SAP Event Management

4711 LOADING
Tracking ID Internal Event Code

Assignment Process to
Internal Event Code Group in
SAP Event Management

4711 Customer Pick-Up


Tracking ID Internal Event Code Group

Event Message in SAP Event Management


4711 LOADING
LOADING 14:00

4711 Customer Pick-Up


Tracking ID Internal Event Code Group

(C) SAP AG 93
Example
...

1. You specify the following expected events for a sales order:


 Picking
 Packing
 Departure
 Arrival at Customer
2. You specify the following internal event codes for your expected events:
 PICK for picking
 PACK for packing
 DEP for departure
 ARRCUST for arrival at customer
3. You specify the external event code set CAR1 for your service provider with external
event code IDs:
 001 for picking
 010 for packing
 030 for departure
 110 for arrival at customer
4. You specify how the external event code IDs are mapped onto the internal event codes.
5. You report the event picking to SAP EM either with the internal event code PICK or with
the external event code ID 001.
See also: Event Message Processing [Page 97].

(C) SAP AG 94
Inbound Event Message Processing
Use
SAP Event Management (SAP EM) executes inbound processing of event messages [Page
88] to
 Check the syntax [Page 96] (for example, is the weight specified correct?) and the
technical definition of the event messages
 Log the event messages
You can display the error list for inbound event message processing using the
transaction /SAPTRX/ER_MS_LIST.
 Save the event messages on the database
 Convert external event codes for event messages into internal event codes, if you use
external event codes.
 Use the tracking ID to search for the event handlers that belong to the event messages
 Use a rule set with its activities to trigger further event message processing in SAP EM
The system can also process event messages that have already been set to Inactive.

For example, you can report damage to a shipment after the shipment has
already been completed in SAP EM and the corresponding event handler has
been set to Inactive.
 Log the processing results in the application log [External] in the event handler list

Activities
SAP EM:
 Receives the event messages from the application system and from external sources
(BAPI, IDoc)
 Checks the syntax of the event message
 Determines which event handlers belong to the event message
 Processes the event message according to the activities in the corresponding rule set

(C) SAP AG 95
Extended Check to and Preprocessing of Event
Messages
Use
SAP Event Management (SAP EM) executes an extended check and preprocesses event
messages to check or change required information within an event message.
If an event message fulfills certain criteria, SAP EM executes the checks or changes.
The following are possible criteria:
 Event code
 Event message sender
 Event location
 Tracking ID code set
By defining plug-in function modules, you can define further checks or changes.

Prerequisites
You have defined the plug-in function modules that you use for the extended check and for
preprocessing in the transaction for defining event message processing criteria
(/SAPTRX/TSC0MBF).

Features
By default, SAP EM checks the following information:
 If an event code exists and is executable
You maintain the event code in Customizing.
For more information about internal and external event code Customizing, see the
Implementation Guide (IMG) for Event Management  Event Handlers and Event
Handler Data  Codes  Event Codes.
 If the information for identifying event handlers exists
 If date and time information is available and if it is technically executable
 The data structure of an attachment, if the event message contains an attachment

SAP EM needs a line counter to ensure that the database key is unique.
If you want to perform further checks or preprocessing on an event message in addition to
those mentioned here, you define the following: you define plug-in function modules in the
transaction for defining criteria for event message processing (/SAPTRX/TSC0MBF).

(C) SAP AG 96
Event Message Processing
Purpose
By processing event messages in SAP Event Management (SAP EM) you can:
 Process the data contained in the event message in a standardized way
 Monitor overdue event messages
 Compare planned and actual event data to evaluate the event messages
 Use the appropriate rule set [Page 112] to trigger follow-up activities in response to
event messages
 Retrieve current information on the business objects and processes that have been
determined to be relevant to supply chain event management

Prerequisites
 You have set up Customizing for SAP EM. You have also defined the following, in
particular:
 Internal, and where appropriate, external event codes [Page 90]
To do so, in Customizing for SAP EM, choose Event Management  Event
Handlers and Event Handler Data  Codes  Event Codes.
 An appropriate rule set for the event handler with its respective rules and the
conditions and activities for these individual rules
To do so, in Customizing for SAP EM, choose Event Management  Reactions
to Event Messages  Define Rule Sets.
 A suitable event handler [Page 43] should also be available for the event message in
SAP EM.
 If you want SAP EM to process event messages for inactive event handlers too, you
can define criteria for forwarding event messages to inactive event handlers and for
processing event messages by inactive event handlers.
For more information about processing event messages for inactive event handlers,
see the Implementation Guide (IMG) for SAP EM under Event Management  Event
Messages, Status Queries, and Web Interface  Define Criteria for Event Message
Processing.
 If you want to log changes to data relevant to event handlers, you have defined the
relevant indicator with the corresponding level of detail. For more information, see the
IMG for SAP EM under Event Management  Event Handlers and Event Handler Data
 Event Handlers  Define Event Handler Types.

Process
...
...

1. Either you or the system reports an event [Page 71] (for example, service provider
delay or proof of delivery by the customer).
2. The event message is transferred to SAP EM using the application interface.
3. If errors occur during processing, SAP EM writes them into the event message
processing error list [Page 176].
4. SAP EM prepares the event message for further processing. After receiving the event
message, SAP EM saves it in a database.
See also: Inbound Event Message Processing [Page 95].

(C) SAP AG 97
5. SAP EM checks if the syntax of the event message is valid and uses the mapping
definitions to convert all coded data values such as the event codes and location codes
into the internal code format.
6. SAP EM checks if the event message is an expected event. The following prerequisites
must be fulfilled for this to be possible:
a. This event message must agree with the internal event code.
b. The location and partner specified in the event message must agree with those
for the expected event in SAP EM.

This is only necessary if you have set the match indicator for location and
partner entries in the expected event profile.
The check enables SAP EM to judge whether:
 The event message that you are sending meets the rules defined.
 The event takes places in the defined period of time and the event is reported in
the defined period of time.
 The event reaches the quality required.
For more information, see Evaluation in the Rule Set [Page 116].
7. SAP EM uses the tracking ID [Page 74] to assign one or more corresponding event
handlers to the event message.
8. SAP EM applies the rule set that belongs to the event handler and executes the
corresponding activities. When SAP EM executes an activity in the rule set that
changes control parameters, for example, SAP EM updates change documents [Page
198] as appropriate.
A background process runs in SAP EM that checks expected events. If partners are
supposed to report expected events within a certain period of time and they do not do
this, these events are overdue. If the background process discovers an overdue event,
it calls the relevant rule set for the event handler and reacts in accordance with the
rules defined in the rule set (see also Expected Event Monitor [Page 81]).

(C) SAP AG 98
Adding Attachments to Event Messages
You can add attachments to an event message that you want to send to SAP Event
Management for an event handler. When you add an attachment to an event message in the
Web interface, you can perform a virus check before sending the event message to SAP
Event Management.

You want to report a delay due to an accident and also send a photograph of the scene of
the accident and your digital signature.

Prerequisites
Prerequisites for Adding an Attachment to an Event Message Using a
BAPI or a Function Module
 The system administrator has defined criteria for saving event messages.

For more information, see Customizing for SAP Event Management under Event
Management Event Messages, Status Queries, and Web Interface Define Criteria
for Event Message Processing .

Prerequisites for Adding an Attachment to an Event Message in the Web


Interface
 The system administrator has configured the settings for this function for your user
using the event message profile, which is part of the user profile.

The administrator has defined a configured field for adding an attachment to an event
message and has assigned this configured field to your event message profile. As a
result, you can see and send attachments to an event message.

The administrator has created the configured field with ATTACHMENTS as theEM
Attribute ID.

The system automatically specifies EVENTMESSAGE as the corresponding EM object.

For more information, see Customizing for SAP Event Management under Event
Management Event Messages, Status Queries, and Web Interface Web Interface
Define Fields for User Profiles and Assign User Profiles and Web Interface
Transactions to Users.

 If you want to use a virus check in the Web interface (classic), the system
administrator has configured a Virus Scan Provider in the J2EE Engine Visual
Administrator.

For more information about the Virus Scan Interface and configuring a Virus Scan
Provider, see the SAP Library for SAP NetWeaver under SAP NetWeaver
Security System Security Virus Scan Interface .

For more information about an overview of the Virus Scan Interface, see SAP
Note 786179.

(C) SAP AG 99
 If the system administrator has configured a Virus Scan Provider in the Web interface
(classic), he or she has also defined the parameter value TRUE for the Virus Scan
Execution parameter in the Global Manager.

Procedure
Adding Attachments to an Event Message Using a BAPI or a Function
Module
1. Place the file in the network, from which the system calls the following:

BAPI EventHandler.AddEventMessages02 or function module


/SAPTRX/BAPI_EH_ADDEVENTMSG_02.

2. Split the file up so that the length of each individual block does not exceed 255
characters.

3. Enter the blocks into table TRACKFILEBIN (binary file) or TRACKFILECHAR (text file).

4. Fill the following fields in header table TRACKFILEHEADER:

o EVTCNT

o FILENAME

o FILECLASS

o MIMETYPE

o FILESIZE

o NUMLINES

5. Call BAPI EventHandler.AddEventMessages02 or function module


/SAPTRX/BAPI_EH_ADDEVENTMSG_02 with table TRACKFILEBIN (binary file) or
TRACKFILECHAR (text file) and header table TRACKFILEHEADER.

6. The system saves the file in the database.

Adding Attachments to an Event Message in the Web Interface


1. Choose either the fast entry page or an action for sending event messages on the
search results page of the Web interface.

The system administrator has created at least one configured field with
ATTACHMENTS as the EM Attribute ID.

A browse pushbutton is available next to this field in the Web interface.

2. Choose Browse.

A new window appears from which you can navigate to the file on your PC that you
want to attach to the event message.

3. Attach the file to the event message and send the event message to SAP Event
Management.

Before the Web interface sends the attachment to SAP Event Management, the Virus
Scan Provider performs a virus check. If, for example, it finds a virus or a connection

(C) SAP AG 100


problem occurs, you get a warning message. This warning message informs you that
the Web interface cannot send the attachment. The Web interface provides detailed
information about the error on the Admin page.

(C) SAP AG 101


Using Event Message Parameters
Use
In SAP Event Management (SAP EM), you can define event message parameters that
contain additional information about an event message. By defining event message
parameters in SAP EM, you define the field values for one of the following options:
 For search queries that enable you to query information in SAP EM quickly
 For displaying additional information that is saved in the event message extensions
SAP EM displays this information as the event list on the user interface.

Features
The event message parameters go directly into the corresponding fields of the event
message header. You use the extension table for the event message header for your own
event message parameters. In this table, you can define your own fields that you can then
use for searches and queries in the Web interface (Web Dynpro ABAP).

If you want to work with event message parameters, you have defined how the
parameter values from the event message are mapped to the parameter values
in SAP EM. For more information, see the Implementation Guide (IMG) for SAP
EM under Event Management  Event Messages, Status Queries, and Web
Interface  Event Message Parameters.
The fields in the extension table must not contain numeric domains. Use
character-type data types of a domain only. For more information, see the IMG
for SAP EM under Event Management  Event Messages, Status Queries, and
Web Interface  Event Message Parameters  Define Extension Table for
Event Message Header.

(C) SAP AG 102


Buffered Event Message Processing
Use
You can specify that event message processing should be buffered, so that reported event
messages are not sent to SAP Event Management (SAP EM) immediately, but at another
time.

You can schedule a background job that sends buffered event messages to
SAP EM once a night, for example.
In this function you select the required buffered event messages that you want to send to SAP
EM.

Prerequisites
 You have specified selection criteria for buffering the event messages.
For more information about buffering event messages, see the Implementation Guide
(IMG) for Event Management under Event Messages, Status Queries, and Web
Interface  Define Criteria for Event Message Processing.
 You have event messages that have been buffered.

Activities
On the SAP Easy Access screen for Event Management, choose Event Reporting  Process
Buffered Event Messages.
If required, view the confirmations for the event messages that have been sent in the
application log (transaction SLG1, object SAPTRX).

(C) SAP AG 103


Individual Event Reporting
Use
You use this function as an additional means to report individual events within an
implementation project. Unlike the standard transaction in the Web interface, you report the
individual events (for example, a supplier address) using mobile devices (for example, a
handheld).

 Due to technical reasons on the text-based handheld side, you can send
each field for reporting event data only once. When you report events via
a BAPI, you can normally send most fields multiple times.
 Since the layout was developed for the input screen of a mobile device,
you cannot use any menu commands (for example, Quit). Instead, you
use the input screen pushbuttons (for example, QuitF9).
 You call transaction /SAPTRX/MI01 directly in the system.

Prerequisites
You have determined the screen layout for mobile devices by defining radio frequency event
message profiles (RF event message profiles) in Customizing for SAP Event Management
(SAP EM).
For more information about defining RF event message profiles, see the Implementation
Guide (IMG) for SAP EM under Event Management  Event Messages, Status Queries, and
Web Interface  Define Layout for Individual Messages.

Activities
9. Choose transaction /SAPTRX/MI01.
10. Specify a radio frequency event message profile (RF event message profile) and
choose GoEnter.
For more information about defining RF event message profiles, see the
Implementation Guide (IMG) for SAP EM under Event Management  Event
Messages, Status Queries, and Web Interface  Define Layout for Individual
Messages.
11. The system displays the input screen that corresponds to the RF event message profile
that you have selected.
If you have already specified default values in the RF event message profile, the
system displays them.
12. If you have the appropriate authorization, you can change the default values, if
required.
13. Specify the required values (for example, event code ID Delayed).
14. To save your entry, choose GoEnter.
15. The system sends the event message to SAP EM. SAP EM processes the event
message (see Inbound Event Message Processing [Page 95]).

(C) SAP AG 104


Expected Event Reporting
Use
By reporting events you can:
 Forward information in a timely way to all partners involved in the business process
 Check if the partners involved in the business process keep to planned or agreed
deadlines
You use this function within an implementation project as an additional means to report the
following for an expected event [Page 77] to SAP Event Management (SAP EM):
 Date
 Time
 Time zone
 Status reason (for example, recipient not available)

You call transaction /SAPTRX/MI02 directly in the system.

Prerequisites
 SAP EM has created event handlers.
 SAP EM has created predefined expected events (expected event list) for each of
these event handlers.

If you have defined a location and location matching for an expected event, the
system automatically uses the location of the expected event when reporting this
event. Therefore, when you match the expected and the reported locations, the
result is always “TRUE”.
If you have defined partner matching for an expected event, the system cannot
apply it for this form of event reporting. In this case, we recommend that you
report events using the Web interface (classic) [External].
For more information about defining expected events, see the Implementation
Guide (IMG) for SAP EM under Event Management  Event Handlers and
Event Handler Data  Expected Events  Define Expected Event Profiles.

Activities
...
...

1. Choose transaction /SAPTRX/MI02.


2. Specify the following to identify an existing event handler:
a. The tracking ID code set and tracking ID code ID, if they are unique
b. In addition, the service provider tracking ID code set and service provider
tracking ID code ID, if the tracking ID code set and the tracking ID code ID are
not unique

 The tracking ID code ID is case sensitive.


 The tracking ID code set is not case sensitive.
 You must also specify leading zeros for the tracking ID code ID.

(C) SAP AG 105


3. Choose Go.
4. SAP EM determines the expected events that belong to the event handler and displays
the following:
 The internal event code text
 The predefined location, if required
 The following for the expected event, if required:
 Planned date
 Planned time
 Planned time zone
 The following for the event message, if required:
 Actual date
 Actual time
 Actual time zone
5. Enter the following to confirm an expected event:
 Date
 Time
 Time zone
 Internal code [Page 90] for the event reason
You define internal event reasons in Customizing for SAP EM.
For more information about defining internal codes for event reasons, see the
Implementation Guide (IMG) for SAP EM under Event Management  Event
Handlers and Event Handler Data  Codes  Event Codes  Define Internal
or External Reasons for Events.
The system displays the event reason in the event handler list [External] when
you query SAP EM, for example, or you use the event reason within conditions
in the rule set [Page 112] of an event handler.
6. Select your confirmations.
7. Choose Post selected messages.
A confirmation screen appears.
8. Choose Send.
The system sends the event confirmation to SAP EM.
9. SAP EM determines the event handler that belongs to the event message and updates
the event handler data.

(C) SAP AG 106


Reactions to and Actions for Events
Reactions to events are preconfigured notification or follow-up options in SAP Event
Management (SAP EM). If a supplier reports a delay, for example, you can define in
Customizing for SAP EM that SAP EM is to send an e-mail to the shift manager. Actions in
response to events are query options in SAP EM. If, for example, a customer complains about
an incomplete delivery, you can start a query to SAP EM. You use the query to check which
service provider transported the delivery and whether this service provider has previously
been unreliable.

Features
You can configure SAP EM in such a way that you can:

 Receive notifications and event data that are sent to SAP EM

 Enter your own data for events in SAP EM

 Make status queries to SAP EM

 Have SAP EM trigger automatic processes in another system

The following table provides a list of how reactions or actions by SAP EM to various
addressees could look:

Examples of Possible Reactions and Actions

Addressee Option 1 Option 2 Option 3

Simple notification
Simple notification using the Alert
using the Alert Framework as for
Framework for the option 1; in
punctual arrival of a addition, the
Customer complete delivery at notification
the customer, or for contains a URL
delays or damage, for that the customer
example, by e-mail or can use to search
fax. for the current
process status.

 Simple Simple notification, The option to start a


notification by as for option 1; you workflow or alerts for
sending can additionally exceptions and
event query a status, for unexpected business
messages to example, about the events.
SAP EM, for following:
example,
about the  The
Employee availability of quantities
raw materials A supplier cannot
that your deliver a raw
at the supplier
supplier, the material on time
has because of a delay
punctual already
arrival of raw to a ship, for
manufactur example. You have
materials ed for a
ordered for already agreed
manufactur delivery times and
production at ing order.
the factory, or prices with several

(C) SAP AG 107


Examples of Possible Reactions and Actions

Addressee Option 1 Option 2 Option 3


delayed or alternative providers.
 The
damaged SAP EM displays
quantity
deliveries. this selection of
that you
alternative providers.
have put
 Own event Moreover, SAP EM
message away
provides a list of
already.
input, for alternative carriers,
example, for for example, quicker,
 How
the start of but more expensive
punctually
production, truck transporters, or
your
end of air transportation
supplier
putaway, or instead of sea
has
the departure transportation.
delivered
of a service
your
provider to When the supplier
products.
the customer. sends the event
message Loading
 How much
End (LOAD) to SAP
scrap there
EM, SAP EM
is for a
automatically
product in
updates the
production.
transportation status
Your partners can to Loaded in the
transfer the data application system..
using an Internet
portal, for example.

 Simple Simple notification, The option to start a


notification as for option 1; you workflow or alerts for
about the can additionally exceptions and
punctual query a status, for unexpected business
loading of a example, about the events.
complete following:
delivery at
the producer,  When the
or about partner can A truck cannot make
delays or start to its deliveries to
Partner, for damage, for load the individual customers
example, example, by delivery. on time because of a
logistics e-mail. road accident. You
service  Where the have already agreed
provider,  Own event delivery delivery times and
subcontract message currently is. prices with several
or, or input, with alternative
supplier information  When the forwarding agents.
about the delivery is The application
availability of expected system displays this
raw materials to arrive at selection of
or means of the alternative
transport, or customer. forwarding agents.
the loading Moreover, the
start or arrival Your partners can
application system
at the transfer the data
provides you with a
customer, for using an Internet
list of all customers
example. portal, for example.
and their required

(C) SAP AG 108


Examples of Possible Reactions and Actions

Addressee Option 1 Option 2 Option 3


delivery times with a
prioritization
according to the
importance of the
customer.

When the supplier


sends the event
message Loading
End (LOAD) to SAP
EM, SAP EM
automatically
updates the
transportation status
to Loaded in the
application system..

Activities
You can define the following reaction options in Customizing for SAP EM:

 In which cases SAP EM is to notify someone:

o When an event is reported within the expected time (regular event)

o When an event is reported earlier or later than expected (for example, an


overdue event)

o When an event is not reported

o When an unexpected event is reported

 How SAP EM is to notify someone, for example, using Alert Management, SAP
workflow, or the Alert Framework.

 Whether SAP EM returns data to the application system to trigger activities using a
rule set, for example, rescheduling.

 Whether SAP EM is to trigger different activities

To do so, define appropriate rule conditions in a rule set. For more information, see
Customizing for SAP EM under Event Management Reactions to Event
Messages Define Rule Sets .

(C) SAP AG 109


Example
Example of Preconfigured Reactions to Events
The following figure shows an example of predefined reactions to events:

E-Mail to Partner:
Notification of
Production Start
Production
Start
E-Mail to Customer:
Notification of
Production Production Start
End

Load Truck at
Dock

Create
Shipment
Document
E-Mail to Partner:
Delay
Departure

Unexpected
Event: E-Mail to Customer:
Delay Delay

Arrival at
Customer Reschedule
Arrival Time in
Application System
Proof of
Delivery

Reactions to Events

(C) SAP AG 110


In this example, you have defined the following in SAP EM using a corresponding rule set:

 As soon an employee reports the production start to SAP EM, SAP EM informs both
your partner and your customer via an e-mail.

 When SAP EM receives a message containing the unexpected event Delay, SAP EM
informs both your partner and your customer via an e-mail, and also triggers the
rescheduling of the arrival time in the application system.

(C) SAP AG 111


Rule Set
Definition
A rule set consists of several rules that define how the event messages for a particular event
handler are processed and evaluated. SAP Event Management (SAP EM) assigns the rule
set that belongs to the event handler type when creating an event handler [Page 56].

Use
 SAP EM processes event messages with the rule set that were set for an event
handler.
 You can use a rule in the rule set to call the expected events that you have defined.
 You can use rule sets to specify that SAP EM is to process event messages [Page 97]
in a different way. You can define a particular rule set for each event handler type, with
each rule set triggering a different reaction from SAP EM to the same event message.

For example, you want SAP EM to react differently to service provider delays,
since your service providers have various levels of reliability. To do this, you
have defined an event handler type for service provider A and one for service
provider B. The rule set for event handler type A plans the shipment start and
shipment end, reported by your service provider, and the proof of delivery,
reported by the customer, as expected events. Your service provider B is more
reliable. You specify only the shipment start and proof of delivery by the
customer as expected events for event handler type B.

Structure
A rule set consists of a set of rules that SAP EM evaluates when processing event messages.
The individual rule consists of a rule condition [Page 115] and a rule activity that SAP EM
executes based on the result of this evaluation.
The following figure provides an overview of a rule set structure:

Rule Set

Condition 1

Rule 1

Activity 1

Condition 2

Rule 2

Activity 2

(C) SAP AG 112


If the evaluation of the rule condition returns “TRUE”, SAP EM calls the activity defined for the
relevant condition.
 The rule activity consists of one (single-task activity) or more (multitask activity) tasks
that trigger EM activities (for example, sending an e-mail).
 The single-task activity can be an event handler method, a function module, or a
multitask activity.

SAP delivers rule activities [Page 204] that you can use within a rule set.
Processing in the rule set then branches to the TRUE or FALSE rule, depending on the
condition evaluation. If you have not defined a value for the condition evaluation, SAP EM
executes the next rule.
You can call several rule conditions within a rule by grouping several rule conditions in a set,
which you call in the rule condition of the rule.
The following figure provides a detailed overview of a rule set structure:

Event Handler Applic.


Object
0:1

Rule Set

0:N

Rule

0:1
Condition
- Boolean Expression
- Plug-In Function Module

0:1 Multitask Activity


- Single-Task Activity
Plug-In Function Module
Event Handler Method
- Multitask Activity

0:N

0:1 Single-Task Activity


- Plug-In Function Module
- Event Handler Method

(C) SAP AG 113


Integration
You can call a BAPI within a function module, and thereby trigger activities in a remote
system. For example, after the customer has completed the proof of delivery, you can have
the system update the delivery document in your application system.

(C) SAP AG 114


Rule Condition
Definition
A decision-making criteria that SAP Event Management uses when checking if it can execute
a task for an event handler.
Rule conditions can be either Boolean equations or function modules.

Use
The rule processor checks the conditions by calling the appropriate rule set [Page 97] for the
respective event handler when processing event messages [Page 112]. Depending on the
result, the rule processor decides whether SAP Event Management needs to react to the
event message [Page 88] (for example, by sending an e-mail), or not.
You can define a Boolean equation with parameters from the event handler and the event
message, or an equation that executes a complex evaluation and then returns the result to
the rule processor.

The following questions are examples of rule conditions:


 Has the final destination been reached?
 Is the event an exception?
 Is the service provider who reports the event the same service provider
that I expected to send the event message?
 Were the goods delivered on time?

(C) SAP AG 115


Evaluation in the Rule Set
Use
The evaluation of the rule set [Page 112] determines how SAP Event Management (SAP EM)
reacts to incoming event messages.
You need this function to check how incoming event messages are processed for your supply
chain event management-relevant (SCEM-relevant) processes in SAP EM, and to specify
how SAP EM reacts to event messages. For example, you can specify that an e-mail is sent
to the person responsible in the case of a delay to a shipment.
You specify how SAP EM reacts to event messages by defining:
 Conditions for the rule activities
 Rule activities with their tasks

For example, you can define as tasks that an e-mail is sent to an employee, or
that application object data is updated, or that the status of event handler is
changed.

Prerequisites
 You have defined a rule set for each event handler type.
 You have defined rules with their activities and conditions within the rule set.

Features
 A rule set consists of a set of rules that SAP EM evaluates one after the other when an
event message is processed.
 Each rule can contain activities and a condition. Depending on whether the evaluation
of the individual condition returns the result “TRUE” or “FALSE”, SAP EM continues to
process the event message with the respective activity, assuming that you have
previously defined this activity.
 A condition can also consist of a condition set.
You use the logical connection between the individual rule conditions (AND or OR
relation) to define how rule processing occurs.
 Each multitask activity consists of a sequence of tasks that SAP EM executes one after
the other.
 The following are examples of activities in SAP EM:
 Single-task activity
A single-task activity is a plug-in function module or a method.
 You can use the plug-in function modules that SAP delivers with SAP EM or you
can define your own. The plug-in function module can refer to event handlers or
other objects (for example, sending an e-mail or updating the status of a means
of transport) in SAP EM, or can call a BAPI in a remote system to update the
business object data.
You can choose from only those methods delivered with the SAP EM Class
Library and cannot define your own without modifying them.
Use your own plug-in function modules for activities.
 The method reads or updates the event handler’s internal data (for example,
activation or deactivation of an event handler, update to event handler data,

(C) SAP AG 116


check of individual values for the event handler’s expected events, such as the
date or sequence).
 Multitask activity
A multitask activity can consist of one or more plug-in function modules,
methods, or multitask activities.
The following figure provides an overview of a rule set structure:

Event Handler Applic.


Object
0:1

Rule Set

0:N

Rule

0:1
Condition
- Boolean Expression
- Plug-In Function Module

0:1 Multitask Activity


- Single-Task Activity
Plug-In Function Module
Event Handler Method
- Multitask Activity

0:N

0:1 Single-Task Activity


- Plug-In Function Module
- Event Handler Method

(C) SAP AG 117


Rule evaluation within a rule set for an incoming event
message
...

1. The event handler controller forwards the incoming event message to the rule
processor that applies the corresponding rule set.
2. SAP EM evaluates the condition for each rule that is applied and calls the individual
activity depending on the result of this evaluation.

SAP delivers rule activities [Page 204] that you can use within a rule set.
3. SAP EM processes the respective tasks for each activity. These tasks can, for
example, call a BAPI to update data in the application system.
The evaluation of rule condition 1 returns “TRUE” and SAP EM executes activity 1.
Activity 1 consists of two activity steps: Update the shipment date and delivery date of
the corresponding application object in the application system using the respective
BAPI call. Processing then continues with rule 2.
The evaluation of rule 2 returns the result “FALSE”. SAP EM does not execute an
activity and processing continues with rule 3.
The evaluation of rule condition 3 returns “TRUE” and SAP EM executes activity 3.
Activity 3 consists of a task: proof of delivery. SAP EM calls a BAPI to process the
proof of delivery in the application system.
4. After SAP EM has evaluated all the rules one after another, the application system
sends a confirmation to SAP EM so that SAP EM saves the updated event handler
data.

(C) SAP AG 118


The following figure provides an overview of the evaluation in the rule set:

Sender

Send Event Message

Event Handler
Process Event Message Activity 1 BAPI
Evaluation
Returns Call
Update Application Object
”TRUE“
Shipment Date
Rule 1 Condition 1
BAPI
Call
Update Application Object
Evaluation
Delivery Date
Returns
Rule
Rule 2 Condition 2 ”FALSE“
Processor

Evaluation
Returns Activity 2 BAPI
”TRUE“ Call
Rule 3 Condition 3 Confirm Proof Application Object
of Delivery

BAPI to Execute Proof


of Delivery

Rule Set
If condition 1 is “TRUE”, execute activity 1: Update shipment and delivery dates; call BAPI to do this.
If condition 2 is “FALSE”, continue with rule 3.
If condition 3 is “TRUE”, execute activity 2: Execute proof of delivery; call Remote Funct ion Call to do this.

Example
You create a shipment document in SAP R/3, for example. You have specified that your
shipment is SCEM-relevant so that SAP EM creates an event handler for your shipment
document. The event messages for the shipment start and shipment end go to SAP EM. SAP
EM calls a rule for these event messages from the rule set belonging to the event handler.
This rule executes an activity. This activity contains the task that calls a BAPI to update the
date or the stages of your shipment in the application system.

(C) SAP AG 119


Rule Set Display
Use
You can use this function to gain a comprehensive overview of a rule set and its components.
You can have the system display every detail on a rule set (for example, the individual rules,
activities, or tasks).

Integration
This function is available to you under Display Rule Set in the transaction for defining rule
sets.
The system displays an overview of the rule set that has been defined in a separate screen.
You can go back to the transaction for defining rule sets from this separate screen.
For more information about defining rule sets, see the Implementation Guide (IMG) for Event
Management  Reactions to Event Messages  Define Rule Sets.

Activities
...

1. On the SAP Easy Access screen for Event Management, choose Monitoring and Lists
 Display Rule Sets.
2. Select an (existing) rule set and display it.
3. To display a rule set while defining it, use the transaction for defining rule sets (see
section Integration).
4. A new screen consisting of two sections appears.
The left-hand side contains a comprehensive overview of the rule set and its
components in the form of a navigation tree.
5. Select the required component (for example, a task).
The detailed information is displayed on the right-hand side of the screen in display
mode.
The following icons are used for displaying components of a rule set:

Ico Object
n
Rule Set
Rule
Rule Condition
Rule Condition Set
Multitask Activity
Single-Task
Activity
Task
TRUE Rule
FALSE Rule

Choose ABAP Routine to display the coding for function modules or methods (for
example, in single-task activities).

(C) SAP AG 120


In the case of multitask activities, only the activity ID is displayed as a detail. This is
because multitask activities consist of a sequence of tasks. You can display the details
for each of these tasks.
The conditions that were created using the condition editor are displayed in HTML
format to make it easier to read them.
The coding is displayed for conditions that were programmed for function modules.

(C) SAP AG 121


Simulating Processes in the SAP Application
System and SAP EM
Use
To see the consequences of saving, updating, or deleting an SCEM-relevant business object
in the application system, you can simulate processes. This provides you with an overview of
all the processes in SCEM.

SAP EM does not save the values from the simulation.

Prerequisites
 You have set up Customizing for the SAP application system.
 You have set up Customizing for SAP Event Management (SAP EM).

Procedure
...

1. In the application system, choose the transaction for defining business process types
(/SAPTRX/ASC0AO).
2. Choose Simulation as the mode for a business process type.
3. Save the change.
In doing this, you have set the simulation mode not only for all SCEM-relevant process
steps in the application system, but also for the process steps in SAP EM.
4. Start the simulation by either saving, changing or deleting an SCEM-relevant business
object in the application system (for example, a shipment document).
The system displays the chosen business process type and the application object types
that belong to it.
5. Choose Continue or Cancel.
When data is updated, SAP EM shows the various processes step-by-step (depending
on your Customizing for the application system and SAP EM). For example, you can
check the following within the various processes:
 The parameter list in the application system
 The current SAP EM
 The expected events created
 The event handler types that SAP EM has determined
If you choose to cancel, the simulation activity is aborted and the SAP Easy Access
screen appears.
The simulation also transfers the SCEM-relevant data from the application system to
SAP EM.

You can cancel the simulation at any point.

(C) SAP AG 122


Result
 The system has simulated all SCEM-relevant processes.
 If the simulation is successful, you can start the process in the active business process
mode.
 If problems occur, you know where and in which process you can make corrections, if
required.

(C) SAP AG 123


Connection to the Alert Framework
The Alert Framework supplies you with alerts (for example, by e-mail or SMS) as a service
provided by the SAP NetWeaver Application Servers. In critical situations such as a delay or
contamination, SAP Event Management calls the Alert Framework. It can inform you, as the
person responsible, about these situations, for example. This notification can contain
information about the event handler that belongs to the event message, for example, the
purchase order number, destination, or status.

In comparison with SAP Business Workflow, the Alert Framework offers simpler handling and
is less performance intensive (see Connection to SAP Business Workflow).

Prerequisites
 You have defined a connection from the Alert Framework to your communication
system (for example, an SMTP server). For more information, see SAP Library for
SAP NetWeaver on SAP Help Portal at http://help.sap.com SAP Technology
Components Technical Operations Manual for SAP NetWeaver Administration of
SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Administration
SAPconnect Communication Interface under the link SMTP Configuration Guide.

 You have defined an RFC connection from SAP Event Management to the Alert
Framework.

When you first start the Alert Framework, you specify an RFC connection to
determine the system on which the Alert Framework runs. This can be the same
system on which your SAP Event Management runs.

If you run your SAP Event Management and the Alert Framework on the same
system and in the same client, you do not need an RFC connection. Enter NONE
in the transaction for changing the RFC destination to the central alert server.

For more information, see SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com SAP NetWeaver Library SAP NetWeaver Developer's
Guide IT Scenario-Driven Enhancements to Applications SAP NetWeaver
Operations Alert Management under the link Triggering Alerts.

 You use an SAP NetWeaver Application Server 6.20 or higher.

The Alert Framework requires a central server on which an SAP NetWeaver


Application Server 6.20 or higher is installed. Since SAP Event Management is based
on SAP NetWeaver Application Server 6.20 or higher, the central server of the Alert
Framework can run on the same system.

Process
1. You establish the connection to your communication system in Customizing for SAP
Event Management under

Reactions to Event Messages Define Alert Framework Connection Define


SAPconnect Administration .

2. You define the RFC connection from SAP Event Management to the Alert Framework
in Customizing for SAP Event Management under Reactions to Event Messages
Define Alert Framework Connection Define RFC Connection to Central Alert
Server .

(C) SAP AG 124


If you run SAP Event Management and the Alert Framework on the same system,
enter NONE here.

3. You create at least one alert category and at least one alert container in Customizing
for the Alert Framework. This is irrespective of whether you run the Alert Framework
and SAP Event Management on the same system.

If you run the Alert Framework and SAP Event Management on the same system,
you define the alert category in Customizing for SAP Event Management under
Reactions to Event Messages Define Alert Framework Connection Define Alert
Categories .

If you run the Alert Framework and SAP Event Management on different systems,
you define the alert category in Customizing for SAP NetWeaver under Application
Server Basis Services Generic Business Tools Alert Management Define
Alert Categories .

4. You specify which alert category the system is to use and how the SAP Event
Management attributes are to be mapped to the elements of the alert container in
Customizing for SAP Event Management. These settings are joined together in an
activity parameter ID.

5. You define how the alert is to be sent, for example, as an e-mail or SMS, and who the
recipient is to be in Customizing for SAP Event Management. In Customizing for SAP
Event Management, choose Reactions to Event Messages Define Alert
Framework Connection Define Alert Framework Integration to SAP Event
Management .

6. You assign the alert category to a rule in Customizing for SAP Event Management
under Reactions to Event Messages Define Rule Set .

You specify in Customizing which alert category SAP Event Management is to trigger
in which rule within the rule set for the corresponding event handler.

You can use the /SAPTRX/CREATE_ALERT rule activity function as a template and
replace the first activity parameter with your activity parameter ID from step 4.

For a detailed description of the activity function, see the function module
description. On the SAP Easy Access screen, choose Tools ABAP
Workbench Development Function Builder . Enter the
/SAPTRX/CREATE_ALERT function module and choose Display. Choose Goto
Documentation .

Example
1. Your customer sends an event message Delivery Delay for a shipment to SAP Event
Management that contains a specific event code, for example, DELAY for delay.

2. SAP Event Management updates the event handlers that belong to the shipment. To
find the event handlers, SAP Event Management uses the corresponding tracking ID
and the internal event code set.

3. Your new rule is contained in the rule set for these event handlers. This rule calls the
ALERT_CREATE rule activity function in response to the event Delay. The rule activity
function connects SAP Event Management to the Alert Framework.

4. The alert is sent to the customer via e-mail.

(C) SAP AG 125


Direct Access to Detailed Information
You can use the Alert Framework to send an alert with a link to a user. This means that this
user can monitor a process from the alert.

Prerequisites
Prerequisites for the Web Interface (Classic)
 You have completed the prerequisites for connecting the Alert Framework (see
Connection to the Alert Framework [Page 124]).

 You have defined the link for the Web interface in Customizing for SAP Event
Management under Reactions to Event Messages Define Alert Framework
Connection Define Alert Framework Integration to SAP Event Management .

Prerequisites for the Web Interface (Web Dynpro ABAP)


 You have completed the prerequisites for connecting the Alert Framework (see
Connection to the Alert Framework [Page 124]).

 You have defined a service user who is allowed to use the direct link. On the SAP
Easy Access screen, choose Tools Administration User Maintenance Users
.

 You have defined a Web interface transaction in Customizing for SAP Event
Management under Event Messages, Status Queries, and Web Interface Web
Interface Define Web Interface Transactions .

 You have assigned the service user that you defined to the Web interface transaction
and to the user profile in Customizing for SAP Event Management under Event
Messages, Status Queries, and Web Interface Web Interface Assign User
Profiles and Web Interface Transactions to Users .

 You have created and configured an Internet Communication Framework service


(ICF service). On the SAP Easy Access screen, choose Tools Administration
Administration Network HTTP Service Hierarchy Maintenance and create a
new ICF service under em_wda_ui SAP Event Management. Make sure that the
name of the ICF service is the same as the name that you use for the Web interface
transaction. Furthermore, make sure that the user who you assign to the new ICF
service is the service user.

For more information, see SAP Library for SAP NetWeaver under SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capability
Platform-Wide Services Connectivity Components of SAP Communication
Technology Communication Between ABAP and Non-ABAP Technologies
Internet Communication Framework Development Server-Side Development
Creating and Configuring an ICF Service .

 You have defined the link for the Web interface in Customizing for SAP Event
Management under Reactions to Event Messages Define Alert Framework
Connection Define Alert Framework Integration to SAP Event Management .

Features
The user can use the link to view the detailed data for event handlers belonging to the alert,
without having to log on in the SAP Event Management system. The user cannot change the
event handler data.

(C) SAP AG 126


In the Web interface (Web Dynpro ABAP), you can define the link for one Web interface
transaction only. When a user calls the link, the ICF starts the ICF service and SAP Event
Management displays the detailed data for the event handlers belonging to the alert.

Assign only the necessary authorizations to the service user, since SAP Event
Management does not apply an authorization or filter concept for this user.

For more information, see Customizing for SAP Event Management under Reactions to
Event Messages Define Alert Framework Connection Define Alert Framework Integration
to SAP Event Management .

(C) SAP AG 127


Connection to SAP Business Workflow
Use
When critical situations occur, SAP Business Workflow as a SAP Web Application Server
service allows you not only to automate a business process, but also to inform the person
responsible.
If you want to react to events, you can link SAP Event Management (SAP EM) to SAP
Business Workflow in accordance with your rule set [Page 112].

For example, your customer sends a proof of delivery that triggers the event
Proof of Delivery in SAP EM, which in turn uses SAP Business Workflow to
trigger the settlement process for the delivery.
You define parameters to link the events that start workflows in the local system or in another
system.
You define the event type linkage in Customizing for SAP EM by:
 Defining the event START_WORKFLOW with object type /SAPTRX/EH
This event links SAP EM to the events that each start a workflow.
 Specifying /SAPTRX/TRIGGER_WORKFLOW as the receiver function module
 Activating the event type linkage
The advantage of the event type linkage is in error handling: In cases where the application
system is not available, the system administrator receives a message and the system saves
the event temporarily.
For more information about SAP Business Workflow, see the SAP Library under SAP
NetWeaver Components  SAP Web Application Server  Business Management (BC-
BMT)  SAP Business Workflow Engine (BC-BMT-WFM).

Prerequisites
SAP has already predefined the event type linkage to trigger a workflow. Check that the
following settings have been made correctly:
 Object type: /SAPTRX/EH
 Event: START_WORKFLOW
 Receiver type: TRIGGER_WORKFLOW
 Receiver call: Function module
 Receiver function module: /SAPTRX/TRIGGER_WORKFLOW
 Linkage activated: Checked
You have created the following in Customizing for SAP EM:
 The activity ID that SAP EM uses as the key
 The object type of the event that triggers the workflow
 The event that triggers the workflow
 The business object key
 An RFC connection for SAP EM if you want to start a workflow in a system other than
the one on which SAP EM runs.
 If you use the workflow locally, choose None or Workflow_local.

(C) SAP AG 128


In this case, you must define an entry for the RFC destination with the same
name Workflow_local to link to the same system on which SAP EM runs.
For more information about setting up an RFC connection to the application system,
see the Implementation Guide (IMG) for SAP EM under Event Management General
Settings in SAP Event Management  Define RFC Connection to Application System.
 At least one rule set [Page 112] that uses the rule for the workflow and its activity.
 You create a rule in your rule set by selecting the activity WORKFLOW_START.
 You specify the first activity parameter. The activity parameter is the activity ID
that you defined previously in SAP EM Customizing.
 You can assign a condition to your rule to control how the workflow is triggered.

For example, you specify the internal event code of the event message as
Arrival at Customer.
For more information about integration between SAP Business Workflow and SAP EM, see
the Implementation Guide (IMG) for SAP EM under Event Management  Reactions to Event
Messages  Define SAP Business Workflow Integration.

Example
...

1. You send an event message Proof of Delivery to SAP EM for a shipment and want to
start a predefined workflow in the application system using this event message.
2. SAP EM updates the event handlers belonging to the shipment, which it finds using the
tracking ID [Page 74] and the internal event code set [Page 90].
3. Your new rule is in the event handler’s rule set. This rule triggers the creation of the
event START_ WORKFLOW when the event Proof of Delivery is reported.
4. The event START_ WORKFLOW starts the workflow that triggers an automated
process (settlement process) in the application system (SAP R/3, SAP APO, SAP
CRM).
The event links SAP EM to SAP Business Workflow.

(C) SAP AG 129


Authorizations and Filters
Extensive authorization and filter options are available in SAP Event Management that you
can use to control information queries to SAP Event Management (see User Interfaces [Page
135]).

You can query and display event handler data using the Web interface or function module
/SAPTRX/BAPI_EH_GET_DATA_GEN. In this case this authorization concept also applies for
the display of event handler data, which are already archived. If you query and display event
handler data using the Archive Information System (transaction SARI), only the standard
authorization concept of the Archive Information System applies.

Authorization Profile
You define authorization profiles to allow the following:

 Allow information to be displayed when querying or evaluating event handler data.

 Allow event handlers to be created and changed in SAP Event Management (see
also Authorizations for Changing Data and Sending Event Messages)

Note that the system only checks the first 40 characters of the parameter values.

For an example of how you define a user authorization with which a user can
display event handler data, see SAP Event Management User.

Filter Profile
A filter profile allows you to restrict the event handler data that is displayed in a user-specific
or role-specific way.

Prerequisites
You have the authorization to assign a user to a role and a profile.

(C) SAP AG 130


Activities
The following figure provides an overview of the connection between user, role, authorization
profile, filter profile, and event handler type:

User

Assignment of user to
role
Role

Assignment of authorization
profile to role
Assignment
to EH type Authorization Profile
(Parameters)

Event Handler Type Event Handler Data


Filter Profile
(Event Handler
Assignment
to EN type Components)

Assignment of filter profile


to role

Role

Assignment of user to
role

User
Direct assignment of user to
filter profile

Overview of Authorizations and Filters

Authorization Profiles
 Depending on the authorization profile, SAP Event Management only displays certain
parameters to the user when creating, changing, or evaluating event handler data.
You define in the SAP Event Management authorization profile the control and info
parameters that SAP Event Management makes available to the user for displaying
or processing data.

 You assign the authorization profile to an event handler type.

 You assign the authorization data to a role.

By assigning the authorization profile to a role, you determine the authorization


objects and their executable activities. For example, a shift manager can only see
data for plant 1100.

For more information about users and roles for the SAP NetWeaver Application
Server (AS) ABAP and Java, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com SAP NetWeaver by Key Capability Security
Identity Management User and Role Administration of AS ABAP and User
Management of the Application Server Java.

For more information about roles in SAP Event Management, see Authorizations for
Changing Data and Sending Event Messages and Roles for SAP Event
Management.

 You assign a role to a user (transaction SU01).

(C) SAP AG 131


For more information about defining authorization profiles, see Customizing for SAP Event
Management under Authorizations and Filters Define Authorization Profiles.

Filter Profiles
 In the filter profile, you specify which event handler components, for example, the
expected events for an event handler, SAP Event Management displays to a user.

 You specify tables, fields, or rows that SAP Event Management does not display to
the user.

 You assign the filter profile to an event handler type.

 You assign the filter profile to a user or to a role.

For more information about defining filter profiles, see Customizing for SAP Event
Management under Authorizations and Filters Define Filter Profiles.

(C) SAP AG 132


Authorizations for Changing Data and Sending
Event Messages
Use
You define an authorization concept in SAP Event Management (SAP EM) to specify:
 Which users are allowed to make which changes to data in the event handler list (event
handler overview and event handler detail overview)

Only if you assign the appropriate authorizations to a user are they able to select
the icons used for making changes in the event handler list (event handler
overview and event handler detail overview).
 Which users are allowed to send event messages to SAP EM

Activities
...

1. Create a new user or maintain an existing one.


2. Assign the user to role SAP_EM_ADMIN or create a new role.
Role SAP_EM_ADMIN contains all the authorizations that are necessary to change data
in the event handler list and to send event messages (see also: SAP Event
Management Administrator [Page 238]). [Page 238]

If you create a new role, note that the subobject (for example, IPAR for
changing info parameters) and the activity (for example, 01 for changes) operate
in combination with each other.

For example, you want a user to be allowed to both change and create info
parameters, but only to delete control parameters.
To do this you create two roles: A role in which you allow the user to change and
create info parameters and a role in which you allow the user to delete control
parameters.
For more information about maintaining the user master record, see the SAP Library under
SAP Technology Components  SAP Web Application Server  Security (BC-SEC) 
Users and Roles (BC-SEC-USR).

(C) SAP AG 133


Example
You want a user to be allowed to do the following:
 Activate or deactivate event handlers
 Create and change info parameters
 Delete control parameters
You create two roles.
 Role 1 is allowed to activate or deactivate event handlers and delete control
parameters
Maintain the following in the user master record:
 Authorization object X_EM_EH_CH (in authorization class EM)
 Subobject CPAR for changing control parameters
 Subobject ACT for activating event handlers
 Activity 06 for deleting control parameters and activity 63 for activating the event
handler status
 Role 2 is allowed to create and change info parameters
Maintain the following in the user master record:
 Authorization object X_EM_EH_CH (in authorization class EM)
 Subobject IPAR for changing info parameters
 Activity 01 for creating info parameters and activity 02 for changing info
parameters
You assign the user to roles 1 and 2.

(C) SAP AG 134


User Interface
The main user interface in SAP Event Management is the web interface to select and monitor
the tracked processes. The web interface displays the selected tracked processes and related
details. It enables you to detect or highlight exceptional situations and to interactively react to
those exceptions. It can also be used to manually report expected and unexpected events.
The layout of the web interface is completely configurable through user and role specific
profiles.

The former WCL user interface for SAP Event Management, accessible through menu
entry “Web interface (classic)”, is no longer part of the standard software package for
SAP Event Management. If necessary it can still be used after upgrade for compatibility
reasons. But new features are not available through this technology.

Prerequisites
In Customizing for SAP Event Management under Event Messages, Status Queries, and
Web Interface Web Interface , you have executed the Customizing activities described in
the section Define Web Interface. As a result, SAP Event Management automatically
generates the required settings so that you can use the Web interface.

Features
For a description of the features, see the following:

 Web Interface [Page 136]

(C) SAP AG 135


Web Interface
You can display a Web interface in a Web browser.

Prerequisites
You have assigned at least one user profile and one scenario to the user in Customizing. For
more information, see Customizing for SAP Event Management under Event Management
Event Messages, Status Queries, and Web Interface Web Interface Define Web
Interface Assign User Profiles and Web Interface Transactions to Users .

Features
You can use the Web interface to do the following:

 Query and display information from SAP Event Management about one or more
event handlers, for example, about identification data (ID data)

 Send event messages to SAP Event Management that might contain an attachment,
for example

 Display attachments for an event message

 Visualize the actual position of an event handler and the event history on a
geographical map (provided the event handler and Event Messages contain the geo
coordinates)

 Interactively personalize the presentation of data shown in the screen, by individually


arranging the position of the screen building blocks, and additional personal settings
such as the time zone in timestamp fields

 Display the hierarchies of ID data

 Display links to an internal or an external address, to another SAP system, or to


another event handler

 Display the document flow networks that belong to a certain event handler

Only the Web interface displays the network. You cannot display the network in SAP
Event Management. If you have the appropriate authorization in your user profile, the
authorization concept allows you to display detailed information about the network
and to execute a drilldown.

See also: Displaying a Network [Page 195]

 Display a Settings Popup for users

 Handle a New Time zone

 Re-display the screen using the Refresh button

You can configure the following for setting up the Web interface:

 Web interface transactions

 Fields for user profiles

 User profiles

 The assignment of user profiles and Web interface transactions to users

(C) SAP AG 136


 The assignment of roles to user profiles

 The order of events for all event handlers belonging to a set using an event
consolidation profile

 The assignment of a link to a configured field

For more information about the individual Web interface settings, see
Customizing for SAP Event Management under Event Management Event
Messages, Status Queries, and Web Interface Web Interface Define Web
Interface .

For more information about frequently asked questions, see Frequently Asked
Questions (FAQ) [Page 147].

The following is not supported for the web interface:

 Mobile user interfaces online or a corresponding screen for Personal Digital


Assistants (PDAs)

 Favorites (although there are Saved searches)

 Fast search

 Display of unplanned measurements

 Display of change documents

 Display of Uniform Resource Locators (URLs) of tracking service providers

(C) SAP AG 137


Modes of Access of the Web Interface
You may access the Web interface for SAP Event Management in the following two modes:

 As a normal user using the logon screen or single sign-on (SSO)

 As a direct link user

The following table explains the differences between these two modes of access:

Modes of Access

Scenario
User Logon Activities User Settings
Assignment

System saves the


Depending on
Multiple assignment in the
Logs on using the the user profile,
Normal scenario database; the
logon page with user all Web
user assignments scenarios are
name and password interface
possible available to the
functions
user on each PC

No logon; user
System saves the
chooses link in e-mail Read
assignment in the
Direct and directly sees the authorization Only one
database; the
link event handler data for only; not scenario
scenario is
user the scenario to which possible to send assigned
available to the
he or she is assigned event messages
user on each PC
in Customizing

Note the following:

 Activities means: the actions and functions that are available to the user in the UI.

 Scenario means: the combination of user profile(s) and web transaction(s) assigned
to the user in SAP Event Management.

More Information
 For more information about logging on with SSO, see Logging On to the Web
Interface with SSO [Page 139]

 For more information about setting up a direct link user, see Setting Up A Direct Link
User [Page 140]

 For more information about personalizing the Web interface (Web Dynpro ABAP),
see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com
SAP NetWeaver Library SAP NetWeaver by Key Capability Application
Platform by Key Capability ABAP Technology UI Technology Web UI
Technology Web Dynpro for ABAP Web Dynpro ABAP: Development in Detail
Advanced Concepts Personalization and Configuration .

(C) SAP AG 138


Logging On to the Web Interface with SSO
You can use Single Sign-On (SSO) when logging on to the Web interface.

Features
You have the following options to use SSO when logging on to the Web interface:

 You can log on to several SAP Event Management systems using a Web interface.
You use X.509 client certificate to avoid having to enter your user information
repeatedly.

For example, you have an SAP Event Management for both your development
system and your test system. You can log on to both systems in multiple clients.
The one Web server communicates with both systems using a different URL.

For more information about X.509 client certificates, see SAP Library for SAP
NetWeaver on SAP Help Portal at http://help.sap.com SAP NetWeaver
Library Administrator's Guide Technical Operations Manual for SAP
NetWeaver General Administration Tasks Security and User Administration
Administration for User Authentication and Single Sign-On (SSO)
Administration When Using X.509 Client Certificates .

 You use logon tickets to communicate with multiple SAP systems (for example, SAP
Event Management and SAP NetWeaver Business Intelligence) using the Web
interface. You only log on once to one of the systems.

For more information about logon tickets, see SAP Library for SAP NetWeaver on
SAP Help Portal at http://help.sap.com SAP NetWeaver Library
Administrator's Guide Technical Operations Manual for SAP NetWeaver
General Administration Tasks Security and User Administration
Administration for User Authentication and Single Sign-On (SSO)
Administration When Using Logon Tickets .

(C) SAP AG 139


Setting Up A Direct Link User
You can set up a direct link user to enable direct access to SAP Event Management
information via URL without intermediate logon screen.

Prerequisites
 You have generated a service user and an Internet Communication Framework
service (ICF service). Furthermore, you have assigned the service user that you
defined to the Web interface transaction and to the user profile. For more information,
see Direct Access to Detailed Information [Page 126] in the section Prerequisites for
the Web Interface (Web Dynpro ABAP).

 You are familiar with programming in ABAP.

Procedure
1. Use the function module /SAPTRX/BAPI_EH_GET_DATA_GEN (Flexible Search for
EH Data) to determine the Globally Unique Identifier (GUID) for the event handler.
The table SELECTIONFIELDS must have been filled in accordance with the selected
Web interface transaction. The table eventhandlerheaders provides the required
event handler GUID in the attribute EH_GUID.

2. Create the link for calling the Web interface transaction that you have configured for
the service user. Add the following parameters to the Uniform Resource Locator
(URL) for the Web transaction /saptrx/em_fpm_ehdetail:

o &sap-client=<Client>

o &sap-language=<Language, for example: EN>

o &action=quick

o &EH_GUID=<EH-GUID>

o &UP ID=<User Profile ID>

The following is an example of a link for calling the Web interface transaction:

https://uscia9s.wdf.sap.corp:44376/sap/bc/webdynpro/saptrx/e
m_fpm_ehdetail?sap-
client=001=EN=quick=HfEgfav7AWNX00002a8Jc0=PTA10_ID

3. Use the link to display the required data. To do so, you can use the method
CREATE_EXTERNAL_WINDOW of the Web Dynpro component interface
IF_WD_WINDOW_MANAGER, for example.

(C) SAP AG 140


Parameter Display (Web Interface)
The system displays the info parameters or control parameters for an event handler in the
Web interface for information or search queries.

Prerequisites
 In Customizing, you have defined the parameter display for info parameters and
control parameters, including the number for displaying indexed parameter values.
For more information, see Customizing for SAP Event Management under Event
Management Event Messages, Status Queries, and Web Interface Configure
Fields for User Profiles .

 In Customizing, you have defined that empty fields are to be hidden, as required. For
more information, see Customizing for SAP Event Management under Event
Management Event Messages, Status Queries, and Web Interface Configure
Fields for User Profiles .

 In Customizing, you have assigned the configured fields to a user profile. For more
information, see Customizing for SAP Event Management under Event
Management Event Messages, Status Queries, and Web Interface Define User
Profiles .

Features
SAP Event Management applies a concept of indexed values for displaying info parameters
and control parameters to save multiple values for one parameter. A parameter can have an
unlimited number of values. In SAP Event Management, you can configure the display of
parameters in the Web interface in such a way that the Web interface displays either all the
values for a parameter or only a subset. If no values exist for a parameter, you can hide these
empty fields.

If you have activated the business function EM, Archiving and Web Interface
Improvements (SCM_EM_HIGHVOL), the following applies: If you want to display
archived data, the archive has the restriction that you cannot use more than one attribute
with cardinality greater than one for the search. You cannot include info or control
parameters in the field catalog.

Activities
When you call the event handler list, event handler overview, or the event handler details, the
Web interface displays the number of indexed parameter values that you defined. If a
parameter has additional values, the Web interface also displays a link. When you click the
link, you see all the parameter values in a separate dialog box.

(C) SAP AG 141


Visualization Using Geographical Maps
The system displays either the actual position of a selected set of event handlers or the event
history of a single selected event handler on a geographical map.

Prerequisites
 Only those event handlers and event messages that have correctly assigned
geographical coordinates (latitude and longitude) can be displayed on the
geographical map.

 The Geomap profiles and Geomap maintenance in the Customizing activity


Define User Profiles are maintained.

 Latitude and longitude must be included in the Customizing activity Event Message
Parameter Mapping.

 The appropriate settings must be made in Customizing for SAP Event Management
under Event Management General Settings in SAP Event Management
Geographical Map .

Features
SAP Event Management has a Map panel in the Web interface where a geographical map is
displayed

If none of the event messages have a latitude or longitude assignments, the Map panel is
automatically hidden.

(C) SAP AG 142


Printable Version for Tables on a Web Page
You can print tables on a Web page.

Features
When you use the Print Version pushbutton, SAP Event Management performs the following:

1. SAP Event Management uses a Remote Function Call connection (RFC connection)
to call a portal service.

2. The portal service uses the Adobe document services server (ADS server) to
generate a Portable Document Format document (PDF document).

3. The ADS server uses an RFC connection to send the PDF document to SAP Event
Management.

4. SAP Event Management displays the PDF document.

For a description of how to create a printable version, see SAP Notes 918236 and 894009.

(C) SAP AG 143


Use of the Event Handler Hierarchy
In the Web interface, you can display the hierarchy for an event handler.

Prerequisites
See Creation of Event Handler Hierarchies

Features
When the event handler type used for the tracking scenario is set up to manage the hierarchy
view, the system automatically adds a hierarchy tree panel to the main screen. The tree view
is used to navigate through all the levels of the hierarchy the event handler is currently part of,
and to display the related event handler details. You can also display the hierarchy valid at
the point in time of an event, by marking the corresponding event in the Event Messages
panel and pressing the button “Display Hierarchy for Event”. The hierarchy for the event is
display in a separate window.

(C) SAP AG 144


Drilldown in the Web Interface
You can use the following drill-down types in the Web interface::

 Drill down to a document in another SAP system

 Drill down to a document using static or dynamic browser links

 Drill down to another event handler

You can use a Web link to call a purchase order in another application for example, or you
can use a Uniform Resource Locator (URL) to send parameters to another application. You
can include variable parameters with links to external URLs that are derived from system
parameters, control parameters, info parameters, the application object ID or a tracking ID.

Prerequisites
 You have implemented PI-Basis 2005.1 or higher. This enables SAP Event
Management to display a document from another SAP system or the content of an
internal or external link. For example, you have assigned a link to the transaction for
displaying a purchase order (ME23) to an event handler. In the Web interface, you
choose the link in the event handler details and SAP Event Management displays the
relevant SAP Graphical User Interface screen (SAP GUI screen).

 You have performed the corresponding Customizing in SAP Event Management. For
more information, see Customizing for SAP Event Management under Event
Messages, Status Queries, and Web Interface Web Interface Assign Link to
Configured Field .

Features
When you use the drilldown in the Web interface, the Web interface calls SAP Event
Management. SAP Event Management checks the Customizing for the user profiles.

 If you use a link to another SAP system, SAP Event Management checks the
following:

o The business object type that SAP Event Management is to use

o The business object method that SAP Event Management is to use

o The transaction that SAP Event Management is to use

o Whether the user is defined in the other SAP system

o Whether Single Sign-On (SSO) is allowed for the user in the other SAP
system

If the user is not defined in the SAP application system or if SSO is not
allowed for the user, SAP Event Management displays the standard
logon screen. The user must log on with the same user that he or she
uses in the SAP application system. After the user has logged on, SAP
Event Management displays the associated transaction (for a purchase
order, for example).

 If you use a link to a URL, SAP Event Management checks which data it is to display.
If you define a URL and SAP Event Management transfers parameters when

(C) SAP AG 145


branching to an application, you must ensure that the application being called can
process these parameters.

For security reasons, you need to maintain whitelists for URLs that contain
variables as parameters (known as “dynamic URLs”). Only URLs that are
admitted through the whitelist customing in SAP Event Management can be
reached. But SAP Event Management does not check whether the display of the
URL data is secure and permitted. You are responsible for the data that SAP
Event Management displays using the URL. The URL call might lie outside the
SAP systems and it is therefore not secure. For example, if a file is called that
enters the system via a function without a virus check, this call is not secure.

We recommend that you use the SAP Web Repository to display certain content
via a URL. You can activate a virus check with the SAP Web Repository to check
documents before an upload. For more information, see:

o Customizing for SAP Event Management under SAP NetWeaver


Application Server System Administration Virus Scan Interface

o SAP Library for SAP Event Management on SAP Help Portal at


http://help.sap.com SAP R/3 Enterprise Release 4.70 SAP
NetWeaver Components SAP Internet Transaction Server ITS
Implementation Models WebRFC Programming SAP Web Reporting
.

(C) SAP AG 146


Frequently Asked Questions (FAQ)
You can find information here about using the Web interface that cover the following topics:

 General information, for example, about data security when data is transferred (see
General Information [Page 148])

 Information about navigating to the Web interface (see Navigation to the Web
Interface [Page 149])

 Information about the administration screen (see Administration Screen [Page 150])

 Information about the search panel (see Search Panel [Page 151])

 Information about tables (see Navigation and Sorting of Tables [Page 153])

 Information about the search result panel (see Search Result Panel [Page 154])

 Information about sending event messages (see Sending of Event Messages (Fast
Entry) [Page 155])

 Information about sending event messages for multiple tracked objects or processes
(see Sending of Event Messages for Multiple Tracked Objects or Processes [Page
156])

 Information about sending event messages (see Sending of Event Messages [Page
157])

 Information about settings for the Web interface (Web Dynpro ABAP) (see Settings
[Page 158])

 Information about the details of tracked objects or processes (see Details of Tracked
Objects and Processes [Page 159])

(C) SAP AG 147


General Information
Questions and Answers in the General Information Area
Question Answer

Yes, if the Web server uses the SSL (Secure Sockets Layer). This
protects all data, such as customer name and address or supplier
name and address, so that unauthorized persons are not able to
decode this information when it is transferred in the Internet.
Furthermore, communication between the Web server and SAP
Event Management can be secured, if the administrator installs
Will my data be Secure Network Communication (SNC).
transferred safely?
For more information about security issues in Web Dynpro ABAP,
see SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com SAP NetWeaver Library SAP NetWeaver
by Key Capability Application Platform by Key Capability ABAP
Technology UI Technology Web UI Technology Web Dynpro
ABAP Security Issues in Web Dynpro for ABAP .

You can search for one or more tracked objects or processes, or sets
of tracked objects or processes, and you can display the data in
What can I do with several levels of detail. You can observe the processing and the
the SAP Event status of these tracked objects and processes and you can send
Management Web event messages to a single tracked object or process or to a group of
application? tracked objects or processes. You can use the Fast Entry function to
send event messages directly to SAP Event Management without
first having to search for a tracked object or process.

This depends on the configuration of the field in Customizing for SAP


Are the input fields
Event Management. Here, the system administrator can configure
case-sensitive?
whether the fields are case-sensitive or not.

Why can I not see If you want to display the most up-to-date version of a screen that
the latest information has already been visited, you have to call the Uniform Resource
on my screen? Locator (URL) again or you have to use a refresh pushbutton.

Can I print the


tracked objects and
Yes. Use the Web browser print function to print the entire screen.
processes displayed
on the screen?

(C) SAP AG 148


Navigation to the Web Interface
Features
Information About How You Can Navigate to the Web Interface
Question Answer

If you choose SAP Event Management Web Interface


Search on the SAP Easy Access screen, the system
How can I search for an launches the Event Management main screen with an open
object or process? search panel. There you select the tracking scenario you want
to use from the drop-down box on the top of the panel and
then you enter your search criteria.

If you choose SAP Event Management Web Interface


How can I send an event Fast Entry on the SAP Easy Access screen, the system
message without first displays the initial screen where you can select a service. You
having to search for the can call the service directly and can send an event message
corresponding tracked without first having to search for the corresponding tracked
object or process? object or process. You can also use the standard User
Interface to directly send event messages.

(C) SAP AG 149


Administration Screen
Features
Information About the Administration Screen
Question Answer

If you want to change the logo in the header of the screens, on the
SAP Easy Access screen, choose Tools ABAP Workbench
Overview Object Navigator . Choose the MIME Repository
pushbutton. In the dialog structure, choose SAP BC WebDynpro
How can I SAP Public SCEM . Exchange the customer_logo.GIF file for
change the your file to change the logo in the header of the screens. Exchange
logo and the the customer_brand_image.jpg file for your file to change the picture in
picture in the the header of the screens.
header of the
screen?

Make sure that the name and the format of the files remain the
same..

By default, all elements in the Web interface that are available in the
View Designer are based on a certain stylesheet provided by SAP.
This is to ensure a consistent look across all applications. You can,
How can I however, use a different stylesheet. For more information, see SAP
change the Library for SAP NetWeaver on SAP Help Portal at
layout of the http://help.sap.com SAP NetWeaver Library SAP NetWeaver
screens? Developer's Guide Fundamentals Using ABAP Core
Development Task UI Technology Web Dynpro for ABAP Web
Dynpro: Development in Detail Advanced Concepts Stylesheets in
Web Dynpro ABAP .

(C) SAP AG 150


Search Panel
Features
Information About the Search Panel
Question Answer

Different tracking scenarios typically require specific search


Why does the search
criteria. A scenario to track purchase orders, for instance, may
panel have different
require other search options than tracking a freight order.
search criteria? Why do
Similarly, for example, the screen that the employee sees
they change when I
contains different fields from those on the manager’s screen.
select a different tracking
The administrator can change the assignment of tracking
scenario?
processes to your user ID, or change the search criteria.

Can I select a tracking Yes. You can select a scenario to which you are assigned and
scenario on this panel? then enter criteria to search for tracked objects and processes.

The system saves your search criteria in the database and adds
the new saved search name to the Saved Searches dropdown
list box. If the search screen contains any date fields, the system
first displays the Save Search Criteria window in which you can
define dynamic date calculation rules. The system copies the
operator for a dynamic date calculation from the selection
screen. The system does not support ranges that include or
exclude dates in a dynamic date calculation. The only exception
to this is where you can use Current Date +/- NNN Days as a
dynamic date calculation. When you choose the OK button in the
Save Search Criteria window, the system then saves your
search criteria and adds the new saved search name to the
Saved Searches dropdown list box. The dropdown list box
What happens if I select displays all saved searches depending on the tracking scenario
Save Search As? you have chosen.

If you want to change the search criteria of an existing saved


search, you can do the following:

 Choose the relevant saved search in the Saved


Searches dropdown list box

 Change the criteria as appropriate

 Save the search criteria under the same name

If you had already defined dynamic date calculation rules for


date fields, you must define and save the rules again.

Why are there default


Depending on your requirements, the administrator who creates
values for some input
your user profile can set default values for input fields.
fields?

In which search fields


All fields with a red asterisk are required input fields.
must I enter values?

Which date and time The date and time format that you use depends on the language
format should I use? that you have chosen. Choose the calendar icon to the right of

(C) SAP AG 151


Question Answer
the input field.

What happens when I An AND relation exists between the fields. This means that the
enter values in several system takes into account all tracked objects and processes that
fields? match all the entered values in your search.

In principle, yes. For example, if you are looking for tracked


objects or processes with similar IDs, you can enter an asterisk
after the first few characters or numbers. If wildcards are not
permitted for a certain field, the system issues a corresponding
Can I search using message.
wildcards?
If you use search helps, the system does not pass values from
the entry field or the selection option to the search help. To limit
the list of returned values, you must make an entry with a
wildcard in the value help popup window.

Does my user profile


Yes. The administrator can define fields as read-only in your
determine which fields
user profile. These fields have a different color.
are read-only?

In this case, the search for tracked objects and processes is not
What happens if I select
restricted in any way. If you use this function and your selection
the Display More Than
criteria are too extensive, the system has to retrieve a large
200 Hits checkbox?
amount of data. This can lead to performance problems.

(C) SAP AG 152


Navigation and Sorting of Tables
Features
Information About the Navigation and Sorting of Tables
Question Answer

Yes. When you choose Settings, you can use the standard Web interface sort
function on the Sort tab page.
Can I sort For more information, see SAP Library for for SAP NetWeaver on SAP Help
the table? Portal at http://help.sap.com Getting Started - Using SAP Software
Working with Tools and Features Working with Lists SAP List Viewer for
Web Dynpro .

(C) SAP AG 153


Search Result Panel
Features
Information About the Search Result Panel
Question Answer

What can I see on this You can see the tracked objects or processes or sets of these
panel? tracked objects or processes that match your selection criteria.

When you select a tracked object or process from the list, the
Which activities can I system displays the corresponding actions, for example, the
perform on this pushbuttons Print Version, Export, and Send Event Messages. If
panel? you have the authorization, you can send event messages for one
or multiple tracked objects or processes.

How are the different


panels in the main When you mark a line the Search Result panel all related panels on
screen updated the screen are updated automatically.
relative to each other?

Yes, if the administrator has assigned an event message profile to


Can I send event your user profile, you can send event messages. If you want to
messages from the select a tracked object or process, mark the relevant row. Choose
Search Result panel? the Send Event Messages pushbutton and choose an action from
the action menu, for example Report Delay.

How can I get details


for one of the tracked Just mark the line showing the tracked object in the Search Result
objects or processes panel. The Details panel is updated automatically.
in the table?

If the administrator has defined the following in Customizing for SAP


Event Management, the system displays corresponding links in the
table fields:
Why does the system
sometimes show links  Links to other URL addresses
in the table fields?
 The representation of the document flow

 The displaying of indexed fields

(C) SAP AG 154


Sending of Event Messages (Fast Entry)
Features
Information About Sending Event Messages
Question Answer

You can send an event message for a tracked object or process without
first having to search for the object or process. You can also send an
Which activities
event message for a tracked object or process that does not currently
can I perform on
exist. Depending on the Customizing settings for SAP Event
this screen?
Management, you can trigger SAP Event Management to create the
tracked object or process.

Why are there


default values for Depending on your requirements, the administrator who creates your
some input user profile can set default values for input fields.
fields?

In which fields
must I enter All fields with a red asterisk are required input fields.
values?

Which date and The date and time format that you use depends on the language that
time format you have chosen. Choose the calendar icon to the right of the input
should I use? field.

Does my user
profile determine Yes. The administrator can define fields as read-only in your user
which fields are profile. These fields have a different color.
read-only?

(C) SAP AG 155


Sending of Event Messages for Multiple Tracked
Objects or Processes
Features
Information About the Sending of Event Messages for Multiple Tracked
Objects or Processes
Question Answer

You can send an event message for multiple tracked objects or processes.
The system updates the data for these event handlers in accordance with
the data in the event message. As a prerequisite, the scenario must permit
Which
the sending of event messages for multiple tracked objects or processes.
activities can I
perform? Select multiple tracked objects or processes and then choose the Send
Event Messages pushbutton. Select an event message, specify the data,
and then choose the Send pushbutton.

(C) SAP AG 156


Sending of Event Messages
Features
Information About Confirming All Expected Event Messages
Question Answer

If you choose the Report All Expected Events pushbutton on the Event
How can I
Messages panel, a dialog box appears containing all the expected
confirm event
events that have not yet been confirmed or that can be reprocessed. To
messages?
confirm these events, choose the Send pushbutton.

Information About Confirming Unexpected Events


Question Answer

Mark the checkbox for the unexpected event to be sent in the Event
Which activities Messages panel and press Apply. A dialog box appears containing data
can I perform? and input fields for the action. Enter data, as required, and choose the
Send pushbutton.

Information About Sending Event Messages


Question Answer

Why are there default


Depending on your requirements, the administrator who
values for some input
creates your user profile can set default values for input fields.
fields?

In which fields must I enter


All fields with a red asterisk are required input fields.
values?

The date and time format that you use depends on the
Which date and time format
language that you have chosen. Choose the calendar icon to
should I use?
the right of the input field.

Does my user profile


Yes. The administrator can define fields as read-only in your
determine which fields are
user profile. These fields have a different color.
read-only?

(C) SAP AG 157


Settings
Features
Information About Settings in the Web Interface
Question Answer

Yes, you can use any of the following:

 The button Personalize - a standard function for the Web


interface

 The button Settings on the top of the Event Management


Screen - a standard function for the Web interface

 The button Open Settings Dialog on top of each panel in the


Can I personalize screen allows you to reach Management specific settings.
the Web There you can define the time zone, to be used for displaying
interface? timestamp, define whether the search screen collapses, or not,
when result are found upon search, and the number of
references shown in fields that have multiple values.

For more information, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com SAP NetWeaver Library SAP
NetWeaver Developer's Guide Fundamentals Using ABAP Core
Development Tasks UI Technology Web Dynpro for ABAP Web
Dynpro ABAP: Development in Detail Advanced Concepts
Personalization and Configuration Personalization .

When do I have
to set the If you use a screen reader and set this indicator on the logon screen,
Accessibility you can use the application more easily.
indicator?

Can I change the Yes. Choose Settings and the Display tab page. The values that you
way in which specify here define the number of rows displayed in the table, for
tables are example. You can make these settings for the list and detail screens, for
displayed? example.

(C) SAP AG 158


Details of Tracked Objects and Processes
Features
Information About the Panels that show Details of Tracked Objects and
Processes
Question Answer

What can I see on You can see detailed information about a tracked object or process.
the Details panel? The level of detail shown depends on your user profile.

You see the following::

 a list of all expected and unexpected events including the


actual date and time of the event
Which can I see on
 the planned date and time (where applicable)
the Event
Messages panel?
 the status of the event

Depending on your user profile, you can also launch activities such as
reporting expected or unexpected events. The other buttons are
standard functions for the Web interface.

The icons show the status of an expected event or indicate an


unexpected event message. The icons are explained in the relevant
What do the icons tooltips. SAP Event Management uses the following five event
in the Event statuses: Reported Expected Event, Overdue Expected Event,
Messages panel Unreported Expected Event with Expected Date/Time, Unreported
indicate? Expected Event That Is Time-Independent, and Unexpected Event.
The icons displayed depend on the settings made in SAP Event
Management.

If your tracking scenario contains sets of tracked objects or processes


What does (Event handler sets) and you have the appropriate authorization, you
Technical View can see all the tracked objects or processes that are part of the set on
mean? the Technical View tab page. In most cases, this view is of interest to
the power user only.

This link displays all the multiple values assigned to a single column or
What is the ...More
field in a table in a new window. It is used to display all values if not all
link used for?
values fit into the corresponding field.

What can I use the


This panel shows a graphical display of the business object network
Document Flow
that is related to the tracked object or process.
panel for?

If the administrator has defined the following in Customizing for SAP


Event Management, the system displays corresponding links on the
Why does the detail screen:
system sometimes
 Links to other URL addresses
display links on the
detail screen?
 The displaying of indexed fields

 The displaying of measurements

(C) SAP AG 159


Monitoring and Evaluating Processes
Various options are available for monitoring and evaluating processes in SAP Event
Management.

Prerequisites
You have defined event handler types with their event handler extension tables (see Event
Handler Extension Table).

Features
The following options are available to you for monitoring and evaluating processes:

 You can execute a range of reports for internal purposes. These provide you, for
example, with a list of all technical error messages or all event handlers with a
specific status (see Reports for Internal Monitoring and Evaluation of Processes).

 By connecting to the Computing Center Management System, you can use the
monitor specific to SAP Event Management (see Connection to the Computing
Center Management System). For example, this monitor shows you a list of all locked
event handlers in SAP Event Management for a specific client.

 Externally, you can make search queries to SAP Event Management using a Web
interface (classic), for example (see Web Interface (Classic) [External]).

An extensive range of layout and authorization options are available to you for these
search queries.

 You can use the connection to SAP NetWeaver Business Intelligence to make
analytical queries and to run evaluations (see Connection to SAP NetWeaver
Business Intelligence).

 You can use the connection to the document flow to display the hierarchical structure
in the Web interface.

(C) SAP AG 160


Use of the Event Handler List
The event handler list provides the system administrator with comprehensive information
about an event handler (EH).

For example, you can display all data for all event handlers with a particular event handler
type.

Features
You can display information about an event handler and can perform a restricted search for
an event handler type, for example. You can also use the event handler list to check whether
SAP Event Management has created or updated data correctly. For example, you can check
whether SAP Event Management has created an event handler in accordance with your
instructions, or you can check whether an event message has been sent to SAP Event
Management.

The following is not supported for the event handler list:

 Display of event handler hierarchy

 Display of event message extension

 Display of event message document reference

 Display of attachments

 ID mapping in configured fields

(C) SAP AG 161


Defining Search Criteria
Prerequisites
If you want to extend the search for information using fields from the event handler extension
table, you must first define these fields in the extension table. Only then can you use them to
define additional search criteria.

For more information about extending event handler header data, see Customizing for SAP
Event Management under Event Management Event Handlers and Event Handler Data
Event Handlers Define Extensions to Event Handler Header .

Procedure
Selection Screen: Static Part
1. On the SAP Easy Access screen, choose Event Management Monitoring and
Lists Event Handler List .

2. Enter your search criteria.

You can specify the following search criteria:

o Event handler identification

 Application system

 Application object type

 Application object

 Tracking ID code set

 Tracking ID

o Processing data

You can specify the business process type, event handler type, and the
status attribute profile as search criteria, for example.

o Management data

You can specify the person who created the event handler or the date when
the event handler was created as search criteria, for example.

You can specify additional search criteria from the event handler extension table (see
section Selection Screen: Dynamic Part).

3. Choose Execute.

4. The system displays an overview list containing all event handlers that match your
search criteria. This list is dependent on your authorization and filter profiles.

5. Select an event handler and display the detailed information for this event handler in
the event handler details.

(C) SAP AG 162


Selection Screen: Dynamic Part
1. Enter an event handler type and choose Additional Data to define the dynamic part of
your search criteria.

SAP Event Management displays the corresponding event handler extension table.

2. Select your own selection criteria and add them to the first selection screen as the
dynamic part.

3. Save your selection.

(C) SAP AG 163


Use of the Event Handler Overview
In SAP Event Management, when you call the event handler overview from the event handler
list, SAP Event Management shows the following information for an event handler:

 The consolidated events (see Event Consolidation Profile)

 The expected events

 The reported event messages (see Event Reporting)

 The error messages

 The current status data of event handlers and the status history

If you have the appropriate authorization, you can change the date and time of an expected
event. This also applies to your additional time categories.

Activities
In the event handler overview, choose Change Expected Event Date and Time to change the
date and/or time of an expected event. SAP Event Management displays a dialog box where
you can enter your changes.

(C) SAP AG 164


Use of Event Handler Details
You can have the system display the detailed information about an event handler. To do so,
from the event handler overview, call the event handler details and display the following
detailed information:

 The header data, all parameters (system, control, and info parameters), the tracking
IDs, and the query IDs

 The history of the expected events, the measurement data, the status details, and
additional detailed information, for example, the change document data

For example, you can use the history to establish if an expected event has been
reported several times. You can use relevant key figures in SAP NetWeaver
Business Intelligence to evaluate this information.

Event handler details can change as a result of the following:

 When SAP Event Management (SAP EM) updates an event handler from the
application system

For example, the arrival at the customer occurs at 13:00 instead of 12:00. Here SAP
EM updates the following data, for example:

o Tracking IDs, query IDs, and authorization data

o Change documents belonging to the event handler

 When you send an event message

o SAP EM performs tasks using rules and activities.

o SAP EM updates the information that is contained in the event message, for
example, information about an external event code set, the sender name,
and the location code ID.

o SAP EM updates the status details, error messages, and measurement data,
as required.

Prerequisites
To use the functions for changing event handlers and their data, for example, Lock and
Unlock in the event handler details, you have maintained the authorization data and
generated profiles for your user role. Here you have used the authorization object
X_EM_EH_CH in the EM class.

Features
If you have the appropriate authorizations, you can change the following event handler data
manually:

 Set the event handler header data to status changeable/not changeable.

 Activate or deactivate event handlers

 Activate or deactivate the application log and specify the degree of detail for logging

 Reprocess event messages for the selected event handler with its actual data

(C) SAP AG 165


If you choose Reprocess Event Messages, you manually trigger a reprocessing of
event messages and SAP EM processes all event messages again. You can choose
between the following processing methods:

o If you choose Simulate, you can use a simulation mode with a graphical
interface and the system simulates the reprocessing, for example, activities in
the rule set.

For example, if an error occurs, you can check the processing logic of an
event handler, and trace the reason why the event messages have not
triggered the corresponding reactions, in other words, activities in the rule
set, in a step-by-step way.

o If you choose Reprocessing, the system reprocesses the event messages in


the background, in other words, the system actually processes the event
messages again.

For example, the system is supposed to send an e-mail on the basis of an


event message and the action that resulted from it. At this time the mail
server is not available. The system does not send the e-mail. You use
Reprocess Event Messages Reprocess to trigger processing manually
and the system sends the e-mail again.

 Add, change, or delete data

The following table provides an overview of which data you can add, change, or
delete:

Data Add Change Delete

Info parameters x x x

Control parameters x x x

System parameters - x x

Query IDs x x x

Tracking IDs x x x

Additional tracking IDs x x x

Event handler statuses - x -

If you want to improve performance, you can hide the historical data for expected events,
measurement data, or status attributes. Set the relevant indicator, for example, Disable Status
Attribute Historical Data, in Customizing for SAP EM under Event Handlers and Event
Handler Data Event Handlers Define Event Handler Types .

Activities
1. On the SAP Easy Access screen, choose Event Management Monitoring and
Lists Event Handler List .

2. Display the event handler list and select the event handler whose data you want to
change.

The system displays the event handler overview.

3. If you want to change data in the event handler details, proceed as follows:

(C) SAP AG 166


1. Choose Event Handler Detail Overview.

The system displays the event handler detail screen (event handler details).

2. Choose the change mode on the respective tab page to manually change
data, for example, system parameters.

If you want to change the status of an event handler, choose the Change
EH Status setting instead of the change mode on the Status Details tab
page.

4. Save your changes.

(C) SAP AG 167


Settings for EH Overview Screen and EH Details
Screen
You can specify which tab pages appear on the event handler overview screen (EH overview
screen) and which on the event handler details screen (EH details screen), and the order in
which the system displays them.

You define the EH overview screen in such a way that here SAP Event Management
displays information about consolidated events, expected events, and event messages
only.

You can make the following settings for the EH overview screen and the EH details screen by
using EH Display Configuration or Set Up EH Display Configuration:

 The tab pages that are displayed

 The order in which the tab pages are displayed

 The tab page that the system displays first when you jump from the event handler list
or the EH overview screen

 The sequence of all tab pages in a predefined sequence by specifying that the
system is to use the default settings

(C) SAP AG 168


Application Log
An application log is available for both the application system and SAP Event Management.

The application log documents messages, exceptions, and errors on both the application side
and the SAP Event Management side. This provides information about communication
operations and problems that occurred while event handlers were being created, event
messages were being processed, or information was being queried.

You can analyze the logs or the corresponding messages according to different thematic
areas and gain more detailed information about the messages.

The application log in the application system provides you with an overview of all the activities
relevant to an application object as well as the appropriate event messages. You can reduce
the memory space for the application log by deactivating it per business object.

The SAP Event Management application log provides you with an overview of all the activities
for an event handler and for its corresponding event messages that have occurred during
event handler processing.

If you have the appropriate authorizations, you can specify the following when creating an
event handler (transaction /SAPTRX/TSC0TT):

 The objects that are logged:

o Event handler creation

o Event message processing

o Updating data from an external source

 The level of detail the system is to use when logging (from only high-level processes
to logging the details of each process)

You can call the application log from both the event handler overview and the event handler
details.

For more information about the application log, see SAP Library on SAP Help Portal at
http://help.sap.com SAP NetWeaver SAP NetWeaver Library SAP NetWeaver by
Key Capability Solution Life Cycle Management by Key Capability Application Log (BC-
SRV-BAL) .

Activities
 Choose transaction /SAPTRX/ASAPLOG for the application log in the SAP system.

 For the SAP Event Management application log, on the SAP Easy Access screen,
choose Event Management Administration Logging Application Log: Display
Logs .

 If you want to deactivate the application log in the application system, in Customizing
for SAP Basis Plug-In, choose Integration with Other SAP Components Interface
to Event Management Define Application Interface Define Used Business
Process Types, Application Object Types, and Event Types .

 When SAP Event Management processes event messages, it saves entries in the
application log. If you want to deactivate logging for these entries in SAP Event
Management, set the Disable Logging checkbox in Customizing for SAP Event
Management under Event Messages, Status Queries, and Web Interface Define
Criteria for Event Message Processing .

(C) SAP AG 169


Reports for Internal Monitoring and Evaluation of
Processes
Use
SAP Event Management (SAP EM) offers you several report options with which to make
timely, internal queries on business processes and processing, and to forward information to
all partners in the supply chain.
You can use these reports to monitor the smooth flow of your business processes (for
example, is my carrier reliable?) and processing in SAP EM (for example, were all my IDoc
formats processed correctly?).

Integration
You can use authorization and filter profiles to restrict the information that is displayed for
queries to SAP EM (see Authorizations and Filters [External]).
Filter profiles restrict the information that is displayed for BAPI calls to SAP EM.

For example, you can use an authorization profile to specify the information that
is displayed for event handlers in the list of event handlers with a specific status
attribute.
You can use a filter profile to specify the detailed information that is displayed for
an event handler in this list.

Prerequisites
You have defined event handler types.
When searching for information, you can use the fields from the event handler extension table
that you have already specified as additional search criteria.
For more information, see the Implementation Guide (IMG) for Event Management under
Event Handlers and Event Handler Data  Event Handlers  Define Extensions to Event
Handler Header.

To make your search more efficient, specify an event handler type [Page 45] in
your search. The system only displays the event handler extension table that
belongs to this event handler type.

Features
SAP EM provides several query options that you call using selection screens in SAP EM. You
can use them to make various search queries to SAP EM about event handler activities and
to gain information on your work environment (the application systems that are working with
SAP EM).
The selection screen consists of a fixed part and a dynamic part. In the dynamic part, you
specify your own selection criteria that come from your event handler extension table, and
which you add to the fixed part.
You can combine search criteria to obtain a wide range of search options.
SAP EM provides the following query reports:
 Event handler list [External]
 List of event handlers with a specific status attribute [Page 172]

(C) SAP AG 170


 Last reported event list [Page 173]
 Event handler set browser [Page 175]
 Event message processing error list [Page 176]
 Event message processing status list [Page 178]
 Expected event overdue list [Page 180]

(C) SAP AG 171


List of Event Handlers with a Specific Status
Attribute
Use
The list of event handlers with a specific status attribute helps you to make decisions in critical
situations.

To decide which measures you must take, have the system list all event
handlers with a delay.

Integration
For information about integration, see Reports for Internal Monitoring and Evaluation of
Processes [Page 170].

Prerequisites
For information about prerequisites, see Defining Search Criteria [External].

Features
You can specify the following search criteria:
 The status attribute name (required) and the status attribute value
 Event handler identification
 Application system
 Application object type
 Application object [Page 18]
 Tracking ID code set
 Tracking ID [Page 74]
 Processing data
For example:
 Business process type [Page 21]
 Event handler type
 Status attribute profile
 Management data
For example:
 Who created the event handler
 When SAP EM created the event handler
You can specify additional search criteria from the event handler header extension table.
The result of your search is a list of all event handlers with the selected status (depending on
authorization and filter profiles).

Activities
Display the list of event handlers with a specific status attribute using the transaction
/SAPTRX/EH_LIST_STAT.

(C) SAP AG 172


Last Reported Event List
Use
The last reported event list provides you with all event handlers with the last event that was
sent to SAP Event Management (SAP EM) (for example, list of event handlers with Delay as
the last reported event).
You can use the external event code [Page 90] (for example, Delayed) to search for these
event handlers in SAP EM.
You can find out at any time who sent the event message to SAP EM.

Integration
For information about integration, see Reports for Internal Monitoring and Evaluation of
Processes [Page 170].

Prerequisites
For information about prerequisites, see Defining Search Criteria [External].

Features
You can specify the following search criteria:
 Event handler identification
 Application system
 Application object type
 Application object [Page 18]
 Tracking ID code set
 Tracking ID [Page 74]
 Processing data
For example:
 Business process type [Page 21]
 Event handler type
 Status attribute profile
 Management data
For example:
 Who created the event handler
 When the event handler was created
 Identification of the event
 Event code
 Event date
 Event time
You can specify additional search criteria from the event handler header extension table.
The result of your search is a list of all last reported events that correspond to your search
criteria (depending on authorization and filter profiles).

(C) SAP AG 173


Activities
Display the last reported event list using the transaction /SAPTRX/EH_LAST_EVT.

(C) SAP AG 174


Event Handler Set Browser
Use
The event handler set browser provides you with information about all event handlers that are
grouped together using an event handler set ID. In this way, you can display all event
handlers that belong to a process.

Integration
For information about integration, see Reports for Internal Monitoring and Evaluation of
Processes [Page 170].

Prerequisites
 You have defined event handler types and at least one event handler set.
 Event handlers and event handler sets exist in SAP Event Management (SAP EM).

Features
You call your query using a selection screen from SAP EM. You can use the selection screen
to make various queries about event handler activities to SAP EM.
You can specify the following search criteria:
 Event handler identification
 Application system
 Application object type [Page 23]
 Application object [Page 18]
 Tracking ID code set
 Tracking ID [Page 74]
 The relationship
For example:
 Event handler set profile ID
 Event handler set relation type [External]
 Consolidation profile ID [Page 50]
 The status (name and/or value) for an event handler set
The result of your search is a list of matching event handlers (depending on authorization and
filter profiles) that SAP EM groups according to the corresponding event handler sets.

Activities
On the SAP Easy Access screen, choose Event Management  Monitoring and Lists 
Event Handler Set Browser.

(C) SAP AG 175


Event Message Processing Error List
Use
You use this list to display all error messages that occurred while a process that is relevant to
supply chain event management (SCEM-relevant) was being processed.

Integration
For information about integration, see Reports for Internal Monitoring and Evaluation of
Processes [Page 170].

Prerequisites
For information about prerequisites, see Defining Search Criteria [External].

Features
You can specify the following search criteria:
 Event message identification
For example:
 Message type
 Message number
 Message date
 Event handler identification
 Application system
 Application object type [Page 23]
 Application object [Page 18]
 Tracking ID code set
 Tracking ID [Page 74]
 Processing data
For example:
 Business process type [Page 21]
 Event handler type
 Status attribute profile
 Management data
For example:
 Date and time when the system created the event handler
 Who created the event handler
You can specify additional search criteria from the event handler header extension table.
The result of your search is a list of all event messages that correspond to your search criteria
(depending on authorization and filter profiles).

Activities
Display the event message processing error list using the transaction
/SAPTRX/ER_MS_LIST.

(C) SAP AG 176


(C) SAP AG 177
Event Message Processing Status List
Use
You can use this report to query event messages that have been sent to SAP Event
Management (SAP EM).

Integration
For information about integration, see Reports for Internal Monitoring and Evaluation of
Processes [Page 170].

Prerequisites
To make the search more efficient, specify a maximum number for your entries. The number
of lines that you specify here is the maximum number of lines up to which the system reads
the information. This value can reduce the system’s response time considerably. If the results
list does not contain your object but the list already contains the total number of entries
specified, increase this value.

Features
You can specify the following search criteria:
 Submission date and time
 Event message submission date
 Event message submission time
 Sender
 Sender code set
 Sender code ID
 Sender name
 Event message
 Event message source type
 Sender event message number
 Message status
 Event ID
 External event code set
 External event code ID
 Event date
 Event time
 Identification
 Tracking ID code set
 Tracking IDs
 Event reason
 Event reason code set
 Event reason code ID
 Provider
 Tracking ID provider code set

(C) SAP AG 178


 Tracking ID provider code ID
 Tracking ID provider name
 Event reporting
 Reporting partner code set
 Reporting partner code ID
 Reporting partner name
The result of your search is a list of all event messages that correspond to your search criteria
(depending on authorization and filter profiles).

Activities
On the SAP Easy Access screen, choose Event Management  Monitoring and Lists 
Event Message Processing Status List.

(C) SAP AG 179


Expected Event Overdue List
Use
This report displays a list of all event handlers that have overdue expected events. You can
use this report to query expected events that have not been reported on time.

Features
You call this report to query overdue expected events.
You call your query using a selection screen from SAP Event Management (SAP EM).
You can specify the following search criteria:
 Identification of the expected event
For example:
 Internal event code [Page 90]
 Event code group
 Expected message date
 Event handler identification
 Tracking ID code set
 Tracking ID [Page 74]
 Application system
 Application object type [Page 23]
 Application object [Page 18]
 Business process type [Page 21]
 Event handler type [Page 45]
The result of your search is a list of all event handlers that correspond to your search criteria
(depending on authorization and filter profiles).

Activities
On the SAP Easy Access screen, choose Event Management  Monitoring and Lists 
Expected Event Overdue List.

(C) SAP AG 180


Connection to the Computing Center Management
System
Use
This function connects SAP Event Management to the Computing Center Management
System (CCMS). It allows you to use the SAP Event Management monitor in the CCMS.
The SAP Event Management monitor is a collection of functions that, for example, displays all
the SAP Event Management messages in an overview screen.

We recommend that you only connect SAP Event Management to the CCMS if
you have appropriate knowledge of the CCMS.

Prerequisites
 You have executed the reports /SAPTRX/SLG1_LINK and
/SAPTRX/SCHEDULE_EM_JOBS_NODE once before calling the SAP Event
Management monitor. This means that the functions for evaluating the application log
and scheduling supply chain event management-relevant (SCEM-relevant) background
jobs appear in the selection of functions for the SAP Event Management monitor.

If you restart the system, you need to execute these two reports again.
 For the monitoring functions in the CCMS that are specific to SAP Event Management,
you have scheduled the relevant background job for each client for which you want to
use these functions in the CCMS. The system displays this background job in the
dialog structure of the SAP Event Management monitor.
Background jobs are:
 /SAPTRX/COLLECT_LOCKED_EH
Number of locked event handlers in the desired client
 /SAPTRX/COLLECT_LOCKED_EHSETS
Number of locked event handler sets in the desired client
 /SAPTRX/COLLECT_UNPROC_EVMSG
Number of unprocessed event messages in the desired client

If you restart the system, schedule these background jobs again.

Features
The following functions are available to you in the SAP Event Management monitor of the
CCMS:
 Navigating to the application log
This function is client-specific and allows you to see all messages (for example, event
handler created) on the SAP Event Management side from the application log, and to
quickly gain an overview of possible problems in SAP Event Management.
Specify SAPTRX as the object for SAP Event Management.
For more information, see SAP Library on SAP Help Portal at
http://help.sap.com  SAP Technology Components  SAP Web

(C) SAP AG 181


Application Server  Basis Services/Communication Interfaces (BC-SRV) 
Application Log (BC-SRV-BAL)  Application Log – End User Guidelines (BC-SRV-
BAL)  Evaluate Logs.
 Scheduling SCEM-relevant background jobs
The scheduling of the functions is client-specific. You can schedule them without
knowing the report names. The overview screen shows you which background jobs you
have scheduled for which periods of time.
 Report for the processor of locked event handlers [Page 235]
 Report for the processor of locked event handler sets [Page 235]
 Report for the expected event monitor [Page 81]
 Report for scheduling Resend Application Object Data for Event Handlers [Page
234]
 Report for deleting the document flow network [Page 197]
 Selecting lock entries for locked event handlers in SAP Event Management
This function is client-specific and you specify the threshold value that corresponds to
your business process. The system gives a warning from this value onwards (for
example, from 1000 locked event handlers upwards).
 Selecting lock entries for locked event handler sets in SAP Event Management
This function is client-specific and you specify the threshold value. The system gives a
warning from this value onwards (for example, from 1000 locked event handler sets
upwards).
 Selecting unprocessed event messages in SAP Event Management
This function is client-specific and you specify the threshold value. The system gives a
warning from this value onwards (for example, from 1000 unprocessed event
messages upwards).

(C) SAP AG 182


Connection to SAP NetWeaver Business
Intelligence
Purpose
You connect SAP Event Management (SAP EM) to SAP NetWeaver Business Intelligence
(SAP NetWeaver BI) to transfer your supply chain event management-relevant data to SAP
NetWeaver BI. In this way, you can evaluate this data in SAP NetWeaver BI analytically.

For example, you can create key figures on:


 The punctuality of your supplier
 Adherence to planned shipment and delivery times
 Customs processing
You use the following as data sources:
 The event handlers and their related information can be found in the following objects:
 Info parameters
 Control parameters
 Event handler header
 Event handler extension structure
 The expected events
 The stored process flow for the expected events
 If required, unexpected events that have been reported

(C) SAP AG 183


Integration
The following figure provides an overview of integrating SAP EM with SAP NetWeaver BI:

You have made the general settings for extracting data in Customizing for SAP EM.
Examples of these settings include the update mode and configuring if and when the SAP
NetWeaver BI upload is automatic.
You want to transfer data belonging to an event handler to SAP NetWeaver BI.
SAP EM determines the event handler type of this event handler. The event handler type
determines the SAP NetWeaver BI profile. You use this profile to define the extraction level,
for example, the event handler header level and event level as well as mapping event handler
and event information into the extraction structures of the related extraction level. After the
data has been transferred, you can determine and query key figures in SAP NetWeaver BI.

(C) SAP AG 184


Prerequisites
 You have configured SAP EM for the initial and the delta upload:
 You have defined an event that uses the activity to trigger the SAP NetWeaver
BI upload in SAP EM.
 You have specified that the event should be posted automatically for the delta
upload. This ensures that the SAP NetWeaver BI upload is updated
automatically.
 You have executed Customizing for SAP NetWeaver BI in SAP EM by:
 Creating an SAP NetWeaver BI profile with the required extraction level
For more information, see the Implementation Guide (IMG) for SAP EM
under Event Management  SAP Business Information Warehouse
Interface  Define SAP BW Profiles.
 Assigning the SAP NetWeaver BI profile to an event handler type
For more information, see the IMG for SAP EM under Event
Management  SAP Business Information Warehouse Interface 
Process for Extracting SAP BW Data.
 You have configured SAP NetWeaver BI.
For more information, see the IMG for SAP EM under Event Management  SAP
Business Information Warehouse Interface  Process for Extracting SAP BW Data.

Process
...

1. You define the following in Customizing for the SAP NetWeaver BI profile:
...

a. The source structures and tables in SAP EM that contain the data that you want
to transfer to SAP NetWeaver BI.

You want to send data for the events Departure and the Arrival at Customer for
your service provider to SAP NetWeaver BI, for example. You specify the event
handler header /SAPTRX/EH_HDR and the table for expected events
/SAPTRX/EH_EXPEV as your source structures.
b. How the source structures and tables are mapped onto the extraction structures.
The event that you have defined to trigger the SAP NetWeaver BI upload calls a
function module that evaluates the actual data for each event handler and fills
the extraction structures in accordance with the Customizing settings you made
for mapping.
If you defined an automatic delta upload in Customizing for mapping, the data is
updated automatically in SAP NetWeaver BI.
2. SAP provides DataSources that are defined using extraction structures.
SAP EM updates the DataSources at the following times:
 Initial upload using a setup table
 Delta upload directly using the delta queue
After you have updated the DataSources, the data is available to SAP NetWeaver BI.
3. The system maps the DataSources one-to-one onto the InfoSources.
SAP NetWeaver BI provides the corresponding InfoSources.
4. SAP NetWeaver BI maps the InfoSources one-to-one onto the operational data storage
(ODS).

(C) SAP AG 185


5. SAP NetWeaver BI collects the ODS data in InfoCubes that are delivered with visibility
processes.
6. You can use queries to evaluate the data in InfoCubes. SAP delivers example queries
with the visibility processes [External].
The following figures provide an overview of the process flow:

Source Structures Extraction Structures DataSources


and Tables

/SAPTRX/EH_HDR
Event Handler Header (EH)
+ Header Extension 0SCEM_1
/SAPTRX/BWTFSEH
/SAPTRX/EH_INFO
+ /SAPTRX/APPENDEH
/SAPTRX/EH_CNTRL
/SAPTRX/EH_EVMSG Events (UE, EE)
/SAPTRX/EH_EXPEV 0SCEM_2
/SAPTRX/BWTFSEE
/SAPTRX/EH_SET + /SAPTRX/APPENDEE
/SAPTRX/EH_EEHST
... Groups (EG)
0SCEM_3
/SAPTRX/EVM_HDR /SAPTRX/BWTFSEG
/SAPTRX/EVM_EHD + /SAPTRX/APPENDEG
/SAPTRX/EVM_LID
... OLTP (SAP EM)

DataSources InfoSources ODS InfoCube

0SCEM_1 0SCEM_1 0EM_DS01

0SCEM_2 0SCEM_2 0EM_DS02 0EM_C01, ...

0SCEM_3 0SCEM_3 0EM_DS03

OLTP (SAP EM) SAP BI

For more information about the individual BI objects, see the SAP Help Portal under SAP
NetWeaver  BI Content  Supply Chain Management  Supply Chain Event
Management.

(C) SAP AG 186


Connection to the SCM Alert Monitor
Use
You can use several predefined activities in SAP Event Management (SAP EM) that use a
function module call to send alerts to the SCM Alert Monitor (Alert Monitor).
You use these alerts to forward information from SAP EM to the partners concerned (for
example, a transportation or production planner) in a timely and proactive way.

Prerequisites
To view the alerts in the SCM Alert Monitor, you must have defined an alert profile (for
example, VS optimization profile, PP/DS alert profile, or overall alert profile) in the monitor
(transaction /SAPAPO/AMON_SETTING).

For more information, see the SAP Library under SCM Basis  Alert Monitor 
Application-Specific Alert Profiles or under
SCM Basis  Alert Monitor  Monitoring and Solving Planning Problems Using
the Alert Monitor.

Features

(C) SAP AG 187


Alert Type in PP/DS
 Machine outage (SCEM)
To send a PP/DS alert from SAP EM to the SCM Alert Monitor, use the SAP EM activity Send
PP/DS Alert to SCM Alert Monitor (SEND_PPDS_APO_ALERT) within a rule set [Page 112].

For more information, see the documentation for function module


/SAPTRX/SEND_PPDS_APO_ALERT that SAP EM uses within the SAP EM
activity.

For more information about monitoring PP/DS alerts, see the SAP Library under
SCM Basis  Alert Monitor  Monitoring and Solving Planning Problems
Using the Alert Monitor  Monitoring PP/DS Alerts.

(C) SAP AG 188


Alert Types in Vehicle Scheduling
 Proposed transfer order declined by external transportation service provider
 Proposed delivery date changed by external transportation service provider
 In progress, proposed delivery date changed by external transportation service
provider.
 In progress, proposed shipment declined by external transportation service provider.
 No answer from transportation service provider
To send a VS alert from SAP EM to the SCM Alert Monitor, use the SAP EM activity Send VS
Alert to SCM Alert Monitor (SEND_VS_APO_ALERT) within a rule set.

For more information, see the documentation for function module


/SAPTRX/SEND_VS_APO_ALERT that SAP EM uses within the SAP EM
activity.

For more information about monitoring VS alerts, see the SAP Library under
SCM Basis  Alert Monitor  Monitoring and Solving Planning Problems
Using the Alert Monitor  Monitoring VS Alerts.

Activities
 You use the relevant rule activity within your rule set.

We recommend that SAP APO creates the event handler, in whose rule set you
use the activity, in SAP EM.
 As soon as the rule condition(s) are met, SAP EM triggers an alert in the SCM Alert
Monitor.
 You display the alerts in the SCM Alert Monitor.

Example

(C) SAP AG 189


Monitoring a Shipment Process from Bidding to
Execution
...

1. You plan a shipment in SAP APO.


2. When you save the shipment planning, SAP APO triggers the creation of event handler
EH1 in SAP EM.
3. The supplier sends his or her answer Rejection to SAP EM in response to your
transportation bid.
4. SAP EM forwards the rejection as a VS alert to the SCM Alert Monitor.
5. You choose a new supplier for your shipment in the SCM Alert Monitor.
6. SAP APO transfers the shipment planning to an SAP R/3 system.
7. When you save the shipment document in SAP R/3, it triggers the creation of event
handler EH2 in SAP EM.
8. You have configured SAP EM in such a way that EH1 and EH2 form an event handler
set EH set 1. This event handler set maps your shipment process from planning to
execution.

(C) SAP AG 190


Connection to the Document Flow
Use
In the application system, business objects (documents) have a hierarchical relationship to
one another. For example, a sales order consists of multiple deliveries that fulfill multiple
shipments. The connection to the document flow enables SAP Event Management to display
this hierarchical structure of the business objects in the Web Interface (Classic) [External] and
in the Web Interface (Web Dynpro ABAP) [Page 136]

For each SAP Event Management, you can connect one local document flow
only.
For performance reasons, we recommend that you do not use the document
flow in scenarios with a high volume of data (for example, scenarios with
handling units).
For more information about the document flow, see the SAP Help Portal under
Documentation  SAP Business Suite  SAP Supply Chain Management 
SAP Supply Chain Management (SAP SCM)  SCM Basis  Cross-System
and Cross-Partner Document Flow.

Prerequisites
You have carried out the Customizing for the connection to the document flow.
 You have specified how you want SAP Event Management to update the document
flow. You have the following options:
 At the same time as creating or updating an event handler
 Via an event message
For more information, see the Implementation Guide (IMG) for SAP Event Management
under Event Management  Interface to Document Flow  Define Document Flow
Groups.
 You have defined the groups [External] and the mapping of event handler information
to the document flow. You can assign each event handler or each event message to
one group only.
For more information, see the IMG for SAP Event Management under Interface to
Document Flow  Define Document Flow Groups.
 If necessary, you have defined your own document categories in Customizing for the
document flow.
For more information, see the IMG for SAP Event Management under Integration with
SAP Components  Cross-System and Cross-Partner Document Flow  Define
Document Categories for Document Flow.
 If necessary, you have defined your own link categories in Customizing for the
document flow.
For more information, see the IMG for SAP Event Management under Integration with
SAP Components  Cross-System and Cross-Partner Document Flow  Define
Object Link Model.

Features
The connection to the document flow comprises the following functions:
 You can create or update a document flow network [Page 193].

(C) SAP AG 191


 You can delete a document flow network [Page 197].
 You can display a document flow network [Page 195].

(C) SAP AG 192


Creation and Updating of a Network
Use
SAP Event Management creates a network in the document flow [External] and updates this
network so that you can display the hierarchical structure for an event handler in the Web
Interface (Classic) [External].

Prerequisites
 You have carried out the Customizing for the connection to the document flow. For
more information about Customizing, see Connection to the Document Flow [Page
191] under Prerequisites.
 You have set up an asynchronous communication with the application system. For
more information, see Customizing for SAP Event Management under General Settings
in SAP Event Management  Define Application System.

Features
You can define whether you update an event handler or an event message and the relevant
network at the same time.
For more information, see the Implementation Guide (IMG) for SAP Event Management under
Interface to Document Flow  Integration with Document Flow.

Locking Concept
It may happen that multiple event handler types exist in a network and that multiple event
messages want to update the same event handler. For this reason, a locking concept is in
use in SAP Event Management. Here the document flow locks the object in the network that
is currently being updated by an event message or event handler from SAP Event
Management. When SAP Event Management updates a document flow, it uses the lock
object /SAPTRX/E_DF and thereby locks the associated documents and predecessor
documents. When SAP Event Management removes the lock on the associated event
handlers or event messages, it simultaneously removes the lock for the document flow. If
SAP Event Management does not update the document flow network after multiple attempts,
it writes an entry to the application log.

For more information about the SAP locking concept, see the SAP NetWeaver
documentation in the SAP help portal under SAP NetWeaver by Key Capability
 Application Platform by Key Capability  ABAP Technology  Client/Server
Technology  The SAP Locking Concept (BC-CST-EQ).

Activities
...

SAP Event Management has created a new event handler or updated an existing one. The
document flow has created a new network or updated an existing one. SAP Event
Management does the following:
 If you have carried out the Customizing for updating the document flow by creating or
changing an event handler, SAP Event Management proceeds as follows:
a. On the basis of the event handler type, SAP Event Management invokes the
activity for updating an event handler.
SAP Event Management finds the parameter for the group in the activity for
updating an event handler, and updates the network accordingly. If you have
defined a condition for updating the network, SAP Event Management evaluates
this condition and updates the network only in accordance with the condition.

(C) SAP AG 193


b. SAP Event Management reads the Customizing for the document flow and
searches in for the source information in SAP Event Management that the
system sends to the document flow to create or update the associated network.
c. SAP Event Management reads the attributes that the document flow saves
together with the source information in the network.
d. SAP Event Management searches for the predecessor document and reads the
target data for creating or updating the network.
e. SAP Event Management sends all the necessary data to the document flow.
If an error occurs in the document flow, SAP Event Management writes an entry
to the application log.
 If you have set up the Customizing for updating the document flow via an event
message, SAP Event Management proceeds as follows:
...

a. SAP Event Management processes this event message.


For this, SAP Event Management applies the rule set [Page 112] and calls your
rule activity for the document flow.
SAP Event Management finds an activity with the parameter for the group for
simultaneously updating the network. You can use a rule set condition for this.
b. SAP Event Management reads the Customizing for the document flow and
searches in for the source information in SAP Event Management that the
system sends to the document flow to create or update the associated network.
c. SAP Event Management reads the attributes that the document flow saves
together with the source information in the network.
d. SAP Event Management searches for the predecessor document and reads the
target data for creating or updating the network.
e. SAP Event Management sends all the necessary data to the document flow.
If an error occurs in the document flow, SAP Event Management writes an entry
to the application log.

(C) SAP AG 194


Displaying a Network
Use
You display a document flow network to be able to monitor and evaluate your processes. The
document flow displays the dependencies between your business objects (predecessor
document and successor document) and specifies the attributes.

Integration
SAP Event Management (SAP EM) works with one local document flow only.

Prerequisites
 You have set the Document Flow indicator in the user profile in Customizing. As a
result, the Web interface (classic) automatically displays the link to the document flow
network that belongs in the event handler list [External].
For more information, see the Implementation Guide (IMG) for SAP EM under Event
Management  Event Messages, Status Queries, and Web Interface  Web Interface
 Define User Profiles.
 In the Web interface (classic), you have defined your personal settings for displaying a
document flow network.
 You have not set the Accessibility Switch under Settings. This means that you
can choose between a graphical or tabular display of the network in the Web
interface (classic).
 You have set the Accessibility Switch under Settings. This means that the
system displays a tabular view of the network in the Web interface (classic) that
your screen reader can read.
 You have chosen the Document Flow Mode under Settings. SAP EM first
displays the mode that you choose here (graphical or tabular) in the Web
interface (classic). The Web interface (classic) also displays a link with which
you can select the other mode.
In the standard system, the graphical view is delivered as the document flow mode for
the Web interface (classic). You can change this setting in the personal settings in the
Web interface (classic).

Features
If an event handler exists and you have read authorization for the nodes of this event handler,
the Web interface (classic) displays the following information:
 The document category, document number and, as appropriate, the document item
number with an active link to the event handler that has generated them. If you have
the appropriate authorizations in your user profile, the Web interface (classic) displays
detailed information, and you can execute a drilldown.
 The relevant parameters, for example, status information or info parameters

For more information, see Web Interface (Classic) [External] and the IMG for
SAP EM under Event Management  Event Messages, Status Queries, and
Web Interface  Web Interface  Define User Profiles.

(C) SAP AG 195


Activities
The following figure provides an overview of the activities for displaying a document flow:

User

Query Response

SAP SCM Java Stack

SAP EM Web Interface

Query XML Construction


RFC Call
JNet Call
Response

Query Response

SAP Basis
Plug-In Query Response

Document Flow JNet

Read Document
XML Interface
Flow Network

...

1. You select one event handler in the Web interface (classic).


2. The Web interface (classic) calls SAP EM and displays the event handler.
3. You want to see the hierarchy for this event handler and choose Document Flow.
4. The Web interface (classic) calls SAP EM. SAP EM calls methods in the document flow
to read the network.
5. The document flow sends the relevant network data to SAP EM.
6. SAP EM sends this data via RFC to the Web interface (classic).
7. The Web interface (classic) creates XML files from this data and sends the XML files to
JNet.
8. JNet sends corresponding GIF files containing this data to the Web interface (classic).
9. The Web interface (classic) displays the document flow network in a new dialog box.
If you want to use additional attributes in the document flow, you have defined them in
Customizing.
For more information, see the IMG for SAP EM under Event Management  Interface to
Document Flow  Define Document Flow Groups.

(C) SAP AG 196


Deletion of a Network
Use
When SAP Event Management (SAP EM) has archived and deleted all the event handlers
that belong to a network, it can delete the relevant network in the document flow.

Integration
SAP EM uses its own document categories and link categories in the document flow to
ensure that a unique assignment of the SAP-EM-relevant networks is possible. In the
standard system, these document categories and link categories start with 1.

Prerequisites
 SAP EM has archived and deleted all event handlers that belong to a network in the
document flow.
 Networks exist in the document flow.
 In Customizing, you have defined the residence time for deleting a network.
For more information, see the Implementation Guide (IMG) for SAP EM under Event
Management  Archive and Delete SAP EM Objects  Define Settings for Deleting
Document Flow.
 You have defined the relevant document categories for deleting a network.
For more information, see the IMG for SAP EM under Event Management  Archive
and Delete SAP EM Objects  Define Settings for Deleting Document Flow.

Features
You can schedule the report /SAPTRX/DELETE_DF as a background job to regularly delete
the networks belonging to event handlers that have already been deleted. When SAP EM
deletes a network, it flags this in the application log. You can also start this report directly.
For more information about deleting individual document flow nodes, see the IMG for SAP EM
under Event Management  Interface to Document Flow  Integration with Document Flow.

Activities
On the SAP Easy Access screen, choose Event Management  Administration 
Processing Control  Schedule Background Jobs for Event Management.
Specify how often the background job is to be executed to delete any relevant networks.

(C) SAP AG 197


Logging with Change Documents
Use
SAP Event Management logs the changes made to data related to event handlers in change
documents [External]. In this way, you can trace the changes made and can always check
what was changed as well as when and how it was changed. This makes it easier for you to
analyze errors.

Prerequisites
You have activated logging with change documents in Customizing for SAP Event
Management under Event Handlers and Event Handler Data  Event Handlers  Define
Event Handler Types.

Features
Creation of a Change Document
When the following data related to event handlers is changed, SAP Event Management writes
a change document:
 Event handler header data
 Expected events
 Info parameters
 Control parameters
 Query IDs
 Tracking IDs
SAP Event Management can also create change documents for multiple event handlers at the
same time. SAP Event Management creates change documents for data changes that you
make directly using transaction /SAPTRX/EH_LIST or that you send to SAP Event
Management with an event message. SAP Event Management also automatically creates a
change document for each dependent change made to expected events, in other words, for
all changes dependent on your manual changes. SAP Event Management saves these
changes under the same user name.

Displaying a Change Document


You can display the change documents in the event handler details on the Change
Documents tab (see Use of Event Handler Details [Page 165]).

Deletion of a Change Document


When you delete an event handler and the corresponding data in SAP Event Management,
the system does not create a change document, but instead it deletes the relevant existing
change documents. Even if you only delete the event handler header data, SAP Event
Management also automatically deletes all the relevant event handler data and change
documents.
If, however, you delete an event handler and the corresponding data in SAP Event
Management and then create a new event handler with the same event handler GUID, the
relevant existing change documents are retained.

Archiving a Change Document


When SAP Event Management archives event handler data, it also archives the relevant
change documents at the same time. For archiving change documents, SAP Event

(C) SAP AG 198


Management uses the archiving object /SAPTRX/A0 to archive event handler data and the
archiving object /SAPTRX/A2 to archive event handler set data.

For more information about the concept behind logging with change documents
and about the structure of change documents, see the SAP NetWeaver
documentation on SAP Help Portal under SAP NetWeaver by Key Capability 
Application Platform by Key Capability  ABAP Technology  ABAP
Workbench (BC-DWB)  BC Extended Applications Function Library 
Change Documents.
See also:
Archiving in SAP Event Management [Page 244]

(C) SAP AG 199


Simulating Processes in the SAP Application
System and SAP EM
Use
To see the consequences of saving, updating, or deleting an SCEM-relevant business object
in the application system, you can simulate processes. This provides you with an overview of
all the processes in SCEM.

SAP EM does not save the values from the simulation.

Prerequisites
 You have set up Customizing for the SAP application system.
 You have set up Customizing for SAP Event Management (SAP EM).

Procedure
...

1. In the application system, choose the transaction for defining business process types
(/SAPTRX/ASC0AO).
2. Choose Simulation as the mode for a business process type.
3. Save the change.
In doing this, you have set the simulation mode not only for all SCEM-relevant process
steps in the application system, but also for the process steps in SAP EM.
4. Start the simulation by either saving, changing or deleting an SCEM-relevant business
object in the application system (for example, a shipment document).
The system displays the chosen business process type and the application object types
that belong to it.
5. Choose Continue or Cancel.
When data is updated, SAP EM shows the various processes step-by-step (depending
on your Customizing for the application system and SAP EM). For example, you can
check the following within the various processes:
 The parameter list in the application system
 The current SAP EM
 The expected events created
 The event handler types that SAP EM has determined
If you choose to cancel, the simulation activity is aborted and the SAP Easy Access
screen appears.
The simulation also transfers the SCEM-relevant data from the application system to
SAP EM.

You can cancel the simulation at any point.

(C) SAP AG 200


Result
 The system has simulated all SCEM-relevant processes.
 If the simulation is successful, you can start the process in the active business process
mode.
 If problems occur, you know where and in which process you can make corrections, if
required.

(C) SAP AG 201


Overview of Activities Delivered
The list of all activities delivered [Page 204] provides you with an overview of all the activities
delivered for SAP Event Management.

For more information about the structure of the list, see Activity List Structure
[Page 203].

(C) SAP AG 202


Activity List Structure
Definition
You can find the following activity types in the overview of activities delivered [Page 204] by
SAP:
 Rule activities
You use these activities within rules to control the processes for processing event
messages in rule sets.
 Activities for the expected event monitor
You use these activities when the program for the expected event monitor determines
that an expected event is overdue. In this way, you determine how the system reacts to
this situation.
 Activities for updating event handlers
You use these activities to modify data before creating an event handler.

SAP reserves the right to change methods when delivering Support Packages
for SAP Event Management. For up-to-date information, see SAP Service
Marketplace.
The technical name, the corresponding description, and the name of the function module or
method used are specified for each activity.

For a detailed description of the activity function, see the function module
description. On the SAP Easy Access screen, choose Tools  ABAP
Workbench  Development  Function Builder. Enter the name of the function
module and choose Display. The system displays the function module coding.
Choose Goto  Documentation.

(C) SAP AG 203


Activity List
Rule Activity Functions
Activity Name Description Name of Method or Function Method or
Module Function
ALERT_CREATE Integration of /SAPTRX/CREATE_ALERT F
Alert
Framework
BW_UPLOAD Upload /SAPTRX/BW_EXTRACTION F
Business
Information
Warehouse
DF_UPDATE Update /SAPTRX/DF_UPDATE F
Document Flow
EH_AUTO_ARCH Event Handler /SAPTRX/EH_AUTO_ARCH F
Automatic
Archiving
EH_AUTO_ARCH_SET Event Handler /SAPTRX/EHSET_AUTO_ARCH F
Set Automatic
Archiving
ID_MAPPING Call ID Mapping /SAPTRX/ID_MAPPING F
Functionality
and Set Rule
Processing
Parameters
RESEND Resend Event /SAPTRX/RESEND F
Messages to
Another Event
Handler
RESEND_MULTIPLE Resend Event /SAPTRX/RESEND_MULTIPLE F
Messages to
Other Event
Handlers
SEND_POD Send a Proof of /SAPTRX/SEND_POD F
Delivery
SEND_PPDS_APO_ALERT Send PP/DS /SAPTRX/SEND_PPDS_APO_A F
Alert to SAP LERT
APO Alert
Monitor
SEND_SNC_DOC_ALERT Send Document /SAPTRX/SEND_SNC_DOC_AL F
Related Alert to ERT
SAP SNC
SEND_SNC_MSG_ALERT Send XML- /SAPTRX/SEND_SNC_MSG_AL F
Message ERT
Related Alert to
SAP SNC
SEND_VS_APO_ALERT Send VS Alert /SAPTRX/SEND_VS_APO_ALE F
to SAP APO RT
Alert Monitor

(C) SAP AG 204


SHIPMENT_DATE_UPDATE Update Actual /SAPTRX/SET_ACT_SHIPMENT F
Dates in the _DDL
SAP R/3
Shipment
SHPMT_DATE_UPDATE Update Actual /SAPTRX/SET_ACT_SHIPMENT F
Dates in the _DDL1
SAP R/3
Shipment (as of
SAP SCM 4.0
with PI2003.1)
SHPMT_ENDDATE_UPDAT Update Actual /SAPTRX/SET_SHIPMENT_EN F
E Shipment End DDATE
Date in the SAP
R/3 Shipment
TM_MAINTAIN_ETA Create/Update /SAPTRX/TMS_CHANGE_ETA F
ETA with or
Without
Reference to
PTA(s) in TM
TM_SET_HSH_STATUS Set Life Cycle /SAPTRX/TMS_SET_HSH_STA F
Status in House TUS
Shipment in
Transportation
Management
WORKFLOW_START Create the /SAPTRX/CREATE_BO_EVENT F
Event
"Start_workflow
" in the BO
"/SAPTRX/EH"
to Trigger the
Workflow

Rule Activity Methods


Activity Name Description Name of Method or Method or
Function Module Function
ADD_TO_SET Add Current Event ACT_ADD_TO_SET M
Handler to Event
Handler Sets
ADD_EHS_TO_PROCESS Add Additional ACT_ADD_EHS_TO_PROC M
Related Event ESS
Handler GUIDs
from Further
Reference Data
ARE_PRIOR_REQS_MET Have Prior ACT_PRIOR_REQS_REPOR M
Required TED
Expected Events
Been Reported for
an Event?
CHECK/SET_PARAM_VALS Check Par. ACT_CHECK_AND_SET_PA M
Values in Evt Msg RAM_VALUES
Against Info/Conrl
Par. Values And
Set the Result

(C) SAP AG 205


CHECK_EH_IN_SETS Check the Status ACT_CHECK_EH_IN_SET M
of Event Handlers
in Event Handler
Set
CHECK_PARAM_VALUE Check Value of ACT_CHECK_PARAMETER M
System, Control, _VALUE
Info, or Rule
Processing
Parameter
CHECK_RELATED_EH Check Status of ACT_CHECK_RELATED_EH M
Related Event
Handlers
CHECK_REPROCESS_FLAG Check Value of ACT_CHECK_REPROCESS M
Class Attribute _FLAG
MY_REPROCES
S
CHECK_SYSPARAM_VALUE Check Parameter ACT_CHECK_SYSTEM_PA M
Values in Evt Msg RAM_VALUE
Against System
Parameter Values
COMPARE Compare Two ACT_COMPARE M
Fields
EE_ALL_REQS_MET Have All Required ACT_ALL_REQS_REPORTE M
Expected Events D
Been Reported?
EE_EXP_DATES_CLEAR Clear the ACT_CLEAR_EXPECTED_D M
Expected Dates ATES
for an Expected
Event
EE_PROCESS Process Expected ACT_PROCESS_EE M
Events

EE_RESET Reset the Actual ACT_RESET_EE M


Dates and Status
for an Expected
Event
EH_ACTIVATE Activate Event ACT_ACTIVATE M
Handler
EH_DEACTIVATE Deactivate Event ACT_DEACTIVATE M
Handler

EH_GUID_SET Retain Event ACT_SET_EH_GUID M


Handler GUID
Currently Being
Processed
EH_HIERARCHY_UPDATE Update Event ACT_UPDATE_EH_HIERAR M
Handler Hierarchy CHY
Table
EHSET_ACTIVATE Activate Event ACT_SET_EHSET_ACTIVE M
Handler Set

(C) SAP AG 206


EHSET_SET_INACTIVE Deactivate Event ACT_SET_EHSET_INACTIV M
Handler Set E

EHSET_STATUS_CHECK Check Status ACT_CHECK_EHSET_STAT M


Records for US
Status Attribute
Name & Value for
Event Handler Set
EHSET_STATUS_SET Create or Update ACT_SET_EHSET_STATUS M
a Status Attribute
Name for Event
Handler Set
ERROR_MESSAGE_CLEAR Clear (Deactivate) ACT_CLEAR_ERR_MSGS M
Error Messages

ERROR_MESSAGE_LOG Log an Error ACT_LOG_ERROR_MSG M


Message

EVENT_CODE_CHECK Does Internal ACT_IS_EVENT_CODE M


Event Code Equal
<Parameter>?
EVM_EE_UPDATE Update Expected ACT_EE_MODIFY M
Event List from
Event Message
EE MODIFY
Table (as of SCM
4.0)
EVM_ETA_UPDATE Update Expected ACT_ETA_EVENT_MSG M
Date for an Event
with Estimated
Deadlines (Only
EM 1.1)
IS_EE_EARLY Is the Event Date ACT_IS_EE_EARLY M
Prior to the
Earliest Expected
Date?
IS_EE_IN_DATE_SEQ Is This Event and ACT_IS_EE_IN_DATE_SEQ M
All Prior Events in
Chronological
Order?
IS_EE_LATE Is This Event Date ACT_IS_EE_LATE M
After the (Latest)
Expected Date?
IS_EE_MSG_EARLY Is the Event Msg. ACT_IS_EE_MSG_EARLY M
Date Prior to the
Earliest Expected
Date?
IS_EE_MSG_LATE Is This Event Msg. ACT_IS_EE_MSG_LATE M
Date After the
(Latest) Expected
Date?

(C) SAP AG 207


IS_EE_REPROCESSED Has This ACT_IS_EE_REPROCESSE M
Expected Event D
Been Reported
Previously?
IS_EQUAL Equate Two ACT_IS_EQUAL M
Fields

IS_EVENT_EXPECTED Is the Event an ACT_IS_EVENT_EXPECTE M


Expected Event (= D
EE Code, Partner,
Location)?
IS_EVENT_IN_GROUP Is the Internal ACT_IS_EVENT_IN_GROUP M
Event Code in
Group
<Parameter>?
IS_EVENT_REPORTED Was Event Msg. ACT_IS_EVENT_REPORTE M
Already Reported D
for Same Event
Handler?
IS_EVM_CODE_EXPECTED Is the Internal ACT_IS_EVM_CODE_EXPE M
Event Code One CTED
of the Expected
Event Codes?
IS_LAST_EE Is This Event the ACT_IS_LAST_EE M
Last Expected
Event?
IS_MEASUREMENT_CONF Did the Event ACT_IS_MEASUREMENT_C M
Message Confirm ONFIRMED
an Expected
Measurement
Result?
IS_MSRMNT_NOT_COMPAR Was Event ACT_IS_MSRMNT_NOT_CO M
Message not MPARABLE
Comparable to the
Expected
Measurement
Result?
IS_MSRMNT_OUT_OF_TOL Did the Reported ACT_IS_MSRMNT_OUT_OF M
Measurement _TOLERANCE
Result Exceed the
Expected Result?
IS_ORIG_EE_LATE Is the Event Date ACT_IS_ORIG_EE_LATE M
After the Original
Expected Date?
IS_ORIG_EE_MSG_LATE Is This Event Msg. ACT_IS_ORIG_EE_MSG_LA M
Date After the TE
Original Expected
Date?

(C) SAP AG 208


IS_REPORTED_FOR_EH Was Event Msg. ACT_IS_REPORTED_FOR_ M
Already Reported EH
for Another Event
Handler?
PARAMETER_CHANGE Adding /Changing ACT_CHANGE_PARAM M
/Deleting Control
and/or Info
Parameter(s)
PROCEDURE_RC_SET Set Return Code ACT_SET_PROC_RC M
for Multi-Task
Activity Explicitly
PROCESS_MEASUREMENT Process ACT_PROCESS_MEASURE M
S Measurement MENTS
Data
PROCESS_UNPROCESSED Check for and ACT_PROCESS_UNPROCE M
Process Any SSED_MSGS
Unprocessed
Event Messages
QUIT_EVM_PROCESSING Quit Event ACT_QUIT_EVM_PROCESS M
Message ING
Processing and
Mark as Irrelevant
RETRIEVE_MSG Retrieve Process- ACT_LOG_MSG M
Related
Messages for
Visibility
Processes
SET_RULE_PROC_PARAM Create, Update, or ACT_SET_ACTIVITY_PARA M
Delete a Rule M
Processing
Parameter
STATUS_CHECK Check Status ACT_CHECK_STATUS M
Records for
Status Attribute
Name & Value for
Event Handler
STATUS_SET Create or Update ACT_SET_STATUS M
a Status Attribute
Name and Update
Status History for
EH
TRACKING_ID_REMOVE Delete Tracking ACT_REMOVE_TRACKING_ M
IDs IDS

TRACKING_ID_SET Create Additional ACT_SET_TRACKING_ID M


Tracking ID(s)
from Event
Message Further
Reference Data
WEBLINK_SET Create a Web ACT_CREATE_WEBLINK M
Link

(C) SAP AG 209


Activity Functions for the Expected Event Monitor
Activity Name Description Name of Method or Function Method or
Module Function
ALERT_CREATE Integration of /SAPTRX/CREATE_ALERT F
Alert
Framework
SEND_SNC_DOC_ALERT Send /SAPTRX/SEND_SNC_DOC_A F
Document LERT
Related Alert
to SAP SNC
SEND_SNC_MSG_ALERT Send XML- /SAPTRX/SEND_SNC_MSG_A F
Message LERT
Related Alert
to SAP SNC
SEND_VS_APO_ALERT Send Vehicle /SAPTRX/SEND_VS_APO_AL F
Scheduling ERT
Alert to SAP
APO Alert
Monitor

Activity Methods for the Expected Event Monitor


Activity Name Description Name of Method or Function Method or
Module Function
CHECK_PARAM_VALUE Check Value ACT_CHECK_PARAMETER_V M
of System, ALUE
Control, Info,
or Rule Proc.
Parameter
COMPARE Compare ACT_COMPARE M
Two Fields

EH_ACTIVATE Activate ACT_ACTIVATE M


Event
Handler
EH_DEACTIVATE Deactivate ACT_DEACTIVATE M
Event
Handler
EHSET_ACTIVATE Activate ACT_SET_EHSET_ACTIVE M
Event
Handler Set
EHSET_SET_INACTIVE Deactivate ACT_SET_EHSET_INACTIVE M
Event
Handler Set
EHSET_STATUS_CHECK Check Status ACT_CHECK_EHSET_STATU M
Records for S
Status
Attribute
Name &
Value for
Event
Handler Set

(C) SAP AG 210


EHSET_STATUS_SET Create or ACT_SET_EHSET_STATUS M
Update a
Status
Attribute
Name for
Event
Handler Set
ERROR_MESSAGE_CLEAR Clear ACT_CLEAR_ERR_MSGS M
(Deactivate)
Error
Messages
ERROR_MESSAGE_LOG Log an Error ACT_LOG_ERROR_MSG M
Message

IS_EE_MSG_OVERDUE Is the ACT_IS_EE_MSG_OVERDUE M


Expected
Event
Message
Overdue?
IS_EE_OVERDUE Is the ACT_IS_EE_EVENT_OVERDU M
Expected E
Event
Overdue?
IS_EQUAL Equate Two ACT_IS_EQUAL M
Fields

OVERDUE_EE_RESET Reset ACT_RESET_OVERDUE_EE M


"Overdue"
Expected
Event Status
Back to
"Expected"
PROCEDURE_RC_SET Set Return ACT_SET_PROC_RC M
Code for
Multi-Task
Activity
Explicitly
SET_RULE_PROC_PARAM Create, ACT_SET_ACTIVITY_PARAM M
Update, or
Delete a Rule
Processing
Parameter
STATUS_CHECK Check Status ACT_CHECK_STATUS M
Records for
Status
Attribute
Name &
Value for
Event
Handler

(C) SAP AG 211


STATUS_SET Create or ACT_SET_STATUS M
Update a
Status
Attribute
Name and
Update
Status
History for
EH

Activity Functions for Updating an Event Handler


Activity Name Description Name of Method or Function Method or
Module Function
ALERT_CREATE Integration of /SAPTRX/CREATE_ALERT F
Alert
Framework
DF_UPDATE_FROM_EH Update /SAPTRX/DF_UPDATE_FRO F
Document Flow M_EH
from Event
Handler
Creation/Updat
e

Activity Methods for Updating an Event Handler


Activity Name Description Name of Method or Method or
Function Module Function
CHECK_PARAM_VALUE Check Value ACT_CHECK_PARAMET M
of System, ER_VALUE
Control, Info,
or Rule
Processing
Parameter
COMPARE Compare Two ACT_COMPARE M
Fields

EH_ACTIVATE Activate Event ACT_SET_EHSET_ACTIV M


Handler E

EH_DEACTIVATE Deactivate ACT_SET_EHSET_INACT M


Event Handler IVE
EHSET_ACTIVATE Activate Event ACT_SET_EHSET_ACTIV M
Handler Set E

EHSET_SET_INACTIVE Deactivate ACT_SET_EHSET_INACT M


Event Handler IVE
Set
EHSET_STATUS_CHECK Check Status ACT_CHECK_EHSET_ST M
Records for ATUS
Status
Attribute
Name & Value
for Event
Handler Set

(C) SAP AG 212


EHSET_STATUS_SET Create or ACT_SET_EHSET_STAT M
Update a US
Status
Attribute
Name for
Event Handler
Set
ERROR_MESSAGE_CLEAR Clear ACT_CLEAR_ERR_MSGS M
(Deactivate)
Error
Messages
ERROR_MESSAGE_LOG Log an Error ACT_LOG_ERROR_MSG M
Message

IS_EQUAL Equate Two ACT_IS_EQUAL M


Fields

PROCEDURE_RC_SET Set Return ACT_SET_PROC_RC M


Code for Multi-
Task Activity
Explicitly
SET_RULE_PROC_PARAM Create, ACT_SET_ACTIVITY_PA M
Update, or RAM
Delete a Rule
Processing
Parameter
STATUS_CHECK Check Status ACT_CHECK_STATUS M
Records for
Status
Attribute
Name & Value
for Event
Handler
STATUS_SET Create or ACT_SET_STATUS M
Update a
Status
Attribute
Name and
Update Status
History for EH

(C) SAP AG 213


Supply Chain Coordination
Purpose
Supply Chain Coordination is one of the key functional areas within the SAP Supply Chain
Management (SAP SCM) solution and comprises supply chain event management (SCEM)
and supply chain performance management (SCPM).
Supply chain event management provides visibility across the entire supply chain, while
supply chain performance management provides metrics and reporting options that you can
use as the basis for optimizing your supply chain.
SAP Event Management (SAP EM) is the application within the SAP SCM solution that
provides or improves visibility within your logistic processes, both in planning and in
execution. The flexibility of the application enables you to map, control, and check all required
business processes.
The role-based approach of SAP EM makes it possible to view the same business process
from various points of view:
 As a manufacturer you are interested to know, for example, whether the different
service providers have delivered your raw materials used in production on time and in
the correct quantity.
 As an individual service provider you are interested to know where a means of
transport or packing materials that contain your product/material are located and at
what time, for example.
 As an individual customer you are interested to know when the supplier delivers the
materials that you have ordered, for example.
You can use SAP EM to process messages about the events in business processes, to notify
those involved in the supply chain in various ways about business events that have occurred,
and to make this information clear.
To optimize reaction times and improve quality and customer satisfaction, you can actively
notify persons responsible to make them aware of critical situations or exceptions.
If you work with data warehouse systems, such as SAP NetWeaver Business Intelligence,
SAP EM supports you in evaluating your results. As a result, you receive detailed information
about the factors in your supply chain that lead to critical situations and you can reduce or
eliminate them.
SAP EM integrates both internal and external partners from your supply chain, and allows you
and your partners to gain a cross-company overview of your processes.
You can implement SAP EM in all planning and execution processes within logistics.
For example:
 In procurement [Page 218]
 In manufacturing [Page 220]
 In order fulfillment [Page 222]
 In asset management [Page 223]
SAP delivers visibility processes (for example, for deliveries in a shipment) that describe the
business process flow and execution in an SAP system landscape.
For more information about the visibility processes, see SAP Service Marketplace at
service.sap.com/scm  Supply Chain Event Management  Visibility Processes.

(C) SAP AG 214


Integration
SAP EM provides event processing across the entire supply chain. It communicates with
application systems such as an SAP ERP or an external system, and transfers data to the
SAP NetWeaver Business Intelligence. There you can perform analytical queries for decision-
makers. SAP delivers an application interface that makes it easier to connect SAP EM to an
SAP system and to configure it in the SAP system. If you integrate SAP EM with an external
system, the respective customer project is responsible for the interface.

Features
You use SAP EM to:
 Transfer data that is relevant to supply chain event management (SCEM-relevant) from
the application system to SAP EM
 Process and then evaluate event messages
This allows you to monitor the progress of processes (for example, goods issue,
receiving and processing purchase orders, production end, or shipment).
 Automatically monitor and trigger reactions to process steps that have not occurred or
are overdue (for example, proactively notify the decision-maker in the case of a delay
or an unreported proof of delivery)
 Gain an overview (status, location, and process flow queries) of SCEM-relevant objects
and thereby find out the current information about an object at any time
 Exchange information between partners (for example, using EDI, the Web, or XML)
 Notify partners (for example, by e-mail or SMS)
 Analyze data in a data warehouse system and adapt future event processing
The following figure provides an overview of the simplified process flow in SAP EM:

SAP Business Suite/Application

Application
Interfaces to SAP and
Interface
External Systems

Predefined Customizing, Rules,


Communication Customizing and Unexpected Events
Layer for Event
Messages and SAP Event Visibility Process
Status Queries
Management

Data Extraction Data Transfer from


SAP EM to SAP NetWeaver BI

SAP NetWeaver
Business Intelligence

Example

(C) SAP AG 215


Tracking a Customer Delivery
You want to track a customer delivery and create the delivery in SAP ERP. This automatically
triggers the monitoring process in SAP EM. The system transfers planned data from the
delivery to SAP EM where it generates expected events with reference to the delivery. Other
partial processes, for example, picking or packing the delivery, send status messages to SAP
EM. If you use SAP NetWeaver Business Intelligence with SAP EM, you can analyze and
evaluate the event progression.

(C) SAP AG 216


Uses of Supply Chain Event Management
The following are examples of application areas for supply chain event management:
 Procurement [Page 218]
 Manufacturing [Page 220]
 Order fulfillment [Page 222]
 Asset management [Page 223]
 Transportation

(C) SAP AG 217


Use in Procurement
The supply chain event management-relevant (SCEM-relevant) process in procurement
begins with the creation of a purchase order for a planned material and ends with the transfer
of data to a data warehouse system. You can evaluate the data there.
When you create a purchase order for a buyer with or without a reference document, the
application system sends this purchase order to the supplier. If the supplier can fulfill the
order, he or she confirms it. If not, he or she sends an appropriate notification to SAP Event
Management (SAP EM). SAP EM sends an alert to the buyer. When the supplier has finished
production, he or she sends an advanced shipping notification (ASN) to the application
system.
All those involved in the process report various events to SAP EM, for example, that the ASN
was sent. SAP EM also tracks the events that occur during goods receipt, invoicing, and the
payment process. You transfer the relevant data to SAP NetWeaver Business Intelligence to
evaluate it analytically.
To track the partner delivery, for example, you can connect the SCEM-relevant process in
procurement with the process from transportation or order fulfillment.
The following figure provides an overview of using SAP EM in procurement:

Supplier
Customer Partner
Buyer Other Customer Roles

Purchase
Requisition
Purchase
Order

Confirmation

Advanced
Shipping Notif. Transport *

Goods Receipt

ERS / Invoice

Payment

Analysis

* Note that the transport in this figure refers to the transportation process. It is not part of the
procurement process.
For more information about the transportation process, see SAP Service Marketplace at
service.sap.com/scm  Supply Chain Event Management  Visibility Processes 
Transportation Visibility – Scenario Description.

(C) SAP AG 218


An example of a procurement situation
A manufacturer of electronic goods orders customer-specific semiconductors in Singapore.
The freight forwarder takes the delivery to Malaysia by truck and then by ship to the
manufacturer of electronic goods.
Within this process, various partners report events to SAP EM using various means of
communication. Examples include the Internet (portals), EDI, and radio frequency devices. By
reporting events during the different phases of the process, the partners help to provide
transparency across the entire business process.
Only the manufacturer of electronic goods who placed the order has an SAP system. The
partners have different systems. The data in SAP EM is updated either by means of an
Internet connection that the manufacturer of electronic goods supports or by means of EDI
transactions.

(C) SAP AG 219


Use in Manufacturing
In manufacturing, the supply chain event management-relevant process manages the events
that make up the entire production process, from planning to the end of production. You or
your partners can report process steps during manufacturing. In this way, the transparency of
the manufacturing process is ensured. In most cases, companies use this data only for
internal purposes and internal transparency. To ensure the transparency of planned and
actual events, you can, however, use SAP Event Management (SAP EM) to report events to
external parties, for example, customers, subcontractors, or sold-to parties. You can use
various information channels to report these events.

(C) SAP AG 220


Example of Processing a Machine Breakdown in the
Manufacturing Process
The following figure provides an example of a manufacturing process that is relevant to
supply chain event management:

Production Production
Order 1 Order 2

Work
Center 1
Machine Maintenance
Breakdown Notification by
Work Process Operator
Center 2

APO Alert
SAP EM Informs
Production Planner

 The line personnel (for example, the process operator) identify a machine breakdown
and create an appropriate maintenance notification.
 SAP EM triggers the creation of an SAP APO alert that informs the production planner
that one of the production orders that have been scheduled (released) for this line is at
risk of not being processed.
 SAP EM tracks the processing of the malfunction notification to the point when the
malfunction has been repaired.
 You can evaluate the effects at a later time. For example, you can check the number of
production orders that had to be rescheduled, and, in this way, you can draw
conclusions about the quality of the original planning.

(C) SAP AG 221


Use in Order Fulfillment
In order fulfillment, the supply chain event management-relevant process begins with the
creation of the sales order. After the sales order has been created, you can send an event
message to the customer (for example, by e-mail) containing information about how to
monitor the status of the process in the Internet. The outbound delivery commences after
picking, packing, and loading. All the partners involved, including logistics providers and
forwarding agents, ensure the information flow to SAP Event Management reporting by
sending event messages both for deliveries that arrive on time and for unexpected events.
The availability of tools for monitoring and visibility purposes provides transparency for both
the customer and for partners at each stage of order fulfillment. Both parties can monitor
planned events and their actual occurrence.
The following figure provides an overview of the connection between the processes in order
fulfillment and in SAP Event Management:

(C) SAP AG 222


Use in Asset Management
In the area of asset management, supply chain event management (SCEM) is primarily
concerned with high-value, movable assets (for example containers, cylinders, or vehicles).
On the one hand, the life cycle of these assets including the owners, conditions, and location
needs to be managed. On the other hand, these assets contain and transport goods. These
goods each represent a separate process to be monitored: from the customer purchase order
through packing, loading into an asset, and shipment to the customer all the way to unloading
the asset, and returning and cleaning it. The processes come to an end as soon as the
customer pays.

(C) SAP AG 223


Example Life Cycle of a Gas Cylinder

GAS CYLINDER
New/Empty

Invoice Clean Fill

Return to Depot Add to Stock

Transfer to
Customer Pick

 You fill the new or empty gas cylinder and add it to your stock.
 The customer orders the number of gas cylinders that are required and you retrieve the
appropriate number.
 The customer receives the filled gas cylinders and returns them to your depot once
they are empty.
 You:
 Create the invoice
 Clean the gas cylinder

(C) SAP AG 224


Processes in Supply Chain Event Management
Purpose
The main areas of supply chain event management (SCEM) are:
 Determining the SCEM relevance of an application object and transferring the SCEM-
relevant data to SAP Event Management (SAP EM)
 Reporting events and triggering follow-up activities
 Monitoring and evaluating processes
 Evaluating in a data warehouse system

(C) SAP AG 225


Determining the SCEM relevance and creating SCEM
data
You are processing a business transaction (for example, creating a sales document) in the
application system. At the same time, the system uses the condition or conditions that have
been defined for SCEM relevance to check if SAP EM is to manage this business process
(see Business Process Type [Page 21]).
If the business process is SCEM-relevant, information is transferred from the application
system (for example, from shipments, manufacturing orders, or service orders) to SAP EM.
SAP EM uses this data to:
 Create an object that represents the application object [Page 18] (event handler [Page
43])
 Create additional information (for example, parameters or expected events that is
relevant to processing in SAP EM. Examples of this information include dates, material
descriptions, or customer addresses.
SAP EM can use this information to compare expected events with actual events or to
notify those involved in the supply chain, for example.
SAP EM can also transfer this information to back end systems (for example, a data
warehouse system).
See also: Application Object Type [Page 23], Data Transfer from the Application System
[Page 35], and Event Handler Creation [Page 56].

(C) SAP AG 226


Reporting events and triggering follow-up activities
When you report events to SAP EM, it processes the data that has been transferred:
 It compares the data reported (for example, time, quantity, and location) with the
expected events (for example, Arrival at Customer, Departure from Warehouse A).
SAP EM can trigger follow-up activities in critical situations (for example, notify a
partner).
 SAP EM updates the data of the event handlers belonging to the relevant event
message to ensure that it displays the current process progress in response to your
event handler queries.
 SAP EM uses a rule set to trigger a follow-up activity in response to an event message.
This rule set contains the expected events, the trigger for activities (for example, an e-
mail notification or triggering follow-up activities in an application system), and the
query authorizations, for example.
You report events to SAP EM in various ways (for example, in the Internet or using EDI).
SAP EM uses the tracking ID to assign the event message [Page 88] to the relevant event
handler.
See also: Event Reporting [Page 85], Evaluation in the Rule Set [Page 116], and Reactions to
and Actions for Events [External].

(C) SAP AG 227


Monitoring and evaluating processes
SAP EM offers various options for monitoring and evaluating process flows. These allow you
to recognize critical situations more rapidly and to react accordingly. In this way, you can
prevent delays to deliveries or production downtime, for example.
 In SAP EM you can monitor and evaluate business processes and processing within
the company and are therefore informed when problems occur in the process flow.
 You can make external queries to SAP EM in the Internet. You provide all those
involved in the supply chain, including external partners and customers, with the
current status of the business processes at any time.
Extensive authorization and layout concepts ensure that data in the Internet is clear
and can be entered or selected safely.
See also: Process Monitoring and Evaluation [External], Reports for Internal Monitoring and
Evaluation of Processes [Page 170], and Connection to the Computing Center Management
System [Page 181].

(C) SAP AG 228


Evaluating in a data warehouse system
You can also execute additional evaluations and valuations after the business process has
been completed. To do this, you connect SAP EM to a data warehouse system, (for example,
SAP NetWeaver Business Intelligence [Page 183]) and you make analytical queries. This
allows you, for example, to evaluate and valuate the quality of performance using key figures.
The system uses standard extractors to select the information from SAP EM that is relevant to
the data warehouse system. The system updates existing key figures or provides new ones.

(C) SAP AG 229


SAP Event Management User
Definition
Multiple employees and partners can be involved in the processes that SAP Event
Management (SAP EM) tracks or are interested in related information. You can tailor the
queries and entries that you make for these processes to your own requirements, for
example, by appropriately configuring the Web interface (classic) [External]).

Use
The following user groups use SAP EM:
 People who want to receive either information about actual events that have already
occurred or static information about the status of the processes within the supply chain.
This includes people in the following roles:
 Customer
Queries actual information, for example, a car dealer queries delivery dates from
the sales representative using a sales order
 Customer Advisor
Accesses actual information and status, for example, for customer inquiries
 Employee
Tracks the processes, for example, within planning, procurement,
manufacturing, and warehouse management
Reacts to unexpected situations
 Manager
Checks if the performance of the service providers and their confirmation of this
performance corresponds with the agreements and the expected events [Page
77] defined
 People who report information about actual events to SAP EM. These people send
information using EDI, BAPI, XML, or the Internet, for example, a service provider
reports a departure.
 People involved in the administration of SAP EM. They complete the Customizing when
SAP EM is initially set up and check all technical process flows within SAP EM, from
the arrival of event messages, through reactions by SAP EM to events, to the archiving
of event handlers [Page 43] and event messages [Page 88].

(C) SAP AG 230


Administration
Purpose
This component contains information about:
 Processing control [Page 234]
 Logging [External]
 The Computing Center Management system [Page 181]
 Consistency checks [Page 232] in SAP Event Management Customizing
 Archiving in SAP Event Management [External]
 The application interface [Page 33]

(C) SAP AG 231


Consistency Checks for SAP EM Customizing
Use
You can execute consistency checks for SAP Event Management (SAP EM) Customizing on
the following objects:
 System parameters
The system checks that the system parameters assigned to all the extension tables
that have been defined have the correct data format and length.
 Extension tables
The system checks the following for each extension table defined:
 If it is active, but an invalid data format is used in a field
 If it is new, but not active
 If it has been changed, but is not active
 If it does not exist
You can specify that the system checks used and unused extension tables.
 Checking application system parameters against SAP EM parameters
The system checks that the parameters defined in the application system are
consistent with those defined in SAP EM.
You can specify the following restrictions:
 The mapping log(s) that are to be checked
 The application system(s) that are to be checked
 The application object type(s) that are to be checked
The system queries all the application system’s info and control parameters for each
mapping log, application system, and application object type. It then compares these
parameters with those in SAP EM.
It checks that all info and control parameters have the correct data format and the
correct data length.
 Foreign keys in Customizing tables
You can select all SAP EM Customizing tables that belong to packages E or C and
begin with the prefix /SAPTRX/ for checking.

We recommend that you execute this consistency check for Web interface and
rule set Customizing.

You can use the following, for example, as selection criteria:


 Foreign key /SAPTRX/UC* to check the Web interface Customizing
 The following foreign keys to check the rule set Customizing
/SAPTRX/RULESET
/SAPTRX/EM_*
/SAPTRX/ACT*

(C) SAP AG 232


It may take some time for the system to check the foreign keys in the
Customizing tables, in particular, if you have completed extensive Customizing
in the application system and in SAP EM.

Activities
On the SAP Easy Access screen for Event Management, choose Administration 
Consistency Checks in Customizing.

(C) SAP AG 233


Processing Control
Use
You use processing control to:
 Trigger expected event monitoring [Page 81] so that SAP Event Management (SAP
EM) reacts accordingly (for example, sends an alert)
 Trigger subsequent processing of unprocessed event messages [Page 235] for locked
event handlers
 Trigger the subsequent addition of an event handler [Page 235] to a locked event
handler set
 Resend application object data for event handlers.
When you try to update event handler data by sending application objects to SAP EM,
it may be the case that the event handler is locked by other processing (for example,
momentary processing of an event message).
To ensure that the system updates the event handler with the data sent once the lock is
released, it temporarily stores the data in a database table (buffer).
This background job checks at regular intervals if data is contained in the database
table and then tries to process it. It updates the event handler that was previously
locked with this data, if necessary.
 Delete networks in the document flow [Page 197].
A higher-level interface is available for all these SAP EM background jobs where you can
schedule the monitoring and processing of the respective objects.

Activities
On the SAP Easy Access screen for Event Management, choose Administration 
Processing Control  Schedule Background Jobs for Event Management.

(C) SAP AG 234


Locked Event Handler or Event Handler Set
Processing
Use
You can schedule these background jobs in SAP Event Management (SAP EM) to execute
the following:
 Subsequent processing of event messages that arrive for an event handler at a time
when SAP EM is locking it

For example, somebody saves a shipment that updates an event handler, while
you are simultaneously trying to send an event message to SAP EM for this
event handler. SAP EM does not process this event message as the data
update from the shipment is locking the event handler. In order that SAP EM
processes the event message for this event handler at a later time, you have
scheduled the appropriate background job correspondingly.
 Assign an event handler once again to an event handler set that SAP EM is locking

For example, a colleague assigns an event handler to an event handler set. In


doing this, the colleague locks this set. You simultaneously try to assign another
event handler to this event handler set. To ensure that, in spite of the temporary
lock, SAP EM assigns your event handler to the set, you have scheduled the
appropriate background job.

Activities
On the SAP Easy Access screen for Event Management, choose Administration 
Processing Control  Schedule Background Jobs for Event Management.

(C) SAP AG 235


Roles for SAP Event Management
You can use the following roles in SAP Event Management:
 SAP EM Administrator for the Application System [Page 237]
 SAP Event Management Administrator [Page 238]
 SAP Event Management User [Page 239]

(C) SAP AG 236


SAP EM Administrator for the Application System
Technical name: /SAPTRX/SAP_AS_ADMIN

Tasks
You can use this role to configure the settings for creating event handlers and sending event
messages from application objects.

Activities in SAP Event Management


Activity Transaction code
Display Application Log for Event Handling /SAPTRX/ASAPLOG
Define Application Object Types and Event Types /SAPTRX/ASC0AO
Define Application Parameters /SAPTRX/ASC0AP
Assign Users to Scenarios /SAPTRX/ASC0SCU
Assign Application Object Types, Event Types, /SAPTRX/ASC0SD1
and SAP EM Relevance Conditions to Scenarios
Assign SAP EM Relevance Functions and /SAPTRX/ASC0SD2
Extractors to Scenarios
Define SAP EM Relevance Conditions /SAPTRX/ASC0TC
Define SAP EM Interface Functions /SAPTRX/ASC0TF
Define Business Process Types /SAPTRX/ASC0TO
Define SAP EM Systems /SAPTRX/ASC0TS
Display ALE Customizing SALE
RFC Destinations (Display and Maintain) SM59
This role also has the general authorization for system administration. This includes, for
example, the authorization to access systems using Remote Function Call (RFC) and to
maintain tables.

(C) SAP AG 237


SAP Event Management Administrator
Technical name: /SAPTRX/SAP_EM_ADMIN

Tasks
You can use this role to execute the following:
 Configure the settings for creating event handlers
 Run reports for displaying or changing event handler data
 Run reports for monitoring event handlers
 Send event messages

Activities in SAP Event Management


Activity Transaction code
All SCEM-relevant activities in SAP EM All transactions that begin with /SAPTRX/*
Exception: All transactions that are found in the Exception: All transactions that begin with
application system /SAPTRX/AS*
Computing Center Management System (CCMS) RZ20
Monitoring
CCMS Customizing Monitor Architecture RZ21
Archive Administration SARA
Table History SCU3
Application Log: Display Logs SLG1
Display ALE Customizing SALE
RFC Destinations (Display and Maintain) SM59
This role also has the following general authorizations for:
 System administration
This includes, for example, the authorization to access systems using Remote Function
Call (RFC) and to maintain tables.
 SAP EM
The role has the authorization, for example, to:
 Change and display event handlers
 Make changes in the event handler list
 Send event messages

(C) SAP AG 238


SAP Event Management User
Technical name: /SAPTRX/SAP_EM_USER

Tasks
You can use this role to execute the following:
 Run reports for displaying event handler data
 Enter and send event messages
 Update event handler data by reporting events

Activities in SAP Event Management


Activity Transaction Code
Display Expected Event Overdue List /SAPTRX/EE_OVD_LIST
Display Last Reported Event List /SAPTRX/EH_LAST_EVT
Display Event Handler List /SAPTRX/EH_LIST
Display List of Event Handlers with a Specific /SAPTRX/EH_LIST_STAT
Status Attribute
Display Event Handler Set Browser /SAPTRX/EH_SET
Display Event Message Processing Error List /SAPTRX/ER_MS_LIST
Display Event Message Processing Status List /SAPTRX/EVM_STATUS
Process Buffered Event Messages /SAPTRX/MI03
Display Rule Sets /SAPTRX/TSC0TRD
Display “My List” as the Web Interface Start Page /SAPTRX/WCL_FAVORITE
Display “Quick Search” as the Web Interface /SAPTRX/WCL_QUICK
Start Page
Display “Search” as the Web Interface Start Page /SAPTRX/WCL_SEARCH
Display “Send Event Messages” as the Web /SAPTRX/WCL_SEND
Interface Start Page

Example

(C) SAP AG 239


Defining authorization as an administrator to display a
customer’s event handler data
A user’s authorization comprises a combination of role and authorization profile.
 The role determines the activities a user can execute.
 The authorization profile, which you define in SAP Event Management (SAP EM),
determines the SAP EM data that a user can work with (create, display, change, or
evaluate).
 You use parameters to define the combination of role and authorization profile.
 You define an authorization parameter in the authorization profile.
 You define the same parameter in the role.
...

1. Defining roles
You define a role Z_Smith (transaction PFCG) that is based on the role
/SAPTRX/SAP_EM_USER.
You assign the following authorization data to the role.
 Activity 03 (display event handler information for queries to SAP EM) for
authorization object X_EM_EH
 Parameter <SHIP_TO_PARTY> with value <Customer Smith>
For more information about users and roles, see the SAP Library under SAP
Technology Components  SAP Web Application Server  Security (BC-SEC) 
Users and Roles (BC-SEC-USR).
2. SAP EM Customizing
You have carried out Customizing for SAP EM (for example, defined control
parameters, event handler types, and parameter mapping).
3. Defining an authorization parameter and assigning the authorization profile
 You define control parameter <SHIP_TO_PARTY> as the authorization
parameter <TRA10_CUSTOMER>.
 You assign the authorization parameter <TRA10_CUSTOMER> to an
authorization profile <TRA10_DELIV>.
 You assign the authorization profile <TRA10_DELIV> to event handler type
(EHT) <TRA10_DELIV>.
For more information about defining authorization profiles, see the Implementation
Guide (IMG) for Event Management  Authorizations and Filters  Define
Authorization Profiles.
4. Consequence of the authorizations defined
 Your user creates a shipment document that contains information about
customer Smith.
 The application system sends this information to SAP EM when saving the
document.
 SAP EM creates an event handler in accordance with Customizing.
 Customer Smith requests data from SAP EM. He or she can see only event
handlers with EHT <TRA10_DELIV> that have the authorization data Parameter
<SHIP_TO_PARTY> equals <Customer Smith>.
 He or she cannot change or send this data, in accordance with your role
definition Z_Smith (see point 1).

(C) SAP AG 240


Data Archiving
With the increased use of a productive business application, the volume of master data and
transaction data in the system database can grow rapidly, which can, in turn, lead to reduced
performance and increased costs. SAP data archiving, an SAP NetWeaver function, enables
you to control your data volume on a long-term basis by relocating data that is no longer
needed in the current business processes to archive files. Here, the data remains available
for read-only access.

The data archiving solution in the application-specific areas is based on the SAP standard
solution for data archiving, which so far has been used in ERP solutions, for example. Before
you start archiving, we recommend that you familiarize yourself with the fundamentals of SAP
data archiving. For more information about data archiving, see Introduction to Data Archiving.

Overview of Archiving Documentation


To enable you to access the information that you need for your archiving more quickly, the
documentation is structured as follows:

 The introduction to data archiving explains the basics of SAP data archiving and
describes the relevant processes and procedures. This is indispensable reading for
understanding data archiving.

 The documentation for data archiving in the application-specific area contains specific
information about using the relevant archiving objects to archive business objects.

(C) SAP AG 241


Archiving with Archive Development Kit (ADK)
Data Archiving – a service provided by SAP NetWeaver – removes mass data that the system
no longer needs online, but which must still be accessible at a later date if required, from the
database. The following illustration demonstrates the archiving process: You use archiving
objects to write documents to archive files that can be stored on other media .

Online Online/Nearline Offline

Display
Archive Access

Database File System Storage System

Database Tables Archive Files Archive Files

Applica-
tion Data Writing and Deleting Storing

Data in the database can only be archived using archiving objects that describe the data
structure and context.

Financial Accounting documents are archived using the archiving object


FI_DOCUMNT. It includes the document header, company code-dependent
postings, change documents, SAPscript texts, and other elements.

Integration
For the majority of the archiving objects the SAP Data Archiving concept is based on the
Archive Development Kit (ADK).
For some applications it is possible to start archiving directly from the application menu. In
these cases the application-specific parameters, such as the archiving object or the archiving
program appear as default values.
Archiving objects for each application component are predefined in the system. Their
structures are described in the application-specific sections.

Features
The archiving procedure is divided into three main steps:
 Creation of archive files
In the write phase the data to be archived is written sequentially into newly created
archive files.
 Delete from the database
The delete program reads the data from the archive files and then deletes it from the
database.

(C) SAP AG 242


 Storage of archive files
The newly created archive files can then be moved to a storage system or copied to a
tape. The removal to an external storage system can be triggered manually or
automatically. It is also possible to store the data before the delete phase.
The archiving programs are generally scheduled in the background. However, they can also
run in online mode.

(C) SAP AG 243


Archiving in SAP Event Management
If you no longer need event handlers, event messages, or event handler sets, you can either
archive and delete them, or you can delete them without previously archiving them. If you
delete event handlers, event messages, or event handler sets, SAP Event Management also
deletes any existing change documents (see Logging with Change Documents [Page 198]).

You can archive the following business objects in SAP Event Management:

Document Category Archiving Object

Event handlers /SAPTRX/A0 [Page 246]

Event messages /SAPTRX/A1 [Page 248]

Event handler sets SAPTRX_A2 [Page 250]

Event handlers SAPTRX_EH [Page 260]

Event messages SAPTRX_EVM [Page 262]

In addition to calling archiving via the archive administration (transaction SARA), you can also
schedule archiving as a regular background job.

For more information, see SAP Help Portal at http://help.sap.com SAP NetWeaver SAP
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management
by Key Capability Data Archiving (CA-ARC) Introduction to Data Archiving (CA-ARC)
Archiving Object .

Implementation Considerations
You have specified the archiving object-specific Customizing for the archiving objects. For
more information, see Customizing for SAP Event Management under Archive and Delete
SAP Event Management Objects Define Archiving-Object-Specific Customizing . The
following archiving objects are delivered for SAP Event Management:

 Archiving object for event handlers/SAPTRX/A0

 Archiving object for event messages/SAPTRX/A1

 Archiving object for event handler setsSAPTRX_A2

The following archiving objects are delivered for SAP Event Management for an archiving
concept for scenarios with a high data volume:

 Archiving object for event handlers SAPTRX_EH

 Archiving object for event messages SAPTRX_EVM

For more information about the archiving in scenarios with a high data volume, see Data
Archiving for High Data Volumes [Page 252].

If you have decided on a specific archiving concept, switching to another one leads to a
disruption. You cannot seamlessly access data from different archive sources.

(C) SAP AG 244


Features
For information about how you can archive SAP Event Management data in the standard
system, see the descriptions for the individual archiving objects:

 Archiving Event Handlers (SCM-EM) [Page 246]

 Archiving Event Messages (SCM-EM) [Page 248]

 Archiving Event Handler Sets (SCM-EM) [Page 250]

For information about how you can archive SAP Event Management data for scenarios with a
high data volume, see the descriptions for the individual archiving objects:

 Archiving Event Handlers (SCM-EM) [Page 260]

 Archiving Event Messages (SCM-EM) [Page 262]

(C) SAP AG 245


Archiving Event Handlers (SCM-EM)
You use the archiving object /SAPTRX/A0 to archive and delete event handlers.

When you no longer need event handlers, you can either simply delete them or you can first
archive them and then delete them. If you only want to delete an event handler, you use the
/SAPTRX/DELETE_EH report for deleting inactive event handlers. You can also use this
report to delete inactive event handlers belonging to an event handler set. The residence time
that you have configured is used as the criterion to archive an event handler. When you
delete event handlers, SAP Event Management also deletes any existing change documents.

The deletion reports are designed in particular for deleting test data.

You archive an event handler that belongs to one or more event handler sets by
deactivating and archiving the entire event handler set (see Archiving Event Handler Sets
(SCM-EM) [Page 250]).

You can specify that event handlers are archived automatically by defining appropriate
activity parameters and using them in function modules within a rule.

You can interrupt a write run for the archiving object at any time.

For more information about performance and about terminating the archiving procedure,
see SAP Notes 69143 and 77305.

For more information, see Customizing for SAP Event Management under Archive and
Delete SAP Event Management Objects Define Residence Times for Archiving or
Deleting .

We recommend that you test higher values for the commit counter.

Structure
Tables
SAP Event Management uses the archiving object /SAPTRX/A0 to archive data from various
tables. For more information about how to display the table names, see Tables and Archiving
Objects [External].

Programs
The following programs are delivered for the archiving object /SAPTRX/A0:

Program Function

/SAPTRX/ARCHIVE_A0_WRITE Write

/SAPTRX/ARCHIVE_A0_DELETE Delete

/SAPTRX/ARCHIVE_A0_RELOAD Reload

Write
You must have deactivated the event handlers to enable you to archive them. From the
archive administration under Customizing Application-Specific Customizing , you can
call the transaction Define Residence Times for Archiving or Deleting (/SAPTRX/RESTM) in

(C) SAP AG 246


Customizing for SAP Event Management. You can define the residence times for event
handlers in this transaction. SAP Event Management checks if the difference between the
date on which the objects were created and the current date is greater than the residence
time. If this is the case, SAP Event Management archives and deletes the event handlers
along with all the relevant data. If change documents exist for the event handler, SAP Event
Management deletes them too. If you do not specify an application system or application
object type, SAP Event Management uses the creation date of the event handler and the
default value of 100 days to calculate the residence time.

For more information, see Customizing for SAP Event Management under Archive and
Delete SAP Event Management Objects Define Residence Times for Archiving or Deleting
.

Delete
If you have chosen Test Mode, SAP Event Management starts the delete program with the
test run variant /SAPTRX/TEST.

If you have not chosen Test Mode, SAP Event Management starts the delete program with
the productive run variant /SAPTRX/PROD.

For more information, see Deleting Archived Data from the Database.

Reload
Reload data in exceptional situations only (see Reloading Data).

The program displays the number of objects that were imported and actually reloaded. This is
the number of event handlers (header data) and not the number of all database sets inserted.

For more information, see Variant Settings for Writing (SCM-EM) [Page 264].

Integration
Display Function for Archived Event Handlers
The archiving object /SAPTRX/A0 only supports a technical view in the Archive Explorer of
the Archive Information System. This view is similar to the display in transaction SE16.

(C) SAP AG 247


Archiving Event Messages (SCM-EM)
You use the archiving object /SAPTRX/A1 to archive and delete event messages.

When you no longer need event messages, you can either simply delete them or you can first
archive them and then delete them. If you only want to delete an event message, you use the
report /SAPTRX/DELETE_EVMSG. The residence time that you have configured is used as
the criterion to archive an event message. When you delete event messages, SAP Event
Management also deletes any existing change documents.

SAP Event Management does not process event messages for event handlers that are
already set to Inactive on the basis of a rule in the rule set. However, you can enable an
event message processing also for these event handlers. In this case, data
inconsistencies between the data in the system and the data in the archive can occur.

For more information, see Customizing for SAP Event Management under Event
Messages, Status Queries, and Web Interface Define Criteria for Event Message
Processing .

The deletion reports are designed in particular for deleting test data. You can also
automatically archive the relevant event messages during an automatic archiving session
for an event handler or an event handler set. You can interrupt a write run for the
archiving object at any time. For more information about performance and about
terminating the archiving procedure, see SAP Notes 69143 and 77305. For more
information, see Customizing for SAP Event Management under Archive and Delete
SAP Event Management Objects Define Residence Times for Archiving or Deleting .

We recommend that you test higher values for the commit counter.

Structure
Tables
SAP Event Management uses the archiving object /SAPTRX/A1 to archive data from various
tables. For more information about how to display the table names, see Tables and Archiving
Objects.

Programs
The following programs are delivered for the archiving object /SAPTRX/A1:

Program Function

/SAPTRX/ARCHIVE_A1_WRITE Write

/SAPTRX/ARCHIVE_A1_DELETE Delete

/SAPTRX/ARCHIVE_A1_RELOAD Reload

Write
In the archive administration under Customizing Application-Specific Customizing , you
can call the transaction Define Residence Times for Archiving or Deleting (/SAPTRX/RESTM)

(C) SAP AG 248


in Customizing for SAP Event Management. You can define a global residence time that
applies to all event messages. You can, however, also define a residence time for a tracking
ID code set that only applies to event messages for this tracking ID code set. SAP Event
Management checks if the difference between the date on which the objects were created
and the current date is greater than the residence time. If this is the case, SAP Event
Management archives and deletes the event messages along with all the relevant data. If you
do not specify a residence time, SAP Event Management uses the creation date of an event
message and the default value of 100 days to calculate the residence time.

If you want to define residence times for a tracking ID code set, in Customizing for SAP Event
Management, choose Archive and Delete SAP Event Management Objects Define
Residence Times for Archiving or Deleting and then choose Residence Times for Event
Message Archiving 1 in the navigation tree.

If you want to define global residence times for event messages, in Customizing for SAP
Event Management, choose Archive and Delete SAP Event Management Objects Define
Residence Times for Archiving or Deleting and then choose Residence Times for Event
Message Archiving 2 in the navigation tree.

For more information, see Customizing for SAP Event Management under Archive and
Delete SAP Event Management Objects Define Residence Times for Archiving or Deleting
.

Delete
If you have chosen Test Mode, SAP Event Management starts the delete program with the
test run variant /SAPTRX/TEST.

If you have not chosen Test Mode, SAP Event Management starts the delete program with
the productive run variant /SAPTRX/PROD.

For more information, see Deleting Archived Data from the Database.

Reload
Reload data in exceptional situations only (see Reloading Data).

The program displays the number of objects that were imported and actually reloaded.

For more information, see Variant Settings for Writing (SCM-EM) [Page 264].

Integration
Display Function for Archived Event Messages

The archiving object /SAPTRX/A1 only supports a technical view in the Archive Explorer of
the Archive Information System. This view is similar to the display in transaction SE16.

(C) SAP AG 249


Archiving Event Handler Sets (SCM-EM)
You use the archiving object SAPTRX_A2 to archive and delete event handler sets.

When you no longer need event handler sets, you can archive them. The residence time that
you have configured is used as the criterion to archive an event handler set. When you delete
event handler sets, SAP Event Management also deletes any existing change documents.

You archive an event handler set by deactivating and archiving the entire set.

If you want to delete inactive event handlers in an event handler set, you use the report
/SAPTRX/DELETE_EH for deleting inactive event handlers. The deletion reports are
designed in particular for deleting test data.

When you delete an application object in the SAP application system, SAP Event
Management marks the corresponding event handlers as deleted, but does not physically
delete them from the database.

You can specify that event handler sets are archived automatically by defining
appropriate activity parameters and using them in function modules within a rule.

You can interrupt a write run for the archiving object at any time.

For more information about performance and about terminating the archiving procedure,
see SAP Notes 69143 and 77305.

For more information, see Customizing for SAP Event Management under Archive and
Delete SAP Event Management Objects Define Residence Times for Archiving or
Deleting .

We recommend that you test higher values for the commit counter.

Structure
Tables
SAP Event Management uses the archiving object SAPTRX_A2 to archive data from various
tables. For more information about how to display the table names, see Tables and Archiving
Objects.

Programs
The following programs are delivered for the archiving object SAPTRX_A2:

Program Function

/SAPTRX/ARCHIVE_A2_WRITE Write

/SAPTRX/ARCHIVE_A2_DELETE Delete

/SAPTRX/ARCHIVE_A2_RELOAD Reload

(C) SAP AG 250


Write
You must have deactivated the event handler sets to enable you to archive them. To do so, in
Customizing for SAP Event Management, choose Reactions to Event Messages Define
Rule Sets and then choose Rule Sets Activity Methods in the navigation tree. Use
the activity method EHSET_SET_INACTIVE to deactivate the event handler set.

If you do not specify a residence time, SAP Event Management uses the creation date of an
event handler set and the default value of 100 days to calculate the residence time.

For more information, see Customizing for SAP Event Management under Archive and
Delete SAP Event Management Objects Define Residence Times for Archiving or Deleting
.

Delete
If you have chosen Test Mode, SAP Event Management starts the delete program with the
test run variant /SAPTRX/TEST.

If you have not chosen Test Mode, SAP Event Management starts the delete program with
the productive run variant /SAPTRX/PROD.

For more information, see Deleting Archived Data from the Database.

Reload
Reload data in exceptional situations only (see Reloading Data).

The program displays the number of objects that were imported and actually reloaded. This is
the number of event handler sets and not the number of all database sets inserted.

For more information, see Variant Settings for Writing (SCM-EM) [Page 264].

Integration
Display Function for Archived Event Handler Sets
The archiving object SAPTRX_A2 only supports a technical view in the Archive Explorer of the
Archive Information System. This view is similar to the display in transaction SE16.

(C) SAP AG 251


Data Archiving for High Data Volumes
You can use this archiving concept for scenarios with a high data volume. For these
scenarios the archiving of data on time is an essential requirement to avoid a data overflow.
This archiving concept uses the following archiving objects:

 SAPTRX_EH Event Handler (see Archiving Event Handlers (SCM-EM) [Page 260]

 SAPTRX_EVM Event Messages (see Archiving Event Messages (SCM-EM) [Page


262]

To ensure data integrity, this archiving concept considers the logical relationship between
event handlers and event messages.

You can use one of the following archiving sequences:

 Archiving Sequence Event Handler and Event Message [Page 254]

This archiving sequence ensures that the event message data is available for as long
as possible depending on how you set up the write and delete program for archiving
event messages. For example, this enables you to use the data as selection criteria
for searches.

The event handler and the event message reside in application tables because once
an event handler or an event message is archived, you can use only a restricted set
of selection criteria.

 Archiving Sequence Event Message and Event Handler [Page 256]

This archiving sequence ensures that the database volume is reduced. Since the
focus in this archiving sequence is mainly on event handlers, the system archives
event messages as soon as possible. Therefore, you can only use the set of selection
criteria for the event handler.

If you use this archiving concept, consider the following:

 The archiving and display of event handler sets is not supported.

 The display of the document flow in the Web interface is not supported.

 If you assign an archiving profile to a user profile, you cannot use the Retrieve Event
Handler Messages for Higher-Level EH option. For more information, see SAP Note
1350818.

 If you define archive information structures, you must take certain technical
considerations into account. For more information, see SAP Note 1350818.

(C) SAP AG 252


Prerequisites
 You have made the archiving settings in Customizing for SAP Event Management
under Archive and Delete SAP Event Management Objects .

 To query and display data from the database together with already archived data, you
have made the necessary settings in Customizing. For more information, see
Customizing for SAP Event Management under Archive and Delete SAP Event
Management Objects Query and Display Archived Data .

You have completed the following activities:

o You have made the Customizing settings for the archiving objects
SAPTRX_EH for the event handler object or SAPTRX_EVM for the event
message object in the transaction for maintaining archiving objects
(transaction AOBJ).

o You have created and activated the field catalog and archive information
structure for the archiving object using the Archive Retrieval Configurator
(transaction SARJ).

o You have defined the archiving sequence.

You cannot change the archiving sequence in Customizing once you


save.

o You have defined an archiving profile and a user profile.

o You have assigned the archiving profile to the user profile that is linked to the
Web interface transaction.

o You have defined the residence time for the archiving object.

(C) SAP AG 253


Archiving Sequence Event Handler and Event
Message
This process represents an archiving sequence. You can use this process to keep event
message data for as long as possible in SAP Event Management.

You begin the archiving process by archiving the event handlers. In preprocessing, the
system marks all inactive event handlers with a positive residence time check as archived.
This means that logically these event handlers are archived. Thereafter, the system writes all
marked event handlers into the archive. In a second step you archive the corresponding event
messages. The system archives all event messages that have a positive residence time
check and that are linked only to already archived event handlers.

A long residence time for event handler and event message objects in application tables
results in a higher requirement for database volume.

Prerequisites
For more information, see Data Archiving for High Data Volumes [Page 252].

Process
1. You deactivate an event handler in one of the following ways:

o Using a rule activity and a rule condition

If no incoming event message fulfills the rule condition, SAP Event


Management does not deactivate the related event handlers and they remain
in the system indefinitely.

o Scheduling the report /SAPTRX/ARCHIVE_EH_DEACTIVATE

To avoid data overflow, you can use this report to deactivate event handlers
manually.

2. You set up the preprocessing, write, and delete program for archiving event handlers
in the initial screen of the Archive Administration (transaction SARA).

1. The preprocessing program for the event handler archiving object


(SAPTRX_EH) checks for inactive event handlers with a positive residence
time check. The program marks these event handlers as archived. You can
no longer change existing data. For example, you cannot update application
object data or process a related event message. This status ensures there is
no data inconsistency between archived data and application data.

Logically the event handler has been archived, but technically it resides in
application tables.

2. The write program for the event handler archiving object selects all logically
archived event handlers and writes them into the archive.

3. The delete program for the event handler archiving object deletes the
archived event handlers from the application tables. It builds up the archive
index table according to the archive information structures maintained for the
archiving object.

(C) SAP AG 254


3. You set up the write and delete program for archiving event messages in the initial
screen of the Archive Administration (transaction SARA).

0. The write program for the event message archiving object (SAPTRX_EVM)
checks if the residence time for the event message archiving object is
positive. If it is positive and the event message is linked only to already
archived event handlers, the write program writes all event messages into the
archive. Event messages, which are linked to event handlers that have not
yet been archived are not written into the archive and reside in application
tables.

1. The delete program for the event message archiving object deletes the
archived event messages from the application tables and builds up the
archive index table according to the archive information structures maintained
for the archiving object.

You can still process event messages that are related to an inactive event handler (see
Overview of Possible Statuses of an Event Handler [Page 258]).

Result
The system has archived all event handlers that are set to inactive and have a positive
residence time check. The system also has archived all event messages that have a positive
residence time check and that are linked only to event handlers already archived.

(C) SAP AG 255


Archiving Sequence Event Message and Event
Handler
This process represents an archiving sequence. You can use this process if you do not want
to keep event message data for as long as possible in SAP Event Management.

If you archive event messages as soon as possible, the database volume is reduced.

You begin the archiving process by archiving the event messages. In the write program the
system writes all event messages with a positive residence time check into the archive. In a
second step, you archive all inactive event handlers with a positive residence time check.

Prerequisites
For more information, see Data Archiving for High Data Volumes [Page 252].

Process
1. You deactivate an event handler by doing one of the following:

o Using a rule activity and a rule condition

If no incoming event message fulfills the rule condition, SAP Event


Management does not deactivate the related event handlers and they remain
in the system indefinitely.

o Scheduling the report /SAPTRX/ARCHIVE_EH_DEACTIVATE

To avoid data overflow, you can use this report to deactivate event handlers
manually.

2. You set up the write and delete program for archiving event messages in the initial
screen of the Archive Administration (transaction SARA).

1. The write program for the event message archive object (SAPTRX_EVM)
checks if the residence time for the event message archiving object is
positive. If it is positive, the write program writes all event messages into the
archive. The system does not check if the corresponding event handler is
already archived.

2. The delete program for the event message archiving object deletes the
archived event messages from application tables and builds up the archive
index table according to the archive information structures maintained for the
archiving object.

3. You set up the preprocessing, write, and delete program for archiving event handlers
in the initial screen of the Archive Administration (transaction SARA).

0. The preprocessing program for the event handler archiving object


(SAPTRX_EH) checks for inactive event handlers with a positive residence
time check. The program marks these event handlers as archived. You can
no longer change existing data. For example, you cannot update application
object data or process a related event message. This status ensures there is
no data inconsistency between archived data and application data.

Logically the event handler has been archived, but technically it resides in
application tables.

(C) SAP AG 256


1. The write program for the event handler archiving object selects all logically
archived event handlers and writes them into the archive.

2. The delete program for the event handler archiving object deletes the
archived event handlers from application tables and builds up the archive
index table according to the archive information structures maintained for the
archiving object.

Result
The system has archived all event messages with a positive residence time check. It also has
archived all event handlers that are set to inactive and have a positive residence time check.

(C) SAP AG 257


Overview of Possible Statuses of an Event Handler
The search and display of both archived data and data from the application depends on the
status of the relevant event handlers. You can find an overview of these statuses below.

Prerequisites
You have made all the necessary Customizing settings for archiving in SAP Event
Management under Archive and Delete SAP Event Management Objects .

Features
This table gives an overview of the possible statuses of an event handler.

Indicator Event Indicator Event Handler Sending of


Handler Is Active Archived event
Comment
(/SAPTRX/EH_ACTIVE) (/SAPTRX/EH_ARCHIVED) messages is
is set is set possible

Standard
case: event
handler is
Yes No Yes
saved in
database and
is active.

Yes, if you
defined criteria
to allow the
system to send
Event
event message
handler is
to an event
No No saved in
handler that has
database but
been set to
is inactive.
Inactive in
Customizing for
SAP Event
Management.

Event
handler is
saved in
database and
logically
archived.
This means
that the
No Yes No archive
report is
already
executed but
the event
handler still
physically
exists in the
database.

(C) SAP AG 258


Indicator Event Indicator Event Handler Sending of
Handler Is Active Archived event
Comment
(/SAPTRX/EH_ACTIVE) (/SAPTRX/EH_ARCHIVED) messages is
is set is set possible

Event
handler is
archived.
This means
that the
deletion
No Yes No report is
already
executed and
the event
handler is
deleted in the
database.

Case 1: Event Handler is Active and Not Archived


In this standard case, SAP Event Management saved an event handler in the database and
marked it as active using the indicator /SAPTRX/EH_ACTIVE Event Handler Is Active. You
can send event messages for this event handler. SAP Event Management processes these
event messages depending on your Customizing settings. The system does not archive the
event handler.

Case 2: Event Handler is Inactive and Not Archived


In this case, SAP Event Management saved an event handler in the database but the event
handler is inactive. This means the indicator /SAPTRX/EH_ACTIVE Event Handler Is Active
is not set. In the standard case, you cannot send event messages for this inactive event
handler. SAP Event Management does not process these event messages. In Customizing
for SAP Event Management, you can define criteria to allow the system to forward or process
an event message for an event handler that has been set to Inactive on the basis of a rule in
the rule set. For more information, see Customizing for SAP Event Management under
Event Messages, Status Queries, and Web Interface Define Criteria for Event Message
Processing . The system does not archive the event handler.

Case 3: Event Handler is Inactive and Logically Archived


In this case, SAP Event Management saved an event handler in the database, but the event
handler is inactive. This means the indicator /SAPTRX/EH_ACTIVE Event Handler Is Active
is not set. SAP Event Management also archived the event handler logically. This means the
indicator /SAPTRX/EH_ARCHIVED Event Handler Archived is set and the archiving report has
already been executed. However, the event handler still physically exists in the database.
SAP Event Management does not process event messages that you send for the logically
archived event handler.

Case 4: Event Handler is Inactive and Archived


In this case, SAP Event Management saved an event handler in the database, but the event
handler is inactive. This means the indicator /SAPTRX/EH_ACTIVE Event Handler Is Active
is not set. SAP Event Management also archived the event handler. This means the indicator
/SAPTRX/EH_ARCHIVED Event Handler Archived is set, and both the archiving and the
deletion reports have already been executed. SAP Event Management deleted the event
handler in the database. The application does not process event messages that you send for
the archived event handler.

(C) SAP AG 259


Archiving Event Handlers (SCM-EM)
You use the archiving object SAPTRX_EH to archive and delete event handlers for high data
volumes (see Data Archiving for High Data Volumes [Page 252]).

You can archive and delete the event handlers that you no longer need.

SAP Event Management does not support archiving event handler sets and deleting
existing change documents

Event handlers can have different statuses. For an overview of possible statuses, see
Overview of Possible Statuses of an Event Handler [Page 258].

The archiving sequence is important for this archiving object. For more information, see the
following documents:

 Archiving Sequence Event Handler and Event Message [Page 254]

 Archiving Sequence Event Message and Event Handler [Page 256]

We recommend that you test higher values for the commit counter.

Structure
Tables
SAP Event Management uses the archiving object SAPTRX_EH to archive data from different
tables. For more information about how to display the table names, see Tables and Archiving
Objects [External].

Programs
The following programs are delivered for the archiving object SAPTRX_EH:

Program Function

/SAPTRX/ARCHIVE_EH_PREPROCESS Preprocessing

/SAPTRX/ARCHIVE_EH_WRITE Write

/SAPTRX/ARCHIVE_EH_DELETE Delete

/SAPTRX/ARCHIVE_EH_RELOAD Reload

Preprocessing
The program marks all inactive event handlers with a positive residence time check. Logically
the event handler object is now archived, but physically it still resides within application tables.
For more information, see the documentation for the preprocessing report
/SAPTRX/ARCHIVE_EH_PREPROCESS in SAP Event Management.

(C) SAP AG 260


Write
The program writes all event handlers that are marked as archived by the preprocessing
program in archive files. For more information, see the documentation for the write report
/SAPTRX/ARCHIVE_EH_WRITE in SAP Event Management.

Delete
The program deletes event handler data in the database after the write program has written
them to archive files. For more information, see the documentation for the delete report
/SAPTRX/ARCHIVE_EH_DELETE in SAP Event Management.

Reload
The program reloads event handler data from archive files back into the database. For more
information, see the documentation for the delete report /SAPTRX/ARCHIVE_EH_RELOAD in
SAP Event Management. Reload data in exceptional situations only. (see Reloading Data).

(C) SAP AG 261


Archiving Event Messages (SCM-EM)
You use the archiving object SAPTRX_EVM to archive and delete event messages for high
data volumes (see Data Archiving for High Data Volumes [Page 252]).

You can archive and delete the event messages that you no longer need. You cannot delete
existing change documents when you delete event messages. If the archive is used, the
display of event messages from superior event handlers in the hierarchy is not possible.

SAP Event Management does not process event messages for event handlers that are
already set to Inactive on the basis of a rule in the rule set. However, you can also enable
an event message processing for these event handlers. In this case, data inconsistencies
between the data in the system and the data in the archive can occur.

For more information, see Customizing for SAP Event Management under Event
Messages, Status Queries, and Web Interface Define Criteria for Event Message
Processing .

The archiving sequence is important for this archiving object. For more information, see the
following documents:

 Archiving Sequence Event Handler and Event Message [Page 254]

 Archiving Sequence Event Message and Event Handler [Page 256]

We recommend that you test higher values for the commit counter.

Structure
Tables
SAP Event Management uses the archiving object SAPTRX_EVM to archive data from various
tables. For more information on how to display the table names, see Tables and Archiving
Objects [External].

Programs
The following programs are delivered for the archiving object SAPTRX_EVM:

Program Function

/SAPTRX/ARCHIVE_EVM_WRITE Write

/SAPTRX/ARCHIVE_EVM_DELETE Delete

/SAPTRX/ARCHIVE_EVM_RELOAD Reload

Write
The program checks which selected event messages exceed the residence time and then
writes them in archive files. For more information, see the documentation for the write report
/SAPTRX/ARCHIVE_EVM_WRITE in SAP Event Management.

(C) SAP AG 262


Delete
The program deletes event message data in the database after the write program has written
them to archive files. For more information, see the documentation for the delete report
/SAPTRX/ARCHIVE_EVM_DELETE in SAP Event Management.

Reload
The program reloads event message data from archive files back into the database. For more
information, see the documentation for the delete report /SAPTRX/ARCHIVE_EVM_RELOAD
in SAP Event Management. Reload data in exceptional situations only (see Reloading Data).

(C) SAP AG 263


Variant Settings for Writing (SCM-EM)
When you schedule the write program, you must either enter an existing variant or create a
new variant. The variant contains the selection criteria for the data that you want to archive in
SAP Event Management.

Features
Writing Event Handlers
Define your selection criteria in the write variant of archiving object /SAPTRX/A0 as follows:

 Selection of application objects for archiving:

o Application system

o Application type

o Application object ID

 Further restrictions for the objects chosen:

o Creation date

o Creation time

o Updated date

o Updated time

o Activation date

o Activation time

o Deactivation date

o Deactivation time

 Additional configuration options:

o Technical options

o Write detailed log

o Archiving session note

(C) SAP AG 264


Writing Event Messages
Define your selection criteria in the write variant of archiving object /SAPTRX/A1 as follows:

 Selection of application objects for archiving:

o Tracking ID code set

o Tracking ID/number

o Sender code set

o Sender ID

o External event code set

o External event code ID

o Internal event code

 Further restrictions for the objects chosen:

o Event date

 Additional configuration options:

o Technical options

o Write detailed log

o Archiving session note

Writing Event Handler Sets


Define your selection criteria in the write variant of archiving object SAPTRX_A2 as follows:

 Selection of application objects for archiving:

o Event handler set profile ID

o Event handler set relation code

o Event handler set relation code ID

 Further restrictions for the objects chosen:

o Creation date

o Deactivation date

 Additional configuration options:

o Technical options

o Write detailed log

o Archiving session note

(C) SAP AG 265


System Installation and Integration
Purpose
SAP Event Management 9.0 is an add on of SAP Enhancement Package 1 for SAP
NetWeaver® 7.3. This means that it can be deployed on any application system with the
release level 7.31. The restriction to specific deployment options as described for former SAP
Event Management releases no longer applies.
If you use SAP R/3 as the application system, you must install the corresponding SAP R/3
Plug-In release on the SAP R/3 side, depending on the business objects (see Connection of
Business Objects [Page 272]) that you want to connect. As of SAP ECC 6.0, the SAP R/3
Plug-In is integrated in SAP ERP Central Component.
The system integration covers integration between the following systems:
 SAP Event Management and the application system

You have an SAP Event Management and an SAP Advanced Planning and
Optimization (SAP APO) that run in the same system. You must configure
different technical Remote Function Call destinations (RFC destinations) for
APO Core Interface (CIF) and for SAP Event Management.
 SAP Event Management and the systems that send event messages to SAP Event
Management
Various interfaces are available that you can optimize, where required (see Interfaces
in SAP Event Management [Page 280]). The most common interfaces are also
available in SAP NetWeaver Process Integration. You can use this to allow eXtensible
Markup Language (XML) as a file format for event messages.
For more information about integration, see Integration with SAP NetWeaver Process
Integration [Page 277].
 SAP Event Management and other systems to track messages and to trigger workflows
and alerts

For more information about system installation and integration, see SAP Service
Marketplace at service.sap.com/SCM  SAP SCM Technology 
Installation and Upgrade Overview.

(C) SAP AG 266


Integration Options for SAP Event Management
The following integration options are available for SAP Event Management:
 Connecting SAP Event Management to other SAP systems using predefined visibility
processes [External]
Connecting SAP Event Management to other SAP systems using SAP Basis Plug-In (see
Connection Using SAP Basis Plug-In [Page 269])
 Connecting business objects from SAP systems using Business Add-Ins (BAdIs)
The BAdI is implemented in the respective application (for example, in SAP APO). The
system uses the BAdI to call the required BAPI.
 Connecting SAP Event Management to external systems using Business Application
Programming Interfaces (BAPIs) and SAP NetWeaver Process Integration.

(C) SAP AG 267


Connection of SAP Systems
Use
You can connect SAP Event Management (SAP EM) to other SAP systems in the following
ways:
 Using SAP Basis Plug-In (PI Basis)
 Using SAP Exchange Infrastructure (XI)

We recommend that you use the application interface (PI Basis and SAP R/3
Plug-In) to connect SAP EM to other SAP systems. SAP has developed this
interface specifically for connecting SAP EM to an SAP system. You also get the
Customizing required for the connection with this connection point.
For more information about connecting to SAP systems, see
 Connection Using SAP Basis Plug-In [Page 269]
 Connection Using SAP R/3 Plug-In [Page 271]
 Connection of Business Objects [Page 272]

(C) SAP AG 268


Connection Using SAP Basis Plug-In
Use
You use SAP Basis Plug-In [Page 270] (Basis PI) to connect SAP Event Management (SAP
EM) to an SAP system. SAP Basis PI is a standardized connection between SAP systems
that enables data to be exchanged between the systems.
If you have installed an SAP R/3 system with release 4.0B or higher, an SAP EM application
interface is automatically available.
The SAP EM application interface consists of the following:
 Customizing transactions (for example, Define Business Process Types) for the
application system
 The tables in the application system that are relevant to SAP EM

The following figure provides an example of the connection between SAP Basis Plug-In and
SAP EM:

SAP
SAP R/3
R/3 Application
Application SAP
SAP Event
Event
Management
Management

SAP
SAPR/3
R/3Plug-In
Plug-In

Web
Web Application
Application
Server
Server

SAP
SAPBasis
BasisPlug-In
Plug-In

For release notes related to SAP Basis Plug-In, see SAP Service Marketplace at
http://service.sap.com  alias Basis-Plug-In  Media Center SAP
Basis Plug-In.

(C) SAP AG 269


SAP Basis Plug-In
Use
The SAP Basis Plug-In is a new software component that provides SAP components with BW
service API technology as well as functions from CRM Middleware, Supply Chain Event
Management, and Financial Basis to establish a connection to these systems.
The SAP Basis Plug-In is an Add-On that you can install on a SAP Web Application Server or
on another product that is based on SAP BASIS 620 and SAP ABA 620 or higher releases of
these software components.
Within SAP R/3 Enterprise, the SAP Basis Plug-In is a prerequisite for the SAP R/3 Plug-In.
The SAP Basis Plug-In and the SAP R/3 Plug-In must always have the same release level,
for example, PI 2004.1 and PI Basis 2004.1. When you are planning an upgrade for the SAP
R/3 Plug-In within SAP R/3 Enterprise, you must also upgrade the SAP Basis Plug-In as well.
As of SAP Basis Plug-In 2005.1, the release level of the two Plug-Ins no longer has to be the
same. However, the SAP R/3 Plug-In Support Package for PI 2004.1, which contains new
interfaces, still requires a particular SAP Basis Plug-In. For example, SAP R/3 Plug-In
Support Package 10 for SAP Plug-In 2004.1 requires the SAP Basis Plug-In 2005.1.
You only need to upgrade the SAP Basis Plug-In in one system within your system landscape
and you can then use the available SAP Basis Plug-In release in all the other systems within
the system landscape.
The release PIB 2004.1 Workplace Plug-In is part of the SAP Basis Plug-In for SAP Basis
640.
The SAP Basis Plug-In is downward compatible and has the same release and maintenance
strategy as the SAP R/3 Plug-In. SAP delivers it together with the SAP R/3 Plug-In. For more
information, see SAP Service Marketplace at service.sap.com/basis-plug-in
 SAP Plug-In  SAP Basis Plug-In  Releases.
For more information about the minimum Support Package level for SAP ABA and SAP Basis
when installing a SAP Basis Plug-In, see SAP Service Marketplace at
service.sap.com/basis-plug-in  SAP Plug-In  SAP Basis Plug-In 
Releases. For more information about the minimum Support Package level for the
corresponding SAP R/3 Plug-In, see SAP Service Marketplace at
service.sap.com/basis-plug-in  SAP Plug-In  SAP R/3 Plug-In  SAP
R/3 Plug-In Releases. This level corresponds to the SAP R/3 or SAP R/3 Enterprise release.

(C) SAP AG 270


Connection Using SAP R/3 Plug-In
Use
The SAP R/3 Plug-In (PI) provides the technical prerequisites with which to implement a
content-based connection (visibility process [External]) to an SAP system. If a Business Add-
In (BAdI) is available, it is used for this content connection to an SAP system.
The following figure provides an overview of the connection between PI and SAP Event
Management (SAP EM):

SAP
SAP R/3
R/3 Application
Application SAP
SAP Event
Event
Management
Management

SAP
SAPR/3
R/3Plug-In
Plug-In

Web
Web Application
Application
Server
Server

SAP
SAPBasis
BasisPlug-In
Plug-In

You have an SAP EM and an SAP Advanced Planning and Optimization (SAP
APO) that run in the same system. You must configure different technical
Remote Function Call destinations (RFC destinations) for APO Core Interface
(CIF) and for SAP EM.

For more information about SAP R/3 Plug-In, see SAP Library for SAP Supply
Chain Management on SAP Help Portal at http://help.sap.com  SAP
Business Suite  SAP Supply Chain Management  SAP Supply Chain
Management (SAP SCM)  SCM Basis  Integration via Core Interface (CIF)
 SAP R/3 Plug-In.
For more information about SAP R/3 Plug-In, see the following SAP Notes:
214503 Release Strategy for SAP R/3 Plug-In
181255 Composite Note for SAP R/3 Plug-In
For more information about using SAP R/3 Plug-In with visibility processes
[External], see SAP Note 677373.

(C) SAP AG 271


Connection of Business Objects
Use
To process business objects from other SAP application systems in SAP Event Management
(SAP EM), you must have defined and implemented an interface between the SAP
application system and the SAP EM interface.
If a connection to a certain business object in an SAP standard system already exists, you do
not have to define one.

For an overview of the existing connections to certain business objects in


standard SAP systems, see SAP Service Marketplace at
service.sap.com/scm  Supply Chain Management  Supply Chain
Event Management  Detailed Information  Connected SAP R/3 and SAP
APO Objects.
For more information about connecting business objects, see SAP Service
Marketplace at service.sap.com/scm  Supply Chain Management 
Supply Chain Event Management  Detailed Information  Connect SAP
Objects to SAP EM.
If a connection to a certain business object in an SAP standard system does not exist, you
must define and implement one yourself.
You can use the following options to connect business objects from other SAP application
systems to SAP EM:
 Business Add-Ins [External] (BAdIs)
The BAdIs implemented in other SAP application systems call Business Application
Programming Interfaces [External] (BAPIs) (for example, to create event handlers or to
report events).

For more information about Business Add-Ins, see the SAP Library under
mySAP Technology Components  SAP Web Application Server  ABAP
Workbench (BC-DWB)  Changing the SAP Standard (BC)  Business Add-
Ins.
 Business Transaction Events (BTE)
 User exits
 Direct calls in the SAP application system
Irrespective of the option that you choose for connecting a business object, you must collect
the following information and transfer it to data containers:
 All application tables that are relevant to the business object
 The business process that is relevant to the business object
The SAP application system uses the data containers to determine the supply chain event
management relevance of an application object and to transfer the relevant data to SAP EM.

Prerequisites
You must have installed an SAP Plug-In in the SAP R/3 system that contains the SAP EM
interface. The Support Packages and SAP Notes that refer to the SAP Plug-In must have
been imported.

(C) SAP AG 272


You must have executed Customizing for the connection in the SAP Plug-In and in SAP EM
to be able to connect to SAP EM.

Features
The following figure shows the overall picture when linking an SAP application system to SAP
EM and the BAdI call:

SAP
SAP System
System SAP
SAP EM
EM

BAPI
Object 1 Application
BAdI
Interface

BAdI call from an Business Implementation Customizing:


existing business Add-In and Customizing
-EH types
object implementation of application
interface for -Events
creating event
-Expected
handlers and
event profiles
expected events
-Rule sets
-…
SAP EM Integration with mySAP Components

Out-of-the-Box Integration with Visibility Processes

 The BAdI that the system calls from a transaction (for example, saving a shipment
document) or using an application system interface (= call from an existing business
object) is found in the SAP system.
 You have defined the application interface settings for the following:
...

 Creating and updating event handlers


 Creating events
You can also connect external systems to SAP EM using BAPI interfaces [Page 275].
 SAP EM contains Customizing that is specific to an event handler type.
All these elements are also provided with a visibility process [External].

You implement the shipment BAdI BADI_LE_SHIPMENT (BAdI implementation


/SAPTRX/LE_SHIPMENT with BAdI method BEFORE_UPDATE) to establish
the technical connection so that SAP EM creates an event handler in
accordance with Customizing, for example.

Activities
...

1. You decide on an interface type.


2. You implement this interface type with the relevant implementation method.

For more information about implementation methods, see SAP Service


Marketplace at service.sap.com/scm  Supply Chain Management 

(C) SAP AG 273


Supply Chain Event Management  Detailed Information  Connect SAP
Objects to SAP EM.
3. After you have completed the implementation, you test your application interface with
the transaction from the SAP application system.

For example, on the SAP Easy Access screen, choose:


 Logistics  Logistics Execution  Inbound Process  Goods Receipt for
Inbound Delivery  Transportation  Create  Single Documents or choose
transaction VT01N (transportation) or
 Logistics  Logistics Execution  Inbound Process  Goods Receipt for
Inbound Delivery  Inbound Delivery  Create  Single Documents or choose
transaction VL31N (inbound delivery).

Result
You have connected a business object to SAP EM. The SAP application system calls the
SAP EM interface. If you have configured Customizing accordingly, the SAP application
system extracts data and sends it to SAP EM. SAP EM performs one of the following options:
 Creates a corresponding event handler
 Updates the corresponding event handler on the basis of an event message
 Reports an event

(C) SAP AG 274


Business Application Programming Interface in
SAP EM

Definition
A Business Application Programming Interface [External] (BAPI) is a standardized
programming interface that provides external access to the SAP system’s business processes
and data.

Use
You use SAP Event Management (SAP EM) to provide transparency within processes. These
processes can occur in one or more SAP or external systems. BAPIs connect SAP systems
or external systems to SAP EM.
The typical business use of SAP EM consists of the following processes:
...

1. An activity in an application system (for example, creating a purchase order or a


shipment) triggers the creation of an event handler in SAP EM. These contain the
planned and unplanned events or milestones. SAP EM tracks these events.
2. The event message reporters (for example, employees, partners, or systems) send
event messages to SAP EM. These event messages update the actual information (for
example, date, time, or location) about an event.
3. In most cases, the people or systems report the actual events (for example, a goods
receipt for a purchase order, or the arrival of the forwarding agent for a shipment) in
this process.
4. Those involved in the business process query information about an event or event
handler.
The following BAPIs are available in SAP EM for these processes:
 BAPI_EH_POST for creating event handlers in SAP EM
 BAPI_ADDEVENTMSG_02 for sending event messages to SAP EM
 BAPI_EH_GET_DATA for querying information from SAP EM

For more information about Business Application Programming Interfaces, see


the SAP Library under SAP Technology Components  Cross-Application
Functions  BAPI User Guide (CA-BFA) or BAPI Programming Guide (CA-
BFA).

To gain an overview of the BAPIs that can be used in SAP EM, call transaction
BAPI in the system. On the Hierarchical tab page, choose Supply Chain
Management  Event Management  Event Handler.

For more information about implementing a BAPI that SAP EM calls, see SAP
Service Marketplace at service.sap.com/scm  Supply Chain Event
Management  Detailed Information.

(C) SAP AG 275


Connection of External Systems
Use
You can integrate with external systems using Business Application Programming Interfaces
(BAPIs), Remote Function Calls (sRFC, aRFC, qRFC), IDocs, and EDI.
The most common interfaces are also available in SAP NetWeaver Process Integration. You
do not, however, have to use it to
connect to external systems.

For more information about the most common interfaces in SAP Event
Management and their optimization, see Interfaces in SAP Event Management
[Page 280].
For more information about connecting external systems, see SAP Marketplace
at service.sap.com/scm  mySAP Technology  Integration  SAP SCM
4.0 Integration  SAP EM 4.0 Integration  1.0 SAP EM Integration.
For more information about XI, see Integration with SAP NetWeaver Process
Integration [Page 277] or SAP Marketplace at service.sap.com/scm 
mySAP Technology  Integration  SAP SCM 4.0 Integration  SAP EM 4.0
Integration  1.0 SAP EM Integration.

(C) SAP AG 276


Integration with SAP NetWeaver Process
Integration
Use
Several interfaces are available for connecting SAP Event Management to SAP NetWeaver
Process Integration [External]. As a result you are able execute the following processes also
in XMLsapurl_link_0008_0002_0003 [External] format via the XI-capable interfaces:
 Send event messages to SAP Event Management
 Make queries to SAP Event Management about event handler data
 Create event handlers
The following figure provides an overview of integrating XI in an SAP Event Management
system landscape:

Application
ApplicationSystems
Systems
Application
Interface
XML

RFC, BAPI, IDoc

Event SAP
SAP Event
Event Master
Event XI Master Data
Data
Reporter XI Management Server
Reporter XML RFC
Management Server

SCEM Solution

Alert
Alert
Framework
Framework

For more information, see SAP Service Marketplace at service.sap.com/xi.

Example
...

1. You create a sales order in the application system.


You have defined corresponding expected events in SAP Event Management.
2. Your partners send the appropriate event messages in XML format.
The Integration Engine [External] of SAP NetWeaver Process Integration receives the
event messages, processes them, and forwards them to SAP Event Management
using Remote Function Call (RFC).
3. SAP Event Management processes these event messages in accordance with the rules
defined in the corresponding rule set:
 If the sales order is not fulfilled, SAP Event Management sends an alert to all
partners. The Alert Framework sends the alerts. In this case, SAP Event

(C) SAP AG 277


Management uses the master data provided by the Master Data Server for the
location.
 As a further reaction, SAP Event Management triggers an update of the sales
order in the application system.

(C) SAP AG 278


Enterprise Services for SAP Event Management
There are also enterprise services available for SAP Event Management. For more
information about how to install the enterprise services documentation, see the Master Guide
for SAP Event Management on SAP Service Marketplace at
http://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP
EM .

(C) SAP AG 279


Interfaces in SAP Event Management
Use
You use interfaces to send data to and from SAP Event Management, for example:
 To send event messages
 To get event handler data
 To create or update event handlers
In the standard case, this occurs as follows:
 The interfaces named below or the user interface [External] send the event messages
to SAP Event Management.
 The user interface gets the event handler data from SAP Event Management.
 The application interface [Page 33] creates or updates the event handlers in SAP Event
Management.
You use the available Business Application Programming Interfaces (BAPIs) of the event
handler business object (type /SAPTRX/EH) or you use the function modules directly via
Remote Function Call (RFC). You can also send event messages, and create or update event
handlers using IDocs. You cannot read event handler data using IDocs.
The following table describes the various options that you have to send data to and from SAP
Event Management:
Description IDoc Type RFC BAPI
Sending event EVMSTA02 /SAPTRX/BAPI_EHA EventHandler.AddEve
messages DDEVENTMSG_02 ntMessages02
Fetching event No IDoc available /SAPTRX/BAPI_EH_ EventHandler.GetDat
handler data GET_DATA a
Creating or updating EHPOST01 /SAPTRX/BAPI_EH_ EventHandler.PostEv
event handlers POST entHandler

For more information about RFC function modules and BAPIs, see SAP Library
on SAP Help Portal:
 http://help.sap.com  SAP NetWeaver  Application Platform 
ABAP Technology  ABAP Programming and Runtime Environment
(BC-ABA)  External Programming Interfaces  RFC Programming in
ABAP
 http://help.sap.com  SAP NetWeaver Library  SAP
NetWeaver by Key Capability  Application Platform by Key Capability
 Business Services  Enhancements, Modifications … (CA-BFA)

Prerequisites
To use the interfaces, you must have installed the relevant Plug-In versions of the SAP R/3
Plug-In and the SAP Basis Plug-In. Up to PI 2004.1, you must install the relevant SAP R/3
Plug-In separately. If you have installed SAP ECC 6.0, the corresponding functions are
available automatically.

(C) SAP AG 280


For more information about connecting business objects with the relevant Plug-In versions,
see SAP Service Marketplace at http://service.sap.com/scm  SAP Supply
Chain Management  Supply Chain Event Management  Detailed Information 
Connecting SAP Application Objects to SAP EM, in the appendix.

Recommendations for Optimizing the Process Flow


for Sending Data to and from SAP Event Management

(C) SAP AG 281


Choosing the input channel
If you use an interface from an SAP system, we recommend that you use the RFC connection
as the input channel. Since the BAPI and IDoc implementations are based on the relevant
function module that underlies the RFC, an RFC call is the most efficient calling method.

(C) SAP AG 282


Inputting event messages: setting input parameters
If you have chosen an RFC connection or a BAPI as the input channel for event messages,
you can use parameters to control the way messages are processed. The following table
provides an overview of the parameters:
Parameter Name Parameter and Usage Parameter Means of Processing
Description Values Event Message
SIMULATE Indicator: simulation (blank) No simulation
mode (system saves
event message or does
not save event X Simulation
message to database;
for test purposes)
BLOCKONERRORIN Indicator: block (blank) Do not block processing
processing if syntax
error occurs (system
only processes event X Block processing
messages with valid
data)
SKIPCHECK Indicator: syntax check (blank) Perform check
not performed

X Skip check
SYNCHRONOUS Processing in (blank) Asynchronous
synchronous mode
instead of default mode
(in most cases, for X Synchronous
debugging and test
purposes)
BUFFER_MODE Mode for buffering (blank) Check event messages
event messages: for buffering
Controls buffering of
event messages
Buffer all event messages
(system saves event A
(no check in Customizing
message to database,
table)
but does not process it).
The system uses this
parameter to check
Do not buffer any event
event messages for
messages (no check in
their relevance to N Customizing table)
buffering (evaluation in
Customizing table). Do not buffer
Depending on the event
evaluation, the system messages (no
buffers or does not check)
buffer the event
message. Only when
the evaluation changes
does the system also
change the type and
scope (buffer all or no
event messages) of
buffering.
For more information,
see below.

(C) SAP AG 283


EH_GENERATION_ Mode for generating (blank) Check event messages
MODE event handlers: for EH generation
The system uses this
parameter to check
Each event message
whether event A
generates an event
messages are relevant
handler (no check in
for generating an event
Customizing table).
handler in SAP Event
Management In this case, you must
(evaluation in the specify the name of the
Customizing tables). function module that
Only when the generates the event
evaluation changes handlers in variable
does the system also EH_GENERATION_FUN
change the type and CTION.
scope (all or no event
messages generate an
event handler) of No event messages
generating the event generate an event handler
handler. N (no check in Customizing
table).
For more information, No generation
see below. of event
handlers
PREPROCESS_MOD Mode for preprocessing (blank) Check event messages
E event messages: for preprocessing
The system uses this
parameter to check
Preprocess all event
whether it preprocesses A
messages (no check in
event messages
Customizing table)
(evaluation in
Customizing tables).
For more information, Do not preprocess any
see below. event messages (no
N check in Customizing
No table)
preprocessing
of event
messages

We recommend that the system processes event messages in the asynchronous mode
(SYNCHRONOUS indicator has the default value blank).
If you set the indicator for buffering event messages, generating event handlers, or for
preprocessing event messages to N, you can improve performance. In this way, you avoid the
system reading unnecessary database tables. To do this, you must know at least one of the
following for your event messages:
 That they do not need buffering
 That they do not generate event handlers
 That they do not need special preprocessing functions
If you set the SKIPCHECK indicator to X, you can improve performance. To do this, you must
ensure that your event messages do not contain any syntax errors.

(C) SAP AG 284


Sending a large number of file attachments with event messages can lead to problems with
archiving data. In this case, we recommend that you save the files to hard disk rather than the
database (transaction /SAPTRX/TSC0MBF).
You can define that SAP Event Management processes event messages using inactive event
handlers (transaction /SAPTRX/TSC0MBF). This can lead to inconsistencies when you
archive event messages. You can avoid these inconsistencies by ensuring that such event
messages only reach SAP Event Management if the corresponding event handler has not yet
been deleted.

For more information about saving event messages to the hard drive and
processing event messages using inactive event handlers, see SAP Service
Marketplace at http://service.sap.com/SCM  SAP Supply Chain
Management  Supply Chain Event Management  Detailed Information 
SAP EM 4.0/4.1 Event Message Input.

(C) SAP AG 285


Inputting event messages: mass processing
If you work with a large number of event messages, we recommend that you call an RFC
connection for entire packages of event messages instead of one RFC connection for each
individual event message. In this way, you can improve system performance.
If you work with particularly large packages, we recommend that you use parallel processing.

(C) SAP AG 286


Visibility Processes
Visibility processes are predefined scenarios delivered by SAP. They enable you to monitor
one or more stages of a business process. Visibility processes are modular and can be
combined to make the business process (or stage) transparent.

When you implement a visibility process, you have access to preconfigured system settings
for an entire scenario.

For scenario descriptions and a configuration guide to the visibility processes delivered by
SAP, see SAP Service Marketplace under service.sap.com/scm SAP SCM in Detail
Event Management Visibility Processes.

Examples of Visibility Processes:

 Handling

 Transportation

 Production Malfunction

 Procurement

 Outbound Delivery

 Outbound/Inbound Delivery

 Ocean-Carrier Booking

 Purchase Order Processing

 Returnable Transport Packaging

 Transportation Management

An example of an industry-specific visibility process is seasonal procurement.

Structure
A visibility process can contain the following parts:

 Interfaces to SAP application systems

 Customizing for rules, status descriptions, and expected events

 User interfaces for sending event messages and for information queries

 Extractors for data transfer from SAP Event Management to SAP NetWeaver
Business Intelligence (SAP BI)

(C) SAP AG 287


The following graphic provides an overview of the parts of a visibility process.

SAP Application System / External System


Configured Interface to SAP and
External Systems
Application Interface

Web
Interface
Configured Customizing in

Data Extraction
SAP Event Management
SAP Event Management

SAP NetWeaver Business Intelligence


(KPIs/CPIs) Data Extraction and
KPIs/CPIs for analytical
SCEM in SAP BI

Integration
The visibility processes delivered can be integrated into a range of applications and systems,
such as:

 Enterprise Resource Planning (ERP)

 SAP Advanced Planning & Optimization (SAP APO)

 SAP Transportation Management (SAP TM)

 SAP Supply Network Collaboration (SAP SNC)

 SAP Auto-ID Infrastructure (SAP AII)

More Information
For more information about the availability of visibility processes in SAP Event Management,
see SAP note 677373.

(C) SAP AG 288


Business Functions in SAP Event Management
The following business functions were introduced with enhancement package 1 for SAP
Event Management 7:

 EM, Archiving and Web Interface Improvement (SCM_EM_HIGHVOL)

 EM, Visibility Process for External Transportation Management System


(SCM_EM_TMCONTENT01)

 OER, Performance-Optimized PTA and Cold Chain (AIE_OER_PTACOLDCHAIN)

Integration
SAP Event Management 9.0 is a new release. Therefore, the switches that are used to
activate or deactivate the business functions are no longer needed. All business functions that
were provided with enhancement package 1 for SAP Event Management 7.0 are available in
SAP Event Management 9.0 as well. All business functions are visible in Event Management
9.0 for compatibility reasons.

As far as their activation status is concerned, the following applies:

 If you had activated one or several business functions in SAP Event Management
7.01 and upgraded to SAP Event Management 9.0, these business functions remain
activated in 9.0.

 SAP Event Management scenarios that were installed in SAP Event Management
7.01 through the activation of a business function, are also available in 9.0.

 A special case is the business function OER, Performance-Optimized PTA and Cold
Chain (AIE_OER_PTACOLDCHAIN). With this business function, in SAP Event
Management 7.01 you could switch from the PTA (Product Tracking and
Authentication) scenario provided in SAP Event Management 7.0 to the high-volume
variant provided with enhancement package 1.

The two scenarios are not compatible. Therefore, before you start capturing data,
you have to decide whether you want to use either the Event Management 7.0
variant or the high-volume variant.

In Event Management 9.0, the switch between the two options has been replaced by
a customizing setting.

More Information
For more information, see the Customizing for SAP Event Management 9.0 under Event
Management Settings for SAP Object Event Repository Activate Performance
Optimization for High-Volume PTA Scenarios .

(C) SAP AG 289


Business Functions in SAP Event Management

(C) SAP AG 290


EM, Archiving and Web Interface Improvements
For information on this business function in SAP Event Management 9.0, see Business
Functions in SAP Event Management [Page 289].

(C) SAP AG 291


EM, Visibility Proc. for External Transportation Mgmt
System
For information on this business function in SAP Event Management 9.0, see Business
Functions in SAP Event Management [Page 289].

(C) SAP AG 292


Business Functions in SAP Object Event
Repository

(C) SAP AG 293


OER, Performance-Optimized PTA and Cold Chain
For information on this business function in SAP Event Management 9.0, see Business
Functions in SAP Event Management [Page 289].

(C) SAP AG 294