You are on page 1of 85

SAP Event Management Infrastructure

PDF download from SAP Help Portal:
http://help.sap.com/saphelp_em900/helpdata/en/3f/09233d32039017e10000000a114084/content.htm
Created on July 11, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 85

Table of content
1 SAP Event Management Infrastructure
1.1 Scenario and Solution Settings
1.2 Application Integration
1.2.1 Application Object
1.2.1.1 Business Process Type
1.2.1.2 Application Object Type
1.2.1.3 Application Object Type Determination
1.2.1.4 Main Object Table and Master Table for Application Objects
1.2.2 Event in the Application System
1.2.2.1 Event Type
1.2.2.2 Event Type Determination
1.2.2.3 Main Object Table and Master Table for Events
1.2.3 Application Interface
1.2.3.1 Data Transfer from the Application System
1.2.3.1.1 Input Help for Defining Parameters
1.3 Event Handler
1.3.1 Event Handler Type
1.3.2 Event Handler Set
1.3.3 Event Handler Set Profile
1.3.4 Event Consolidation Profile
1.3.5 Parameters
1.3.5.1 Event Handler Extension Table
1.3.6 Creation of Event Handlers
1.3.7 Creation of Event Handler Hierarchies
1.3.8 Event Handler Updating
1.3.9 Event Handler/Event Handler Set Deactivation/Activation
1.3.10 Query IDs
1.3.11 Status Attribute
1.4 Event
1.4.1 Tracking ID
1.4.2 Expected Event
1.4.2.1 Expected Event Update Via Event Message
1.4.3 Expected Event Monitor
1.4.3.1 Parameter Selection for Expected Event Monitor
1.4.4 Event Reporting
1.4.4.1 Event Message
1.4.4.1.1 Internal Event Code and External Event Code
1.4.4.1.2 Inbound Event Message Processing
1.4.4.1.3 Extended Check to and Preprocessing of Event Messages
1.4.4.1.4 Event Message Processing
1.4.4.1.5 Adding Attachments to Event Messages
1.4.4.1.6 Using Event Message Parameters
1.4.4.1.7 Buffered Event Message Processing
1.4.4.2 Individual Event Reporting
1.4.4.3 Expected Event Reporting
1.4.5 Reactions to and Actions for Events
1.4.5.1 Rule Set
1.4.5.1.1 Rule Condition
1.4.5.1.2 Evaluation in the Rule Set
1.4.5.1.3 Rule Set Display
1.4.5.1.4 Simulating Processes in the SAP Application System and SAP EM
1.4.5.2 Connection to the Alert Framework
1.4.5.2.1 Direct Access to Detailed Information
1.4.5.3 Connection to SAP Business Workflow
1.5 Authorizations and Filters
1.5.1 Authorizations for Changing Data and Sending Event Messages
1.6 User Interface
1.6.1 Web Interface
1.6.1.1 Modes of Access of the Web Interface
1.6.1.1.1 Logging On to the Web Interface with SSO

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 85

1.6.1.1.2 Setting Up A Direct Link User
1.6.1.2 Parameter Display (Web Interface)
1.6.1.3 Visualization Using Geographical Maps
1.6.1.4 Printable Version for Tables on a Web Page
1.6.1.5 Use of the Event Handler Hierarchy
1.6.1.6 Drilldown in the Web Interface
1.6.1.7 Frequently Asked Questions (FAQ)
1.6.1.7.1 General Information
1.6.1.7.2 Navigation to the Web Interface
1.6.1.7.3 Administration Screen
1.6.1.7.4 Search Panel
1.6.1.7.5 Navigation and Sorting of Tables
1.6.1.7.6 Search Result Panel
1.6.1.7.7 Sending of Event Messages (Fast Entry)
1.6.1.7.8 Sending of Event Messages for Multiple Tracked Objects or Proces
1.6.1.7.9 Sending of Event Messages
1.6.1.7.10 Settings
1.6.1.7.11 Details of Tracked Objects and Processes
1.7 Monitoring and Evaluating Processes
1.7.1 Use of the Event Handler List
1.7.1.1 Defining Search Criteria
1.7.1.2 Use of the Event Handler Overview
1.7.1.3 Use of Event Handler Details
1.7.1.4 Settings for EH Overview Screen and EH Details Screen
1.7.2 Application Log
1.7.3 Reports for Internal Monitoring and Evaluation of Processes
1.7.3.1 List of Event Handlers with a Specific Status Attribute
1.7.3.2 Last Reported Event List
1.7.3.3 Event Handler Set Browser
1.7.3.4 Event Message Processing Error List
1.7.3.5 Event Message Processing Status List
1.7.3.6 Expected Event Overdue List
1.7.4 Connection to the Computing Center Management System
1.7.5 Connection to SAP NetWeaver Business Intelligence
1.7.6 Connection to the SCM Alert Monitor
1.7.7 Connection to the Document Flow
1.7.7.1 Creation and Updating of a Network
1.7.7.2 Displaying a Network
1.7.7.3 Deletion of a Network
1.7.8 Logging with Change Documents
1.7.9 Simulating Processes in the SAP Application System and SAP EM
1.8 Overview of Activities Delivered
1.8.1 Activity List Structure
1.8.2 Activity List

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 85

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 SAPcomponents and non-SAPcomponents, for example SAP ERP or SAPNetWeaver Business
Intelligence.
The scope of integration varies depending on the SAP Event Management release and the individual SAPapplication 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.
○ 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).

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 85

On the system interface of both the application system and SAP EM. see the Implementation Guide (IMG) for Event Management → Solutions and Scenarios → Assign Users to Scenarios . It simplifies and improves your Customizing procedure in the application system and in SAP EM. or activities) that are not relevant to supply chain event management Customizing on the application system side and SAP EM Customizing. A scenario can be assigned to several solutions (one-to-N relationship). The following figure provides an overview of the interfaces and participants with which SAP Event Management communicates: See also: ● Connection of SAP Systems ● Connection of External Systems ● Interfaces in SAP Event Management 1. For example. to specify that these scenarios can be used with the SAP industry solution SAP for Automotive. Page 5 of 85 .1 Scenario and Solution Settings Use This function allows you to use scenarios and solutions in the application system and in SAP Event Management (SAP EM). to check whether standards have been fulfilled and to check the quality of the execution. SAP delivers an application interface in the application system. ● 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 SAPNetWeaver Business Intelligence for evaluation purposes. If you are not assigned to a scenario. ● An interface to connect internal and external systems and devices to SAP Event Management. This function hides entries (for example. A solution can contain various groups of scenarios. for example. event handler type. and only receive parameters for Customizing in the application system and SAP EM that are appropriate to tracking deliveries in an LTL shipment. For more information about assigning users to scenarios. All rights reserved. You assign a user to all existing scenarios by either entering an asterisk (*) or by not entering any value. which send event messages and queries to SAP Event Management. the system displays all Customizing entries. PUBLIC © 2014 SAP SE or an SAP affiliate company. For connections to external systems. for example. Prerequisites You must be assigned to one or more scenarios that you want to configure. you can work with a Web browser or with a Personal Digital Assistant (PDA). Example You assign yourself to a fulfillment visibility process. This assignment restricts the number of entries for Customizing. you only see those entries for the scenario or solution that you work with. or must assign yourself to them. for example. a standardized interface exists in SAP Event Management.For connections to an SAP system. You assign all scenarios that belong to an SAP business area to a solution. parameters. You assign the scenarios production pallet tracking and vehicle order planning to the automotive solution.

● The system notifies SAP EM of each application object for which the condition is fulfilled. All rights reserved. SAP EM creates an event handler for each application object or updates it (see also Event Handler Creation. To do this. for example: ● ● ● ● ● ● ● To create a physical connection between the application system and SAP EM. it checks the conditions that have been defined for the respective event types.2 Application Integration Purpose To define the objects and processes that SAP Event Management (SAP EM) is to track. see the Implementation Guide (IMG) for the application system under Integration with SAP Components → Interface to Event Management. 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). The extractors specified in the application object type transfer the SCEM-relevant data from the application objects and events to SAP EM. you define the supply chain event management relevance (SCEM relevance) of individual application objects (see also Application Object Type). These conditions specify the SCEM relevance of an application object. ● The system checks its list of event types that belong to the business process type. You have set up the logical system between the application system and SAP EM. 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. or tracking IDs. ● If it does not find an appropriate event type.Solution Scenario Automotive Tracking vehicle orders Tracking automotive production Supplier replenishment Production Replenishment within production Oil and Gas Tracking shipment containers 1. for example. You have specified one or more SAP EMs in the application system. the business process type is known to the system. 2. Process 1. ● If the system finds event types that fit. Prerequisites You have set up Customizing for SAP EM in the application system. 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). SAP EM also creates a change document belonging to the event handler. you define the SCEM relevance of the individual events in the application system (see also Event Type). as required. expected events. 4. 3. Event Handler Updating). if possible PUBLIC © 2014 SAP SE or an SAP affiliate company. You create or change a document in the application system and save it. it writes a message to the application log and terminates the transaction. These conditions specify the SCEM relevance of an event. it checks the conditions that have been defined for the respective application object types. Page 6 of 85 . You have specified the business process types in the application system. if possible ● Sent the event message belonging to the event to SAP EM. You have made the following settings. ● If it does not find an appropriate application object type. ● The system notifies SAP EM of each event for which the condition is fulfilled. 5. it writes a message to the application log and terminates the transaction. 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. You report events for an object or process to SAP EM or the system does this. The application system executes the following for application objects and events: Application Objects Events ● The system checks its list of application object types that belong to the business process type. This might be parameters. you have defined the RFC connection from the application system to SAP EM. You have defined the application object types and event types in the application system. SAP EM processes the events reported for the relevant event handler(s). Documents or parts of documents are assigned to a business process type in a fixed way. You have specified the conditions for SCEM relevance in the application system and assigned them to the application object types and event types. In this way. ● If the system finds application object types that fit.

You map an entire procurement process. you define the purchase order item as the application object type. You define the delivery. In procurement. you specify the level of detail of the SCEM-relevant objects and processes. To track an entire business process and its sub-processes. An application object can map not only an entire business object in the application system.2. On the other hand.1. you can also specify that the individual pallets belonging to the supplier are SCEMrelevant objects. you can create an event handler for each sub-process. for example. This means that you can also send events from other business objects to this event handler. By determining the application objects. You can track a fulfillment process with its sales order. or saving an SCEM-relevant application object in the application system. 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). 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 or a system can report events to an application object. All rights reserved. SAP EM creates an event handler that represents this application object (one-to-one relationship). You join these event handlers together in an event handler set. but does not physically delete them from the database. SAP EM marks the corresponding event handler(s) as deleted. you track an entire truck) ● A one-to-N relationship (for example. The following figure provides an overview of the relationship between the application object and the event handler: PUBLIC © 2014 SAP SE or an SAP affiliate company. changing.1 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). and Financial Accounting as event types. The application system sends the SCEM-relevant data from these objects and processes to SAP Event Management (SAP EM). delivery. invoice. Page 7 of 85 . When you delete an application object in the application system. In this case. the corresponding event handler represents the entire follow-on process and not just the purchase order item. but also parts of objects. you track the individual packages in a truck as part of an SCEM-relevant process) The following figure provides an overview of the relationships between business objects and application objects: As a result of determining. and shipment. You have an SCEM-relevant application object. Purchase Order Item . You can also map cross-business-object processes in conjunction with event types.

SAP delivers a selection of business process types with SAP Event Management. For example. You assign a business process type to each business object in the application system. which the application system transfers to SAP Event Management for an SCEM-relevant object.1. matches any of those saved in the event handler. The system needs the business process type as the main criteria for assigning an application object type to an event handler type. 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. it can create event handlers and update them. Page 8 of 85 . Example Examples of business process types include: ● ● ● ● ● A A A A A sales order purchasing transaction manufacturing order shipment delivery The following figure gives you an example of the link between the business process type and the business object: PUBLIC © 2014 SAP SE or an SAP affiliate company.1 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 . and relevant changes (events) that are relevant to supply chain event management (SCEM-relevant) (see also Application Object Type Determination. Use You need the business process type to determine the business objects. You can also define your own business process types in Customizing in the application system and in SAP Event Management. Event Type Determination).1. SAP Event Management processes the event message and updates the event handler. All rights reserved. If the business process type. business processes.2. In this way. the system needs the business process type to find the corresponding event handler for incoming event messages. 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 and creates an event handler if the business process type is the same.

In this example. You can define multiple application object types for a business process type. PUBLIC © 2014 SAP SE or an SAP affiliate company.1. SAP Event Management (SAP EM) only processes the incoming event messages for objects or processes that fulfill this condition. You have assigned the business process type Shipment to the shipment. An n-to-one relationship exists with the business process types in the application system. ● You track the container that transports the goods. SAP EM needs these for information and query purposes and to check the SCEM process (see also. there are four business objects. All rights reserved. and system parameters. info. 20” container on Atlantic route) grouped goods shipment to the East coast of the US 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. a railroad wagon) railroad shipment with dangerous goods handling unit as part of a delivery (for example. Page 9 of 85 . either you or a system can send internal or external messages to this object and SAP EM can execute the SCEM process.2 Application Object Type Definition A classification of the application object by defining a condition. Monitoring and Evaluating Processes). Together with the name of the application system.2. two of which you have defined as being SCEM-relevant: ● You track the business process for processing a sales order. since the handling unit container belongs to the shipment. 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. 1. You consider the sales order as a whole. You have assigned the business process type Sales Order to it. You can use the application object type to determine the control. In this way. Example Examples of application object types include: ● ● ● ● ● ● A A A A A A standard purchase order delivery handling unit of a particular type on a particular route as part of a shipment (for example. they provide a unique reference between the application object and event handler. You use the application object type to determine the tracking IDs that identify objects. The system uses this reference to refer to the business object and its business process type. The application system writes the application object type and the application object ID into a status table.

● 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). Prerequisites ● You have defined application object types and their supply chain event management relevance (SCEM relevance) in Customizing. Main Object Table and Master Table for Application Objects Definition The main object table and. ● The SAP EM system that creates the corresponding event handler ● How the application interface processes errors (that is. ● 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. or for all application objects with this AOT. The system uses this reference to refer to the business object in the application system. application object type 3 wagon). As a result however. The application system writes the application object type and the application object ID into a status table. and the business process itself (application object type 4 LTL shipment). ● You have assigned the application object type to a business process type in Customizing. the master table specify where the data used to evaluate whether an object is relevant to supply chain event management is located. the master table. and. process terminated for the application object to be processed. The main object table represents the application object. you can create the relationship between your business processes and the application object type. in some cases. Multiple application object types can represent a single business process type. you can use four application object types to represent your shipment process SH. All rights reserved.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. but also the means of transportation (application object type 2 container. Integration This function is part of the process for creating event handlers. Page 10 of 85 . These track not only the packaging (application object type 1 UPS package). Use PUBLIC © 2014 SAP SE or an SAP affiliate company. Features By determining the application object type. the application object type is no longer available. ● You have specified the main object table. if required. or the entire operation terminated) 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) ● The application object ID Example In this example. The master table represents additional information about the application object. 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. in Customizing for determining the application object type.

(provides the inspection lot ---- number) process ● Purchase order number ● Purchase order item A tracking ID: EPL_INSPLOT ● Inspection lot number Quality control visibility process Event in the Application System Definition An event is an incident that has occurred. ● In the application system you assign a main object table and. Page 11 of 85 . you execute the following: ● You define which application tables are available for a business process type in the application system (transaction /SAPTRX/ASC0TO). W ESC_SHIPMT Fulfillment visibility process ESC_SHIPMT Fulfillment visibility process ESC_PURORD Procurement visibility ● Delivery number ● Shipment number A tracking ID: ● Shipment number (provides the shipment number) You are tracking one or PURCHASE_ITEM_NEW more purchase order items in a purchase order. a master table from these available application tables to the relevant application object type (transaction /SAPTRX/ASC0AO). see Event. The application system sends the SCEM-relevant data for these events to SAP Event Management (SAP EM).2. Example The following table provides example uses of main object tables and master tables: Example Main Object Table Master Table Tracking IDs and Query Assigned Business Options for SAP Event Process Type Delivered With Management You are tracking one or SHIPMENT_ITEM_NEW SHIPMENT_HEADER_NE Several tracking IDs: more deliveries in a (provides one or more W shipment. For examples of events. 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. Use You use events in the application system to define whether changes to application objects or processes are relevant to supply chain event management (SCEMrelevant). if required.1 Event Type Definition A classification of the event by defining a condition. 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. You can define tracking IDs in the extractor from the main object table and the master table. 1.2. PUBLIC © 2014 SAP SE or an SAP affiliate company. delivery numbers for the shipment) (provides the shipment number) You are only tracking a SHIPMENT_HEADER_NE ---- shipment. To define the main object table and the master table. see Event. You can define multiple event types for a business process type. All rights reserved.You need the information from the main object table and the master table to define the condition for determining the application object type in the application system. The system displays all the application tables that you have assigned to the relevant business process type in the input help. (provides the purchase order ADER_NEW number) (provides one or more PURCHASE_ORDER_HE Several tracking IDs: purchase order items) You are tracking an INSPLOT_NEW inspection lot.

2. ● 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 The tracking ID is part of the event data and is determined by the extractor. the application object type is no longer available. 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 1.Use You use the event type to determine the supply chain event management relevance (SCEM relevance) of events in the application system.2. All rights reserved. if required. with the data record before the data is saved. You enable the application system to use the event type together with the tracking ID to assign the event to the event handler or event handlers in SAP Event Management (SAP EM). The application system determines the event handler using the tracking ID specified in the extractor. Features By determining the event type. and. SAP Event Management can process the event correctly (see also Event Reporting). ● 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.2 Event Type Determination Use This function uses a classification of the event based on a condition or function that you define in Customizing. If you want to define SCEM relevance conditions for document changes. ● You have specified the main object table. Example The delivery generates five different events. you can also specify the main object table. Multiple event types can represent a business process type. As a result however. 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. Prerequisites ● You have defined event types and their supply chain event management relevance (SCEM relevance) in Customizing. the master table. SAP Event Management only processes these events using the relevant event handlers. ● You have assigned the event type to a business process type in Customizing. In this way. You determine the SCEM relevance by using a condition that you define in the application system and that you assign to an event type. the master table. in Customizing for determining the event type. you can create the relationship between your business processes and the event type. and. The application system sends these to the corresponding event handler in SAP EM. In this way. You save the following with the events: ● The completion of a delivery PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 12 of 85 . 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. 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 use the event type to determine the tracking IDs that allow you to identify event handlers in SAP Event Management. if required. Integration This function is part of the process for reporting events.

Page 13 of 85 . All rights reserved. The application interface calls the Business Application Programming Interfaces (BAPIs) in SAP EM. application object types. Both tables with the data record before the current data save also specify the state that the business object had before its current state. if the route was changed. 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. On the other hand. you want to track a handling unit only for overseas shipments. You can define tracking IDs in the extractor from the main object table and the master table. The main object table represents the event. information from the main object table (handling unit) to determine the tracking ID. Prerequisites 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.3 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 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. You define a condition that queries the change in status from Loading Begin to Loaded. The system uses the application interface to send this data to SAP EM. expected events) from the application system. To do this you need. on the one hand. PUBLIC © 2014 SAP SE or an SAP affiliate company. the route) to process events in the event handler.2. Example For example. 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. 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.● 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 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. 1. The master table represents additional information about the event. see theImplementation Guide (IMG) for the ERP system under Integration with Other SAP Components → Interface to Event Management . for example. you also need additional information from the shipment (for example.

The SAP Basis Plug-In that contains the application interface as of SAP Basis Plug-In 2002. Page 14 of 85 . It automatically creates the parameters (parameter list. 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. For example. The application system also generates the event data that belongs to this event type. you can define a Customizing for the extractors and work with table-based extraction. You use business object keys as a back link from SAP EM to the application system.1. The application system determines the application object types.0B. the system creates an info parameter list with the AS info parameters P1 and P9 for application object AO1. PUBLIC © 2014 SAP SE or an SAP affiliate company. For example.20 or higher. ● 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. the application interface for SAP EM uses Business Application Programming Interfaces (BAPIs). query IDs. As of PI Basis 2006. 2. you have completed the following in Customizing for the application system: ● Specified extractors A and B for creating the info parameter list. The process begins when you create or change a document in the application system. 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 in SAP EM Save events 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 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. You assign function module XYZ to extractor A and function module XY5 to extractor B. To communicate with SAP EM.1. The system also creates the event data for event EV1. All rights reserved. milestones. The application interface is also part of the SAP R/3 Plug-In for all SAP R/3 releases as of 4.Example The following figure provides an example of a system landscape for the application interface. and tracking IDs) in the individual extractors that are assigned to the application object types. is an add-on that you can install on a Web Application Server or SAP product with SAP Basis 6.

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. All rights reserved. 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. PUBLIC © 2014 SAP SE or an SAP affiliate company. 3. The following figure provides you with a simplified overview of the standard case for transferring application data from the application system to SAP EM: 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). The back link using the business object key allows you to assign a business object in a unique way.A shipment consists of two deliveries and two handling units. the SAP EM info parameters X5 and Z3 and the event EV1 are transferred to event handler EH1. Page 15 of 85 . For example. SAP EM transfers the data to the event handler that belongs to the application object.

For example. · Created a shipment document SHD that belongs to application object type AOT1. You can specify a description for the parameters. you have completed the following in Customizing for the application system: · Specified extractor A for creating the info parameter list. the system continues to extract application data from the application system and transfer it to SAP EM . This gives you a quicker overview of the application system (AS) parameters that you can use for defining parameters in SAP EM . The application system creates an application object AO1 for application object type AOT1. 2.Input Help for Defining Parameters Purpose The system provides you with an input help for defining parameters in SAP Event Management (SAP EM) . The application system automatically creates a parameter list. All rights reserved. You specify a description for the info parameters. Page 16 of 85 . SAP EM displays the parameter list to you as an input help when you define parameter mapping. The following figure shows you the simplified automatic creation of the input help. the system creates an info parameter list with the AS info parameters P1 and P9 for application object AO1 . The application system determines the application object types. You assign extractor A to function module XYZ. You can also create the input help manually in the transaction for defining SAP EM interface functions (/SAPTRX/ASC0TF). 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 in SAP EM Process Flow 1. If you have set the mode of the business process type for your SCEM-relevant application objects to Active . · Assigned extractor A to the application object type AOT1. PUBLIC © 2014 SAP SE or an SAP affiliate company. The process begins when you create or change a document (application object of a specific application object type) in the application system. For example. The system stores the parameter list in a Customizing table.

SAP EM does not display an input help for entering application system info parameters. To do this. SAP EM displays the input help for entering application system info parameters. This info parameter mapping profile is to be valid for application system XYZ and application object type AOT1. The following figure shows you a simplified overview of using the input help: PUBLIC © 2014 SAP SE or an SAP affiliate company. 4. the application system transfers the input help to SAP EM . The application system checks whether or not application object type AOT1 exists: ¡ If it does exist.Simple Example Use for the Input Help 1. Page 17 of 85 . SAP EM asks the application system for the input help belonging to application object type AOT1. 2. the application system does not transfer an input help to SAP EM . All rights reserved. ¡ If it does not exist. You have SAP EM display the input help for the info parameters. 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. 3.

The event handler information makes it possible to process events that are reported to SAP EM for an application object.1. within a supply chain network) or a business object (for example. destination. It contains this information in a form that is independent of its origin. Page 18 of 85 . size. All rights reserved. SAP Event Management (SAP EM) tracks this business process or business object.3 Event Handler Definition An event handler represents a business process (for example. SAP EM creates just one event handler for each SCEM-relevant application object. and temperature Structure The event handler determines the following: ● ● ● ● ● ● The expected events belonging to the application object An excerpt from the original data and master data (for example. and interim stops ● Route and carrier information ● Shipment container number ● Weight. or unexpected events and attributes to identify and track the related business processes. or production order) that is relevant to supply chain event management (SCEM-relevant). Examples of information are: ● Identifiers that are used in event messages (for example. The event handler contains all the information necessary to track just this one application object. shipment. arrival at place of destination or proof of delivery) ● Information about the origin. a purchase order. Several event handlers can map a related business process. business partners. so that SAP EM can map and track business processes in a uniform way. An event handler contains expected. and serial number) ● Events that SAP EM either expects or requires for an application object (for example. A business process can consist of one or more application objects. This information is required for monitoring event message processing. materials) The identifiers for internal and external reference The parameters The status The rules The user defines the expected events and rules in SAP EM. the service provider’s own shipment number. reported. locations. Integration PUBLIC © 2014 SAP SE or an SAP affiliate company. type. container number. Use Application objects map business objects in the application system for the SCEM-relevant process. sales order number. and to check if the actual events occur in line with the expected events.

for example. see Customizing for SAP Event Management under Authorizations and Filters . see Customizing for SAP Event Management under Event Messages. Example 1. and you start the search. You track a sea shipment that consists of three legs: Two preliminary legs on the road during which your forwarding agent transports your deliveries to the departure harbor A main leg during which your forwarding agent continues with the transportation of your deliveries by sea 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. The event handler list shows you the events for each of these legs. choose Event Management Monitoring and Lists Event Handler Set Browser or choose transaction /SAPTRX/EH_SET. Page 19 of 85 . 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.3. The system displays the results list (see Use of the Event Handler List) with the same number of event handlers as you have deliveries in your transportation chain. departure and arrival times. SAP EM creates an event handler. Status Queries. Each event handler set consists of three event handlers: One for the preliminary legs. The event handler set forms a link between these related event handlers. and Web Interface Web Interface Define Web Interface Transactions . 1. one for the main leg. 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 for an event handler for processing event messages ● The profile settings for the following profiles: ○ The expected event profile ○ 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 ● The activation of the application log and the degree of detail of the logging ● The possibility to hide the historical data for expected events. and one for the subsequent leg. measurement data.3.3. 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. SAP Event Management does not show the user the information for details for which he or she does not have authorization. 1. You define this using the settings in the filter concept. SAP Event Management displays the event handler to the Web interface user (see User Interfaces) in accordance with Customizing. Note For more information about the settings in the filter concept. 1. for queries. for example.3 Event Handler Set Profile PUBLIC © 2014 SAP SE or an SAP affiliate company. and that contains the expected events. 2.If you save an application object in the application system and the corresponding application object type is SCEM-relevant. The list shows you the same information that the customer can see using the Web interface.1 Event Handler Type Definition The event handler type is the definition of the business process or the business objects that an event handler represents. 3. 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. You specify the two SAP ERP delivery numbers as the tracking IDs and therefore as the search criteria. All rights reserved. For more information.2 Event Handler Set A group of event handlers that logically belong together and that map a certain process within the supply chain.

An event handler set relation consists of an event handler set relation type and an event handler set relation code. 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. Page 20 of 85 . fields. Use You use event handler set profiles to define the event handler set relations. The following figure shows the relation between authorization profiles. All rights reserved. Prerequisites You have defined event handler types. the user-specific authorization profile filters a subset from all the event handlers found. so that SAP EM can create event handler sets. filter profiles. For more information. fields. ● Event handler set relations with their event handler set relation types and event handler set relation codes PUBLIC © 2014 SAP SE or an SAP affiliate company. see Authorizations and Filters. or rows for an event handler set. Depending on the event handler type. You assign multiple event handler set profiles to an event handler type. ● An event consolidation profile This profile determines the order in which SAP EM displays the events for the event handler set that it has consolidated to the user. or rows for event handlers in an event handler set. ● 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. ● A status attribute profile It determines the overall status for all the event handlers in a set. 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.Definition Specifies the relations between event handlers that SAP Event Management (SAP EM) uses to group these event handlers in an event handler set. In turn. if an event handler belongs to multiple business processes. and event handler set profiles: During a search request in the Web interface. the user-specific filter profile forms a subset from that subset. 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. the event handler set profile hides individual tables. You can hide individual tables.

choose Event Handlers and Event Handler Data → Event Handlers → Define Event Consolidation Profiles . 4. together with system parameters. You use the Web interface to start a search query to SAP EM . You create an event handler set profile. see the Implementation Guide (IMG) for SAP Event Management under Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Set Profiles. or query ID code sets. System parameters These are all the control parameters that the application system transfers to the corresponding fields in the event handler extension table. so that SAP EM groups event handlers (for example. and System Parameters You use control. They are defined and stored in SAP Event Management in the form of control. You can form the set using control parameters. event handler set relation code Control Parameter and the corresponding parameter name Business Process Type). SAP EM uses the relation type business process type to search for the event handlers that correspond to your query. 5. For more information about defining event handler set profiles. 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. You assign the event handler set profile to event handler type LTL Shipment .5 Parameters Parameters are variables of objects and processes that are relevant to supply chain event management (SCEM-relevant). 3. ○ If the event handler set relation code (control parameter name. ○ You use the assignment of the event handler set relation code to the event handler set relation type to specify the condition. name of the tracking ID code set. SAP Event Management stores information from the application system in the following parameter types: Control parameters You use control parameters.○ The event handler set relation type specifies the type of relation between event handlers within a set. Info. Activities In the Implementation Guide (IMG) for Event Management. Preconfigure the Web interface for search queries about event handler sets appropriately. set the corresponding indicator within an info parameter. 1. tracking ID code sets. A consolidated list is displayed containing all event handlers that correspond to your query. Example 1. SAP EM sorts the events in descending order by the date and time when SAP EM created the event handler. you can also set values for rule processing parameters while processing a rule set. Page 21 of 85 . and system parameters. 2.3. You can use these rule processing parameters to transfer values from one task to the next task in the rule. All rights reserved. The parameters contain the information from the application system about an application object. 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. If you do not use an event consolidation profile. This means that you can use SAP Event Management independently of an application system. you can use them for processing in the rule set. to specify the event handler type and the characteristics for an event handler. and system parameters in SAP Event Management in the rule set for processing search or information queries. info.3. SAP EM first sorts the events according to the fields from the event handler header table and then according to the event handler types. 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. In addition. you create a parameter list for control and info parameters in the application system. To do this. 1. info. To select the control and info parameters in SAP Event Management Customizing. SAP EM creates an event handler set. for example. the PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP EM checks the conditions that you have defined for assigning event handler type LTL Shipment to the event handler set.4 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) on the consolidated page of the Web interface. Control. name of the query ID code set) is identical. If you have permitted the use of info parameters for condition processing.

if necessary. create your own. and rule processing parameters and the transaction for defining system 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 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 System Parameters SAP Event Management saves system parameters in their own database fields in the event handler extension table in Customizing. Page 22 of 85 . for example. You can. using activity method Updating Field Value in Header Extension Table (HDR_EXT_VALUE_UPDATE). and the departure date as system parameters. You can access this value using an activity within a rule or using a rule condition. info. Example For a transportation process. System parameters to specify the field values for typical search queries to SAP Event Management. We deliver control and info parameters. The Web interface displays parameters and other event handler data. for example. the service provider name. Info parameters for information and query purposes. you define the country of origin and the destination country. SAP Event Management saves the information in a string format with a maximum length of 255 characters. 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). see Customizing for SAP Event Management in the application system under Event Management Interface Define Application Interface . All rights reserved. however. For more information. document type. Specify Parameters in SAP Event Management In SAP Event Management. Control parameters save selected information in a string format with a maximum length of 60 characters. location. Rule Processing Parameters In SAP Event Management. For more information about defining parameters. 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. see Customizing for SAP Event Management under Event Handlers and Event Handler Data Parameters . You need the parameters for the following: Control parameters to define and to check the process steps in SAP Event Management. You store the field values for your typical search queries as a record in the event handler database table in Customizing. 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 can define your own system parameters using this extension table and you can then change the value. SAP Event Management uses parameters to change event handlers. the mode. You get these parameters as a selection list when defining expected events and control parameters in Customizing for SAP Event Management.service provider ID or the destination ID. the name of the carrier. You have both read and write access to rule processing parameters during rule set processing. 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. choose the transaction for defining control. PUBLIC © 2014 SAP SE or an SAP affiliate company. or material type. You use an activity to set the value of a rule processing parameter. you use rule processing parameters to transfer values from one task to another task in a rule. and set up a targeted index for these fields. for example (see Event Handler Updating).

3.3. For more information.01.) Use The user can use the fields in the extension table as additional options for search and report queries about event handlers. Fields in the extension table must not contain numeric domains. 1. System parameters are mapped from the application system to the fields in the extension table. Event handlers are created in SAP Event Management in various ways: PUBLIC © 2014 SAP SE or an SAP affiliate company.6 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. The extension table is found in the event handler header data. Only use character-type data types for the domains.5. Example Control Parameters Name Index Value Service Provider ABC Mode TRUCK Priority HIGH Material Class FROZEN GOODS Info Parameters Name Index Value Color BLUE 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. see Parameter Display (Web Interface (Web Dynpro ABAP) and (Classic)). All rights reserved. (See also: Parameters → Structure section. 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.1 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.Note For more information. see Defining Search Criteria. Page 23 of 85 . For more information about adding additional data from the extension table as selection criteria in the event handler list.01 1.

it continues to execute the checks for generating an event handler. 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. If it does not find any suitable event handlers. It checks whether SAP Event Management can create one or more event handlers. it uses this and updates the event handler. It determines which SAP Event Management system is responsible for the application object type. It checks if suitable event handlers already exist. ● Sending an event message creates an event handler. b. see Customizing for SAP Event Management under Event Messages. It specifies the business process type (BPT) of the business object. The application system executes the following: a. 1. f. and info parameters (see Parameters) ● You have defined the following in SAP Event Management: ○ The event handler types ○ The condition for determining the event handler type ○ The expected event profile ○ The parameter profile ○ The status attribute profile ○ The rule set ● 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. 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).sap. (An application system can work with several SAP Event Management systems simultaneously. Page 24 of 85 . you can use transaction /SAP/TRX/EH_CREATE. To check how event messages are processed for an event handler. application object type. All rights reserved. system. 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). ● The application system calls a Business Application Programming Interface (BAPI). SAP Event Management executes the following: a. Activities The event handler creation process begins as soon as you save a document in the application system. see SAP Service Marketplace at http://service. d. ● You have set up the RFC connections that create the link between the application system and SAP Event Management. 2. It creates control parameters for all application objects that are SCEM-relevant. If it finds a suitable event handler.) c. You save your document in the application system. b. It standardizes the control parameters that have been sent from the application system so that it can process them. For example.● The application interface creates event handlers for application objects. It checks if it can generate the event handler. you can create different event handlers using the application interface. e. Status Queries. The steps for creating an event handler are shared between the application system and SAP Event Management. and Web Interface → Define Criteria for Event Message Processing .com/scm → Supply Chain Event Management → Detailed Information. the system requires the expected events and the rule set that belong to the event handler. 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 ○ The condition for determining the application object type ○ The function for determining expected events ○ The control. you can specify the expected events according to the quality of the supplier. Integration Depending on the objects that you want to track and the partners who are involved. as defined in Customizing in SAP Event Management. 3. The visibility process allows you to connect to your business objects in the application system. ● 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. c. If you test functions in SAP Event Management purely for test purposes and do not want to set up a corresponding application system. PUBLIC © 2014 SAP SE or an SAP affiliate company. 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. For more information about manually creating event handlers for test purposes. This triggers the creation of an event handler in SAP Event Management.

2. (The application system does not send the data until it continues with the saving process. For more information about setting data in a further reference table. At the same time. It sends the result of the check to the application system. 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 example. query IDs. The Web interface (Web Dynpro ABAP) displays this information. See also: step 5e) c. See step 5e) e. tracking IDs. (The application system does not update the status until it continues with the saving process.d. It flags the application log for an update. 4. 6. ○ It sends the confirmation for completed transactions to the application system. For more information about displaying event handler hierarchies. You specify in this reference table how SAP EM can determine the lower-level event handlers for the higher-level event handler. these two event handlers can have a hierarchical relationship to one another. In accordance with your Customizing. 3. See also: step 5e) d. see the Implementation Guide (IMG) for SAP EM under Event Management → Event Messages. It sends the marker for sending the collected data to SAP Event Management. expected events. The process begins when you create the required event handlers. It returns to saving the business object. It marks open communication processes for a status update in the status table. In this example. 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. Prerequisites You have created your own event handler within the hierarchy that you want to track. 5. 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. see the documentation for activity method ADD_EH_TO_PROCESS (CO /SAPTRX/CL_EH_EVENT_MSG_MODEL ACT_ADD_EHS_TO_PROCESS). You have also set up the entire Customizing for SAP EM. You want to track shipment SHIP0001 that contains HU HU02 and HU HU03. It collects all data from the parameter containers (control and info parameters. You need a higher-level event handler for the event handler hierarchy. Process 1. 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. SAP EM archives the hierarchical information together with the archiving object /SAPTRX/A0 Event Handlers and the archiving object SAPTRX_A2 Event Handler Sets. you make sure that the event handlers EH_HU02 and EH_HU03 are updated in SAP EM. Page 25 of 85 . 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 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 application system does not update the application log until it continues with the saving process. it is the event handler EH_SHIP0001 for shipment SHIP0001. The application system then executes the following: a. ○ It calls the activities for updating processes. Status Queries. ● The plug-in function module creates an event handler and SAP Event Management processes the event message. b. All actions that have been marked for execution are completed in the application system. The application system continues to process the confirmed application objects. business object keys). if you have two event handlers. and Web Interface → Web Interface → Configure Fields for User Profiles or Define User Profiles. 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. For this to occur. All rights reserved. SAP Event Management determines the event handler type and creates an event handler with the relevant expected events and status attributes. Since HUs HU02 and HU03 are assigned to shipment SHIP0001. one for a shipment and one for a handling unit (HU) within this shipment. You send an event message to SAP EM with a further reference table for the higher-level event handler. the event message must meet the predefined criteria. 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. To do so.

The application system executes the following: a. For more information. in Customizing for SAP Event Management. ○ The expected event profile To do so. see Customizing for SAP Event Management under Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types. ● If you want to log changes to data relevant to event handlers. in Customizing. see SAP Help Portal at http://help. 5. Prerequisites ● You have specified the following in the application system: ○ The application object types ○ The condition for determining the application object type ○ The function for determining expected events ○ The control. 1.8 Event Handler Updating Purpose By updating event handler data. 1. in Customizing for SAP Event Management.○ EH_GUID_SET Retain Event Handler GUID Currently Being Processed In this way. 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 have configured the RFC connections between the application system and SAP Event Management.) PUBLIC © 2014 SAP SE or an SAP affiliate company. ○ The status attribute profile To do so. For more information. choose Event Handlers and Event Handler Data → Event Handlers → Define Conditions for Event Handler Types and Event Handler Sets. choose General Settings in SAP Event Management → Define RFC Connection to Application System. You save your document in the application system. (An application system can work with several SAP Event Management systems simultaneously. execute the following: ○ In Customizing for the application system. choose Reactions to Event Messages → Define Rule Sets . in Customizing for SAP Event Management. 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. ● 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. 2. To do this. as for creating event handlers. 4. SAP EM creates the event handler hierarchy between the higher-level event handler and the lower-level event handlers. b. All rights reserved. It determines which SAP Event Management system is responsible for the application object type. For an example of how you can use an event handler hierarchy. see SAP Service Marketplace at http://service.com/scm → Supply Chain Event Management → Visibility Processes → Generic Configuration Guide. choose Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types. system. choose Event Handlers and Event Handler Data → Parameters → Define Parameter Mapping.sap. choose Integration with SAP Components → Interface to Event Management. see the activity documentation (CO /SAPTRX/CL_EH_EVENT_MSG_MODEL ACT_UPDATE_EH_HIERARCHY). For more information. choose Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. the system can check how event messages are processed for an event handler. The visibility process allows you to connect to your business objects in the application system. choose Event Handlers and Event Handler Data → Status → Define Status Attribute Profiles. You log on to the Web interface and search for your shipment SHIP0001. 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.com → SAP Business Suite → SAP Auto-ID Infrastructure → SAP Solutions for RFID → SAP Object Event Repository → Supported Processes → Product Tracking and Authentication . in Customizing for SAP Event Management. choose Integration with SAP Components → Interface to Event Management → Define System Configuration → Define RFC Connection to SAP EM. ○ The parameter profile To do so. 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. ○ The rule set To do so. Process The steps for updating an event handler are shared between the application system and SAP Event Management. and info parameters (see Parameters) To do so. ○ The condition for determining the event handler type To do so. you have defined the relevant indicator with the corresponding level of detail. in Customizing for SAP Event Management. ● You have defined the following in SAP Event Management: ○ The event handler types To do so.3. 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. Page 26 of 85 . ○ In Customizing for SAP Event Management. in Customizing for SAP Event Management. To do this.sap.

The application system then executes the following: a. SAP Event Management updates the corresponding change documents. The application system continues to process the confirmed application objects. It retrieves the application object types for the BPT from the application system and determines whether they are relevant to supply chain event management. that is. Then it calls the activities for updating the process and sends the confirmation of the completed transactions to the application system. It specifies the business process type (BPT) of the business object. see also step 6e. If it finds a suitable event handler. It sends the marker for sending the collected data to SAP Event Management. see also step 6e. b. 4. It returns to saving the business object. If you have activated logging with change documents and use activities in the rule set that change data relevant to change documents. SAP Event Management determines the event handler type and updates the event handler with the relevant expected events and status attributes. At the same time. SAP delivers methods or function modules for activities.3. All rights reserved. If necessary. It sends the result of the check to the application system. it sends the data. c. When the application system continues with the saving process. The application system checks if the event handler has the correct status for the application object. When the application system continues with the saving process. You want to track your deliveries. When the application system continues with the saving process. it updates the application log. b. It checks if suitable event handlers already exist. 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. if required The expected event profile The parameter profile The status attribute profile The rule set Activities 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. it uses this and updates the event handler. You define an activity to deactivate an event handler in the rule set for SAP Event Management (SAP EM). It collects all the data from the parameter containers. for testing purposes). SAP Event Management also standardizes the data from the parameter containers in the application system into a view that it can process. query IDs. It flags the application log for an update. All actions that have been marked for execution are completed in the application system. e. PUBLIC © 2014 SAP SE or an SAP affiliate company. It standardizes the control parameters that have been sent from the application system into a view that it can process. c. It creates control parameters for all application objects that are SCEM-relevant. As soon as your delivery arrives at your customer. or tracking IDs that belong to a relevant application object. SAP EM deactivates the relevant event handler. 7. or tracking IDs that belong to a relevant application object. info parameters. Page 27 of 85 . query IDs. 6. it continues to execute the checks for generating an event handler. d. info parameters. 5. d. it performs the status update. Prerequisites You have defined the following in SAP EM: ● ● ● ● ● ● ● The event handler types The condition for determining the event handler type The event handler set profile. e. SAP Event Management deletes any control parameters. It marks open communication processes for a status update in the status table. If it does not find any suitable event handlers. c. see also step 6e. SAP Event Management executes the following: a. 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. it has not been set to inactive (for example.

Event Handlers and Event Handler Data You classify the status attribute values in status attribute types that are either the YES/NO type or the Status Attribute Value type.When the last expected event is reported for an event handler. Both parties can query the event handler status in the Internet using the sales order number.10 Query IDs Definition An additional identification to the tracking ID that you can also use to address an event handler so that you can send queries to SAP Event Management (SAP EM).3. 6. 2. 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 . 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. When you send actual data on the status of an event handler or event handler set to SAP Event Management in an event message. 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 save your setting. you have defined the sales order number and the delivery number as query IDs in Customizing for the application system. The system displays the event handler information that you are authorized to change in change mode. You specify the reporting of the last expected event as a rule condition. You have the authorization to manually deactivate and activate event handlers. choose EH Display Configuration and configure the event handler data display so that the system displays the Header Data tab page. 1. Select the event handler to be deactivated or activated from the event handler list. whereas the sales representative knows the sales order number and the delivery number. 3. 7. The customer only knows the sales order number. for example. depending on the result. All rights reserved. Page 28 of 85 .11 Status Attribute Description of the current status of an event handler or event handler set. When the system executes the method or function module for an event handler that belongs to several event handler sets. When creating an event handler or event handler set. 5. you define an appropriate rule in the rule set that calls the method for deactivating event handlers. You define a status attribute Fill Status with status attribute values Empty/Half-Full/Full . 1. SAP Event Management updates the status attribute. If the system does not display this tab page. The status attribute consists of a name and one or more values. You can also use the status as a search criterion for event handlers. Example PUBLIC © 2014 SAP SE or an SAP affiliate company. You choose Display → Change . You select the Header Data tab page.3. for example. Examples of query IDs are a sales order number or a purchase order number. 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. 8. If you have defined an activity in the rule set for updating statuses. Note For more information about status attribute Customizing. it deactivates or activates these sets and all event handlers belonging to the sets. 4. To do this. the evaluation of the condition may trigger this activity. SAP EM uses the query ID to find the event handler that matches your search query. 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 . The event handler overview appears and you display the detailed event handler header data. SAP Event Management checks the condition from the rule set of the event handler or event handler set. For example. the deactivation of this event handler is triggered. Manual Deactivation and Activation of Event Handlers 1. see Customizing for Event Management under Statuses . You activate or deactivate the event handler using the corresponding checkbox field in the Status frame. You specify the default value in Customizing for SAP Event Management.

no information about whether the actual event has occurred is available for unreported events. ● Unexpected event The event occurs. actively notify those persons involved. 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. see Customizing for SAP Event Management under Statuses Define Status Attributes . premature. Page 29 of 85 . the late arrival of a service provider).A status attribute type specifies. and applies quality characteristics for execution and reporting habits. Note For more information about defining status attribute types. ● Overdue event The event does not occur within the expected time (for example. delayed. for example. change of route for a service provider). Event Handlers and Event Handler Data You group one or more status attribute types in a status attribute profile. but it was not planned (for example. which you assign to an event handler type. for example. PUBLIC © 2014 SAP SE or an SAP affiliate company. Event Handlers and Event Handler Data 1. about the production level) in response to queries (see Event Reporting). All rights reserved. and can then. When processing event messages SAP Event Management checks if expected events have been met. and unexpected) ● Events that have not been reported (overdue) Until the planned end time is reached. production stop. ● You can use SAP Event Management to make your supply chain measurable. traffic jam. ● 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. by comparing expected events with the actual events. 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.4 Event Definition An event is an incident that has occurred. For more information about using events in the application system. see Customizing for SAP Event Management under Statuses Define Status Attribute Profiles . The following figure provides an overview of the three event categories and the life cycle of an event handler: Event Reporting When reporting events you differentiate between: ● Events that have been reported (regular. ● 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). see Event in the Application System. the punctual arrival of materials). the status Shipment On Time as YES/NO or the status of a vehicle as Loaded/Empty or as Delayed/Deviated from Route/Damaged . Note For more information about defining status attribute profiles.

○ You report an event as a sales representative using the sales order number. The combination of the tracking ID and tracking ID code set does not have to be unique. However. For example. and each delivery has its own event handler in SAP EM. ○ You report an event as a carrier using the shipment number. you define the time for an expected s hipment start to be two hours after l oading end. 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). Planned events are reported to SAP Event Management or determined in the following ways: ● The application system sends the data to SAP Event Management. but expected (event and event message) ○ Overdue (as far as is known. In this way. he or she can overwrite the expected events that are defined in SAP Event Management with the new data. ● You enter the data externally and report in the Internet or using EDI. shipment number 1234) and the same tracking ID code set (for example. 1. The tracking ID code set allows you to classify the tracking IDs. you define the different tracking IDs for this application object type. For example.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). ● You use tracking IDs as search criteria when making queries in SAP EM . ● When events are reported. document processing). ● SAP Event Management determines the data itself. For example. it is possible to have both a pallet with tracking ID 1234 and a container with tracking ID 1234 . but instead for a later time.4. There are two deliveries for a shipment. For example. for example. a tender is sent to a service provider who cannot complete the order for the required time. Both have the same tracking ID (for example. All rights reserved. you can send external or internal messages to this object. Since the service provider has the appropriate authorization. Examples Multiple tracking IDs linked to one event handler 1. If you define the function for the tracking ID in the application object type. Examples of tracking IDs are a container number or a shipment number. ● External partners report the data. SAP EM uses tracking IDs and tracking ID code sets to find the corresponding event handler(s). ● You enter the data manually in SAP Event Management. PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP EM processes an event message that is sent to this tracking ID and tracking ID code set for both event handlers. you assign the pallet to the tracking ID code set PAL for pallet and the container to tracking ID code set CON for container. SAP EM uses the tracking ID that is provided in the event message to find the corresponding event handler. You report an event. Each object has its own event handler. the event has not yet occurred. The application system determines the tracking IDs. 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. for example.1 Tracking ID Definition An identification with which to address an event handler so that an external or internal message can be sent to it. Use ● SAP Event Management (SAP EM) uses the tracking ID (together with the tracking ID code set) to identify event handlers. Page 30 of 85 . HU40).

Use ● SAP Event Management needs expected events to be defined to monitor overdue or unreported events. You define the list of expected events in this profile. You also use this to PUBLIC © 2014 SAP SE or an SAP affiliate company.○ You report an event as a production employee using the manufacturing order number. You report events for a pallet. 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. 2. All rights reserved. SAP EM finds the appropriate event handler using the combination of tracking ID and tracking ID code set. you define an expected event profile.2 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. and a shipment order for three different event handlers. In Customizing for SAP Event Management. These event handlers have the same tracking ID but different tracking ID code sets. for example. Page 31 of 85 . The following figure shows the connection between several tracking IDs belonging to one event handler: Multiple tracking IDs linked to different event handlers 1. service provider punctuality or quality assurance. The following figure shows the connection between multiple tracking IDs belonging to different event handlers: 1. a manufacturing order. SAP EM can only find the event handler that matches the event message by using the tracking ID code set. 2. ● You can use expected events that have been defined and then fulfilled as quality criteria.4.

if required ● Additional dates and times for your own purposes. 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 Check Check Check for location code set and location code ID for partner code set and partner code ID for data code set and data code ID for transferring data for location data. add. SAP Event Management determines the data for an expected event itself. SAP EM updates the following expected event data: ● The estimated deadlines (for example. with which to update expected event data. You send the data for an expected event: ○ From the application system ○ Externally from an external system 2. new date or new time) Prerequisites You have defined an activity. In this case. Conditions. The profiles allow SAP Event Management to automatically create expected events for an event handler. partner data. expected transportation time. for adhering to base plans. you can trigger an update of the expected event list (delete. and Activities in SAP Event Management → Define Activities for SAP Event Management . Page 32 of 85 . For more information about defining SAP Event Management activities. if required Partner code IDs. if required PUBLIC © 2014 SAP SE or an SAP affiliate company. EVM_EE_UPDATE . and update events). see the Implementation Guide (IMG) for Event Management → General Settings in SAP Event Management → Functions. if required Location code IDs. 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. new location or new partner) ● The deadlines for the next expected events (for example. or other corresponding data You can also define the following: ● The date and time with tolerances. All rights reserved. You have defined the following in Customizing: ● ● ● ● ● ● An expected event profile Internal and. external event codes for the expected events Location code sets. 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. if required Partner code sets. for example. estimated arrival time at location) ● The next expected events (for example. optionally. 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 Integration The following options are available for reporting data for the list of expected events to SAP Event Management: 1. Expected Event Update Via Event Message Use By sending an event message to SAP Event Management (SAP EM).specify the database fields relevant to SAP Event Management.

choose Reactions to Event Messages → Define Rule Sets. to react to these overdue events. define your own activity by copying activity EVM_EE_UPDATE and changing it correspondingly. All rights reserved. For more information. SAP EM bundles the expected events. the requirement type of this expected event is set to Not required . At the same time. In the Implementation Guide (IMG) for Event Management . Choose Activity Methods in the dialog structure and select the EVM_EE_UPDATE method. When you use the seasonal procurement process. Choose Display Function Module Documentation . If you create an expected event using a BAPI.4. Prerequisites If you want to activate extra selection options for seasonal procurement in addition to the default selection parameters for seasonal procurement. 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.3 Expected Event Monitor Use This report checks the expected events of an active event handler for overdue messages and triggers activities where necessary. if you have defined it ○ The internal event code. See also: Parameter Selection for Expected Event Monitor. 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 use the process for seasonal procurement. SAP EM reads all the expected events for this event handler. if you have not defined an external one ○ The following data. you can use the selection fields specific to seasonal procurement. see the relevant activity description. you must have set the Seasonal Procurement indicator. ● You can also update the expected event list independently of reported events. In the case of overdue expected events belonging to the seasonal procurement process. Page 33 of 85 . SAP EM processes overdue expected events belonging to the seasonal procurement process in a different way from other overdue events. SAP Event Management (SAP EM) uses the expected event monitor to recognize overdue expected events.Features ● The following are keys for the update of the expected event list: ○ The event counter ○ The event action ○ The external event code. SAP EM determines from these expected events the which one is valid and which has the highest internal priority. 1. You can define activities. sending an e-mail. SAP delivers activities for the expected event monitor (for example. ● You can update the data for your additional time categories. you have executed the following: PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP EM works on event handlers and not on individual expected events. 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. for example. When you select an overdue expected event for an event handler belonging to the seasonal procurement process. Features You can start this program as a background process. for comparing two fields or activating an event handler set).

You have defined an expected event profile in Customizing for each event handler type. You can activate additional selection options for seasonal procurement by executing the relevant Customizing and setting the relevant value for the GET/SET parameter. 3. SAP EM receives the event message and prepares it for additional processing (for example. 2. All rights reserved. You specify the external event code consisting of an event code set and an event code ID.4 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. see the report documentation for report /SAPTRX/EE_MONITOR. it executes automatic activities. If you want to use the unspecific selection parameters. Here it can be the case that a direct data backflow takes place from the SAP system to SAP EM. those that are not specific to seasonal procurement.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. you have set the parameter value X for GET/SET parameter /SAPTRX/EE_MON_SEL ( Display Monitor Fields ). If your partners use external event code sets and event codes. ● You have defined the internal event codes in Customizing. 1. service provider or partner. Process 1. or if an appropriate interface must be implemented. for example) report an event to SAP EM. checks the validity of the event message). This backflow can result in changes to the expected events for event handlers. 4. 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 (as an employee. These changes have a direct effect on the selection of overdue expected events in this report. and if so how ● Document the business process Prerequisites ● ● ● ● You have defined the business process types and event handler types in Customizing. that is. Page 34 of 85 . Features Selection Parameters for Seasonal Procurement In the standard system. you can define the way in which SAP Event Management (SAP EM) maps the external events codes onto internal ones. You have checked if a means already exists to report events. 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 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 .4. as required. 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. ● You have set the parameter value X for GET/SET parameter /SAPTRX/EE_MON_SEL ( Display Monitor Fields ). You have defined a rule set in Customizing for each event handler type to check event messages. You have an existing EDI system and an EDI converter that can send IDocs. You specify the tracking ID. for example.● You have created an entry and set the Seasonal Procurement indicator in Customizing for SAP Event Management (SAP EM). The following figure provides an overview of the standard process flow: PUBLIC © 2014 SAP SE or an SAP affiliate company.

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.For more information about the process flow in SAP EM.1 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 or unplanned incidents within the supply chain. 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.4. All rights reserved. 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). You can also send attachments (for example. Page 35 of 85 . 1. a tracking ID that identifies the objects that SAP Event Management is to track PUBLIC © 2014 SAP SE or an SAP affiliate company. Message Sources You can send event messages from both internal and external data sources. 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. see Inbound Event Message Processing and Event Message Processing. a digital signature) with an event message to SAP Event Management .4. An event message can contain data for multiple events and multiple document references.

Mapping External Event Codes onto Internal Event Codes 1. The following figure provides an overview of mapping external event codes onto internal event codes: PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Status Queries. such as ANSI X12214 status code. The internal event code makes it possible for SAP EM to display the external event code in a standardized way. An external event (for example.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 service provider reports his departure to SAP Event Management by on-board computer at 10:00. External Event Code The external event code displays the event type for an event message. Example You are expecting a delivery of car tires at 13:00. as appropriate One or more attachments. and Web Interface → URL Templates for Tracking ID Providers. see Customizing for SAP Event Management under Event Messages. SAP Event Management sends you an e-mail informing you that the carrier departed at 10:00 with your delivery. 3. If you have defined internal event code groups. It corresponds to the industry standard codes. The following figure provides an example: Use The event codes identify the event that has occurred and that is to be updated in SAP EM. the transportation route One or more document references. Page 36 of 85 . or CLM code. SAP Event Management (SAP EM) differentiates between the internal event code and the external event code. PUAR). Internal Event Code The internal event code displays the internal type of the event for an event message. SAP EM assigns the internal event code to the appropriate internal event code group. You send an event message with an external event code to SAP EM. SAP EM maps the external event code onto the internal event code in accordance with Customizing. 2. 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. delivery arrival) is mapped onto an internal event code (for example. 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. You specify the internal event code in SAP EM. as appropriate A Uniform Resource Locator (URL) for the tracking service provider’s Web page For more information about using and defining a link to a tracking service provider’s URL. RosettaNet. EDI standard code). You specify the external event code in SAP EM.

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.

Inbound Event Message Processing
Use
SAP Event Management ( SAP EM ) executes inbound processing of event messages to
· Check the syntax (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

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 37 of 85

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 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

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).

1.4.4.1.4 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 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

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 38 of 85

Prerequisites
● You have set up Customizing for SAP EM. You have also defined the following, in particular:
○ Internal, and where appropriate, external event codes
To do so, in Customizing for SAP EM, choose Event Managemen t → 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 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.
2.
3.
4.

Either you or the system reports an event (for example, service provider delay or proof of delivery by the customer).
The event message is transferred to SAP EM using the application interface.
If errors occur during processing, SAP EM writes them into the event message processing error list.
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.
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.
7. SAP EM uses the tracking ID 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 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).

1.4.4.1.5 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.

Example
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
Define Criteria for Event Message Processing .

Event Management

Event Messages, Status Queries, and Web Interface

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 the EM 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 .

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 39 of 85

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.

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

SAP

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:
EVTCNT
FILENAME
FILECLASS
MIMETYPE
FILESIZE
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.

Note
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 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.

1.4.4.1.6 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.

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 40 of 85

If you have already specified default values in the RF event message profile. you can change the default values. For more information about defining RF event message profiles. and Web Interface → Define Criteria for Event Message Processing . 2. ● You call transaction /SAPTRX/MI01 directly in the system. Page 41 of 85 . you use the input screen pushbuttons (for example. Status Queries. you can normally send most fields multiple times. 1. but at another time. and Web Interface → Define Layout for Individual Messages .2 Individual Event Reporting Use You use this function as an additional means to report individual events within an implementation project. ● Since the layout was developed for the input screen of a mobile device. Quit). so that reported event messages are not sent to SAP Event Management (SAP EM) immediately. and Web Interface → Define Layout for Individual Messages . Status Queries. if required. for example. a supplier address) using mobile devices (for example. For more information about buffering event messages. For more information about defining RF event message profiles. Specify the required values (for example. Prerequisites ● You have specified selection criteria for buffering the event messages.4. 7.4. In this function you select the required buffered event messages that you want to send to SAP EM. Activities On the SAP Easy Access screen for Event Management . choose GoEnter .4. event code ID Delayed ). 5.4. 1. a handheld).4. If you have the appropriate authorization. view the confirmations for the event messages that have been sent in the application log (transaction SLG1 . 6. Specify a radio frequency event message profile (RF event message profile) and choose GoEnter . To save your entry. Choose transaction /SAPTRX/MI01. Unlike the standard transaction in the Web interface. Instead. You can schedule a background job that sends buffered event messages to SAP EM once a night.1. you report the individual events (for example. Status Queries. see the Implementation Guide (IMG) for SAP EM under Event Management → Event Messages.4. object SAPTRX ). If required. 4. see the Implementation Guide (IMG) for SAP EM under Event Management → Event Messages. QuitF9 ). The system displays the input screen that corresponds to the RF event message profile that you have selected. 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). you cannot use any menu commands (for example. SAP EM processes the event message (see Inbound Event Message Processing). The system sends the event message to SAP EM . choose Event Reporting → Process Buffered Event Messages . 3. ● Due to technical reasons on the text-based handheld side. Activities 1. When you report events via a BAPI.1. the system displays them.3 Expected Event Reporting PUBLIC © 2014 SAP SE or an SAP affiliate company.7 Buffered Event Message Processing Use You can specify that event message processing should be buffered. see the Implementation Guide (IMG) for Event Management under Event Messages. All rights reserved. ● You have event messages that have been buffered. you can send each field for reporting event data only once.

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 result is always “TRUE”. Prerequisites ● SAP EM has created event handlers. Page 42 of 85 . recipient not available) You call transaction /SAPTRX/MI02 directly in the system. 8.5 Reactions to and Actions for Events Reactions to events are preconfigured notification or follow-up options in SAP Event Management (SAP EM). Select your confirmations. Choose Send. or you use the event reason within conditions in the rule set of an event handler. ● SAP EM has created predefined expected events (expected event list) for each of these event handlers. if required: ■ Actual date ■ Actual time ■ Actual time zone Enter the following to confirm an expected event: ○ Date ○ Time ○ Time zone ○ Internal code for the event reason You define internal event reasons in Customizing for SAP EM. when you match the expected and the reported locations. ● The tracking ID code ID is case sensitive. If you have defined a location and location matching for an expected event. Therefore. 9. the service provider tracking ID code set and service provider tracking ID code ID.4. If a supplier reports a delay. Actions in response to events are query options in SAP EM. 6. All rights reserved. ● The tracking ID code set is not case sensitive. If. Activities 1. Choose transaction /SAPTRX/MI02. 1. The system displays the event reason in the event handler list when you query SAP EM. Specify the following to identify an existing event handler: a. see the Implementation Guide (IMG) for SAP EM under Event Management → Event Handlers and Event Handler Data → Expected Events → Define Expected Event Profiles . Choose Go . if they are unique b. for example. 2. In this case. 5. 4.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 to SAP Event Management (SAP EM): ● ● ● ● Date Time Time zone Status reason (for example. ● You must also specify leading zeros for the tracking ID code ID. if required: ■ Planned date ■ Planned time ■ Planned time zone ○ The following for the event message. If you have defined partner matching for an expected event. if the tracking ID code set and the tracking ID code ID are not unique 3. 7. if required ○ The following for the expected event. you can define in Customizing for SAP EM that SAP EM is to send an e-mail to the shift manager. the system automatically uses the location of the expected event when reporting this event. SAP EM determines the event handler that belongs to the event message and updates the event handler data. For more information about defining internal codes for event reasons. Choose Post selected messages . The system sends the event confirmation to SAP EM. For more information about defining expected events. The tracking ID code set and tracking ID code ID. A confirmation screen appears. we recommend that you report events using the Web interface (classic). for example. the system cannot apply it for this form of event reporting. SAP EM determines the expected events that belong to the event handler and displays the following: ○ The internal event code text ○ The predefined location. In addition. for PUBLIC © 2014 SAP SE or an SAP affiliate company.

For more information. define appropriate rule conditions in a rule set. When the delivery is expected to arrive at the customer. Whether SAP EM returns data to the application system to trigger activities using a rule set. exceptions and unexpected business about the following: events. end of putaway. or supplier Simple notification about the punctual loading of a complete delivery at the producer. in addition. or about Simple notification. SAP EM automatically updates the transportation status to Loaded in the application system. All rights reserved. additionally query a status. Whether SAP EM is to trigger different activities To do so. SAP workflow. Framework as for option 1. a customer complains about an incomplete delivery. Moreover. logistics service provider. or the departure of a service provider to the customer. Partner. using Alert Management. 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 Customer Simple notification using the Alert Simple notification using the Alert Framework for the punctual arrival of a complete delivery at the customer. SAP EM provides a list of alternative carriers. subcontractor. as for option 1. you can The option to start a workflow or alerts for exceptions and unexpected business messages to SAP EM. or delayed or damaged deliveries. Your partners can transfer the data using an Internet portal. You have already agreed delivery times and prices with several alternative providers. the application system provides you with a list of all customers and their required delivery times with a prioritization according to the importance of the customer. or for delays or damage. you can start a query to SAP EM. The quantity that you have put away already. Activities You can define the following reaction options in Customizing for SAP EM: In which cases SAP EM is to notify someone: When an event is reported within the expected time (regular event) When an event is reported earlier or later than expected (for example. Where the delivery currently is. or the loading start or arrival at the customer. but more expensive truck transporters. with information about the availability of raw materials or means of transport. SAP EM automatically updates the transportation status to Loaded in the application system. Own event message input. by email. for the start of production. for example. for example. for example. for example. How much scrap there is for a product in production. for example. When the supplier sends the event message Loading End (LOAD) to SAP EM. the punctual arrival of raw materials ordered for production at the factory. Moreover. for example. or air transportation instead of sea transportation. SAP EM displays this selection of alternative providers. The application system displays this selection of alternative forwarding agents. the notification contains a URL that the customer can use to search for the current process status. Your partners can transfer the data using an Internet portal. for example. Own event message input. about the following: events. for example. Example A truck cannot make its deliveries to individual customers on time because of a road accident. You use the query to check which service provider transported the delivery and whether this service provider has previously been unreliable. an overdue event) When an event is not reported When an unexpected event is reported How SAP EM is to notify someone. for example. for example. Employee Option 3 Simple notification by sending event Simple notification. see Customizing for SAP EM under Event Management PUBLIC © 2014 SAP SE or an SAP affiliate company. by e-mail or fax. delays or damage. for example.example. When the supplier sends the event message Loading End (LOAD) to SAP EM. for example. How punctually your supplier has delivered your products. as for option 1. rescheduling. Example A supplier cannot deliver a raw material on time because of a delay to a ship. for example. for example. or the Alert Framework. When the partner can start to load the delivery. Reactions to Page 43 of 85 . The quantities that your supplier has already manufactured for a manufacturing order. you can The option to start a workflow or alerts for additionally query a status. about the availability of raw materials at the supplier. You have already agreed delivery times and prices with several alternative forwarding agents. quicker.

When SAP EM receives a message containing the unexpected event Delay . To do this. All rights reserved. 1. SAP EM informs both your partner and your customer via an e-mail. Example Example of Preconfigured Reactions to Events The following figure shows an example of predefined reactions to events: Reactions to Events In this example. with each rule set triggering a different reaction from SAP EM to the same event message. SAP EM informs both your partner and your customer via an e-mail.Event Messages Define Rule Sets . You can define a particular rule set for each event handler type. and also triggers the rescheduling of the arrival time in the application system. you have defined the following in SAP EM using a corresponding rule set: As soon an employee reports the production start to SAP EM. The rule set for event handler type A plans the PUBLIC © 2014 SAP SE or an SAP affiliate company. ● You can use rule sets to specify that SAP EM is to process event messages in a different way. since your service providers have various levels of reliability. you have defined an event handler type for service provider A and one for service provider B. you want SAP EM to react differently to service provider delays. ● You can use a rule in the rule set to call the expected events that you have defined.1 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.4. SAP Event Management (SAP EM) assigns the rule set that belongs to the event handler type when creating an event handler.5. Use ● SAP EM processes event messages with the rule set that were set for an event handler. Page 44 of 85 . For example.

The following figure provides a detailed overview of a rule set structure: Integration You can call a BAPI within a function module. sending an e-mail). or a multitask activity. SAP EM executes the next rule. you can have the system update the delivery document in your application system. Page 45 of 85 . and thereby trigger activities in a remote system. SAP delivers rule activities that you can use within a rule set. which you call in the rule condition of the rule. PUBLIC © 2014 SAP SE or an SAP affiliate company. If you have not defined a value for the condition evaluation. 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. The individual rule consists of a rule condition and a rule activity that SAP EM executes based on the result of this evaluation. Structure A rule set consists of a set of rules that SAP EM evaluates when processing event messages. after the customer has completed the proof of delivery. reported by your service provider. For example.shipment start and shipment end. All rights reserved. ● The single-task activity can be an event handler method. Your service provider B is more reliable. Processing in the rule set then branches to the TRUE or FALSE rule. reported by the customer. The following figure provides an overview of a rule set structure: If the evaluation of the rule condition returns “TRUE”. as expected events. You can call several rule conditions within a rule by grouping several rule conditions in a set. You specify only the shipment start and proof of delivery by the customer as expected events for event handler type B. a function module. depending on the condition evaluation. and the proof of delivery.

1 Rule Condition Definition A decision-making criteria that SAP Event Management uses when checking if it can execute a task for an event handler. by sending an e-mail). or not. sending an e-mail or updating the status of a means of transport) in SAP EM. ○ You can use the plug-in function modules that SAP delivers with SAP EM or you can define your own. Features ● A rule set consists of a set of rules that SAP EM evaluates one after the other when an event message is processed.4. ● Each rule can contain activities and a condition. you can specify that an e-mail is sent to the person responsible in the case of a delay to a shipment. such as the date or sequence). ○ The method reads or updates the event handler’s internal data (for example. ● 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. or can call a BAPI in a remote system to update the business object data. you can define as tasks that an e-mail is sent to an employee. or that application object data is updated. ● Each multitask activity consists of a sequence of tasks that SAP EM executes one after the other. For example.5. You specify how SAP EM reacts to event messages by defining: ● Conditions for the rule activities ● Rule activities with their tasks For example. activation or deactivation of an event handler. You can define a Boolean equation with parameters from the event handler and the event message. ● You have defined rules with their activities and conditions within the rule set.1.5. You use the logical connection between the individual rule conditions (AND or OR relation) to define how rule processing occurs.4. update to event handler data. Rule conditions can be either Boolean equations or function modules. All rights reserved.1. or that the status of event handler is changed. ● A condition can also consist of a condition set. or an equation that executes a complex evaluation and then returns the result to the rule processor. ○ Multitask activity PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 46 of 85 . the rule processor decides whether SAP Event Management needs to react to the event message (for example. 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? 1. SAP EM continues to process the event message with the respective activity. assuming that you have previously defined this activity. Depending on whether the evaluation of the individual condition returns the result “TRUE” or “FALSE”. The plug-in function module can refer to event handlers or other objects (for example.1. Use The rule processor checks the conditions by calling the appropriate rule set for the respective event handler when processing event messages. and to specify how SAP EM reacts to event messages. Prerequisites ● You have defined a rule set for each event handler type.2 Evaluation in the Rule Set Use The evaluation of the rule set determines how SAP Event Management (SAP EM)reacts to incoming event messages. You can choose from only those methods delivered with the SAP EM Class Library and cannot define your own without modifying them. check of individual values for the event handler’s expected events. Depending on the result. Use your own plug-in function modules for activities. 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.

2. The evaluation of rule condition 3 returns “TRUE” and SAP EM executes activity 3 . 3. SAP EM calls a BAPI to process the proof of delivery in the application system. SAP EM processes the respective tasks for each activity. the application system sends a confirmation to SAP EM so that SAP EM saves the updated event handler data. The following figure provides an overview of the evaluation in the rule set: PUBLIC © 2014 SAP SE or an SAP affiliate company. Activity 3 consists of a task: proof of delivery. methods. SAP EM evaluates the condition for each rule that is applied and calls the individual activity depending on the result of this evaluation. Processing then continues with rule 2 . Page 47 of 85 . for example. 4. The event handler controller forwards the incoming event message to the rule processor that applies the corresponding rule set. call a BAPI to update data in the application system. SAP delivers rule activities that you can use within a rule set. or multitask activities.A multitask activity can consist of one or more plug-in function modules. These tasks can. All rights reserved. After SAP EM has evaluated all the rules one after another. The following figure provides an overview of a rule set structure: Activities Rule evaluation within a rule set for an incoming event message 1. SAP EM does not execute an activity and processing continues with rule 3 . The evaluation of rule 2 returns the result “FALSE”. 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. The evaluation of rule condition 1 returns “TRUE” and SAP EM executes activity 1 .

A new screen consisting of two sections appears. The event messages for the shipment start and shipment end go to SAP EM.5. a task). You can have the system display every detail on a rule set (for example. To display a rule set while defining it. 3. Select an (existing) rule set and display it. The following icons are used for displaying components of a rule set: Icon Object Rule Set Rule Rule Condition PUBLIC © 2014 SAP SE or an SAP affiliate company. 1. SAP EM calls a rule for these event messages from the rule set belonging to the event handler. 2. The left-hand side contains a comprehensive overview of the rule set and its components in the form of a navigation tree. Select the required component (for example. This rule executes an activity. All rights reserved. The detailed information is displayed on the right-hand side of the screen in display mode. the individual rules. Integration This function is available to you under Display Rule Set in the transaction for defining rule sets. This activity contains the task that calls a BAPI to update the date or the stages of your shipment in the application system.3 Rule Set Display Use You can use this function to gain a comprehensive overview of a rule set and its components. for example. see the Implementation Guide (IMG) for Event Management → Reactions to Event Messages → Define Rule Sets.1. Page 48 of 85 . You have specified that your shipment is SCEM-relevant so that SAP EM creates an event handler for your shipment document. or tasks).4. For more information about defining rule sets. 4.Example You create a shipment document in SAP R/3. 5. You can go back to the transaction for defining rule sets from this separate screen. choose Monitoring and Lists → Display Rule Sets . activities. Activities 1. use the transaction for defining rule sets (see section Integration). The system displays an overview of the rule set that has been defined in a separate screen. On the SAP Easy Access screen for Event Management .

4. as the person responsible. Page 49 of 85 . or deleting an SCEM-relevant business object in the application system. The conditions that were created using the condition editor are displayed in HTML format to make it easier to read them. for example. you can simulate processes. The simulation also transfers the SCEM-relevant data from the application system to SAP EM . 2.5. When data is updated. changing or deleting an SCEM-relevant business object in the application system (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. 4. choose the transaction for defining business process types (/SAPTRX/ASC0AO). This is because multitask activities consist of a sequence of tasks. SAP EM shows the various processes step-by-step (depending on your Customizing for the application system and SAP EM). about these situations. Choose Simulation as the mode for a business process type. but also for the process steps in SAP EM . In the case of multitask activities. · If the simulation is successful. Choose Continue or Cancel . · You have set up Customizing for SAP Event Management (SAP EM). Result · The system has simulated all SCEM-relevant processes. 3. Start the simulation by either saving. if required.2 Connection to the Alert Framework The Alert Framework supplies you with alerts (for example. In critical situations such as a delay or contamination. 5. In doing this. the simulation activity is aborted and the SAP Easy Access screen appears. Simulating Processes in the SAP Application System and SAP EM Use To see the consequences of saving. for example. you can start the process in the active business process mode. the purchase order PUBLIC © 2014 SAP SE or an SAP affiliate company. only the activity ID is displayed as a detail. This provides you with an overview of all the processes in SCEM. This notification can contain information about the event handler that belongs to the event message. In the application system. · If problems occur. Save the change. The coding is displayed for conditions that were programmed for function modules. Prerequisites · You have set up Customizing for the SAP application system. Procedure 1. All rights reserved. you have set the simulation mode not only for all SCEM-relevant process steps in the application system. You can display the details for each of these tasks. you know where and in which process you can make corrections. For example. The system displays the chosen business process type and the application object types that belong to it. 1. updating. SAP Event Management calls the Alert Framework.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. by e-mail or SMS) as a service provided by the SAP NetWeaver Application Servers. in single-task activities). It can inform you. a shipment document). You can cancel the simulation at any point. SAP EM does not save the values from the simulation.

2.sap. for example. 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 . you do not need an RFC connection. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. Since SAP Event Management is based on SAP NetWeaver Application Server 6. destination. In Customizing for SAP Event Management. or status. you define the alert category in Customizing for SAP NetWeaver under Application Server Basis Services Generic Business Tools Alert Management Define Alert Categories . 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 . The Alert Framework requires a central server on which an SAP NetWeaver Application Server 6. SAP Event Management uses the corresponding tracking ID and the internal event code set. All rights reserved. 3. 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.com Developer's Guide IT Scenario-Driven Enhancements to Applications SAP NetWeaver Operations Triggering Alerts . This rule calls the ALERT_CREATE rule activity function in response to the event Delay . 4. On the SAP Easy Access screen. for example.20 or higher.2.1 Direct Access to Detailed Information You can use the Alert Framework to send an alert with a link to a user. you specify an RFC connection to determine the system on which the Alert Framework runs. Choose Documentation ABAP Goto . You assign the alert category to a rule in Customizing for SAP Event Management under Reactions to Event Messages Define Rule Set . 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. 3. SAP NetWeaver Library SAP NetWeaver Alert Management under the link You use an SAP NetWeaver Application Server 6. Page 50 of 85 . If you run the Alert Framework and SAP Event Management on the same system. You create at least one alert category and at least one alert container in Customizing for the Alert Framework. DELAY for delay. 1. you define the alert category in Customizing for SAP Event Management under Reactions to Event Messages Define Alert Framework Connection Define Alert Categories . as an e-mail or SMS. Your customer sends an event message Delivery Delay for a shipment to SAP Event Management that contains a specific event code. Note If you run your SAP Event Management and the Alert Framework on the same system and in the same client. see the function module description. In comparison with SAP Business Workflow. To find the event handlers. 6. If you run the Alert Framework and SAP Event Management on different systems.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 . Enter the /SAPTRX/CREATE_ALERT function module and choose Display . 4.20 or higher is installed. You define how the alert is to be sent. These settings are joined together in an activity parameter ID. SAP Event Management updates the event handlers that belong to the shipment. The rule activity function connects SAP Event Management to the Alert Framework. an SMTP server).20 or higher. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. For more information. choose Reactions to Event Messages Define Alert Framework Connection Define Alert Framework Integration to SAP Event Management . Note For a detailed description of the activity function. the Alert Framework offers simpler handling and is less performance intensive (see Connection to SAP Business Workflow). This is irrespective of whether you run the Alert Framework and SAP Event Management on the same system. enter NONE here. the central server of the Alert Framework can run on the same system.5.4. and who the recipient is to be in Customizing for SAP Event Management. 5.number. When you first start the Alert Framework. Your new rule is contained in the rule set for these event handlers. For more information. 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. This means that this user can monitor a process from the alert. Example 1. This can be the same system on which your SAP Event Management runs. If you run SAP Event Management and the Alert Framework on the same system. choose Tools Workbench Development Function Builder . Prerequisites PUBLIC © 2014 SAP SE or an SAP affiliate company. You have defined an RFC connection from SAP Event Management to the Alert Framework. Enter NONE in the transaction for changing the RFC destination to the central alert server.sap. Prerequisites You have defined a connection from the Alert Framework to your communication system (for example. The alert is sent to the customer via e-mail. 2. Process 1.

● 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. You have defined the link for the Web interface in Customizing for SAP Event Management under Framework Connection Define Alert Framework Integration to SAP Event Management . Status Queries. All rights reserved. SAP Business Workflow as a SAP Web Application Server service allows you not only to automate a business process. When a user calls the link. 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. you can link SAP Event Management (SAP EM) to SAP Business Workflow in accordance with your rule set. your customer sends a proof of delivery that triggers the event Proof of Delivery in SAP EM. 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. 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 can define the link for one Web interface transaction only. For more information. and Web Interface Web Interface Assign User Profiles and Web Interface Transactions to Users . The user cannot change the event handler data. You have defined the link for the Web interface in Customizing for SAP Event Management under Reactions to Event Messages Framework Connection Define Alert Framework Integration to SAP Event Management . Page 51 of 85 . On the SAP Easy Access screen. Furthermore. You define parameters to link the events that start workflows in the local system or in another system. Make sure that the name of the ICF service is the same as the name that you use for the Web interface transaction. On the SAP Easy Access screen. Prerequisites SAP has already predefined the event type linkage to trigger a workflow. make sure that the user who you assign to the new ICF service is the service user. see Customizing for SAP Event Management under Framework Integration to SAP Event Management . the ICF starts the ICF service and SAP Event Management displays the detailed data for the event handlers belonging to the alert. Reactions to Event Messages Define Alert Framework Connection Define Alert Connection to SAP Business Workflow Use When critical situations occur. but also to inform the person responsible. Define Alert Prerequisites for the Web Interface (Web Dynpro ABAP) You have completed the prerequisites for connecting the Alert Framework (see Connection to the Alert Framework). and Web Interface Web Interface Define Web Interface Transactions . Check that the following settings have been made correctly: ● ● ● ● Object type: /SAPTRX/EH Event: START_WORKFLOW Receiver type: TRIGGER_WORKFLOW Receiver call: Function module PUBLIC © 2014 SAP SE or an SAP affiliate company. If you want to react to events. You have defined a service user who is allowed to use the direct link. Note Assign only the necessary authorizations to the service user. Status Queries. For more information about SAP Business Workflow. In the Web interface (Web Dynpro ABAP). see the SAP Library under SAP NetWeaver Components → SAP Web Application Server → Business Management (BC-BMT) → SAP Business Workflow Engine (BC-BMT-WFM) . choose Tools Administration Administration Network HTTP Service Hierarchy Maintenance and create a new ICF service under em_wda_ui SAP Event Management . For example. since SAP Event Management does not apply an authorization or filter concept for this user. Reactions to Event Messages Define Alert 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. For more information. the system administrator receives a message and the system saves the event temporarily. which in turn uses SAP Business Workflow to trigger the settlement process for the delivery. You have created and configured an Internet Communication Framework service (ICF service). choose Tools Administration User Maintenance Users . You have defined a Web interface transaction in Customizing for SAP Event Management under Event Messages.Prerequisites for the Web Interface (Classic) You have completed the prerequisites for connecting the Alert Framework (see Connection to the Alert Framework).

Allow event handlers to be created and changed in SAP Event Management (see also Authorizations for Changing Data and Sending Event Messages) Note Note that the system only checks the first 40 characters of the parameter values. you specify the internal event code of the event message as Arrival at Customer . authorization profile. If you use the workflow locally. In this case. SAP APO. The event START_ WORKFLOW starts the workflow that triggers an automated process (settlement process) in the application system (SAP R/3. only the standard authorization concept of the Archive Information System applies. ● At least one rule set that uses the rule for the workflow and its activity. ○ You can assign a condition to your rule to control how the workflow is triggered. The event links SAP EM to SAP Business Workflow. which it finds using the tracking ID and the internal event code set. Prerequisites You have the authorization to assign a user to a role and a profile. You can query and display event handler data using the Web interface or function module /SAPTRX/BAPI_EH_GET_DATA_GEN. role. 2. Example 1. see the Implementation Guide (IMG) for SAP EM under Event Management → General Settings in SAP Event Management → Define RFC Connection to Application System . All rights reserved. which are already archived. 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. SAP CRM). and event handler type: PUBLIC © 2014 SAP SE or an SAP affiliate company. For more information about integration between SAP Business Workflow and SAP EM. Activities The following figure provides an overview of the connection between user.● 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. For example. In this case this authorization concept also applies for the display of event handler data. ○ You create a rule in your rule set by selecting the activity WORKFLOW_START. see SAP Event Management User. Authorization Profile You define authorization profiles to allow the following: Allow information to be displayed when querying or evaluating event handler data. ○ You specify the first activity parameter. choose None or Workflow_local . This rule triggers the creation of the event START_ WORKFLOW when the event Proof of Delivery is reported.5 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). 3. Filter Profile A filter profile allows you to restrict the event handler data that is displayed in a user-specific or role-specific way. For more information about setting up an RFC connection to the application system. Your new rule is in the event handler’s rule set. see the Implementation Guide (IMG) for SAP EM under Event Management → Reactions to Event Messages → Define SAP Business Workflow Integration. 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. 1. If you query and display event handler data using the Archive Information System (transaction SARI). Page 52 of 85 . SAP EM updates the event handlers belonging to the shipment. For an example of how you define a user authorization with which a user can display event handler data. 4. filter profile. The activity parameter is the activity ID that you defined previously in SAP EM Customizing.

You assign the authorization profile to an event handler type. 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). By assigning the authorization profile to a role. SAP Event Management only displays certain parameters to the user when creating. For more information about defining authorization profiles. or evaluating event handler data.Overview of Authorizations and Filters Authorization Profiles Depending on the authorization profile. For more information about users and roles for the SAP NetWeaver Application Server (AS) ABAP and Java. fields. You specify tables. Authorizations and Filters Define Authorization Filter Profiles In the filter profile. For example. a shift manager can only see data for plant 1100. For more information about defining filter profiles. see Customizing for SAP Event Management under Authorizations and Filters Define Filter Profiles. You assign a role to a user (transaction SU01). ● Which users are allowed to send event messages to SAP EM PUBLIC © 2014 SAP SE or an SAP affiliate company. the expected events for an event handler. You assign the filter profile to an event handler type.com SAP NetWeaver by Key Capability Security Identity Management User and Role Administration of AS ABAP and User Management of the Application Server Java . or rows that SAP Event Management does not display to the user. see Customizing for SAP Event Management under Profiles. For more information about roles in SAP Event Management. changing. you specify which event handler components. see Authorizations for Changing Data and Sending Event Messages and Roles for SAP Event Management.sap. Page 53 of 85 . All rights reserved. You assign the authorization data to a role. for example. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. you determine the authorization objects and their executable activities. 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. SAP Event Management displays to a user. You assign the filter profile to a user or to a role.

It enables you to detect or highlight exceptional situations and to interactively react to those exceptions. Features For a description of the features. see the SAP Library under SAP Technology Components → SAP Web Application Server → Security (BC-SEC) → Users and Roles (BC-SEC-USR) .6. 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. IPAR for changing info parameters) and the activity (for example. see the following: Web Interface 1. accessible through menu entry “Web interface (classic)”. 1. All rights reserved.Activities 1. and Web Interface Web Interface . PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP Event Management automatically generates the required settings so that you can use the Web interface. As a result. The layout of the web interface is completely configurable through user and role specific profiles. Prerequisites In Customizing for SAP Event Management under Event Messages. Status Queries. Assign the user to role SAP_EM_ADMIN or create a new role. you want a user to be allowed to both change and create info parameters. ● 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. 2. Role SAP_EM_ADMINcontains 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). you have executed the Customizing activities described in the section Define Web Interface . but only to delete control parameters. For example. If necessary it can still be used after upgrade for compatibility reasons.1 Web Interface You can display a Web interface in a Web browser. The web interface displays the selected tracked processes and related details. For more information about maintaining the user master record. But new features are not available through this technology. If you create a new role. note that the subobject (for example. Create a new user or maintain an existing one. 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. is no longer part of the standard software package for SAP Event Management. Page 54 of 85 . 01 for changes) operate in combination with each other. Note The former WCL user interface for SAP Event Management. It can also be used to manually report expected and unexpected events.6 User Interface The main user interface in SAP Event Management is the web interface to select and monitor the tracked processes.

the scenarios are available to the user on each PC No logon. All rights reserved.Prerequisites You have assigned at least one user profile and one scenario to the user in Customizing. For more information about frequently asked questions. Status Queries. See also: Displaying a Network 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 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 Note For more information about the individual Web interface settings.1. 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. Event Management Event 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 1. For more information. Page 55 of 85 . about identification data (ID data) Send event messages to SAP Event Management that might contain an attachment. If you have the appropriate authorization in your user profile. the scenario is available to the user on each PC Note the following: Activities means: the actions and functions that are available to the user in the UI. the authorization concept allows you to display detailed information about the network and to execute a drilldown. Scenario means: the combination of user profile(s) and web transaction(s) assigned to the user in SAP Event Management. user chooses link in email and directly sees the event handler data for the scenario to which he or she is assigned in Customizing Read authorization only. for example. to another SAP system. see Frequently Asked Questions (FAQ). by individually arranging the position of the screen building blocks. or to another event handler Display the document flow networks that belong to a certain event handler Only the Web interface displays the network. 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.1 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 User Logon Normal user Direct link user Activities Scenario Assignment User Settings Logs on using the logon page with Depending on the user profile. see Customizing for SAP Event Management under Messages. all Multiple scenario assignments System saves the assignment in user name and password Web interface functions possible the database. see Customizing for SAP Event Management under Event Management Event Messages. not possible to send event messages Only one scenario assigned System saves the assignment in the database.6. and Web Interface Web Interface Define Web Interface Assign User Profiles and Web Interface Transactions to Users . You cannot display the network in SAP Event Management. PUBLIC © 2014 SAP SE or an SAP affiliate company. Status Queries. 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. and Web Interface Web Interface Define Web Interface .

You can log on to both systems in multiple clients.6. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. You are familiar with programming in ABAP. Note For more information about X. Use the link to display the required data. Prerequisites You have generated a service user and an Internet Communication Framework service (ICF service).More Information For more information about logging on with SSO. see Direct Access to Detailed Information in the section Prerequisites for the Web Interface (Web Dynpro ABAP). Procedure 1.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 . The table eventhandlerheaders provides the required event handler GUID in the attribute EH_GUID.509 Client Certificates . 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. Add the following parameters to the Uniform Resource Locator (URL) for the Web transaction /saptrx/em_fpm_ehdetail: &sap-client=<Client> &sap-language=<Language. Note For more information about logon tickets. The one Web server communicates with both systems using a different URL.sap. 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 have an SAP Event Management for both your development system and your test system.1. for example.1 Logging On to the Web Interface with SSO You can use Single Sign-On (SSO) when logging on to the Web interface.509 client certificates. You only log on once to one of the systems. To do so.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.sap. Furthermore. You use logon tickets to communicate with multiple SAP systems (for example. 1. You use X. see Logging On to the Web Interface with SSO For more information about setting up a direct link user.wdf.2 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.1.6.corp:44376/sap/bc/webdynpro/saptrx/em_fpm_ehdetail?sapclient=001=EN=quick=HfEgfav7AWNX00002a8Jc0=PTA10_ID 3. for example: EN> &action=quick &EH_GUID=<EH-GUID> &UP ID=<User Profile ID> Example The following is an example of a link for calling the Web interface transaction: https://uscia9s. All rights reserved.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 .sap. you can use the method CREATE_EXTERNAL_WINDOW of the Web Dynpro component interface IF_WD_WINDOW_MANAGER. Create the link for calling the Web interface transaction that you have configured for the service user.1. see Setting Up A Direct Link User For more information about personalizing the Web interface (Web Dynpro ABAP).1. you have assigned the service user that you defined to the Web interface transaction and to the user profile. PUBLIC © 2014 SAP SE or an SAP affiliate company. For more information. SAP Event Management and SAP NetWeaver Business Intelligence) using the Web interface. 2. Example For example.509 client certificate to avoid having to enter your user information repeatedly. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. Page 56 of 85 . 1. The table SELECTIONFIELDS must have been filled in accordance with the selected Web interface transaction. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.

When you click the link.6. In Customizing.1. the following applies: If you want to display archived data. Prerequisites In Customizing. All rights reserved. you see all the parameter values in a separate dialog box. Status Queries. Archiving and Web Interface Improvements (SCM_EM_HIGHVOL). The appropriate settings must be made in Customizing for SAP Event Management under Management Geographical Map . Status Queries. 1. In SAP Event Management. or the event handler details. you have defined the parameter display for info parameters and control parameters. and Web Interface Configure Fields for 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. you have assigned the configured fields to a user profile. For more information. including the number for displaying indexed parameter values. and Web Interface Define User Profiles . You cannot include info or control parameters in the field catalog.1. In Customizing. 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 archive has the restriction that you cannot use more than one attribute with cardinality greater than one for the search. the Web interface also displays a link. For more information. you have defined that empty fields are to be hidden. If no values exist for a parameter. event handler overview.2 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. Latitude and longitude must be included in the Customizing activity Event Message Parameter Mapping. see Customizing for SAP Event Management under Event Management Event Messages. For more information. and Web Interface Configure Fields for User Profiles .4 Printable Version for Tables on a Web Page You can print tables on a Web page. Status Queries.1. as required.3 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. the Web interface displays the number of indexed parameter values that you defined. Page 57 of 85 . A parameter can have an unlimited number of values.6. Event Management General Settings in SAP Event Features SAP Event Management has a Map panel in the Web interface where a geographical map is displayed Note If none of the event messages have a latitude or longitude assignments. the Map panel is automatically hidden. see Customizing for SAP Event Management under Event Management Event Messages. you can hide these empty fields. Activities When you call the event handler list. Activities 1. 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. Note If you have activated the business function EM. If a parameter has additional values. The Geomap profiles and Geomap maintenance in the Customizing activity Define User Profiles are maintained. Features PUBLIC © 2014 SAP SE or an SAP affiliate company. see Customizing for SAP Event Management under Event Management Event Messages.6.1.

you need to maintain whitelists for URLs that contain variables as parameters (known as “dynamic URLs”). If you define a URL and SAP Event Management transfers parameters when branching to an application.6. see SAP Notes 918236 and 894009. control parameters.6 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. SAP Event Management displays the associated transaction (for a purchase order. The URL call might lie outside the SAP systems and it is therefore not secure. info parameters. You can activate a virus check with the SAP Web PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP Event Management displays the PDF document. Note For security reasons. For a description of how to create a printable version. In the Web interface. this call is not secure.1. see Customizing for SAP Event Management under Event Messages. Page 58 of 85 . After the user has logged on. SAP Event Management displays the standard logon screen. SAP Event Management checks which data it is to display. If you use a link to a URL. The hierarchy for the event is display in a separate window. All rights reserved. the Web interface calls SAP Event Management. 4. The user must log on with the same user that he or she uses in the SAP application system. you must ensure that the application being called can process these parameters. The portal service uses the Adobe document services server (ADS server) to generate a Portable Document Format document (PDF document). the application object ID or a tracking ID. you can display the hierarchy for an event handler. The ADS server uses an RFC connection to send the PDF document to SAP Event Management. Only URLs that are admitted through the whitelist customing in SAP Event Management can be reached. and to display the related event handler details. Features When you use the drilldown in the Web interface. This enables SAP Event Management to display a document from another SAP system or the content of an internal or external link. SAP Event Management performs the following: 1. SAP Event Management uses a Remote Function Call connection (RFC connection) to call a portal service. the system automatically adds a hierarchy tree panel to the main screen.1. We recommend that you use the SAP Web Repository to display certain content via a URL.1 or higher. If you use a link to another SAP system.6. for example). 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. You can include variable parameters with links to external URLs that are derived from system parameters. You have performed the corresponding Customizing in SAP Event Management. The tree view is used to navigate through all the levels of the hierarchy the event handler is currently part of. 1.5 Use of the Event Handler Hierarchy In the Web interface. and Web Interface Web Interface Assign Link to Configured Field .When you use the Print Version pushbutton. or you can use a Uniform Resource Locator (URL) to send parameters to another application. Prerequisites You have implemented PI-Basis 2005. 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 can also display the hierarchy valid at the point in time of an event. You are responsible for the data that SAP Event Management displays using the URL. For example. if a file is called that enters the system via a function without a virus check. For example. 3. you have assigned a link to the transaction for displaying a purchase order (ME23) to an event handler. by marking the corresponding event in the Event Messages panel and pressing the button “Display Hierarchy for Event”. SAP Event Management checks the Customizing for the user profiles. 1. For more information. 2. SAP Event Management checks the following: The business object type that SAP Event Management is to use The business object method that SAP Event Management is to use The transaction that SAP Event Management is to use Whether the user is defined in the other SAP system Whether Single Sign-On (SSO) is allowed for the user in the other SAP system Note If the user is not defined in the SAP application system or if SSO is not allowed for the user. Status Queries. But SAP Event Management does not check whether the display of the URL data is secure and permitted.

Page 59 of 85 . PUBLIC © 2014 SAP SE or an SAP affiliate company.1. This protects all data. communication between the Web server and SAP Event Management can be secured. the system launches the Event Management main screen with an open search panel. All rights reserved. Furthermore. or sets of tracked objects or processes. Why can I not see the latest information on my screen? If you want to display the most up-to-date version of a screen that has already been visited. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.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 . the system displays the initial screen where you can select a service. for example. What can I do with the SAP Event Management Web application? You can search for one or more tracked objects or processes.1.com SAP R/3 Enterprise Release 4. about data security when data is transferred (see General Information) Information about navigating to the Web interface (see Navigation to the Web Interface) Information about the administration screen (see Administration Screen) Information about the search panel (see Search Panel) Information about tables (see Navigation and Sorting of Tables) Information about the search result panel (see Search Result Panel) Information about sending event messages (see Sending of Event Messages (Fast Entry)) Information about sending event messages for multiple tracked objects or processes (see Sending of Event Messages for Multiple Tracked Objects or Processes) Information about sending event messages (see Sending of Event Messages) Information about settings for the Web interface (Web Dynpro ABAP) (see Settings) Information about the details of tracked objects or processes (see Details of Tracked Objects and Processes) 1. the system administrator can configure whether the fields are casesensitive or not.1.sap. 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. There you select the tracking scenario you want to use from the dropdown box on the top of the panel and then you enter your search criteria.7 Frequently Asked Questions (FAQ) You can find information here about using the Web interface that cover the following topics: General information. if the administrator installs Secure Network Communication (SNC).7. You can observe the processing and the status of these tracked objects and processes and you can send event messages to a single tracked object or process or to a group of tracked objects or processes. Are the input fields case-sensitive? This depends on the configuration of the field in Customizing for SAP Event Management. if the Web server uses the SSL (Secure Sockets Layer). You can call the service directly and can send an event message without first having to search for the corresponding tracked object or process.6. For more information. Here. so that unauthorized persons are not able to decode this information when it is transferred in the Internet. 1. Can I print the tracked objects and processes displayed on the screen? Yes. 1. You can also use the standard User Interface to directly send event messages.Repository to check documents before an upload.1 General Information Questions and Answers in the General Information Area Question Answer Will my data be transferred safely? Yes. Use the Web browser print function to print the entire screen. you have to call the Uniform Resource Locator (URL) again or you have to use a refresh pushbutton. such as customer name and address or supplier name and address. For more information about security issues in Web Dynpro ABAP. and you can display the data in several levels of detail.70 SAP NetWeaver Components SAP Internet Transaction Server ITS Implementation Models WebRFC Programming SAP Web Reporting .6. How can I send an event message without first having to search for the corresponding tracked object or process? If you choose SAP Event Management Web Interface Fast Entry on the SAP Easy Access screen.7.2 Navigation to the Web Interface Features Information About How You Can Navigate to the Web Interface Question Answer How can I search for an object or process? If you choose SAP Event Management Web Interface Search on the SAP Easy Access screen. see: Customizing for SAP Event Management under SAP NetWeaver Application Server System Administration Virus Scan Interface SAP Library for SAP Event Management on SAP Help Portal at http://help.sap.6.

6.1. Exchange the customer_brand_image. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. You can select a scenario to which you are assigned and then enter criteria to search for tracked objects and processes. What happens when I enter values in several fields? An AND relation exists between the fields. Similarly.6.1. The dropdown list box displays all saved searches depending on the tracking scenario you have chosen.1. or change the search criteria.NNN Days as a dynamic date calculation. the system then saves your search criteria and adds the new saved search name to the Saved Searches dropdown list box. Exchange the customer_logo. choose Tools ABAP Workbench Overview Object Navigator .com SAP NetWeaver Library SAP NetWeaver 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 . This is to ensure a consistent look across all applications. 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. the administrator who creates your user profile can set default values for input fields. How can I change the layout of the screens? By default. Page 60 of 85 .sap.4 Search Panel Features Information About the Search Panel Question Answer Why does the search panel have different search criteria? Why do they change when I Different tracking scenarios typically require specific search criteria. all elements in the Web interface that are available in the View Designer are based on a certain stylesheet provided by SAP. Why are there default values for some input fields? Depending on your requirements. Can I select a tracking scenario on this panel? Yes. If the search screen contains any date fields. yes. Choose the calendar icon to the right of the input field. If you want to change the search criteria of an existing saved search. the screen that the employee sees contains different fields from those on the manager’s screen.7. All rights reserved. The system copies the operator for a dynamic date calculation from the selection screen. however. may require other search options than tracking a freight order.3 Administration Screen Features Information About the Administration Screen Question Answer How can I change the logo and the picture in the header of the screen? If you want to change the logo in the header of the screens. if you are looking for tracked objects or processes with PUBLIC © 2014 SAP SE or an SAP affiliate company. The administrator can change the assignment of tracking processes to your user ID. The only exception to this is where you can use Current Date +/. In the dialog structure. Which date and time format should I use? The date and time format that you use depends on the language that you have chosen. choose SAP BC WebDynpro SAP Public SCEM . In which search fields must I enter values? All fields with a red asterisk are required input fields. The system does not support ranges that include or exclude dates in a dynamic date calculation. For example. 1. on the SAP Easy Access screen. What happens if I select Save Search As ? The system saves your search criteria in the database and adds the new saved search name to the Saved Searches dropdown list box. A scenario to track select a different tracking scenario? purchase orders. Can I search using wildcards? In principle. the system first displays the Save Search Criteria window in which you can define dynamic date calculation rules.jpg file for your file to change the picture in the header of the screens.GIF file for your file to change the logo in the header of the screens.7. you must define and save the rules again. You can. Note Make sure that the name and the format of the files remain the same. When you choose the OK button in the Save Search Criteria window. For more information. for instance. Choose the MIME Repository pushbutton. use a different stylesheet. This means that the system takes into account all tracked objects and processes that match all the entered values in your search. for example.

the system has to retrieve a large amount of data. If wildcards are not permitted for a certain field. How can I get details for one of the tracked objects or processes in the table? Just mark the line showing the tracked object in the Search Result panel. you must make an entry with a wildcard in the value help popup window. You can also send an event message for a tracked object or process that does not currently exist.7. Page 61 of 85 .1. you can send event messages.7 Sending of Event Messages (Fast Entry) Features Information About Sending Event Messages Question Answer Which activities can I perform on this screen? You can send an event message for a tracked object or process without first having to search for the object or process.7. Depending on the Customizing settings for SAP Event Management. For more information. These fields have a different color. 1.similar IDs. Does my user profile determine which fields are read-only? Yes. mark the relevant row.com Getting Started . If you use this function and your selection criteria are too extensive.7.6. Which activities can I perform on this panel? When you select a tracked object or process from the list. the system displays corresponding links in the table fields: Links to other URL addresses The representation of the document flow The displaying of indexed fields 1. Export . This can lead to performance problems. Why does the system sometimes show links in the table fields? If the administrator has defined the following in Customizing for SAP Event Management. if the administrator has assigned an event message profile to your user profile.6. and Send Event Messages . the system issues a corresponding message. you can use the standard Web interface sort function on the Sort tab page. 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. for example Report Delay . for example.Using SAP Software Working with Tools and Features Working with Lists SAP List Viewer for Web Dynpro . you can send event messages for one or multiple tracked objects or processes. If you use search helps. The administrator can define fields as read-only in your user profile. the system displays the corresponding actions.5 Navigation and Sorting of Tables Features Information About the Navigation and Sorting of Tables Question Answer Can I sort the table? Yes. see SAP Library for for SAP NetWeaver on SAP Help Portal at http://help. you can trigger SAP Event Management to create the tracked object PUBLIC © 2014 SAP SE or an SAP affiliate company. you can enter an asterisk after the first few characters or numbers. If you want to select a tracked object or process. the pushbuttons Print Version . All rights reserved. How are the different panels in the main screen updated relative to each other? When you mark a line the Search Result panel all related panels on the screen are updated automatically.6. Choose the Send Event Messages pushbutton and choose an action from the action menu.1. If you have the authorization. 1. Can I send event messages from the Search Result panel? Yes. The Details panel is updated automatically.6 Search Result Panel Features Information About the Search Result Panel Question Answer What can I see on this panel? You can see the tracked objects or processes or sets of these tracked objects or processes that match your selection criteria. the search for tracked objects and processes is not restricted in any way.1. What happens if I select the Display More Than 200 Hits checkbox? In this case. When you choose Settings .sap.

Choose the calendar icon to the right of the input field. In which fields must I enter values? All fields with a red asterisk are required input fields. These fields have a different color. and then choose the Send pushbutton. All rights reserved. The administrator can define fields as read-only in your user profile. 1. Page 62 of 85 . Does my user profile determine which fields are read-only? Yes.6.10 Settings Features Information About Settings in the Web Interface PUBLIC © 2014 SAP SE or an SAP affiliate company. Select an event message. Information About Confirming Unexpected Events Question Answer Which activities can I perform? Mark the checkbox for the unexpected event to be sent in the Event Messages panel and press Apply . a dialog box appears containing all the expected events that have not yet been confirmed or that can be reprocessed. The system updates the data for these event handlers in accordance with the data in the event message. To confirm these events. A dialog box appears containing data and input fields for the action. and choose the Send pushbutton. the administrator who creates your user profile can set default values for input fields.8 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 Which activities can I perform? You can send an event message for multiple tracked objects or processes. The administrator can define fields as read-only in your user profile. In which fields must I enter values? All fields with a red asterisk are required input fields. As a prerequisite. Which date and time format should I use? The date and time format that you use depends on the language that you have chosen. Why are there default values for some input fields? Depending on your requirements. 1. as required. These fields have a different color.7.6. Choose the calendar icon to the right of the input field.7. Enter data.or process. 1.9 Sending of Event Messages Features Information About Confirming All Expected Event Messages Question Answer How can I confirm event messages? If you choose the Report All Expected Events pushbutton on the Event Messages panel. Does my user profile determine which fields are read-only? Yes. the scenario must permit the sending of event messages for multiple tracked objects or processes. the administrator who creates your user profile can set default values for input fields.1. Information About Sending Event Messages Question Answer Why are there default values for some input fields? Depending on your requirements.7. Select multiple tracked objects or processes and then choose the Send Event Messages pushbutton. specify the data.6.1. Which date and time format should I use? The date and time format that you use depends on the language that you have chosen.1. choose the Send pushbutton.

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 . For more information. or not. and the number of references shown in fields that have multiple values. When do I have to set the Accessibility indicator? If you use a screen reader and set this indicator on the logon screen. for example.7.a standard function for the Web interface The button Open Settings Dialog on top of each panel in the screen allows you to reach Management specific settings. Can I change the way in which tables are displayed? Yes. What does Technical View mean? If your tracking scenario contains sets of tracked objects or processes (Event handler sets) and you have the appropriate authorization. and Unexpected Event . Overdue Expected Event .. Unreported Expected Event That Is Time-Independent . It is used to display all values if not all values fit into the corresponding field. Page 63 of 85 . PUBLIC © 2014 SAP SE or an SAP affiliate company. The level of detail shown depends on your user profile. the system displays corresponding links on the detail screen: Links to other URL addresses The displaying of indexed fields The displaying of measurements 1. to be used for displaying timestamp.Question Answer Can I personalize the Web interface? Yes. The other buttons are standard functions for the Web interface. All rights reserved. Unreported Expected Event with Expected Date/Time . see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. In most cases. The values that you specify here define the number of rows displayed in the table. you can see all the tracked objects or processes that are part of the set on the Technical View tab page. when result are found upon search. You can make these settings for the list and detail screens. for example.7 Monitoring and Evaluating Processes Various options are available for monitoring and evaluating processes in SAP Event Management. Choose Settings and the Display tab page. Why does the system sometimes display links on the detail screen? If the administrator has defined the following in Customizing for SAP Event Management.1. you can use the application more easily. 1. The icons displayed depend on the settings made in SAP Event Management. Prerequisites You have defined event handler types with their event handler extension tables (see Event Handler Extension Table). The icons are explained in the relevant tooltips. What do the icons in the Event Messages panel indicate? The icons show the status of an expected event or indicate an unexpected event message.a standard function for the Web interface The button Settings on the top of the Event Management Screen . you can use any of the following: The button Personalize . What can I use the Document Flow panel for? This panel shows a graphical display of the business object network that is related to the tracked object or process. What is the . you can also launch activities such as reporting expected or unexpected events. There you can define the time zone.More link used for? This link displays all the multiple values assigned to a single column or field in a table in a new window. Which can I see on the Event Messages panel? You see the following:: a list of all expected and unexpected events including the actual date and time of the event the planned date and time (where applicable) the status of the event Depending on your user profile.11 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 the Details panel? You can see detailed information about a tracked object or process. define whether the search screen collapses.. this view is of interest to the power user only.6. SAP Event Management uses the following five event statuses: Reported Expected Event .sap.

for example. By connecting to the Computing Center Management System. Externally. You can specify additional search criteria from the event handler extension table (see section Selection Screen: Dynamic Part). Only then can you use them to define additional search criteria. You can also use the event handler list to check whether SAP Event Management has created or updated data correctly. Select an event handler and display the detailed information for this event handler in the event handler details.1 Use of the Event Handler List The event handler list provides the system administrator with comprehensive information about an event handler (EH). Features You can display information about an event handler and can perform a restricted search for an event handler type. choose Event Management Monitoring and Lists Event Handler List . Page 64 of 85 . All rights reserved. Enter an event handler type and choose Additional Data to define the dynamic part of your search criteria. You can use the connection to the document flow to display the hierarchical structure in the Web interface. you can use the monitor specific to SAP Event Management (see Connection to the Computing Center Management System).1 Defining Search Criteria Prerequisites If you want to extend the search for information using fields from the event handler extension table. this monitor shows you a list of all locked event handlers in SAP Event Management for a specific client. see Customizing for SAP Event Management under and Event Handler Data Event Handlers Define Extensions to Event Handler Header . For example.7. Event Management Event Handlers Procedure Selection Screen: Static Part 1. 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). 1. Example For example. This list is dependent on your authorization and filter profiles. For more information about extending event handler header data. 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 specify the following search criteria: Event handler identification Application system Application object type Application object Tracking ID code set Tracking ID Processing data You can specify the business process type. Enter your search criteria. event handler type. you can display all data for all event handlers with a particular event handler type. Management data You can specify the person who created the event handler or the date when the event handler was created as search criteria. 2. for example.Features The following options are available to you for monitoring and evaluating processes: You can execute a range of reports for internal purposes. you can make search queries to SAP Event Management using a Web interface (classic). for example (see Web Interface (Classic)). The system displays an overview list containing all event handlers that match your search criteria. 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 1. 3. Selection Screen: Dynamic Part 1.1. On the SAP Easy Access screen. or you can check whether an event message has been sent to SAP Event Management. An extensive range of layout and authorization options are available to you for these search queries. 4.7. for example. 5. you must first define these fields in the extension table. For example. for example. Choose Execute . you can check whether SAP Event Management has created an event handler in accordance with your instructions. These provide you. PUBLIC © 2014 SAP SE or an SAP affiliate company. and the status attribute profile as search criteria.

Change Delete Page 65 of 85 . and measurement data. To do so. and authorization data Change documents belonging to the event handler When you send an event message SAP EM performs tasks using rules and activities. in other words.1. call the event handler details and display the following detailed information: The header data. for example. the status details. the sender name. You can choose between the following processing methods: If you choose Simulate . change. Lock and Unlock in the event handler details. You can use relevant key figures in SAP NetWeaver Business Intelligence to evaluate this information. 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. control. or delete: Data Add PUBLIC © 2014 SAP SE or an SAP affiliate company. as required. activities in the rule set. in a step-by-step way. If you choose Reprocessing . and trace the reason why the event messages have not triggered the corresponding reactions. 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. you manually trigger a reprocessing of event messages and SAP EM processes all event messages again. Here SAP EM updates the following data. For example. all parameters (system. and additional detailed information. you have maintained the authorization data and generated profiles for your user role. the system actually processes the event messages again. the measurement data. 1. the system is supposed to send an e-mail on the basis of an event message and the action that resulted from it. You use Reprocess Event Messages Reprocess to trigger processing manually and the system sends the e-mail again. At this time the mail server is not available. the system reprocesses the event messages in the background. Activities In the event handler overview. 1. Add. For example. for example: Tracking IDs. the change document data Example For example.2 Use of the Event Handler Overview In SAP Event Management. Save your selection. for example. from the event handler overview. choose Change Expected Event Date and Time to change the date and/or time of an expected event.7. All rights reserved. the arrival at the customer occurs at 13:00 instead of 12:00. for example. you can change the following event handler data manually: Set the event handler header data to status changeable/not changeable .7. query IDs. and the location code ID. SAP EM updates the status details. information about an external event code set. This also applies to your additional time categories. the tracking IDs. and info parameters). and the query IDs The history of the expected events. when you call the event handler overview from the event handler list. error messages. you can change the date and time of an expected event. 3. SAP Event Management displays a dialog box where you can enter your changes. in other words. you can use a simulation mode with a graphical interface and the system simulates the reprocessing. you can check the processing logic of an event handler.SAP Event Management displays the corresponding event handler extension table.3 Use of Event Handler Details You can have the system display the detailed information about an event handler. activities in the rule set. if an error occurs. Here you have used the authorization object X_EM_EH_CH in the EM class. or delete data The following table provides an overview of which data you can add. 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 If you choose Reprocess Event Messages . for example. 2. change. Prerequisites To use the functions for changing event handlers and their data. Select your own selection criteria and add them to the first selection screen as the dynamic part. Features If you have the appropriate authorizations. SAP EM updates the information that is contained in the event message.1. you can use the history to establish if an expected event has been reported several times. The system does not send the e-mail.

2. choose the Change EH Status setting instead of the change mode on the Status Details tab page. Disable Status Attribute Historical Data . or status attributes.7. The system displays the event handler overview. Save your changes. for example.com SAP NetWeaver SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Application Log (BC-SRV-BAL) . measurement data. 3.2 Application Log An application log is available for both the application system and SAP Event Management. You can analyze the logs or the corresponding messages according to different thematic areas and gain more detailed information about the messages. 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 1. and event messages only. For more information about the application log. On the SAP Easy Access screen. 1. Activities 1. 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. 4.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. and errors on both the application side and the SAP Event Management side. proceed as follows: 1.1. 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. The application log documents messages. event messages were being processed. see SAP Library on SAP Help Portal at http://help. If you have the appropriate authorizations. expected events. Choose the change mode on the respective tab page to manually change data. This provides information about communication operations and problems that occurred while event handlers were being created. you can specify the following when creating an event handler (transaction /SAPTRX/TSC0TT): The objects that are logged: Event handler creation Event message processing 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. SAP NetWeaver Library Page 66 of 85 . Display the event handler list and select the event handler whose data you want to change.7. All rights reserved. The system displays the event handler detail screen (event handler details).sap. system parameters. exceptions. Note If you want to change the status of an event handler. and the order in which the system displays them. If you want to change data in the event handler details. Set the relevant indicator. 2. Choose Event Handler Detail Overview . you can hide the historical data for expected events. Example You define the EH overview screen in such a way that here SAP Event Management displays information about consolidated events. in Customizing for SAP EM under Event Handlers and Event Handler Data Event Handlers Define Event Handler Types . or information was being queried. PUBLIC © 2014 SAP SE or an SAP affiliate company. choose Event Management Monitoring and Lists Event Handler List . for example. You can reduce the memory space for the application log by deactivating it per business object.4 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).

set the Disable Logging checkbox in Customizing for SAP Event Management under Event Messages. in Customizing for SAP Basis Plug-In. You can combine search criteria to obtain a wide range of search options. specify an event handler type in your search. Page 67 of 85 . 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 the SAP Event Management application log. and Web Interface Define Criteria for Event Message Processing . see the Implementation Guide (IMG) for Event Management under Event Handlers and Event Handler Data → Event Handlers → Define Extensions to Event Handler Header. Prerequisites You have defined event handler types. SAP EM provides the following query reports: ● ● ● ● ● ● ● Event handler list List of event handlers with a specific status attribute Last reported event list Event handler set browser Event message processing error list Event message processing status list Expected event overdue list 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. If you want to deactivate logging for these entries in SAP Event Management. and to forward information to all partners in the supply chain. you specify your own selection criteria that come from your event handler extension table. In the dynamic part. choose Integration with Other SAP Components Interface to Event Management Define Application Interface Define Used Business Process Types. and which you add to the fixed part. Features SAP EM provides several query options that you call using selection screens in SAP EM. To make your search more efficient. When SAP Event Management processes event messages. The selection screen consists of a fixed part and a dynamic part. PUBLIC © 2014 SAP SE or an SAP affiliate company. is my carrier reliable?) and processing in SAP EM (for example. were all my IDoc formats processed correctly?). 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. and Event Types . The system only displays the event handler extension table that belongs to this event handler type. All rights reserved. Integration You can use authorization and filter profiles to restrict the information that is displayed for queries to SAP EM (see Authorizations and Filters). on the SAP Easy Access screen. Filter profiles restrict the information that is displayed for BAPI calls to SAP EM. it saves entries in the application log. Status Queries. For example. 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). Reports for Internal Monitoring and Evaluation of Processes Use SAP Event Management (SAP EM) offers you several report options with which to make timely. choose Event Management Administration Logging Application Log: Display Logs . Application Object Types. If you want to deactivate the application log in the application system. internal queries on business processes and processing. You can use these reports to monitor the smooth flow of your business processes (for example. For more information.Activities Choose transaction /SAPTRX/ASAPLOG for the application log in the SAP system. You can use a filter profile to specify the detailed information that is displayed for an event handler in this list.

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. see Defining Search Criteria. Features You can specify the following search criteria: · Event handler identification ¡ Application system ¡ Application object type PUBLIC © 2014 SAP SE or an SAP affiliate company. list of event handlers with Delay as the last reported event). have the system list all event handlers with a delay. Delayed) to search for these event handlers in SAP EM . see Defining Search Criteria. The result of your search is a list of all event handlers with the selected status (depending on authorization and filter profiles). Integration For information about integration. Page 68 of 85 . see Reports for Internal Monitoring and Evaluation of Processes. You can find out at any time who sent the event message to SAP EM . Integration For information about integration. Prerequisites For information about prerequisites. All rights reserved. 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 ¡ Tracking ID code set ¡ Tracking ID · Processing data For example: ¡ Business process type ¡ 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. Prerequisites For information about prerequisites.To decide which measures you must take. You can use the external event code (for example. see Reports for Internal Monitoring and Evaluation of Processes. Activities Display the list of event handlers with a specific status attribute using the transaction /SAPTRX/EH_LIST_STAT.

see Reports for Internal Monitoring and Evaluation of Processes. You can use the selection screen to make various queries about event handler activities to SAP EM. Integration For information about integration.3. Features You call your query using a selection screen from SAP EM. Activities On the SAP Easy Access screen. PUBLIC © 2014 SAP SE or an SAP affiliate company. 1.7. Prerequisites ● You have defined event handler types and at least one event handler set. In this way. choose Event Management → Monitoring and Lists → Event Handler Set Browser .3 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.¡ Application object ¡ Tracking ID code set ¡ Tracking ID · Processing data For example: ¡ Business process type ¡ 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. ● Event handlers and event handler sets exist in SAP Event Management (SAP EM). Page 69 of 85 . 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). You can specify the following search criteria: ● Event handler identification ○ Application system ○ Application object type ○ Application object ○ Tracking ID code set ○ Tracking ID ● The relationship For example: ○ Event handler set profile ID ○ Event handler set relation type ○ Consolidation profile ID ● 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 Display the last reported event list using the transaction /SAPTRX/EH_LAST_EVT. you can display all event handlers that belong to a process. All rights reserved.

Integration For information about integration. Prerequisites For information about prerequisites. see Reports for Internal Monitoring and Evaluation of Processes. 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.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. Prerequisites To make the search more efficient. 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). All rights reserved. Page 70 of 85 . Activities Display the event message processing error list using the transaction /SAPTRX/ER_MS_LIST. This value can reduce the system’s response time considerably. 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 ¡ Application object ¡ Tracking ID code set ¡ Tracking ID · Processing data For example: ¡ Business process type ¡ 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. see Defining Search Criteria. The result of your search is a list of all event messages that correspond to your search criteria (depending on authorization and filter profiles). If the results list does not contain your object but the list PUBLIC © 2014 SAP SE or an SAP affiliate company. see Reports for Internal Monitoring and Evaluation of Processes. Integration For information about integration.

All rights reserved.6 Expected Event Overdue List Use This report displays a list of all event handlers that have overdue expected events. Features You call this report to query overdue expected events. You call your query using a selection screen from SAP Event Management (SAP EM).3. 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 ○ 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).7. 1. Activities On the SAP Easy Access screen. PUBLIC © 2014 SAP SE or an SAP affiliate company.already contains the total number of entries specified. Page 71 of 85 . You can use this report to query expected events that have not been reported on time. choose Event Management → Monitoring and Lists → Event Message Processing Status List . You can specify the following search criteria: ● Identification of the expected event For example: ○ Internal event code ○ Event code group ○ Expected message date ● Event handler identification ○ Tracking ID code set ○ Tracking ID ○ Application system ○ Application object type ○ Application object ○ Business process type ○ Event handler type The result of your search is a list of all event handlers that correspond to your search criteria (depending on authorization and filter profiles). increase this value.

see SAP Library on SAP Help Portal at http://help. For more information. choose Event Management → Monitoring and Lists → Expected Event Overdue List. Connection to the Computing Center Management System Use This function connects SAP Event Management to the Computing Center Management System (CCMS). 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. from 1000 locked event handlers upwards). ● Scheduling SCEM-relevant background jobs The scheduling of the functions is client-specific. Prerequisites ● You have executed the reports /SAPTRX/SLG1_LINK and /SAPTRX/SCHEDULE_EM_JOBS_NODE once before calling the SAP Event Management monitor. ● Selecting unprocessed event messages in SAP Event Management This function is client-specific and you specify the threshold value.com → SAP Technology Components → SAP Web Application Server → Basis Services/Communication Interfaces (BC-SRV) → Application Log (BC-SRV-BAL) → Application Log – End User Guidelines (BC-SRV-BAL) → Evaluate Logs. Specify SAPTRX as the object for SAP Event Management.Activities On the SAP Easy Access screen. ● For the monitoring functions in the CCMS that are specific to SAP Event Management. We recommend that you only connect SAP Event Management to the CCMS if you have appropriate knowledge of the CCMS.sap. and to quickly gain an overview of possible problems in SAP Event Management. from 1000 locked event handler sets upwards). 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. you need to execute these two reports again. The system gives a warning from this value onwards (for example. ● Selecting lock entries for locked event handler sets in SAP Event Management This function is client-specific and you specify the threshold value. event handler created) on the SAP Event Management side from the application log. you have scheduled the relevant background job for each client for which you want to use these functions in the CCMS. The overview screen shows you which background jobs you have scheduled for which periods of time. The SAP Event Management monitor is a collection of functions that. It allows you to use the SAP Event Management monitor in the CCMS. for example. PUBLIC © 2014 SAP SE or an SAP affiliate company. ○ Report for the processor of locked event handlers ○ Report for the processor of locked event handler sets ○ Report for the expected event monitor ○ Report for scheduling Resend Application Object Data for Event Handlers ○ Report for deleting the document flow network ● 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. The system gives a warning from this value onwards (for example. schedule these background jobs again. from 1000 unprocessed event messages upwards). You can schedule them without knowing the report names. displays all the SAP Event Management messages in an overview screen. If you restart the system. 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. All rights reserved. The system displays this background job in the dialog structure of the SAP Event Management monitor. Page 72 of 85 .

For more information. In this way. you can evaluate this data in SAP NetWeaver BI analytically. ○ 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. You want to transfer data belonging to an event handler to SAP NetWeaver BI. You use this profile to define the extraction level. you can determine and query key figures in SAP NetWeaver BI . SAP EM determines the event handler type of this event handler. see the IMG for SAP EM under Event Management → SAP Business Information Warehouse Interface → Process for Extracting SAP BW Data . This ensures that the SAP NetWeaver BI upload is updated automatically. unexpected events that have been reported 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. After the data has been transferred. ○ You have specified that the event should be posted automatically for the delta upload. The event handler type determines the SAP NetWeaver BI profile. For example. ■ Assigning the SAP NetWeaver BI profile to an event handler type For more information. 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. for example. see the Implementation Guide (IMG) for SAP EM under Event Management → SAP Business Information Warehouse Interface → Define SAP BW Profiles . Examples of these settings include the update mode and configuring if and when the SAP NetWeaver BI upload is automatic. see the IMG for SAP EM under Event Management → SAP Business Information Warehouse Interface → Process for Extracting SAP BW Data . 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. All rights reserved. Page 73 of 85 . 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. PUBLIC © 2014 SAP SE or an SAP affiliate company. ● You have configured SAP NetWeaver BI.Purpose You connect SAP Event Management (SAP EM) to SAP NetWeaver Business Intelligence (SAP NetWeaver BI) to transfer your supply chain event managementrelevant data to SAP NetWeaver BI.

You can use queries to evaluate the data in InfoCubes. You define the following in Customizing for the SAP NetWeaver BI profile: a. 6. You use these alerts to forward information from SAP EM to the partners concerned (for example. for example. The following figures provide an overview of the process flow: For more information about the individual BI objects. the data is updated automatically in SAP NetWeaver BI.Process 1. 2. b. SAP provides DataSources that are defined using extraction structures. 4. The system maps the DataSources one-to-one onto the InfoSources. You specify the event handler header /SAPTRX/EH_HDR and the table for expected events /SAPTRX/EH_EXPEV as your source structures. If you defined an automatic delta upload in Customizing for mapping. The source structures and tables in SAP EM that contain the data that you want to transfer to SAP NetWeaver BI. the data is available to SAP NetWeaver BI. SAP NetWeaver BI provides the corresponding InfoSources. see the SAP Help Portal under SAP NetWeaver → BI Content → Supply Chain Management → Supply Chain Event Management. 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. 3. SAP delivers example queries with the visibility processes. 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). SAP NetWeaver BI maps the InfoSources one-to-one onto the operational data storage (ODS). 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. 5. You want to send data for the events Departure and the Arrival at Customer for your service provider to SAP NetWeaver BI. SAP NetWeaver BI collects the ODS data in InfoCubes that are delivered with visibility processes. a transportation or production planner) in a timely and proactive PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 74 of 85 . All rights reserved. How the source structures and tables are mapped onto the extraction structures.

When you save the shipment planning. 3. 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. SAP APO transfers the shipment planning to an SAP R/3 system. see the documentation for function module /SAPTRX/SEND_PPDS_APO_ALERT that SAP EM uses within the SAP EM activity. The supplier sends his or her answer Rejection to SAP EM in response to your transportation bid. You plan a shipment in SAP APO. You choose a new supplier for your shipment in the SCM Alert Monitor. see the SAP Library under SCM Basis → Alert Monitor → Monitoring and Solving Planning Problems Using the Alert Monitor → Monitoring VS Alerts . In progress. We recommend that SAP APO creates the event handler. For more information. SAP EM triggers an alert in the SCM Alert Monitor. proposed shipment declined by external transportation service provider. Activities ● You use the relevant rule activity within your rule set. proposed delivery date changed by external transportation service provider. 7. 6. Connection to the Document Flow Use PUBLIC © 2014 SAP SE or an SAP affiliate company. PP/DS alert profile.way. For more information about monitoring VS alerts. 4. in whose rule set you use the activity. All rights reserved. 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. Page 75 of 85 . it triggers the creation of event handler EH2 in SAP EM. For more information. SAP EM forwards the rejection as a VS alert to the SCM Alert Monitor. SAP APO triggers the creation of event handler EH1 in SAP EM. Prerequisites To view the alerts in the SCM Alert Monitor. 8. Example Monitoring a Shipment Process from Bidding to Execution 1. in SAP EM. 5. Features Alert Type in PP/DS ● Machine outage (SCEM) To send a PP/DS alert from SAP EM to the SCM Alert Monitor. For more information about monitoring PP/DS alerts. VS optimization profile. use the SAP EM activity Send PP/DS Alert to SCM Alert Monitor (SEND_PPDS_APO_ALERT) within a rule set. ● You display the alerts in the SCM Alert Monitor. or overall alert profile) in the monitor (transaction /SAPAPO/AMON_SETTING). 2. No answer from transportation service provider To send a VS alert from SAP EM to the SCM Alert Monitor. 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. When you save the shipment document in SAP R/3. see the SAP Library under SCM Basis → Alert Monitor → Monitoring and Solving Planning Problems Using the Alert Monitor → Monitoring PP/DS Alerts . For more information. use the SAP EM activity Send VS Alert to SCM Alert Monitor (SEND_VS_APO_ALERT) within a rule set. ● As soon as the rule condition(s) are met. you must have defined an alert profile (for example. see the documentation for function module /SAPTRX/SEND_VS_APO_ALERT that SAP EM uses within the SAP EM activity.

For this reason. ● You can delete a document flow network. business objects (documents) have a hierarchical relationship to one another. If SAP Event Management does not update the document flow network after multiple attempts. see Customizing for SAP Event Management under General Settings in SAP Event Management → Define Application System . see the SAP NetWeaver documentation in the SAP help portal under SAP NetWeaver by PUBLIC © 2014 SAP SE or an SAP affiliate company. see the Implementation Guide (IMG) for SAP Event Management under Event Management → Interface to Document Flow → Define Document Flow Groups . For more information. For more information about the document flow. a locking concept is in use in SAP Event Management. For more information about Customizing. 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 . Creation and Updating of a Network Use SAP Event Management creates a network in the document flow and updates this network so that you can display the hierarchical structure for an event handler in the Web Interface (Classic). ● If necessary. For more information. For more information. For more information. ● You have specified how you want SAP Event Management to update the 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. Features You can define whether you update an event handler or an event message and the relevant network at the same time. ● You can display a document flow network. For example. 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. it simultaneously removes the lock for the document flow. see the IMG for SAP Event Management under Interface to Document Flow → Define Document Flow Groups . you have defined your own document categories in Customizing for the document flow.In the application system. see Connection to the Document Flow under Prerequisites . Page 76 of 85 . see the Implementation Guide (IMG) for SAP Event Management under Interface to Document Flow → Integration with Document Flow . ● If necessary. ● You have defined the groups and the mapping of event handler information to the document flow. see the IMG for SAP Event Management under Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Define Object Link Model . it uses the lock object /SAPTRX/E_DF and thereby locks the associated documents and predecessor documents. Prerequisites ● You have carried out the Customizing for the connection to the document flow. a sales order consists of multiple deliveries that fulfill multiple shipments. For performance reasons. scenarios with handling units). it writes an entry to the application log. you have defined your own link categories in Customizing for the document flow. you can connect one local document flow only. Prerequisites You have carried out the Customizing for the connection to the document flow. You can assign each event handler or each event message to one group only. For more information about the SAP locking concept. You have the following options: ○ At the same time as creating or updating an event handler ○ Via an event message For more information. All rights reserved. For more information. When SAP Event Management removes the lock on the associated event handlers or event messages. When SAP Event Management updates a document flow. we recommend that you do not use the document flow in scenarios with a high volume of data (for example. Features The connection to the document flow comprises the following functions: ● You can create or update a document flow network. ● You have set up an asynchronous communication with the application system. The connection to the document flow enables SAP Event Management to display this hierarchical structure of the business objects in the Web Interface (Classic) and in the Web Interface (Web Dynpro ABAP) For each SAP Event Management. 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.

7. SAP Event Management sends all the necessary data to the document flow. status information or info parameters For more information.2 Displaying a Network Use You display a document flow network to be able to monitor and evaluate your processes. 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. SAP Event Management proceeds as follows: a. 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. b. for example. As a result. you have defined your personal settings for displaying a document flow network. SAP Event Management writes an entry to the application log. All rights reserved.Key Capability → Application Platform by Key Capability → ABAP Technology → Client/Server Technology → The SAP Locking Concept (BC-CST-EQ) . and Web Interface → Web Interface → Define User Profiles . SAP EM first displays the mode that you choose here (graphical or tabular) in the Web interface (classic). the Web interface (classic) displays detailed information. e. and you can execute a drilldown. document number and. d. If you have the appropriate authorizations in your user profile. SAP Event Management searches for the predecessor document and reads the target data for creating or updating the network. For this. This means that the system displays a tabular view of the network in the Web interface (classic) that your screen reader can read. and updates the network accordingly. Status Queries . ● The relevant parameters. b. and Web Interface → Web Interface → Define User Profiles . the Web interface (classic) automatically displays the link to the document flow network that belongs in the event handler list. 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. If you have defined a condition for updating the network. ● In the Web interface (classic). For more information. This means that you can choose between a graphical or tabular display of the network in the Web interface (classic). as appropriate. SAP Event Management finds an activity with the parameter for the group for simultaneously updating the network. SAP Event Management reads the attributes that the document flow saves together with the source information in the network. Features If an event handler exists and you have read authorization for the nodes of this event handler. SAP Event Management reads the attributes that the document flow saves together with the source information in the network. You can change this setting in the personal settings in the Web interface (classic). see Web Interface (Classic) and the IMG for SAP EM under Event Management → Event Messages. the Web interface (classic) displays the following information: ● The document category. SAP Event Management finds the parameter for the group in the activity for updating an event handler. Prerequisites ● You have set the Document Flow indicator in the user profile in Customizing. c. SAP Event Management processes this event message.7. the graphical view is delivered as the document flow mode for the Web interface (classic). If an error occurs in the document flow. ● If you have set up the Customizing for updating the document flow via an event message. d. The document flow displays the dependencies between your business objects (predecessor document and successor document) and specifies the attributes. In the standard system. Integration SAP Event Management ( SAP EM ) works with one local document flow only. SAP Event Management proceeds as follows: a. On the basis of the event handler type. The Web interface (classic) also displays a link with which you can select the other mode. c. SAP Event Management invokes the activity for updating an event handler. SAP Event Management evaluates this condition and updates the network only in accordance with the condition. the document item number with an active link to the event handler that has generated them. ○ You have chosen the Document Flow Mode under Settings . You can use a rule set condition for this. ○ You have set the Accessibility Switch under Settings . see the Implementation Guide (IMG) for SAP EM under Event Management → Event Messages. Status Queries . SAP Event Management sends all the necessary data to the document flow. SAP Event Management searches for the predecessor document and reads the target data for creating or updating the network. SAP Event Management applies the rule set and calls your rule activity for the document flow. PUBLIC © 2014 SAP SE or an SAP affiliate company. If an error occurs in the document flow. Page 77 of 85 . Activities SAP Event Managementhas created a new event handler or updated an existing one. The document flow has created a new network or updated an existing one. 1. SAP Event Management writes an entry to the application log. e. ○ You have not set the Accessibility Switch under Settings .

these document categories and link categories start with 1 . You want to see the hierarchy for this event handler and choose Document Flow . When SAP EM deletes a network. The document flow sends the relevant network data to SAP EM. 9. JNet sends corresponding GIF files containing this data to the Web interface (classic). it can delete the relevant network in the document flow. The Web interface (classic) calls SAP EM. If you want to use additional attributes in the document flow. 8. ● Networks exist in the document flow. SAP EM sends this data via RFC to the Web interface (classic). For more information. ● You have defined the relevant document categories for deleting a network. 6. ● In Customizing.3 Deletion of a Network Use When SAP Event Management (SAP EM) has archived and deleted all the event handlers that belong to a network. SAP EM calls methods in the document flow to read the network. 3. The Web interface (classic) creates XML files from this data and sends the XML files to JNet.Activities The following figure provides an overview of the activities for displaying a document flow: 1. You can also start this report directly. it flags this in the application log. Page 78 of 85 . You select one event handler in the Web interface (classic). 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. 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 . see the IMG for SAP EM under Event Management → Interface to Document Flow → Define Document Flow Groups . The Web interface (classic) displays the document flow network in a new dialog box. 7.7. you have defined the residence time for deleting a network. The Web interface (classic) calls SAP EM and displays the event handler. PUBLIC © 2014 SAP SE or an SAP affiliate company. see the IMG for SAP EM under Event Management → Archive and Delete SAP EM Objects → Define Settings for Deleting Document Flow . For more information.7. 5.relevant networks is possible. 2. Prerequisites ● SAP EM has archived and deleted all event handlers that belong to a network in the document flow. you have defined them in Customizing. 1. All rights reserved. see the Implementation Guide (IMG) for SAP EM under Event Management → Archive and Delete SAP EM Objects → Define Settings for Deleting Document Flow . In the standard system. For more information. 4.

See also: Archiving in SAP Event Management PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP Event Management also automatically deletes all the relevant event handler data and change documents. Even if you only delete the event handler header data. SAP Event Management uses the archiving object /SAPTRX/A0 to archive event handler data and the archiving object /SAPTRX/A2 to archive event handler set data. In this way. in other words. 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. This makes it easier for you to analyze errors. SAP Event Management saves these changes under the same user name.7. 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. Activities On the SAP Easy Access screen. for all changes dependent on your manual changes.For more information about deleting individual document flow nodes. however. choose Event Management → Management . For more information about the concept behind logging with change documents and about the structure of change documents. For archiving change documents. 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). but instead it deletes the relevant existing change documents. Features Creation of a Change Document When the following data related to event handlers is changed. If.8 Logging with Change Documents Use SAP Event Management logs the changes made to data related to event handlers in change documents. Deletion of a Change Document When you delete an event handler and the corresponding data in SAP Event Management. 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 . it also archives the relevant change documents at the same time. Administration → Processing Control → Schedule Background Jobs for Event Specify how often the background job is to be executed to delete any relevant networks. 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. Page 79 of 85 . you can trace the changes made and can always check what was changed as well as when and how it was changed. 1. SAP Event Management also automatically creates a change document for each dependent change made to expected events. see the IMG for SAP EM under Event Management → Interface to Document Flow → Integration with Document Flow . All rights reserved. the relevant existing change documents are retained. the system does not create a change document. 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. Archiving a Change Document When SAP Event Management archives event handler data.

When data is updated. 5. Choose Continue or Cancel . Start the simulation by either saving. you know where and in which process you can make corrections. Save the change. you determine how the system reacts to this situation. In this way. · If problems occur. 4. the simulation activity is aborted and the SAP Easy Access screen appears. you can start the process in the active business process mode. but also for the process steps in SAP EM . choose the transaction for defining business process types (/SAPTRX/ASC0AO). changing or deleting an SCEM-relevant business object in the application system (for example. updating. All rights reserved.8 Overview of Activities Delivered The list of all activities delivered provides you with an overview of all the activities delivered for SAP Event Management .Simulating Processes in the SAP Application System and SAP EM Use To see the consequences of saving. SAP EM shows the various processes step-by-step (depending on your Customizing for the application system and SAP EM). In doing this. In the application system. · If the simulation is successful. ● 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. see Activity List Structure. or deleting an SCEM-relevant business object in the application system. This provides you with an overview of all the processes in SCEM. 2. · You have set up Customizing for SAP Event Management (SAP EM). For example. if required.8. a shipment document). PUBLIC © 2014 SAP SE or an SAP affiliate company. Procedure 1. Prerequisites · You have set up Customizing for the SAP application system. 1. The system displays the chosen business process type and the application object types that belong to it. SAP EM does not save the values from the simulation. The simulation also transfers the SCEM-relevant data from the application system to SAP EM . For more information about the structure of the list. 3. you can simulate processes. Choose Simulation as the mode for a business process type. you have set the simulation mode not only for all SCEM-relevant process steps in the application system. ● Activities for updating event handlers You use these activities to modify data before creating an event handler. You can cancel the simulation at any point. Page 80 of 85 . 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. 1.1 Activity List Structure Definition You can find the following activity types in the overview of activities delivered by SAP: ● Rule activities You use these activities within rules to control the processes for processing event messages in rule sets. Result · The system has simulated all SCEM-relevant processes.

Enter the name of the function module and choose Display . Values And Set the Result ACT_CHECK_AND_SET_PARAM_VAL UES M CHECK_EH_IN_SETS Check the Status of Event Handlers in ACT_CHECK_EH_IN_SET M PUBLIC © 2014 SAP SE or an SAP affiliate company. On the SAP Easy Access screen.0 with PI2003. For up-to-date information. the corresponding description. and the name of the function module or method used are specified for each activity. All rights reserved. The technical name. Values in Evt Msg Against Info/Conrl Par. Choose Goto → Documentation.SAP reserves the right to change methods when delivering Support Packages for SAP Event Management. The system displays the function module coding. Page 81 of 85 . 1. choose Tools → ABAP Workbench → Development → Function Builder. see SAP Service Marketplace.2 Activity List Rule Activity Functions Activity Name Description Name of Method or Function Module Method or Function ALERT_CREATE Integration of Alert Framework /SAPTRX/CREATE_ALERT F BW_UPLOAD Upload Business Information Warehouse /SAPTRX/BW_EXTRACTION F DF_UPDATE Update Document Flow /SAPTRX/DF_UPDATE F EH_AUTO_ARCH Event Handler Automatic Archiving /SAPTRX/EH_AUTO_ARCH F EH_AUTO_ARCH_SET Event Handler Set Automatic Archiving /SAPTRX/EHSET_AUTO_ARCH F ID_MAPPING Call ID Mapping Functionality and Set Rule /SAPTRX/ID_MAPPING Processing Parameters F RESEND Resend Event Messages to Another Event /SAPTRX/RESEND F Handler RESEND_MULTIPLE Resend Event Messages to Other Event Handlers /SAPTRX/RESEND_MULTIPLE F SEND_POD Send a Proof of Delivery /SAPTRX/SEND_POD F SEND_PPDS_APO_ALERT Send PP/DS Alert to SAP APO Alert Monitor /SAPTRX/SEND_PPDS_APO_ALERT F SEND_SNC_DOC_ALERT Send Document Related Alert to SAP SNC /SAPTRX/SEND_SNC_DOC_ALERT F SEND_SNC_MSG_ALERT Send XML-Message Related Alert to SAP /SAPTRX/SEND_SNC_MSG_ALERT F SNC SEND_VS_APO_ALERT Send VS Alert to SAP APO Alert Monitor /SAPTRX/SEND_VS_APO_ALERT F SHIPMENT_DATE_UPDATE Update Actual Dates in the SAP R/3 Shipment /SAPTRX/SET_ACT_SHIPMENT_DDL F SHPMT_DATE_UPDATE Update Actual Dates in the SAP R/3 Shipment (as of SAP SCM 4.8. see the function module description. For a detailed description of the activity function.1) /SAPTRX/SET_ACT_SHIPMENT_DDL1 F SHPMT_ENDDATE_UPDATE Update Actual Shipment End Date in the /SAPTRX/SET_SHIPMENT_ENDDATE F SAP R/3 Shipment TM_MAINTAIN_ETA Create/Update ETA with or Without Reference to PTA(s) in TM /SAPTRX/TMS_CHANGE_ETA F TM_SET_HSH_STATUS Set Life Cycle Status in House Shipment in Transportation Management /SAPTRX/TMS_SET_HSH_STATUS F WORKFLOW_START Create the Event "Start_workflow" in the /SAPTRX/CREATE_BO_EVENT BO "/SAPTRX/EH" to Trigger the Workflow F Activity Name Description Name of Method or Function Module Method or Function ADD_TO_SET Add Current Event Handler to Event Handler Sets ACT_ADD_TO_SET M ADD_EHS_TO_PROCESS Add Additional Related Event Handler ACT_ADD_EHS_TO_PROCESS M Rule Activity Methods GUIDs from Further Reference Data ARE_PRIOR_REQS_MET Have Prior Required Expected Events Been ACT_PRIOR_REQS_REPORTED Reported for an Event? M CHECK/SET_PARAM_VALS Check Par.

Date Prior to the Earliest Expected Date? ACT_IS_EE_MSG_EARLY M IS_EE_MSG_LATE Is This Event Msg. Partner. Info. Page 82 of 85 .0) ACT_EE_MODIFY M EVM_ETA_UPDATE Update Expected Date for an Event with Estimated Deadlines (Only EM 1.1) ACT_ETA_EVENT_MSG M IS_EE_EARLY Is the Event Date Prior to the Earliest Expected Date? ACT_IS_EE_EARLY M IS_EE_IN_DATE_SEQ Is This Event and All Prior Events in Chronological Order? ACT_IS_EE_IN_DATE_SEQ M IS_EE_LATE Is This Event Date After the (Latest) Expected Date? ACT_IS_EE_LATE M IS_EE_MSG_EARLY Is the Event Msg. Location)? ACT_IS_EVENT_EXPECTED M IS_EVENT_IN_GROUP Is the Internal Event Code in Group <Parameter>? ACT_IS_EVENT_IN_GROUP M IS_EVENT_REPORTED Was Event Msg. Date After the (Latest) Expected Date? ACT_IS_EE_MSG_LATE M IS_EE_REPROCESSED Has This Expected Event Been Reported Previously? ACT_IS_EE_REPROCESSED M IS_EQUAL Equate Two Fields ACT_IS_EQUAL M IS_EVENT_EXPECTED Is the Event an Expected Event (= EE Code. Already Reported for ACT_IS_EVENT_REPORTED M Same Event Handler? IS_EVM_CODE_EXPECTED Is the Internal Event Code One of the Expected Event Codes? ACT_IS_EVM_CODE_EXPECTED M IS_LAST_EE Is This Event the Last Expected Event? ACT_IS_LAST_EE M PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.Event Handler Set CHECK_PARAM_VALUE Check Value of System. Control. or ACT_CHECK_PARAMETER_VALUE M Rule Processing Parameter CHECK_RELATED_EH Check Status of Related Event Handlers ACT_CHECK_RELATED_EH M CHECK_REPROCESS_FLAG Check Value of Class Attribute MY_REPROCESS ACT_CHECK_REPROCESS_FLAG M CHECK_SYSPARAM_VALUE Check Parameter Values in Evt Msg Against System Parameter Values ACT_CHECK_SYSTEM_PARAM_VALU E M COMPARE Compare Two Fields ACT_COMPARE M EE_ALL_REQS_MET Have All Required Expected Events Been ACT_ALL_REQS_REPORTED M Reported? EE_EXP_DATES_CLEAR Clear the Expected Dates for an Expected Event ACT_CLEAR_EXPECTED_DATES M EE_PROCESS Process Expected Events ACT_PROCESS_EE M EE_RESET Reset the Actual Dates and Status for an Expected Event ACT_RESET_EE M EH_ACTIVATE Activate Event Handler ACT_ACTIVATE M EH_DEACTIVATE Deactivate Event Handler ACT_DEACTIVATE M EH_GUID_SET Retain Event Handler GUID Currently Being Processed ACT_SET_EH_GUID M EH_HIERARCHY_UPDATE Update Event Handler Hierarchy Table ACT_UPDATE_EH_HIERARCHY M EHSET_ACTIVATE Activate Event Handler Set ACT_SET_EHSET_ACTIVE M EHSET_SET_INACTIVE Deactivate Event Handler Set ACT_SET_EHSET_INACTIVE M EHSET_STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler Set ACT_CHECK_EHSET_STATUS M EHSET_STATUS_SET Create or Update a Status Attribute Name for Event Handler Set ACT_SET_EHSET_STATUS M ERROR_MESSAGE_CLEAR Clear (Deactivate) Error Messages ACT_CLEAR_ERR_MSGS M ERROR_MESSAGE_LOG Log an Error Message ACT_LOG_ERROR_MSG M EVENT_CODE_CHECK Does Internal Event Code Equal <Parameter>? ACT_IS_EVENT_CODE M EVM_EE_UPDATE Update Expected Event List from Event Message EE MODIFY Table (as of SCM 4.

or Rule Proc. All rights reserved. Already Reported for Another Event Handler? ACT_IS_REPORTED_FOR_EH M PARAMETER_CHANGE Adding /Changing /Deleting Control and/or Info Parameter(s) ACT_CHANGE_PARAM M PROCEDURE_RC_SET Set Return Code for Multi-Task Activity Explicitly ACT_SET_PROC_RC M PROCESS_MEASUREMENTS Process Measurement Data ACT_PROCESS_MEASUREMENTS M PROCESS_UNPROCESSED Check for and Process Any Unprocessed Event Messages ACT_PROCESS_UNPROCESSED_MS GS M QUIT_EVM_PROCESSING Quit Event Message Processing and Mark ACT_QUIT_EVM_PROCESSING M as Irrelevant RETRIEVE_MSG Retrieve Process-Related Messages for Visibility Processes ACT_LOG_MSG M SET_RULE_PROC_PARAM Create.IS_MEASUREMENT_CONF Did the Event Message Confirm an Expected Measurement Result? ACT_IS_MEASUREMENT_CONFIRME D M IS_MSRMNT_NOT_COMPAR Was Event Message not Comparable to the ACT_IS_MSRMNT_NOT_COMPARABL M Expected Measurement Result? E IS_MSRMNT_OUT_OF_TOL Did the Reported Measurement Result Exceed the Expected Result? ACT_IS_MSRMNT_OUT_OF_TOLERA NCE M IS_ORIG_EE_LATE Is the Event Date After the Original Expected Date? ACT_IS_ORIG_EE_LATE M IS_ORIG_EE_MSG_LATE Is This Event Msg. Date After the Original Expected Date? ACT_IS_ORIG_EE_MSG_LATE M IS_REPORTED_FOR_EH Was Event Msg. or Delete a Rule Processing Parameter ACT_SET_ACTIVITY_PARAM M STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler ACT_CHECK_STATUS M STATUS_SET Create or Update a Status Attribute Name and Update Status History for EH ACT_SET_STATUS M TRACKING_ID_REMOVE Delete Tracking IDs ACT_REMOVE_TRACKING_IDS M TRACKING_ID_SET Create Additional Tracking ID(s) from Event ACT_SET_TRACKING_ID Message Further Reference Data M WEBLINK_SET Create a Web Link M ACT_CREATE_WEBLINK Activity Functions for the Expected Event Monitor Activity Name Description Name of Method or Function Module Method or Function ALERT_CREATE Integration of Alert Framework /SAPTRX/CREATE_ALERT F SEND_SNC_DOC_ALERT Send Document Related Alert to SAP SNC /SAPTRX/SEND_SNC_DOC_ALERT F SEND_SNC_MSG_ALERT Send XML-Message Related Alert to SAP SNC /SAPTRX/SEND_SNC_MSG_ALERT F SEND_VS_APO_ALERT Send Vehicle Scheduling Alert to SAP APO Alert Monitor /SAPTRX/SEND_VS_APO_ALERT F Activity Methods for the Expected Event Monitor Activity Name Description Name of Method or Function Module Method or Function CHECK_PARAM_VALUE Check Value of System. Control. Parameter ACT_CHECK_PARAMETER_VALUE M COMPARE Compare Two Fields ACT_COMPARE M EH_ACTIVATE Activate Event Handler ACT_ACTIVATE M EH_DEACTIVATE Deactivate Event Handler ACT_DEACTIVATE M EHSET_ACTIVATE Activate Event Handler Set ACT_SET_EHSET_ACTIVE M EHSET_SET_INACTIVE Deactivate Event Handler Set ACT_SET_EHSET_INACTIVE M PUBLIC © 2014 SAP SE or an SAP affiliate company. Update. Info. Page 83 of 85 .

EHSET_STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler Set ACT_CHECK_EHSET_STATUS M EHSET_STATUS_SET Create or Update a Status Attribute Name for Event Handler Set ACT_SET_EHSET_STATUS M ERROR_MESSAGE_CLEAR Clear (Deactivate) Error Messages ACT_CLEAR_ERR_MSGS M ERROR_MESSAGE_LOG Log an Error Message ACT_LOG_ERROR_MSG M IS_EE_MSG_OVERDUE Is the Expected Event Message Overdue? ACT_IS_EE_MSG_OVERDUE M IS_EE_OVERDUE Is the Expected Event Overdue? ACT_IS_EE_EVENT_OVERDUE M IS_EQUAL Equate Two Fields ACT_IS_EQUAL M OVERDUE_EE_RESET Reset "Overdue" Expected Event Status Back to "Expected" ACT_RESET_OVERDUE_EE M PROCEDURE_RC_SET Set Return Code for Multi-Task Activity Explicitly ACT_SET_PROC_RC M SET_RULE_PROC_PARAM Create. or Rule Processing Parameter ACT_CHECK_PARAMETER_VALUE M COMPARE Compare Two Fields ACT_COMPARE M EH_ACTIVATE Activate Event Handler ACT_SET_EHSET_ACTIVE M EH_DEACTIVATE Deactivate Event Handler ACT_SET_EHSET_INACTIVE M EHSET_ACTIVATE Activate Event Handler Set ACT_SET_EHSET_ACTIVE M EHSET_SET_INACTIVE Deactivate Event Handler Set ACT_SET_EHSET_INACTIVE M EHSET_STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler Set ACT_CHECK_EHSET_STATUS M EHSET_STATUS_SET Create or Update a Status Attribute Name for Event Handler Set ACT_SET_EHSET_STATUS M ERROR_MESSAGE_CLEAR Clear (Deactivate) Error Messages ACT_CLEAR_ERR_MSGS M ERROR_MESSAGE_LOG Log an Error Message ACT_LOG_ERROR_MSG M IS_EQUAL Equate Two Fields ACT_IS_EQUAL M PROCEDURE_RC_SET Set Return Code for Multi-Task Activity Explicitly ACT_SET_PROC_RC M SET_RULE_PROC_PARAM Create. or Delete a Rule Processing Parameter ACT_SET_ACTIVITY_PARAM M STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler ACT_CHECK_STATUS M STATUS_SET Create or Update a Status Attribute Name and Update Status History for EH ACT_SET_STATUS M Activity Functions for Updating an Event Handler Activity Name Description Name of Method or Function Module Method or Function ALERT_CREATE Integration of Alert Framework /SAPTRX/CREATE_ALERT F DF_UPDATE_FROM_EH Update Document Flow from Event Handler Creation/Update /SAPTRX/DF_UPDATE_FROM_EH F Activity Methods for Updating an Event Handler Activity Name Description Name of Method or Function Module Method or Function CHECK_PARAM_VALUE Check Value of System. Page 84 of 85 . Update. Control. Info. All rights reserved. or Delete a Rule Processing Parameter ACT_SET_ACTIVITY_PARAM M STATUS_CHECK Check Status Records for Status Attribute Name & Value for Event Handler ACT_CHECK_STATUS M STATUS_SET Create or Update a Status Attribute Name ACT_SET_STATUS M and Update Status History for EH PUBLIC © 2014 SAP SE or an SAP affiliate company. Update.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 85 of 85 .