1 2 Previous Next

SAP Event Management

29 Posts

This topic discusses the Unknown truth of SAP ERP, SAP Event Management and SAP Customer Relationship Management Trio Combination.


Before going into the topic let's see 'How Supply Chain Management is important in today’s end to end business process?'.


Supply chain is everywhere from running your home, in health services, hotel, retail, Wholesale, oil and gas company.


Some of you may remember an incident which took place during 2005 Katrina Hurricane disaster in New Orleans. Wal-mart, the world’s largest retailer shipped 2500 containers of disaster relief products quickly and efficiently to the devastated region in the first two and a half weeks. In fact they beat the federal emergency management agency and red cross on proven efficient supply chain. Walmart is considered to be the master of supply chain management and their efficient work during a natural disaster shows that Walmart is truly a master of supply chain management (Source: Total Supply Chain Management By Ron Basu, J. Nevan Wright).


Not only for Walmart, but, Supply Chain Management acts as a crucial part for many clients across the globe. Procuring and delivering to customers has become quite a challenge in each and every step in end to end business process cycle.


To understand the supply chain management in detail, I will take you through a scenario...


When we buy 12 cans of cola in a cardboard case from super market, the only thing we notice is the refreshing drink inside the can. But the end to end process involved, from manufacturing the cola till delivery to supermarket is lengthy process.


Bauxite ore is mined in Australia and then transferred in Trucks to nearby mill to produce powdery Alumina. Bulk Alumina is then transferred from mill to port in Truck and from there to the destination country in Ship. The molten aluminum is cast into ingots and shipped by boats or trucks to Philadelphia, US. The ingot goes into several processes to make coils. Thin coils are then shipped by truck to Can maker’s warehouse in Illinois State, US. Cans are manufactured and shipped to bottlers warehouse in pallets by truck. The cola company fill the cans and ships to supermarket by truck and cola finally reaches you.

Now we understand there are several sub-processes involved to make cola in can and deliver to supermarket. The key here is effective supply chain management which brings the products on time to port to reach destination country or to reach warehouse, to manufacture on planned time, to ship to warehouse and deliver to super market.

Now, let’s move on to understand how the trio of SAP ERP, SAP EM and SAP CRM will bring effective supply chain management.


When a supermarket orders 1000 cans of Cola, SAP ERP system raises sales order to process the order. All monitoring from order creation till receiving the payment is done by SAP EM system. SAP EM also captures expected and unexpected events. If any unexpected or unreported event occurs then SAP EM triggers a task in SAP CRM via ERMS and assigns it to relevant team for further processing.


The Sales Order is converted into production order for manufacturing. If there is any issue with production order then an unexpected event triggers to SAP EM and SAP EM will create a task in SAP CRM and assign it to production planner via ERMS to look at it. If there is no response, the issue will be escalated to the next level.


On successful completion of production, the purchasing team raises a PO to vendor to supply 1000 cans. When there is any delivery delay, short of qty, delivery time adjustment, SAP EM will trigger a task in CRM and assign it to customer service team via ERMS to notify customer about these changes.


Similarly if there is any shipment delay due to nature cause or cross border customs issues then SAP EM will trigger a task in CRM and assign it to shipment team or destination country customer service team.





In all of these scenarios, the issues have been addressed and resolved on time due to effective integration of SAP CRM with SAP EM and ERP. This proactive approach makes the business model transparent and deliver product on time without any delay. In case there is a delay, the customer would be happy if they are notified well in advance.


Everyone knows SAP ERP and SAP Event Management integration in today’s supply chain management, but integrating SAP Customer Relationship Management with SAP ERP and SAP EM are unusual but it gives a lot of benefit.


Some advantages as as follows:


  • Proactive customer service
  • Assign a task to relevant team
  • High visibility
  • Leverage to action immediately within SLA
  • Fill the gaps and tighten the integration of supply chain management
  • Mitigate the risk of losing customers
  • Monitor and evaluate your customer service


As of now, SAP Event Management has not been integrated with SAP Customer Relationship Management in Standard SAP. However, the customized solution gives you 100% transparent visibility on Sales and proactive service approach.

SAP has integrated SAP Fiori with SAP Event Management 9.2.  This is another major milestone in SAP Event Management and this tool is going to attract more customers who would like to view KPI’s with graphical visualization in real time through SAP Smart Business cockpits.  However, SAP hasn’t published the guide on “Available Features and Integration options” as of now in SAP OSS note 2093429 - Create an own Fiori app for Event Management 9.2



Release of SAP Fiori application with SAP Event Management 9.2, we can create our own FIORI application and make a new user experience (UX) across all devices (computers, smartphones, tablets etc.) to clients.



This is a good news but “What is SAP Fiori?”

SAP Fiori is the new user experience (UX) for SAP software. It applies modern design principles for a completely reimagined user experience. SAP Fiori UX represents a personalized, responsive and simple user experience across devices and deployment options.



Current SAP Fiori products for SAP Business Suite:



SAP Fiori for Request Approvals

SAP Fiori for SAP ERP

SAP Fiori for SAP CRM

SAP Fiori for SAP SRM

SAP Fiori for SAP SCM

SAP Fiori for SNC

SAP Fiori for MDG

And so on....



SAP FIORI product information link and check this brief video introduction of it.



I will update the features in this same article once SAP has officially released the information.

This Note is a few months old now but can't see it mentioned here at SCN...

Good info on TM/EM connectivity.





Some settings described in the documents do not comply with the current release.



Change History and Updates for the document - please implement the changes as described.

SAP TM 9.1 SP00 and higher with SAP Event Management 9.0 SP04 and higher - latest release v4.21 June 2014 (see attached PDF).

Guides for previous releases are available from Solution Manager.

These are some frequent issues which we come across while we do SAP Event Management Development and Quality system upgrade or patching.

Issue 1: Event Handlers are not created and updated in SAP Event Management post upgrade or patching

When you create a sales order, event handler doesn’t get created in SAP Event Management system.


To find out the root cause, I set a breakpoint in the beginning of functional module CALL FUNCTION 'GET_R3_EXTENSION_SWITCH' inside Sales order BADI /SAPTRX/SD_SALESORD -> Method IF_EX_BADI_SD_SALES~SAVE_DOCUMENT.




      i_structure_package = l_structure_package


      e_active            = l_extflag


After setting the breakpoint, when I create a new sales order in ECC system, I can check, what is the importing value returned by the parameter “l_extflag”.  In this case, I could see importing value returned by l_extflag is “blank”. The blank value shows that Business Transaction Event PI-EM is disabled in Transaction code BF11.




Business Transaction Event PI-EM is disabled in Transaction code BF11.




Enable Business Transaction Event PI-EM in Transaction code BF11.  To test if it works now, create a new sales order and it should create an event handler in SAP Event Management.




During patching / upgrade, Business Transaction Event PI-EM checkbox is being overwritten automatically to “Uncheck”.

Issue 2: Error “Target SAP system not found: Please check the customizing for the link and the customizing for the RFC connection”


SAP EM WebUI - We may want to check the existing sales orders, which have been created in the past. Here, I check if we can navigate to ECC Sales Order screen via Display link.  When I click on the sales order hyperlink, it throws an error Target SAP system not found: Please check the customizing for the link and the customizing for the RFC connection”.



First, check the configuration in IMG -> Event Management -> Event Messages, Status Queries, and Web Interface -> Web Interface -> Assign Link to Configured Field –> Assign Business Object Information / Assign Target Configured Field. In case you see any problem with configuration, fix it here. If all configuration looks fine, then we need to debug a little more from SAP EM WebUI.



Let’s move on to SAP EM WebUI to check why and where the issue occurs.  Following are the actual steps that I did in SAP EM WebUI to identify where the problem is.


  1. Executed Tcode SE24 and entered /SAPTRX/CL_EM_WDA_UI.
  2. Selected Method - GET_RFC_DESTINATION - returns name of rfc destination for link to SAP system.
  3. Set  External Breakpoint or Ctrl+Shift+F9 in the Method - GET_RFC_DESTINATION.
  4. Clicked Sales order hyperlink or display link in SAP EM WebUI.
  5. ABAP debugger screen appeared and stopped at CASE iv_log_sys_from.
  6. Executed F5 three times and double clicked on IV_LOG_SYS.
  7. I could see Application Object System ID was populated in WHERE app_system_id = iv_log_sys.
  8. It was pointing out to production system instead of patching upgrade system id.
  9. To track back from where this field was getting populated, I checked Standard Tab in debugging screen.
  10. In ABAP and Screen Stack block, double clicked the METHOD - CREATE_LINK_TO_SAP.
  11. The cursor shows at lv_rfc_dest = wd_assist->get_rfc_destination.
  12. I could see lv_log_sys was getting value from lv_aosys (line 3,564: lv_log_sys = lv_aosys).
  13. The lv_aosys value was coming from  line 3,489: lv_aosys = ls_hdr-ao_system.
  14. I checked  the line 3,486: READ TABLE lt_hdr INTO ls_hdr had called and filled the data of ao_system.
  15. Double clicked ls_hdr to check entry in ao_system. Hmm... The value of production id was coming from this field.
  16. The data is got from table /SAPTRX/EH_HDR-AO_SYSTEM (ls_hdr filled data from /saptrx/bapi_eh_disp_hdr).




When you perform validation, post system upgrade or patching work, do not use old completed event handlers for display link validation, because old (mean production) application system id resides in event handler header table /SAPTRX/EH_HDR-AO_SYSTEM.

Issue 3: “HTTP Error not found” in SAP EM WebDynpro-based UI navigation by using the "Display Details" button

When you highlight a line item and click “Display Details” button in SAP EM WebUI, it throws an error message as “HTTP 404 Not Found” in Internet Explorer browser (if your default browser is Chrome or Firefox, then it shows only a blank screen and no message).



Root cause:



  1. The issue is a change in the kernel implementation of method cl_http_utility=>fields_to_string() now causes the escape of the name part of the name/value pairs provided to the method.
  2. Correction is required in /SAPTRX/EM_WDA_UI COMPONENTCONTROLLER.





Implement this SAP OSS note 2002844 - Garbled URLs for the WebDynpro UI to fix the issue.



Kernel Patching / upgrade caused the issue.

Issue 4: Error - “Logon balancing error85: Message Server for _tsystem ‘XXX’ not found – check spelling and/or configuration”


When you click Sales order / Delivery / Shipment hyperlink in SAP EM WebUI, a login box appears (if you are not logged in already). Once you enter your user id and password credentials in popup screen, you get an error message immediately as “Logon balancing error85: Message Server for _tsystem ‘XXX’ not found – check spelling and/or configuration”.





  1. Check if your SAP GUI logon pad version is SAPGUI 720 or lower
  2. If yes, then you need to upgrade your user logon pad to SAPGUI 7.30 Patch 5 or upgrade SAPGUI logon pad depending on your SAP EM upgrade or patching versions.





We need to check which SAP GUI Logon pad is suitable for your SAP EM upgrade or patching.

Bonus Points: Post refresh activity in SAP EM


When there is a post refresh activity in SAP EM and Application Source System, we need to change SAP EM Logical system in the below configurations to show the correct system id's.


1. SAP Event Management :


  1. IMG -> Event Management -> Event Handlers and Event Handler Data -> Parameters -> Define Parameter Mapping -> Assign Profile to Mapping Area -> Application System Field -> Change correct system id (Dev or QA or Preproduction)



2. SAP ECC System:


  1. IMG -> Integration with Other mySAP.com Components -> Event Management Interface -> Define Application Interface -> Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types -> Define Used Business Process Types -> Define Application Object Types -> General Data Tab -> Event Manager Field -> Change correct system id (Dev or QA or Preproduction)
  2. IMG -> Integration with Other mySAP.com Components -> Event Management Interface -> Define Application Interface -> Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types -> Define Used Business Process Types Define Event Types -> General Data Tab -> Event Manager Field -> Change correct system id (Dev or QA or Preproduction)



If you have encountered any issues during SAP EM upgrade or patching, please list your problems and solutions in the comments section of this post.

In this post I have described how the process works to receive an inbound event message using ES, AIF and how to re-process the failed event messages.





FWO: Forwarding order

TO: Freight order / Transport order

FU: Freight unit

TU: Trailer unit


Using SAP EM Enterprise Service  TrackedProcessEventNotificationCreateRequest_In events are posted in EM. SAP PO/PI service interface and interface mapping required from PI/PO end.


SAP AIF supports for event message re-processing by changing the event details such as location, event code, tracking id and date /time. Authorisation based on event tracking ID is also promising in AIF but it requires custom development in AIF.

Security roles for business users are required to re-process the error event message in AIF. Using event message tracking id, standard EM authorisation is sufficient for accessing AIF monitoring tool.


AIF Monitoring Dashboard selection screen



AIF Event Message re-processing



Data structure space from the right bottom of the AIF dashboard support for event message reprocessing by changing the event details.



Structure value turns to yellow colour by default after changing the values.



Message mapping based on master/ transactional data in AIF is easy to maintain rather than building the complex message mapping in PI/PO or any other integration tools. PI Inbound message  queue can be deleted after the error as it may block the subsequent event processing.


Benefits of using AIF in EM

Event message re-processing

Tracking id mapping and custom business validations

Allowing the business user to re-process the event messages

The latest support package SP07 has been released for SAP EM 9.0 on 18th of July 2014. The support package contains - among some corrections - one new feature: Direct Search via URL. Details about this you can find here: http://scn.sap.com/docs/DOC-54696


Cheers, Daniel

SAP has recently released updates on OSS note 1976948 - Update for document "Integration of SAP TM and Event Management".   This OSS note gives us necessary information to configure integration of SAP TM and SAP EM.




SAP Transportation Management 9.1

SAP Event Management 9.0 with SP4 or higher


Go to above link and download it.  As per this document, most of the configurations are preconfigured in SAP TM and SAP EM if you are in these latest releases.

SAP Released SP06 on May 2nd 2014 for SAP EM 9.0.

Highlights include correcting issues and improving performance for OER related functionality. See below for the list of OSS notes included in the support pack.

AIE-OER Object Event Repository

  • 1963146 Queries may not return the original EPCIS message
  • 1964316 Performance issues when capturing an EPCIS message with a la
  • 1968226 Lock table overflow during EPCIS message processing
  • 1974869 Performance optimization for capturing of EPCIS messages
  • 1976112 Avoid call of method CHECK_REPOST_DATA
  • 1976153 Enable mass check for archived event handlers when processing
  • 1978145 Unnecessary call of FM /SAPTRX/FIND_EH_GUIDS when processing
  • 1979272 Query result in wrong order when ordered by ‘QUANTITY’
  • 1979566 Performance improvement for method CHECK_MAX_EVENT_COUNT

SCM-EM-MGR Event Manager

  • 1883931 Documentation missing for report /SAPTRX/EE_MONITOR_ADVANCED
  • 1960510 Performance optimization for capturing EPCIS messages

SCM-EM-MGR-CON Control Processing

  • 1972632 Unnecessary retrieval of event handler data when processing

SCM-EM-MGR-EVP Event Processing

  • 1957964 New parameter for activity TM_MAINTAIN_EXEC_INF
  • 1970392 Activity QUIT_EVM_PROCESSING effects processing of other event

SCM-EM-MGR-ISQ Information System and Queries

  • 1951993 Display of consolidated events not correct if one event message
  • 1958813 Performance enhancement for SimpleEventQuery
  • 1962186 Performance enhancement for SimpleEventQuery
  • 1971371 Split up of SELECT in method get_by_trk_ids
  • 1972756 Event message display is wrong if multiple event handlers ar
  • 1973329 Performance enhancement for SimpleEventQuery
  • 1974554 ‘By System’ indicator is not evaluated for hidden configured
  • 1975648 Columns of tab ‘Event Messages’ are not wrapped
  • 1976444 ‘Event Messages’ tab is getting collapsed after sending even
  • 1978096 Method FILTER_DATA performs unnecessary SELECTs

SAP Note 1976948 is where you will find the latest updates to the SAP TM EM Integration guide.


For SAP TM 9.1 SP00 and higher with SAP Event Management 9.0 SP04 and higher, the latest PDF version (v4.2 Feb2014), is directly available from this SAP Note.  This version, and all future versions, will be available in Solution Manager by means of the regular quarterly update.


  • Integration guides for all previous SAP TM releases are available from Solution Manager.


http://sapcampaigns.de/suiteonhana/   --> Check the video in the bottom left corner

SAP Smart Business for Event Management




SAP Smart Business for event management is a collection providing an overview of the most important key performance indicators for a transportation manager. It allows the transportation manager to monitor the operational transportation business based on the latest reported events including the following:

  • delays of deliveries in transit or those that arrived at customer sites with an overdue proof of delivery (POD)
  • average cycle times (time between the actual event dates and times of: when picking begins, PICKBEG, and the last event POD)
  • reporting completeness and compliance – what percentage of transports were reported and how accurate were those reports?

The transportation manager can use this ability to monitor the business to track deliveries and get insights into the business. This helps the transportation manager to spot as soon as possible anything that might need to be investigated more closely, and if necessary to correct any small issues in the operational business before they escalate.

What is SAP Event Management?


SAP Event Management provides visibility on business process to track and trace, monitor, automate exception, provide proactive alert and resolution. It Manages and tracks events across the process efficiently in real time.


What is SAP EM Rapid-deployment Solutions?


SAP Event Management Rapid-deployment solutions provide pre-configured / pre-packaged SAP Best Practices, Templates, Tools, Accelerators, Training Materials and Handbooks to simplify your business processes and helps to implement within weeks.


What’s delivered in SAP Event Management Rapid-deployment Solutions?


  • Order tracking and exception management for a sell-to-order scenario (Mandatory)
  • Order tracking and exception management for a make-to-order scenario (Optional)
  • Order tracking and exception management for a purchase-to-order scenario (Optional)


What is the Business Benefits?


    • Reduces process handling errors
    • Raise exception on time / before
    • Avoid undetected delays and late deliveries
    • No missing DIFOT
    • No costly SLA fines    
    • Identify hidden risks
    • Lesser lead time in Order-to-cash cycle
    • Increased customer satisfaction
    • Meet global customs requirements
    • End to End visibility of order cycle


What Business Process Scope is covered?



SAP EM Business Process Scope.png


Solutions in scope - Order Tracking and Exception Management from Sell-from-Stock (Mandatory):


    • Track and Trace each sales order line item
    • Set and release credit, delivery and billing blocks
    • Track and Trace delivery creation and goods issue events and set unexpected event for short picked qty / changes in qty
    • Track and Trace ocean / land shipment planning, start and end events and raise unexpected event for shipment delay
    • Track and Trace POD, billing document creation and release to accounting document
    • Track and Trace incoming customer payments


Solutions in scope - Order Tracking and Exception Management from Purchase-to-Order (Optional)


    • Track and Trace each sales order line item
    • Track and Trace Purchase order creation and goods receipt
    • Trigger unexpected events for PO change and cancellation
    • Track and Trace delivery creation and goods issue events and set unexpected event for short picked qty / changes in qty
    • Track and Trace ocean / land shipment planning, start and end events and raise unexpected event for shipment delay
    • Track and Trace POD, billing creation and release to accounting
    • Track and Trace incoming customer payments


Solutions in scope - Order Tracking and Exception Management from Make-to-Order (Optional)


    • Track and Trace sales order line item
    • Track and Trace creation, release, start and end of production order process.  Trigger unexpected events for production order change and cancellation.
    • Track and Trace delivery creation and goods issue events and set unexpected event for short picked qty / changes in qty
    • Track and Trace ocean / land shipment planning, start and end events and raise unexpected event for shipment delay
    • Track and Trace POD, billing creation and release to accounting
    • Track and Trace incoming customer payments


Pre-defined Accelerators / Deliverables


    • Project plan documentations – Solution details and summary
    • RDS model setup in sandbox
    • Kick-Off workshop – scoping questionnaire template & business role option
    • SAP SOLMAN Template
    • SAP OSS note assistant
    • Software requirements document for SAP EM and SAP ERP and SAP Best Practices Add-on
    • Implementation content files
    • Pre-configured business process documents and process diagrams
    • Configuration and scenarios documents
    • Test plans and scripts
    • Delivery acceptance forms etc

Achieving Go Live in Four Weeks


    1. Prepare project (1 week)
    2. Kick-Off Workshop presentations (1 week)
    3. Select scoping questionnaire options(1 week)
    4. System landscape setup and Installation(1 week)
    5. Implement optional scenarios (1 week)
    6. Solution activation and confirmation (2 weeks)
    7. Train key users (2 weeks)
    8. Testing of solutions (2 weeks)
    9. Switch to QA and Production (2 weeks)
    10. Performance Testing (1 week)
    11. Prepare End-User Training and get UAT Sign-Off (1 week)


System Requirements


SAP Event Management as an Add-On to SAP ERP:


            SAP EhP6 or EhP7 for SAP ERP 6.0

            SAP Event Management 9.0

            SAP Solution Manager 7.1 (Optional)


System Landscape


SAP EM Add-on option.png



SAP OSS notes help


Order Tracking and Exception Management RDSThis SAP OSS note carries additional information, installation and documentation details of SAP Order Tracking and Exception Management rapid-deployment solution v1.90 – Released on 3rd Mar 2014.


1670483 - RDS SAP EM for order tracking and exception management - This SAP OSS note carries information, installation and documentation details of SAP Order Tracking and Exception Management rapid-deployment solution for SAP EM 7.01 – Released on 26th Oct 2012.

So, now that SP5 is released what is inside?

The following is a list of OSS notes implemented in SCEMSRV SP 5 released on 10th Feb 2014.

Application System Configuration

    Event Manager

      1. 1922364  EM Customizing - Resource Description missing 
      2. 1923070  Corrections for EM 9.0 SP04 
      3. 1923159  Event Handler without Event Message Extension Table ID 
      4. 1925570  Recreation of EH after EH Post although no EE changed 
      5. 1939846  Short Dump duplicate database records insert LOG_LOCKED_EH 
      6. 1940935  Drop-down menu and checkboxes for event message sending are 
      7. 1941990  Resource Tracking - Loading, Planned Status Attribute, Actua 
      8. 1952767  Activity ACT_EE_MODIFY - does not use expected event profile 


      1. 1939277  Archiving: Minor performance improvements for archiving even 
      2. 1946071  Customizing: Define Criteria for Event Message Processing wi 
      3. 1950410  Runtime error MESSAGE_TYPE_X in auto archive report 


      1. 1934476  Update Execution Information in TM - Replace Tracking ID wit 
      2. 1941295  Resource Tracking - Customizing Actual Location 
      3. 1950747  Resource Tracking -Authorization Profile missing 
      4. 1950930  Resource Tracking - Parameter Storage Location RES30_ACT_STO 
      5. 1953946  Resource Tracking - Remove Planned Status 

    Control Processing  

      1. 1915817  Performance optimization for processing overdue events 
      2. 1919850  Performance optimization for processing overdue events 
      3. 1925884  Performance optimization of processing EE Monitor activities 
      4. 1926575  Time as input parameter for report /SAPTRX/EE_MONITOR_PACK
      5. 1928378  Time as input parameter for report /SAPTRX/EE_MONITOR_PACK 
      6. 1935720  Authorization check is not working correctly 

    Event Processing  

      1. 1741550  It is not possible to send event message with partner ID 
      2. 1945425  Long runtime during processing of Event Messages for previou 

    Information System and Queries  

      1. 1913410  Time zone conversion for event transmission date is wrong 
      2. 1913497  No validation of time zone when entering individual entry 
      3. 1914991  WDA UI: Search for query IDs unsuccessful 
      4. 1916772  Performance Optimization 'Event Messages' tab 
      5. 1917815  Search help is not regarded in configured field of a group 
      6. 1922408  Event date filter is not working for archived data 
      7. 1925154  Correction for Zoom-Function in Geo-Map 
      8. 1927268  WDA UI: Specifying columns for event handler set fields 
      9. 1928154  Geo-Map: Performance Correction 
      10. 1928828  WDA UI: Address data from hidden fields is lost 
      11. 1936897  WDA UI: Potentially wrong value takeover from address fields 
      12. 1946791  Geo-Map: Layout Settings 

    Integration with Event Management  

      1. 1921665  Resource Tracking - Customizing 

    In summary:

    Quite a few corrections in the SAP EM / TM integration space as well as the Web Dynpro Geo-Map component. Expected event monitoring was improved with 1 new report and an enhancement to the existing one. Performance around processing locked EH's was also improved.

    The latest support package SP05 has been released for SAP EM 9.0 on 10th of February 2014. The support package contains some corrections and some new EM features.

    The new EM features include the following:

    • new report /SAPTRX/PROCESS_LOCKED_EHS_PPF to parallelize the processing of locked event handlers
    • new activity parameters for rule set activity TM_MAINTAIN_EXEC_INF, which is used in the integration scenarios between SAP TM and SAP EM to propagate event messages to SAP TM:
      • new optional activity parameter REPLACE_TRXID can be used to populate the TOR ID with different value than the tracking ID, which is taken by default.
      • new optional activity parameter ERR_IN_APP_LOG can be used to avoid short dumps in SAP TM, that can occur e.g. if incorrect data is sent to SAP TM (non-existing TOR ID, wrong TORSTOPUUID,...). If the parameter is set, an error message is written in the application log instead.
    • new activity parameters for rule set activity ACT_EE_MODIFY, that enable the activity to take settings of an expected event profile into account when adding expected event:
      • new optional activity parameter Use EH EE Prof. can be used to use the expected event profile of the event handler type
      • new optional activity parameter EE Profile can be used to provide an expected event profile directly, if parameter Use EH EE Prof. is not used



    Cheers, Daniel

    SAP has released 2 new OSS notes October of last year that will bring certain relief to those SAP EM implementations that are running with large volumes and high numbers of expected events. I bring it up here again because I still see implementations where folks are not leveraging these new improvements!

    For those of us that breathe SAP Event Management ;) we have seen numerous implementations where the /SAPTRX/EE_MONITOR job steps on itself or simply runs forever… Help has arrived …

    OPTION 1: Process all overdue events in one run

    Report /SAPTRX/EE_MONITOR_ADVANCED has been released in OSS note 1915817 to replace the original /SAPTRX/EE_MONITOR. This report loops through all expected events that have not been reported and where the date occurs in the past. This is where the performance improvement is achieved. The selection screen (shown below) has an option to select the date based on the Expected Event Date or the Expected Message Date. The original report used the first option and selected on both the dates. By understanding which value your implementation is using (Message or Event) you can select the appropriate option to run the report.

    If you select the Expected Event Date option then the EVT index is used on the select on /SAPTRX/EH_EXPEV (via view /SAPTRX/V_EXPE_A). For the Message Expected Date option the MSG index is used instead.


    OPTION 2: Process “packs” of overdue events in several runs

    Report /SAPTRX/EE_MONITOR_PACK has been modified in OSS note 1919850. This report allows you to process overdue events in packets. This allows you to reduce the backlog of overdue events by ensuring that the program runs to completion instead of clocking forever because there are too many overdue events to process…

    The selection screen (shown below) has been extended to include the same options as mentioned above and also behaves in the same way when selecting data based on the specified indexes.

    In summary, if you are using expected events in your implementation and are running the overdue monitor, you should go ahead and implement these 2 notes and then schedule the overdue monitor accordingly.

    General Functionality:


    The visualization of the different scenarios with the SAP EM 9.0 Geo-Map was enhanced with further functionality. Until now it was possible to display one
    or more Event Handlers on the Geo-Map. In relation to a selected Event Handler all reported Event Messages are displayed with suitable coordinates.



    Further informations can be found under the following link:







    New Function - Display Planned Messages:


    Now it is also possible to display not only the reported Event Messages per Event Handler, it is also possible to display planned Event Messages. To distinguish the reported from the planned Route it is set to a different color for the different Event Message status. For example, the screen shows all reported Event Messages with the color blue and the unreported (planned) Event Messages with the color purple.



    A description "How to display the Planned Route on the Geo-Map" can be found here -> http://scn.sap.com/docs/DOC-44725


    With the BAdI Implemention it is easy to realize the individual layout requirements. The Enhancement Guide for the BAdI can be found under the
    following link:






    New Function - Show all Event Messages:


    Until now it was just possible to display further details per Event Handler or Event Message with the right mouse click. In addition to this functionality, it is also feasible to display all Event Messages by selecting more than one Event Handlers. With right mouse click on an Event Handler, it is realized to display or hide all Event Messages for this Event Handler.






    The possibility to display and hide all Event Messages for all selected Event Handler is also realized by right mouse click somewhere on the geo-map.






    New Functionality - Highlight the selected Event Message:



    A further nicely feature is to highlight and locate selected Event Messages. By displaying one or more Event Handlers and selecting one Event Message in the Event Message table the selected Event Message is highlighted and zoomed to on the Geo-Map.





    Filter Blog

    By author: By date:
    By tag: