Professional Documents
Culture Documents
Manage Supply Chain Event Management mySAP SCM 4.1
Manage Supply Chain Event Management mySAP SCM 4.1
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
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
System Requirements
This document applies to mySAP SCM release 4.1.
© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 4
Preliminary Tasks
© 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.
© 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 30,000,000 70
Medium 75,000,000 190
Large 150,000,000 390
Extra Large 300,000,000 780
Monitoring Procedure
The following chapter describes the most important tools for monitoring the SAP EM System.
© 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.
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.
© 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.
© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 13
© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 14
© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 15
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
© 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.
© 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 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
SAP Documentation
SAP SCM 4.1 documentation is available on CD or in the SAP Help Portal in German or English.
© 2006 SAP AG
Best Practice: Manage Supply Chain Event Manager in mySAP SCM 4.1 19
© 2006 SAP AG