1 2 Previous Next

SAP Event Management

24 Posts

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.

 

Prerequisites:

 

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

 

http://help.sap.com/saphelp_hba/helpdata/en/b1/d56552e2311357e10000000a445394/frameset.htm

 

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 


    Administration

      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 


    Configuration  

      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.

     

    GeneralFunctions.png

    Further informations can be found under the following link:

     

    /community/scm/event-management/blog/2012/12/21/sap-event-management-90--em-and-visual-business-integration

     

     

     

     

    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.

     

    PlannedMessages.png

    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:

     

    http://scn.sap.com/docs/DOC-50073

     

     

     

    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.

     

    ShowAllEVM1.png

     

    ShowAllEVM2.png

     

    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.

     

    ShowAllEVM3.png

     

    ShowAllEVM4.png

     

    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.

     

     

    HighlightEVM.png

    SAP Event Management 9.0 was delivered with the new feature of a geo-map component. The component using SAP Visual Business 2.0 is capable of displaying event handler and event message information in a geographical context. It is integrated into the standard user interface and can be configured using geo-map profiles. Take a look here to see the scenario:

     

    http://scn.sap.com/community/scm/event-management/blog/2012/12/21/sap-event-management-90--em-and-visual-business-integration

     

    For customer project having requirements going beyond the standard, it is possible to enhance the geo-map component in multiple ways. The following document describes the available options including example implementations.

     

    http://scn.sap.com/docs/DOC-50073

    How-To Access TM - EM Integration Guide SAP TM >= 9.0

     

    SAP TM 9.0:

     

    http://help.sap.com/transportationmanagement90

         -> Configuration and Deployment Information

              -> Link to SAP Solution Manager Content Documentation (confirm "I Agree")

                   -> Integration Guides

                        -> Integration of SAP Event Management

     

     

    SAP TM 9.1:

     

    http://help.sap.com/transportationmanagement91

         -> Configuration and Deployment Information

              -> Link to SAP Solution Manager Content Documentation (confirm "I Agree")

                   -> Integration Guides

                        -> > Integration of SAP Event Management

    Scenario

    You would like to calculate group durations in Event Management for combination of events like Shipment Start and Shipment End. These durations can then be extracted into BW using the data source 0SCEM_3.

     

     

    Example

    Consider the following shipment in ECC. We are interested in capturing the planned and actual transit time for the shipment. Transit time will be defined as time elapsed between the events Shipment Start and Shipment End.

     

    shipment.jpg

     

    The Step By Step Solution

    Execute the transaction SPRO in the Event Management system and then click on the SAP Reference IMG button. In the IMG open the node:


    2.png

     

    SAP Customization Implementation Guide > Event Management > SAP Business Information Warehouse Interface > Define SAP BW Profiles.

    3.png

    Now select the BW Profile that you are using for extracting Event Management data into BW and then double click on Group Duration Calculation in the left pane.

     

    NOTE: BW Profile is used in customizing for mapping event handler information into extraction structures for the SAP Business Information Warehouse. The SAP BW profile is assigned to an event handler type to allow event handler data to be extracted.

    4.png

    In the pop-up box which appears use the Search Help button to select the group ID for which you would like to setup the duration calculation and hit enter. If no group ID exists then you will need to create one.

    5.png

    6.png

    On the change screen hit the “New Entries” button for creating new duration calculation. Now make the appropriate selections for the entries in the Group Duration Calculation.

    7.png 

     

    The selections that you make here are very important and requires a bit of an explanation here.

     

    • The data source 0SCEM_3 provides us with fifteen duration fields, “DURATION_01” to “DURATION_15” for each group ID defined in the system.

     

    • You have a free hand here to decide which field will represent which duration. In the screenshot above we have selected DURATION_01 to represent the planned duration between the events “DEPARTURE” and “Proof of Delivery (POD)”. Similarly DURATION_02 in our case represents the actual duration between the events “DEPARTURE” and “Proof of Delivery (POD)”.

     

    • Src. Table will be the table from where these actual and planned values will be fetched. In our example it is the “Expected Events” table and it is numbered 4 in the system.

     

    • TST1 and TST2 are the fields which store the planned and actual time type. In our example for DURATION_01 we have selected TST1 and TST2 both as “EVENT_EXP_DATE” (the planned time) and for DURATION_02 TST1 and TST2 both as “EVENT_DATE_UTC” (the actual time).

     

    When you are done setting up the duration calculations save them and exit out of SPRO. Now we need to re-initialize the data source so that these calculations come into effect for historical records. On the SAP Easy Access screen, under the SAP Menu and drill down to the following node:


    SAP Menu > Event Management > Administration > SAP Netweaver BI Upload > Intial Setup Tables


    Here you can choose to delete the event handler header table, events table and the expected events group table. This is similar to deletion of the setup tables in ECC.

    8.png

    Now to refill the setup tables go to the following node in the SAP menu:

     

    SAP Menu > Event Management > Administration > SAP Netweaver BI Upload > Initial Data upload to SAP Netweaver BI.

     

    Make the appropriate selections here for the data that you wish to initialize. Make sure that the Event code is set to “0INT”.

    9.png

    Results

     

    With the above settings if you run the extractor 0SCEM_3 it should correctly calculate the group durations in Event Management as shown in the image below.

    10.png

    Scenario

    You would like to calculate durations in Event Management for different events like “Carrier Arrival”, “Load Begin”, “Departure” etc for Shipments. These durations can then be extracted into BW using the data source 0SCEM_2.

     

    Example

    Consider the following shipment in ECC. We are interested in capturing the delay between the planned and the actual times for each of the events (Check-in, Loading start etc).

     

    shipment.jpg


    The Step By Step Solution

    Execute the transaction SPRO in the Event Management system and then click on the SAP Reference IMG button.


    spro.jpg

    In the IMG open the node:

    SAP Customization Implementation Guide > Event Management > SAP Business Information Warehouse Interface > Define SAP BW Profiles.


    node.jpg

    Now select the BW Profile that you are using for extracting Event Management data into BW and then double click on Event Duration Calculation in the left pane.

    NOTE: BW Profile is used in customizing for mapping event handler information into extraction structures for the SAP Business Information Warehouse. The SAP BW profile is assigned to an event handler type to allow event handler data to be extracted.


    profile.jpg

    In the pop-up box which appears use the Search Help button to select the event for which you would like to setup the duration calculation and hit enter. Let’s say we select the event “ARRIV_CARR” which is the carrier arrival in this case.


    pop.jpg

    Hit the “New Entries” button for creating new duration calculation. Now make the appropriate selections for the entries in the Event Duration Calculation.


    entries.jpg


    The selections that you make here are very important and requires a bit of an explanation here:


    • The data source 0SCEM_2 provides us with five duration fields, “EVT_DURATION_01” to “EVT_DURATION_05” for each event defined in the system.
    • You have a free hand here to decide which field will represent which duration. In the screenshot above we have selected EVT_DURATION_01 to represent the difference between planned and the actual time for the event “ARRIV_CARR”. Similarly EVT_DURATION_02 in our case represents difference between the planned message arrival time in Event Management system and the actual time the message was received for the event “ARRIV_CARR”.
    • Src. Table will be the table from where these actual and planned values will be fetched. In our example it is the “Event Message Header” table and it is numbered 4 in the system.
    • TST1 and TST2 are the fields which store the planned and actual time respectively. In our example for EVT_DURATION_01 we have selected TST1 as “EVENT_EXP_DATE” (the planned time) and TST2 as “EVENT_DATE_UTC” (the actual time).


    Once you are done with these settings we can then save them. Follow the same instructions for the other events like “LOAD_BEGIN”, “LOAD_END” etc.


    When you are done setting up the duration calculations for all the events, save them and exit out of SPRO. Now we need to re-initialize the data source so that these calculations come into effect for all records. On the SAP Easy Access screen, under the SAP Menu and drill down to the following node:


    SAP Menu > Event Management > Administration > SAP Netweaver BI Upload > Intial Setup Tables


    Here you can choose to delete the event handler header table, events table and the expected events group table. This is similar to deletion of the setup tables in ECC.


    init.jpg

    Now to refill the setup tables go to the following node in the SAP menu:


    SAP Menu > Event Management > Administration > SAP Netweaver BI Upload > Initial Data upload to SAP Netweaver BI.


    Make the appropriate selections here for the data that you wish to initialize. Make sure that the Event code is set to “0INT”.


    upload.jpg

     

    Results

    With the above settings if you run the extractor 0SCEM_2 it should correctly calculate the duration in Event Management for different events like “Carrier Arrival”, “Load Begin”, “Departure” etc for Shipments.


    last.jpg

    There is a new blog posting under SAP Transportation Management describing how to configure the geo-map content for SAP Visual Business 2.0. As this component is also used in SAP EM 9.0, this information can also be used to configure SAP EM 9.0.

     

    http://scn.sap.com/community/scm/transportation-management/blog/2013/02/18/monday-knowledge-snippet-mks--29-configuration-of-geo-map-content

    Actions

    Filter Blog

    By author: By date:
    By tag: