Introduction to SAP Event Management

By Nisha Verma, IBM India

What is SAP Event Management?

Supply Chain Event Management (SCEM) can be defined as an application supporting control processes for managing events within and between companies in real-time.

This integrated software functionality supports five major business processes including the ability to monitor what is happening within the supply chain, notify the right person in case of a delay or critical event, simulate activities, control your processes and measure your supply chain activities so that you can adapt your business process and make it more effective and efficient. SAP Event Management offers visibility on processes, assets as well as performance along entire supply chain. Extensive tracking & tracing functionalities allow process monitoring, automated exception resolution, proactive alerting as well as extensive reporting - in one single solution.  

SAP Event management which is part of SCM module of SAP is a new module implemented in very few companies. Since this is a tracking system, its best use is possible in logistic companies like DHL, NOL etc where this module can be used to track their cargo at different places during transit process. SAP provides visibility processes for scenarios related to business processes carried out in application systems. It’s more of technical as even few SPRO steps are more inclined towards technical related stuff as explained below.  

We can track business transactions happening in application system by making data flow between application system & EM systems. Application system can be ECC, TM (Transportation Management) etc. Data flows through EM* queues from an application system to EM system.  

New terminologies:-  

There are new terminologies related to event management like BPT (Business process type), AOT (Application object type), Event type, tracking id, event handler etc. Business process type corresponds to business document like ECC delivery – ESC_DELIV stands for this in EM system.

Below you can see SPRO setting done in ECC for EM functionality.

 

 

 While AOT relates to at what level of document, data flow is being considered, like for sales order, we can define different AOTs for header, line item, schedule line item. Similarly for delivery, we can define similar AOTs with handling unit in addition as seen below.

Above screenshot shows standard AOT defined in ECC having sequence number 10 & 20. If we define customized AOT, then we would need to give a lower sequence number so that our customized AOT gets triggered. Lower sequence number means higher priority.  

Tracking Id refers to document number in EM like delivery no, sales order number etc. And each relevant business process is represented in SAP EM as event handler which includes attributes like tracking id & parameters. There are three types of parameters in EM – control, info & system parameters which are defined in rule set in SPRO in EM system.  

Event types  

Since EM is meant for tracking events related to business process, so we need to list out expected events pertaining to business process. For example, for ECC delivery, expected events can be picking, packing, goods issue etc.  

Data will be posted against each of these expected events as per the design and we can also define reaction to such events in EM.Like if goods issue event is posted in EM, then we need to trigger an email to customer. Here, we can make use of alert framework using which an alert be it sms or email can be sent to specified persons.  

Event handlers are created in SAP Event Management (SAP EM) in various ways:

·         The application interface creates event handlers for application objects.

·         Sending an event message creates an event handler.

·         The application system calls a Business Application Programming Interface (BAPI). This triggers the creation of an event handler in SAP EM.

The application system writes the application object type and the application object ID into a status table. Together with the name of the application system, they provide a unique reference between the application object and event handler. The system uses this reference to refer to the business object and its business process type. An n-to-one relationship exists with the business process types in the application system.

We can view event handler details by using transaction /SAPTRX/EH_LIST in EM system.  

Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image