Manage Supply Chain Event Management in

mySAP SCM (4.1)

Best Practice for Solution Management
Version Date: April 2006
This version is valid for mySAP SCM 4.1
The newest version of this Best Practice can always be obtained through
the SAP Solution Manager or the SAP Service Marketplace.

Contents
Applicability, Goals and Requirements .....................................................................................................2
Best Practice Procedure and Verification .................................................................................................4
Preliminary Tasks ...............................................................................................................................4
Monitoring Procedure .........................................................................................................................7
Most Important Monitoring Tools ..................................................................................................7
Archiving and Deletion .................................................................................................................9
Set up a process ........................................................................................................................11
Overview of regularly-used Jobs, Transactions and Monitoring Tasks ......................................12
Management of mySAP Technology ..........................................................................................13
Further Information .................................................................................................................................18

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 2

Applicability, Goals and Requirements

To ensure that this Best Practice is the one you need, consider the following goals and requirements.

Goal of Using this Service

This Best Practice Document enables you to set up a monitoring and emergency concept for
the Event Management System (SAP EM), which is part of SAP´s Supply Chain
Management (SCM) solution. It is possible to use SAP EM to monitor processes for SAP ERP,
SAP Advanced Planning and Optimization (SAP APO 3.0, 3.1), Supply Chain Management
System (SCM 4.0, 4.1), CRM, SRM etc. and legacy Systems.
The concept aims to:
o Define procedures for monitoring, error handling and escalation management for the Event
Management System.
o Define the roles and responsibilities for all persons involved in the customer’s support and
monitoring organization, with respect to the Event Management System.
These procedures ensure the smooth and reliable flow and handling of the Event Management
business processes.

Staff and Skills Requirements

To implement this Best Practice, you require the following teams:

Application Management Team

The SCM / SAP EM business process management concept, which this Best Practice aims to
produce, should be created by the Application Management Team. This team combines experts from
your company:
o Business department
o Solution support organization (for example, the IT department and the Help Desk)
o Implementation project team

Execution Teams
The execution teams are the following groups, which, taken together, form the customer’s Solution
Support Organization:
o The Business Process Champion for each business process
o Application Support
o Development Support
o Program Scheduling Management
o Software Monitoring Team
o System Monitoring Team
More information about the roles and responsibilities of these teams can be found in the Best Practice
General Business Process Management, which you can obtain through the SAP Solution Manager.
For further information please see the online help: http://help.sap.com/

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 3

Necessary or Useful Training Courses:

o TZSCV6 Implement Event Management with SAP SCM 4.1

System Requirements
This document applies to mySAP SCM release 4.1.

Duration and Timing

Duration
Creating a business process management concept can take around one week per business
process.
Implementing the business process management concept can take around one additional week.
Timing
The best time to apply this Best Practice is during the planning phase or during the implementation
phase for your mySAP solution.

How to Use this Best Practice

Read the whole document prior to the project start then use it to guide you through the different steps
of the project. This Best Practice document is divided into the following parts:
o Monitoring
o Archiving and Deletion
o Regular Jobs and Monitoring Tasks
o Important SAP Notes
o Management of mySAP Technology

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 4

Best Practice Procedure and Verification

Preliminary Tasks

The SCM System Landscape

The main components of an SAP SCM system landscape are summarized in the following table.
SAP Supply The SAP Supply Chain Management System facilitates the strategic, tactical, and
Chain operational planning processes.
Management
SAP SCM consists of several software components. First, there is a relational
System
database system (RDBMS), known as the SCM DB, as well as an SAP R/3 Basis,
and the SCM application programs. In addition, there is a separate, very fast,
object-oriented SAP database, called the liveCache, and a number of programs
that execute elaborate optimization algorithms, called the optimizers. These
components can run on the same or on different servers.
OLTP System The Online Transaction Processing system covers functionality for sales and
distribution, material and inventory management, controlling, shop floor control,
logistics execution, and so on.
OLAP System An Online Analysis Processing system like SAP Business Warehouse can provide
cumulated historical data as basic statistical information for reporting tools. The
Supply Chain Event Management System can be used as source of the necessary
reporting data.
Web The Web Communication layer can be used as communication interface and for
Communication the monitoring for all internal and external parties.
Layer (WCL)

SAP Event Management

SAP Event Management (SAP EM) is the application within the mySAP SCM solution that provides or
improves visibility within your logistic processes, both in planning and in execution. The flexibility of the
application enables you to map, control, and check all required business processes.
SAP Event Management (SAP EM) allows to track goods movements and to query the process status
of the movement flows at any time. SAP EM enables you to coordinate your planning and activities
with your partners by exchanging information across systems. You can specify reactions to critical
situations. SAP EM can send a warning as an e-mail, or trigger processes in other application
systems.
The role-based approach of SAP EM makes it possible to view the same business process from
various points of view:
• Manufacturers are interested to know, whether the different service providers have delivered
the raw materials used in production on time and in the correct quantity.
• An individual service provider is interested to know where a means of transport or packing
materials that contain product/material are located and at what time.
• An individual customer is interested to know when the supplier delivers the materials that is
ordered.
SAP EM can be used to process messages about the events in business processes, to notify those
involved in the supply chain in various ways about business events that have occurred, and to make
this information clear.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 5

SAP EM integrates both internal and external partners from the supply chain, and this gains a cross-
company overview of the processes.
SAP EM can be implemented in all planning and execution processes within logistics.
There are some standard scenarios for EM existing and described in detail at SAP Marketplace.
Please use following link. http://service.sap.com/scm -> Supply Chain Event Management -> Visibility
Process.

Integration
SAP EM provides event processing across the entire supply chain. It communicates with application
systems such as an SAP R/3 or an external system, and transfers data to SAP Business Information
Warehouse (SAP BW). It is possible to make analytical queries for decision-makers in SAP BW. SAP
delivers an application interface that makes it easier to connect SAP EM to an SAP system and to
configure it in the SAP system.
SAP EM can work in principle with all SAP components and non-SAP components. The scope of
integration varies depending on the SAP EM release and the individual SAP application component
release. For more information about installing and integrating SAP EM, see the SAP Service
Marketplace under http://service.sap.com/scm → mySAP SCM Technology → Installation, Upgrade,
and Migration.

Features
SAP EM can link, update, and evaluate the event messages with the application data from the supply
chain network. It enables to:
Monitor, measure, and evaluate business processes:
o SAP EM automatically monitors events that occur and those that have not been reported (for
example, a goods issue, a purchase order transfer, production end, or an unreported proof of
delivery).
o SAP EM 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.
o Employ checking processes and notify persons responsible to control events.
o SAP EM checks the objects that are relevant to supply chain event management as soon as
the application system saves them.
o SAP EM can automatically inform the decision maker in critical situations that action is
required (for example, automatic re-scheduling of the subsequent process step when a delay
has occurred).
o Exchange and query information between partners (for example, e-mail or Internet)
o Data Transfer to SAP Event Management
o SAP EM receives SAP EM-relevant data from various sources such as service providers, GPS
systems, scanners for wagon and container labels, on-board computers in vehicles, and
service suppliers.
Data in the following formats can be sent:
o EDI (An EDI converter prepares the EDI data entry to be converted into IDoc format for the
SAP EM BAPI interface)
o IDoc (it is possible to use a separate IDoc for creating event handlers and one for sending
event messages).
o XML
Make the setting in SAP EM to determine whether the SAP EM-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.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 6

Before performing this Best Practice, ensure that the following preliminary tasks or checks in the
system are carried out:
o An SAP R/3 for release: 4.0B, 4.5B, 4.6B, 4.6C or 4.7 is successfully installed
o An SAP SCM system is successfully installed
o The relevant SAP EM Customizing settings in SAP R/3, SAP ECC and SAP SCM are made.

Questionnaire
The Sizing Check determines whether the available hardware resources of the SCM System are
sufficient to handle the expected workload. This check is important to prevent severe performance
problems that can be caused by underestimating the hardware requirement. We can deliver remotely
a Going Live Analyses Session (GA), Going Live Optimization Session (GO) and a Going Live
Verifications Session (GV).
Question Answer
Number of users for WCL
Highest Number of Event Messages expected per
day
Highest Number of Event Handlers expected per
day
Available configured Disk Space
Expected resident time (in days) for data to be
stored before archiving

Minimum Configuration
We recommend the same hardware as for the SAP Web Application Server 6.40. SAP Event
Management uses the standard tools for this function available in the SAP Web Application Server
6.40, and does not require an application specific tool – Please see Solution Management Guide for
Web Application Server 6.40.

Sizing CPU and Memory

For detailed sizing get in contact with SAP and the hardware partner. The following information only
provides guideline requirements and basic reference for CPU power, memory and hard disk.
For a detailed hardware sizing, please contact the hardware partner.
Memory consumption depends on the size of the packages that contain event messages. The most
efficient size is about 100 event messages in a single transmission. As the size of the event handler
package increases, the average memory consumption per package decreases. CPU consumption,
however, increases slightly.
For sizing we assume:
o Four event messages per event handler
o A peak sizing for CPU. Note that the categories between CPU and disk can vary.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 7

Category Highest Number of Event Handlers per Day CPU in SAPS Memory in GB

Small 100,000 300 1

Medium 250,000 600 2
Large 500,000 1250 4
Extra Large 1,000,000 2500 8

Sizing the Disk

For sizing we assume:
o A residence time of one month. A higher residence time leads to larger disk requirements.
o Event processing and event handler creation is logged. This is a large contributor to disk size

Category Number of Events per Year Disk in GB

Small 30,000,000 70
Medium 75,000,000 190
Large 150,000,000 390
Extra Large 300,000,000 780

Internet Communication Manager

The Internet Communication Manager (ICM) receives and sends requests (for example, incoming
HTTP requests) from or to the Internet. The Internet Communication Manager is the part of SAP Web
Application Server, which functions as the interface between the Internet and the SAP application
server.
Transaction SMICM is used to monitor and administrate the Internet Communication Manager.

Monitoring Procedure
The following chapter describes the most important tools for monitoring the SAP EM System.

Most Important Monitoring Tools

Alert monitoring with CCMS
Proactive automatic monitoring is the basis to ensure reliable operations for the SAP system
environment. SAP provides the infrastructure and recommendations how to setup the alert monitoring
to recognize critical situations for Event Management as fast as possible.
This function connects SAP Event Management (SAP EM) to the Computing Center Management
System (CCMS). It allows the use of the specific Event Management monitor in the Computing Center
Management System to view critical technical situations for example locked or unprocessed events
messages. For this purpose it is possible to define threshold values.
We recommend that you only connect SAP EM to the Computing Center Management System if you
have appropriate knowledge of Computing Center Management.
For more information on the Computing Center Management System, see the SAP Library

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 8

Processing Control
On the SAP Easy Access screen of the SAP menu for Event Management, choose Administration /
Processing Control
1. Trigger expected event monitoring so that SAP Event Management reacts accordingly (for example,
sends an alert).
The expected event monitor is a report that the system starts as a background process. It checks if
expected events that should be reported within a specific period of time have since become overdue. If
the monitor discovers an overdue event, SAP Event Management reacts in accordance with the rules
that have been defined.
SAP delivers activities for the expected event monitor (for example, for comparing two fields or
activating an event handler set).
2. Trigger subsequent processing of unprocessed event messages for locked event handlers.
Trigger subsequent processing of event messages that arrive for an event handler at a time when SAP
EM is locking it. For example, someone saves a shipment that updates an event handler, while
someone else is simultaneously trying to send an event message to SAP EM for this event handler.
SAP EM does not process this event message as the data update from the shipment is locking the
event handler. In order that SAP EM processes the event message for this event handler at a later
time, the appropriate background job correspondingly has to be scheduled.
3. Trigger the subsequent addition of an event handler to a locked event handler set.
Assign an event handler once again to an event handler set that SAP EM is locking. For example, a
colleague assigns an event handler to an event handler set. In doing this, the colleague locks this set.
It simultaneously tries to assign another event handler to this event handler set. To ensure that the
SAP EM assigns the event handler to the set in spite of the temporary lock, the appropriate
background job must be scheduled.
4. Resend application object data for event handlers
When trying to update event handler data by sending application objects to SAP EM, it may be the
case that the event handler is locked by other processing (for example, momentary processing of an
event message).
To ensure that the system updates the event handler with the data sent once the lock is released, it
temporarily stores the data in a database table (buffer).
This background job checks at regular intervals if data is contained in the database table and then
tries to process it. If necessary, it updates the event handler that was previously locked with this data.
A higher-level interface is available for all those SAP EM background jobs where the monitoring and
processing of the respective objects can be scheduled.

Application Log
An application log is available for both the application system (R/3 System) and SAP Event
Management System (SAP EM). Choose transaction /SAPTRX/ASAPLOG for the SAP EM
Application Log interface. This application log documents messages, exceptions, and fields. This data
provides information on communication processes and problems that occurred on the application side
when event handlers were created or event messages were processed in SAP EM, and when
information queries were made to SAP EM.
You can analyze the logs or the corresponding messages according to different themed areas and
gain more detailed information on the messages. The SAP EM application log provides an overview of
all activities for an event handler and for its corresponding event messages that have occurred during
event handler processing.
For the evaluation of SAP EM application log, choose Event Management Æ Administration Æ
Logging Æ Application Log: Display Logs in the SAP Easy Access screen (transaction SLG1).
It is necessary to have the appropriate authorizations, to define the following:
• The objects that are logged: Event handler creation, Event message processing and updating data
from an external source

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 9

• The level of detail that the system should use when logging (from only high-level processes to
logging the details of each process)
The application log can be called from both the event handler overview and the event handler detail
overview.
For more information, see the SAP Library.

Interface Monitoring
Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.
SAP Event Management uses the standard tools for this function available in the SAP Web Application
Server 6.40, and does not require an application specific tool – Please see Solution Management
Guide for Web Application Server 6.40.
If the Event Management scenario requires qRFC processing, the inbound and the outbound RFC
queues can be monitored, using the transactions SMQ1 and SMQ2.

Archiving and Deletion

Archiving
No longer needed objects that are relevant to supply chain event management (SAP EM relevant),
could be archived or simply deleted. SAP delivers the following standard archiving objects for SAP
Event Management
o Archiving object for event handlers /SAPTRX/A0
o Archiving object for event messages /SAPTRX/A1
To archive SAP EM-relevant objects and then deletes them from the database:
o Specify the archiving objects in customizing (Transaction /SAPTRX/AOBJ)

o The event handlers and event handler sets must be deactivated before archiving them (e.g. via
Rule in Rule set).

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 10

o Specify the time intervals (residence times) for the archiving objects. To change a route you no
longer need the event handler with all its expected events for the old route planning. You trigger
the archiving and/or deletion of the event handler in one of the ways described below:
ƒ You archive an event handler that belongs to one or more event handler sets by
deactivating and archiving the entire set.
ƒ You can specify that event handlers and event handler sets are archived automatically by
defining appropriate activity parameters and using them in plug-in function modules within
a rule.
The system checks if the difference between the date on which the objects were created and the
current date is greater than the residence time. If this is the case, the event handlers and the event
messages along with all data belonging to them are archived.
For more information on automatic archiving, see the SAP Implementation Guide for Event
Management Æ Archive or Delete Event Handlers and Event Messages Æ Define Residence Times
for Archiving or Deleting.
If the customizing table is blank, then the system default for archiving is 100days. That is all events will
automatically be archived after 100 days.
The default value for the event handler residence time is the date when the event handler was
created. You can also select the date when an event handler is deactivated.
Messages or Event Handler can be archived individually with the archiving object /SAPTRX/A1.
It is possible to specify that once a week all event handlers that are older than three months and
whose indicator has been set to inactive should be archived.
See notes 69143 and 77305 for information on the performance and termination of the archiving
procedure. We recommend testing higher values for the commit counter.

Fastest Growth Tables for EM

The fastest growth tables are dependent on the number of parameters, rules, and expected events
one has. For Event Handlers, pay special attention to the following tables:
/SAPTRX/EH_INFO
/SAPTRX/EH_CNTRL
/SAPTRX/EH_EXPE
/SAPTRX/EH_STHST
/SAPTRX/EH_TASK
For event messages it is also dependent on how the customer uses Event Management. If using file
attachments, pay special attention to the tables
/SAPTRX/EVM_AFB (can be stored in a file system instead)
/SAPTRX/EVM_AFC
Otherwise pay attention to table
/SAPTRX/EH_EVMSG
Additional structures may require monitoring if filled when the BAPI is called.
Additional tables starting with /SAPTRX/EVM* may require monitoring if they are used in the process.
For the Web Communication Layer, The Logging Manager can be configured to log at four different
levels of granularity – Debug, Info, Warning and Error, with Debug being the most detail, and Error
being the least detail. For customers collecting a lot of detail in the Logging Manager, this should be
monitored for archiving purposes. Details can be found in the WCL Install Guide, under Logging
Manager.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 11

Deletion
To delete an event handler or an event message is possible in one of the following ways:
o Deleting an application object in the application system, the corresponding event handler(s) is
deleted in SAP EM.
o By specifying an appropriate rule in the rule set. Specify for the delivery processes that all event
handlers that are older than two weeks and for whose delivery process the bill has been paid are
to be deleted in SAP EM.
o By executing one of the following deletion reports. Report for deleting inactive event handlers
(/SAPTRX/DELETE_EH) which should be not archived.
o In addition this report can be used to delete inactive event handlers belonging to an event handler
set. Report for deleting event messages (/SAPTRX/DELETE_ EVMSG) which should be not
archived.
o The deletion reports are designed in particular for deleting test data.
Deleting: the system deletes the corresponding event handlers and/or event messages.
Check using transaction SPRO Æ Event Management Æ Archive or Delete Event Handlers and Event
Messages
Æ Check to see if the delete jobs are scheduled.

Set up a process
To set up a monitoring process, the following steps need to be performed:
Application Object Types are Defined in the Application System
The application object type is used to determine the supply chain event management relevance of
objects or processes in the application system. The SAP EM relevance is determined by using a
condition that can be defined in the application system and assigned to an application object type.
SAP Event Management processes the incoming event messages according to the Rules defined for
the Event Handlers.
The application object type can be used to determine the tracking IDs that identify objects. In addition
it can be used to determine the control, info, and system parameters. SAP EM needs these for
information and query purposes and to check the SAP EM process.
System parameters are defined in the Event Management System after a mapping from the control
parameters took place. In this way, either manual or a system can send internal or external messages
to this object and SAP EM can execute the SAP EM process.
The application system writes the application object type and the application object ID into a status
table. Together with the name of the application system, they provide a unique reference between the
application object and event handler. The system uses this reference to refer to the business object
and its business process type. A many-to-one relationship exists with the business process types in
the application system.
The Following Objects are Defined in SAP EM:
o The event handler types
o The condition for determining the event handler type
o The expected event profile
o The parameter profile
o The status attribute profile
o The rule set

© 2006 SAP AG
 Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 12

Customizing
The Customizing for the application interface must be set up and have the corresponding visibility
scenario installed in the application system or have an own process defined. The visibility scenario
enables connection to the business objects in the application system.
There are some standard scenarios for EM existing and described in detail at SAP Marketplace.
Please use following link. http://service.sap.com/scm -> Supply Chain Event Management -> Visibility
Process.
Set Up the RFC Connections That Create the Link Between the Application System and SAP EM.
To establish the physical connection between SAP NW BI and SAP EM, you need to create an entry
in the transaction SM59.

Overview of regularly-used Jobs, Transactions

and Monitoring Tasks
Monitoring Monitor TA/Tool Monitor Freq. Monitoring Activity or Respon- Escalation
Object Error Handling sibility Procedure
Procedure
Set up of /SAPTRX/SLG1_LI Once before Schedule background Program Contact
monitoring NK starting to work job for each client that scheduling application
the first time wants to be monitored in manageme support
with SAP EM the CCMS. nt
(not working
with CCMS)
Set up of /SAPTRX/SCHEDU Once before Schedule background Program Contact
monitoring LE_EM_JOBS_NO starting to work job for each client that scheduling application
DE the first time wants to be monitored in manageme support
with SAP EM the CCMS. nt
(not working
with CCMS)
Processors Report 6 times per day Schedule a regular job Program Contact
of locked /SAPTRX/PROCES in transaction scheduling application
event S_LOCKED_EHS /saptrx/emjobs. See manageme support
handlers SAP Note 656990. nt
Processor Report 6 times per day Schedule a regular job Program Contact
of locked /SAPTRX/PROCES (when working in transaction scheduling application
event S_LOCKED_SETS with EH Sets) /saptrx/emjobs. See manageme support
handler SAP Note 656990. nt
sets
Resend Report 6 times per day Schedule a regular job Program Contact
Application /SAPTRX/R_REPO in transaction scheduling application
Object ST_AI_LOGS /saptrx/emjobs. See manageme support
Data for SAP Note 656990. nt
Event
Handlers
Number of /SAPTRX/COLLEC 6 times per day Schedule a regular job Program Contact
locked T_LOCKED_EH (when working in transaction scheduling application
event with EH Sets) /saptrx/emjobs. See manageme support
handlers in SAP Note 656990.. nt
the desired
client

© 2006 SAP AG
 Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 13

Monitoring Monitor TA/Tool Monitor Freq. Monitoring Activity or Respon- Escalation

Object Error Handling sibility Procedure
Procedure
Number of /SAPTRX/COLLEC 6 times per days Schedule a regular job Program Contact
locked T_LOCKED_EHSE in transaction scheduling application
event TS /saptrx/emjobs. See manageme support
handler SAP Note 656990. nt
sets in the
desired
client
Display transaction Daily Display the application Program Contact
Application /SAPTRX/ASAPLO log in the SAP EM. scheduling application
Log in SAP G manageme support
EM nt
Evaluation Transaction SLG1 Daily Evaluate the application Program Contact
of log in the SAP EM scheduling application
Application manageme support
Log nt
Continuous Report Display functionality Program Contact
ly identifies /SAPTRX/EE_MON scheduling application
expected ITOR manageme support
events that nt
are
overdue.
Status of /SAPTRX/EH_LIST Display functionality Application Contact
events and manageme application
error nt support
messages
shown.
List to see /SAPTRX/EVM_ST Display functionality Program Contact
if objects ATUS scheduling application
are manageme support
processed nt
correctly.
The list
reflects
only data
errors, not
business
process
issues.
Inbound Transaction SMQ1 / Daily Status of the inbound Program Contact
and SMQ2 and outbound queues scheduling software
Outbound manageme monitoring
queues nt team
monitoring

Management of mySAP Technology

SAP provides you with an infrastructure, which helps your technical support consultant and system
administrators to effectively manage all SAP components and carry out all tasks related to middleware
technology.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 14

The aims of managing mySAP Technology are as follows:

o Provide a central interface to manage administrative tasks for middleware
o Improve the process of problem resolution for the entire solution
o Provide standardized administration of user profiles
You can find more information about the underlying technology in the Technical Operations Manual for
mySAP Technology in the SAP Library under mySAP Technology Components.

Backup/Restore and Recovery

Based on the type of application data a component holds we introduce a categorization scheme for
system components that can be used to analyze the backup requirements of any system component
and to easily determine an appropriate backup method for this component. The following table
contains a component list for your solution and the appropriate Categories of system components for
Backup & Recovery.
Categories of system components for Backup & Recovery
Categories of Category Properties Suggested Backup and Example
system Recovery Methods
components
I Only software, no - No backup, new installation BDOC-modeler
configuration or application in case of a restore or
data - Initial software backup after
installation and upgrade
- Backup of log files
II Only software and - Backup after changes have SAP Gateway
configuration information, been applied or Comm. Station
no application data - No backup, New SAP Business
installation and configuration Connector
in case of a restore SAP IPC (2.0C)
- Backup of log files
III Only replicated application Data: SAP IMS / Search
data, replication time is - No data backup needed Engine * SAP IPC
sufficiently small for a Backup of software, (2.0B) * Webserver *
restore configuration, log files SAP ITS
IV Only replicated application Data: - Application specific SAP IMS / Search
data, backup recommended file system backup or - Engine * Webserver *
because replication time is Multiple instances Backup of
too long data not managed software, configuration, log
by a DBMS files
V Only replicated application Data: - Database and log SAP IPC (2.0B) *
data, backup recommended backup or - Multiple Catalog Server
because replication time is instances Backup of
too long data managed by software, configuration, log
a DBMS files
VI Original application data, Data: - Application specific Webserver *
standalone system, data file system backup Backup
not managed by a DBMS of software, configuration,
log files
VII Original application data, Data: - Database and log x
standalone system, data backup Backup of software,
managed by a DBMS, not configuration, log files
based on SAP WebAS

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 15

Categories of Category Properties Suggested Backup and Example

system Recovery Methods
components
VIII Original application data, Data: - Database and log Standalone SAP R/3
standalone system, based backup, application log
on SAP WebAS backup (e.g. job logs in file
system) Backup of software,
configuration, log files
IX Original application data, Data: - Application specific
data exchange with other file system backup, data
systems, data not managed consistency with other
by a DBMS systems must be regarded
Backup of software,
configuration, log files
X Original application data, Data: - Database and log SAP liveCache SAP
data exchange with other backup, data consistency Mobile Workbench
systems, data managed by with other systems must be
a DBMS, not based on SAP regarded. Backup of
WebAS software, configuration, log
files
XI Original application data, Data: - Database and log SAP R/3 SAP CRM
data exchange with other backup, application log SAP APO SAP BW
systems, based on SAP backup (e.g. job logs in file
WebAS system), data consistency
with other systems must be
regarded Backup of
software, configuration, log
files

Additional information
SAP Event Management uses the standard tools for the following functions available in the SAP Web
Application Server 6.40, and does not require an application specific tool – Please see Solution
Management Guide for Web Application Server 6.40:
• System copy
• Periodical tasks
• Required manual periodical tasks
• Logon and Load Balancing
• Printing
• High availability
• User Management
• Software Change Management

User Management specific information

To create users and roles in SAP EM, see the SAP Help Portal at help.sap.com -> SAP NetWeaver
->Administrator’s Guide -> SAP NetWeaver Security Guide-> User Administration and Authentication.
Roles
SAP EM provides the following standard roles: /SAPTRX/SAP_EM_ADMIN
Authorization Objects
The roles that SAP EM delivers have preconfigured authorization objects associated with them. If you
create new roles or modify existing roles, you can use the authorization objects associated with these
roles.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 16

In SAP EM, users must be assigned to the correct authorization objects (with correct fields and values)
to be able to access the respective transactions and functions. Furthermore, restrictions defined using
event handler type authorization profiles are assigned here.
SAP EM provides the following standard authorizations:
• X_EM_EH (display event handler)
• X_EM_EH_CH (change event handler data)
• X_EM_EVM (send event messages)
By defining authorization and filter profiles you ensure that before displaying SAP EM data, the system
checks whether all event handler data can be displayed, for example if a partner is only allowed to see
the deliveries specified for him or her (authorization profile), or which event handler fields can be
displayed, for example if partners are only allowed to see particular events (filter profile).
Define Authorization Profiles
You can use authorization profiles to customize the contents that are displayed and the options for
confirming events, for example, if a partner is only allowed to see the deliveries specified for that
partner with the following transaction: /SAPTRX/TSCOAP
SAP Customizing Implementation Guide -> Event Management -> Authorizations and Filters -> Define
Conditions for Data Filtering
• Authorization Profiles
The authorization profile consists of one or more parameter sets that the system uses to create the
authorization parameters for an event handler. You assign the authorization profile to the event
handler type to determine which event handlers are displayed to the user and which event handlers
the user may change or create. The system displays all event handlers to the user which correspond
to the value in the control and info parameters of the user’s authorization profile.
• Authorization Parameter Sets
Assigning this value to the respective parameter in the user role maintenance screen (transaction
code PFCG) gives the respective users authorization to view the process.

Define Filter Profiles

You can use filter profiles to customize the contents that are displayed and the options for confirming
events, for example, if partners are only allowed to see particular events.
You determine which tables, fields and/or rows that are not displayed. You can define a condition or a
function for displaying an event handler component, which the system evaluates before it displays this
event handler component to the user. A field restriction can be defined for all fields of an event handler
component, but you can only define row restrictions for the following event handler components:
control parameter and info parameter via the parameter name, event messages via the internal event
code, expected events via the internal event code, query IDs via the query ID type, tracking IDs via the
tracking ID type, and status attributes via the status attribute type.
To define the filter profiles use transaction code /SAPTRX/TSCOFP.
SAP Customizing Implementation Guide -> Event Management -> Authorizations and Filters -> Define
Filter Profiles

Software Change Management specific information

Software Change Management standardizes and automates software distribution, maintenance, and
testing procedures for complex software landscapes and multiple software development platforms.
These functions support your project teams, development teams, and application support teams.
The goal of software change management is to establish consistent, solution-wide change
management that allows for specific maintenance procedures, global rollouts, including localizations,
and open integration with third-party products.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 17

This section provides additional information about the most important software components. The
following topics are covered:
• Transport and Change Management - Enables and secures the distribution of software changes from
the development environment to the quality assurance and productive environment.
• Development Request and Development Release Management – Enables customer-specific
maintenance procedures and open integration with third-party products.
• Template Management – Enables and secures the rollout of global templates, including localizations.
• Quality and Test Management - Reduces the time, costs, and risks associated with software
changes.
• Support Packages and SAP Notes Implementation – Provides standardized software distribution and
maintenance procedures. Details for Support Packages and SAP Notes for SAP Event Management
can be found at SAP SCM 4.0 Support Packages (SP), XI content, SAP liveCache Page
• Release and Upgrade Management – Reduces the time, costs, and risks associated with upgrades.
You can view which components are installed by following menu path System # Status, and selecting
the Component Information button in the SAP System data section.
All upgrades are made using the standard SAP upgrade tools.

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 18

Further Information
Troubleshooting
If executing this Best Practice did not produce the desired results, proceed as follows:
• Search for related SAP Notes
• Open an SAP Customer message describing your problem

Literature
For more detailed information about how to administer an SAP R/3 System, see:
• Sigrid Hagemann, Liane Will, SAP R/3 System Administration, 2003

For information about the administration of SAP APO systems, see:

• Liane Will, SAP APO System Administration, 2002

For information about how to monitor and tune general system performance, see:
• Thomas Schneider, SAP Performance Optimization Guide, 2003

For background information on administrative tasks with emphasis on system planning and setup, see:
• Hartwig Brand, SAP R/3 Implementation with ASAP, 1999

Other Best Practice Documents

In SAP Service Marketplace, quick link /scm >> Related Topics / Best Practices for Solution
Management: mySAP SCM, you can find several Best Practice Documents for Solution Management
like this one.

Background Information and References

SAP Documentation
SAP SCM 4.1 documentation is available on CD or in the SAP Help Portal in German or English.

Important SAP Notes

Note number Description
664072 Application Object ID Extractor
677373 Release restrictions Visibility Process
716176 Memory problems when using Application Log
718697 Application log settings are not working after upgrade
724520 Event Message BAPI performance enhancement
737042 Activity PARAMETER_CHANGE deletes wrong parameter
738947 Build tool for WCL.
746256 Alternative BPT is not considered when creating EH
752661 Deletion of EH and BW upload: Performance improvement
755397 Monitoring WCL 4.1 in CCMS
760035 Query ID contains log. system instead of appl. system name
787694 Endless loop when displaying EH data in Application system

© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 19

Note number Description

793979 Cross transport of BW procurement development
805294 Short dump CONVT_NO_NUMBER when archiving EH Sets
805298 Selection criteria for EH Set archiving not working
822831 Incompatible structure /SAPTRX/BAPI_EH_EXPECTED_EVENT
839899 Parameters and file attachments are not processed
849268 Activity OVERDUE_EE_RESET does not reset overdue flag
853741 Passing parameters to the workflow
858905 Buffering of table /SAPTRX/AOTREF not necessary
863551 Event message table /saptrx/evm_unpr not archived correct

Feedback and Questions

Send any feedback by formulating an SAP customer message to component SV-SMG-SER. You can
do this at http://service.sap.com/message.

© Copyright 2006 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries
all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are provided “as
is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained within these materials. SAP has no control over the information
that you may access through the use of hot links contained in these materials and does not endorse your use of third party
Web pages nor provide any warranty whatsoever relating to third party Web pages.

© 2006 SAP AG