Slides

238293380 sap-transportation-management-and-sap-event-management

Description
1. SAP Transportation Management & SAP Event Management 1 2. 2 Agenda SAP Transportation Management & SAP Event Management „ Business Purpose „ Solution…
Categories
Published
of 36
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  • 1. SAP Transportation Management & SAP Event Management 1
  • 2. 2 Agenda SAP Transportation Management & SAP Event Management „ Business Purpose „ Solution Overview SAP Event Management Details „ Solution Details „ Solution Configuration Application Interface
  • 3. Event Management – Business Purpose 3 Order Taking Visibility „ Status tracking of the order processing „ Based on single consignment order (shipment request) „ Life cycle – from order entry to start of execution „ Assigned roles – shipper/ordering party, transportation dispatcher Order Execution Visibility „ Status tracking of order / shipment execution „ Based on single shipment „ Life cycle – start of execution to proof of delivery „ Assigned roles – shipper/ordering party, transportation dispatcher, consignee Resource Visibility „ Status tracking of a single resource (e.g. container, truck, trailer, railcar) „ Assigned role – Transportation dispatcher
  • 4. Solution Overview – Business Purpose SAP Event Management (SAP EM) monitors: „ The execution of the planned transportation activities (PTA) „ Offers communication channels to customers, partners and employees SAP EM can control: „ The visibility process through rule based processes „ The business process through integration with the SAP TM system In case of delays or deviations from plans, SAP EM can: „ Alert staff members, partners or initiate other activities „ Update SAP TM automatically 4
  • 5. Solution Overview – Order Taking and Execution Visibility Process Order Taking Order Execution 5 Transfer Order Shipment Request Freight Units Shipper/Ordering Party Transportation Dispatcher Shipper/Ordering Party Consignee Loc A Loc Z Create Planning Confirm Assign Shipment Transportation Dispatcherr Shipper/ordering Party Consignee Shipment Loc A Loc B Loc C Loc Z Departure Arrival/ Departure Arrival/ Departure Arrival Event Handler for Shipment Request Event Handler for Shipment
  • 6. Solution Overview – Order Taking and Execution Visibility Process Order Taking Order Execution 6 Create Planning Confirm Assign Shipment Departure Arrival/ Departure Arrival/ Departure Arrival Event Handler for Shipment Request Event Handler for Shipment
  • 7. Solution Overview – Transportation and Event Management Process Flow SAP TM SAP EM 7 Shipment activated Create Exec. Loading Activity Confirm Departure Alert Delay Shipment Event Handler created Event Depar-ture Delay Consignee Notification Query And Display Shipment Status Event Loading Retrieve Shipment Tracking Data Event Import Arrival Carrier Reports Loading Carrier Reports Departure Carrier Reports Import Arrival Business object creates event handler Received events update business object data Business objects send events User activates business object User queries retrieve tracking data Events trigger notfications Overdue events raise alerts Shipment status be “Executed” to work with EM
  • 8. Solution Overview – Executed Transportation Activities Executed Transportation Activities have a from and a to date-time and status. Executed Transportation Activities can be created/changed in SAP TM and from SAP EM SAP EM only reports Events and they have an associated time, but no status In the integration between SAP EM and SAP TM the Executed Transportation Activity is created or updated and a status is updated. „ Example 1: SAP EM Event “Departure” creates an ETA “Transportation” only with a start date-time the status “In Execution” „ Example2: SAP EM Event “Arrival at destination” updated the ETA “Transportation” with the end date-time and the status “Executed”. SAP TM SAP EM 8 Create Transportation ETA Departure Update Transportation ETA Arrival at Destination
  • 9. Solution Overview – Standard Tracking and Tracing Scenarios 9 Transportation Execution Visibility (Tour) „ On-time Status of a standard tour (e.g. vessel voyage) „ Life cycle: from tour execution start to tour execution end „ Tour resource level updates „ Assigned roles: Customer(shipper/ordering party/consignee), Transportion Dispatcher, Transportation service planner Tendering Visibility „ Tendering process between LSP and TSP / freight forwarders „ Life cycle: tendering offer to tendering answer or time-out „ Assigned roles: Transportation Dispatcher
  • 10. Solution Overview – Providing the Right Information to the Right People ... to CNO SAP Event Management provides visibility throughout the supply chain. This screen shows a view where the sales executive or the customer can see exactly the status of a make-to-order process, including production and distribution steps, at any given time. A role-based approach with a thorough filter and authorization concept makes it possible to view one business process, spreading different applications, from various points of view. 10
  • 11. Solution Overview – Web Access 11 User Role & Tracking Scenario Selection Profile Display Overview List Profile
  • 12. 12 Web Access – Detail View All Web Interface fields are fully customizeable ! Display Detail Profile Display Event Profile
  • 13. Solution Overview – Reporting Procurement Scenario Procurement Scenario IIssssuuee PPuurrcchhaassee OOrrddeerr Order Order Acknowledgement Acknowledgement PPrroodduuccttiioonn SSttaarrtt PPrroodduuccttiioonn FFiinniisshh SShhiippmmeenntt AArrrriivvaall GGooooddss RReecceeiipptt 13 Buyer: Online SAP R/3 Transaction Warehouse Forklift Operator: RF Device Carrier: Onboard Device Carrier: Manual Event Message Voice Recognition Web Offline PDA Customer: Sends Acknowledgement EDI or XML or BAPI… There are many ways to communicate the actual events. Possible communication scenarios include updating with an online transaction, EDI/XML connection, Onboard Devices, manual entry, offline PDA’s, voice recognition, login with a web interface, or updating using an RF Device.
  • 14. 14 Reactions on Alerts Received Alert Overview Single Alert Detail View Solution Overview – Example of Alert Inbox in SAP TM
  • 15. Solution Overview – Alerting Business Partners The Alert Framework is provided as part of the SAP Web Application Server. The application must define its own alert categories and implement the triggering of the alert instances to realize Alert Management. Alerts can also be triggered by external alert providers. They are all sent to the alert inboxes of the alert recipients, but can additionally be sent by other channels, such as by Internet mail, SMS, or to external alert systems. You must configure and schedule the processing of the alerts to meet your requirements. 15 Event Message Short Message Fax E-mail If Event Code = ‘Delay’ then inform partner Personalized alert-delivery Support for: „ E-mail „ Short Message Services „ Pager „ WAP & WAP Push Subscription on alert-categories Escalation: „ to superior or system administrator in case of missing confirmation Follow Up Activities: „ URL based direct navigation into application. For example, to favor to repair the mistake or for error analysis Alert forwarding: „ “This Info is important for my colleague as well”
  • 16. Solution Overview – New Developments in SAP EM 7.0 16 New Web UI Enhancements Usability Improvements „ Multiple event sending „ Report all expected events „ Send + display measurements & attachments „ Document flow – graph + table presentation „ Change logo & branding „ Screen flow & interaction „ Speaking Browser window titles
  • 17. 17 Agenda SAP Transportation Management & SAP Event Management „ Business Purpose „ Solution Overview SAP Event Management Details „ Solution Details „ Solution Configuration Application Interface
  • 18. 18 Solution Details – Types of Events SAP Supply Chain Event Management is capable of processing several different types of events. Within a given process, you have events that you expect to have happen and you have actual events that happen. You want to compare the actual event against what you expected. The first type of event is an event that you expect to happen within a particular time frame and it happens as expected. That is a regular event. A second type of event is an event that you expect to happen within a particular time frame and it happens outside the expected time frame. This is an overdue event. An overdue event can cause a subsequent event to be rescheduled, or it could just be recorded as an overdue event. A third type of event that could occur is one that is unexpected. This could be, for example, where you have a truck that breaks down or a malfunction in a piece of equipment – something that could potentially have an affect on subsequent events and something needs to be rescheduled or another action needs to be taken because of this unexpected event. An unexpected event could trigger an alert or other type of notification. The fourth type of event is an unreported event. In this case, you expect an event to occur within a particular time frame, but it for whatever reason, it is not reported. It is possible that something still needs to happen following this event so you could set a time limit that sends a message or causes something to happen when the event is unreported in a certain time period.
  • 19. Solution Details – Event Handler and an Event Handler Type Status Attribute Profile 19 Event Handler Event Handler Type Ruleset Expected Events Profile Expected Events Status Attributes Tracking ID’s Parameters The Event Handler Type describes what kind of application objects are represented by an Event Handler. In the Event Handler Type, you describe the ruleset, the status profile, the expected events profile and the authorization profile. The Event Handler Type controls which expected events are generated and the status attributes, tracking ID’s and any other parameters that correspond to those expected events.
  • 20. Event Handler Identification 20 Solution Details – Event Message Reporting Carrier reports Unloading ( Execution of PTA) Event Message Tracking ID CS = ‘PTA’ Tracking ID = ‘30000438’ Event Code = ‘UNLOADING’ Event Date = ’03.10.2008’ Event Time = ’13:14’ Event Timezone = ‘CET’ Event Handler EH Type ‘ODT10_HSH’ Tracking IDs HSH 000005330 PTA 10000218 PTA 20000232 PTA 30000438 … Expected Events - LOADING 01.10. 10:31 CET - DEPARTURE 01.10. 11:04 CET - ARRIVAL DEST 03.10. 12:17 CET - UNLOADING … Event Message Posting 03.10. 13:14 CET BAPI IDOC XI The Tracking ID of an Event Message determines, to which Event Handler the Message is reported. Event Handlers can carry multiple Tracking IDs. The Event Code describes the type of Event that is reported
  • 21. Solution Details – Structure of Event Messages in SAP EM The event message carries a tracking ID and event codes. This enables SAP EM to find the appropriate event handler and the expected event to check against its content. An event message is posted through a remote-enabled function module, possible through BAPI, IDOC and XI or Direct Call of the function module. 21 Event/Status Tracking ID Locations Partners Estimated Time Delivery Status Subseq. Status Load Transfer Meas. Result Text All event messages must be sent through the remote function module /SAPTRX/BAPI_EH_ADDEVENTMSG_02 (from SAP EM 4.0 on). The BAPI is based on this function module. The IDOC and XI also calls an RFC to SAP Event Management with this function module.
  • 22. 3r3drd P Paratryt yA Apppplicliactaitoionn SSAAPP B Buussinineessss S Suuitiete Event Handler 22 Solution Details – Architectural Landscape SAP EM SAP Business Warehouse OUTPUT CHANNELS Internet Mobile Device SAP Business Suite Internet, Applications Legacy Application Mobile Device Technical Devices (RFID, Scanners) SAP SAP CRM ... ERP Application Interface XI; BAPI; IDoc Event Handler Event Handler BAPI INPUT CHANNELS XI; BAPI; IDoc This architectural landscape slide is repeated here to indicate which parts of the landscape come into play for creating events. It is at this where the legacy or other SAP system determines wheter or not an event Handler is created, and so is then created in the Event Manager. Then within the Event Manager it is determined what will be the expected events and the timing of those events. At this point, multiple devices might be used or required to update the Event Manager. It is also possible for the Application System to provide the update to the Event Handler Now in the architectural landscape we look at what comes into play for retrieving events. This this point, multiple devices might be required to retrieve the status of an event handler. These devices might include a mobile device, a PDA or a web browser. It is also possible to retrieve messages directly from the EM or from the SAP system. At this point in the arctitectural landscape we are now concerned with what comes of the EM for triggering follow up activities to another SAP or Legacy system We are now looking at the system and data flow for monitoring and reporting. Analytical reporting occurs in the BW. Key Performance Indicators and Collaborative Performance Idicators are updated by activity in the event manager.
  • 23. 23 Agenda SAP Transportation Management & SAP Event Management „ Business Purpose „ Solution Overview SAP Event Management Details „ Solution Details „ Solution Configuration Application Interface
  • 24. Rule Set Structure Single- or multitask Activities and Functions are: „ Executed when an actual event is posted for an expected event „ Used for triggering activities like „ inform business partners „ trigger follow-up activities „ upload data to SAP Business Information Warehouse Depending on whether the rule condition evaluation returns a TRUE or FALSE, SAP EM calls the activities that have been defined for the respective condition. The rule activity consists of one (single-task) or many (multi-task) activities that trigger the follow-up action (for example sending an email). The rule activity itself might be an event handler method, a function module or a multi-task 24 activity. You can call several rule conditions within a rule by grouping several rule conditions in a set, which you call in the rule condition of the rule. You can call a BAPI within a function module and trigger activities in a remote system.
  • 25. Ruleset for Shipment Event Handler 25 Rule Condition Multitask Activity Branch Conditions Single task: Alert Creation
  • 26. SAP EM Application Interface additions in TM 26 Define Event Manager relevance
  • 27. Solution Configuration – Assigning an Alert Category in SAP EM You specify which alert category the system uses and how the container elements for this alert category are filled from SAP Event Management, in order to use the Alert Framework for notification in certain situations (for example, delay, contamination). You can specify different alert categories for different critical situations. You assign the alert category within a processing step of a rule in the rule set. You use the activity parameter ID, which you have specified in this IMG activity, as the key. You can maintain a hyperlink, which you attach, for example, at the end of an e-mail. You can use the template for Customizing and adapt it to your own requirements. EM IMG: SAP Customizing Implementation Guide Æ Event Management Æ Reactions to Event Messages Æ Define Alert Framework Connection Æ Define Alert Categories 27 Internet Mail SMS / Pager Fax Control Parameter e.g. e-mail address Container Elements: Variables used in the Alert Category
  • 28. Solution Configuration – Defining a Alert Container in SAP TM The alert container is a container for the exchange of (application-specific) variables, such as company code or material number, between the local systems (alert providers) and the central alert server. It is therefore the interface between the application that triggers the alert and the central Alert Framework. 28 Alert Category: SAP EM_ODT10_BLOCK General Settings Transaction: ALRTCATDEF
  • 29. Solution Configuration – Defining a Alert Container in SAP TM The alert container is a container for the exchange of (application-specific) variables, such as company code or material number, between the local systems (alert providers) and the central alert server. It is therefore the interface between the application that triggers the alert and the central Alert Framework. 29 Container Definition: Variables transferred from SAP Event Management
  • 30. Solution Configuration – Defining a Alert Container in SAP TM When you use application-specific variables in your container definition, you supply the values for these variables by writing them into the container as name-value pairs. These are then interpreted by the Alert Framework on the central system. The Alert Framework uses the alert container not only for the exchange of application-specific variables, but also for the exchange of internal information. 30 Short text and Long text: short text is sent via SMS and displayed in the alert-inbox Long text appears in the detailed view of the alert-inbox Optional: Define subsequent activities as hyperlinks/URLs
  • 31. 31 Agenda SAP Transportation Management & SAP Event Management „ Business Purpose „ Solution Overview SAP Event Management Details „ Solution Details „ Solution Configuration Application Interface
  • 32. Extracting Relevant Data From an SAP Appl. System SAP Event Management SAP Application System Shipment Tour Resource … Your business process first determines whether or not an Event Handler is created. As you are processing documents in your application system, there is a check to see if an event handler should be created for that particular function. Data is gathered in the Application System specific to that business process and configuration that you have defined to control the event process itself. Then, the event handler is created in SAP Event Management. 32 SAP Event Management „ expected events „ info parameters „ control parameters „ tracking / query IDs „ business object key Event Handler extract application data
  • 33. 33 Application Logs Event Management Application Object Type Business Object Parameters Mapping EH Type Log File Application System Status table /SAPTRX/AOTREF AOT AO-ID Main table MT Key Log ID The Application System and SAP EM log all activities that are done during processes. In the log you can check why e.g. Event Handlers are not created or which customizing setting is used.
  • 34. Application Logs – /SAPTRX/ASAPLOG Logs all activities you do during the creation/changing of Event Handlers. When you save the business object, it saves everything into a log and you can view this log for example, when an Event Handler isn’t created as you expect it to be. Logs exist in both SAP EM and AS. Log can be switched off in AS under SAPTRX/ASC0AO Æ General Data Æ Check box Appl. Log. Deactiv. 34
  • 35. 35 Configuration of Log Level Log EH Posting: Writes an application log for an event handler when posting updates from an application system. Log Msg. Proc: Writes an application log during event message processing. Log Ext. Update: Writes an application log for external updates (for example, BAPIs) and manual changes in transaction /SAPTRX/EH_LIST. You can choose the level of detail recorded in these logs.
  • 36. 36 Copyright 2009 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i,
  • Jatin

    Jul 23, 2017
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks