7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management http://slidepdf.com/reader/full/sap-event-management-scenarios-for-sap-transportation-management-56dbec1c5dbfb 1/45 (C) SAP AG Page 1 of 45SAP Event Management Scenarios for SAP Transportation Management A guide for administrators and consultantsRelease: SAP EM 9.0, SAP TM 9.0 Version: 1.3 PUBLIC Document Version: December 2013
45
Embed
SAP Event Management - Scenarios for SAP Transportation Management
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
SAP Library document classification: PUBLICNo part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior
notice.No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without priornotice.
Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems,
POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, SystemStorage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registeredtrademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari,Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World aretrademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, GoogleVoice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks ofGoogle Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of Business ObjectsSoftware Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein shouldbe construed as constituting an additional warranty.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
Table of ContentsRelated Documents ................................................................................................................................. 6
Related Notes .......................................................................................................................................... 6
Document History .................................................................................................................................... 6
IntroductionSAP Event Management 9.0 provides a set of visibility processes to monitor the execution of
transportation processes managed in SAP Transportation Management 9.0.
The present document is a detailed description of these visibility processes and the integration of SAP
Event Management 9.0 with SAP Transportation Management 9.0. It mainly aims at readers havingexpertise in SAP Event Management, who want to understand the principles and the detailed of
implementation of the Event Management content for SAP Transportation Management. Its focus is on
a concise and complete description of the EM features. In that regard it is supplementary to the TM
scenario guides, which (where applicable) show, how EM is used to monitor a given process.
The initial overview chapter may also address a broader public, who wants to learn the scope and the
main features of this content.
OverviewThe Content of SAP Event Management for SAP Transportation Management focuses on monitoring
the execution of the transportation processes. Consequently it refers to those business documents in
SAP TM that are execution relevant, i. e.
Freight Order
Freight Booking
Freight Unit
Instruction
The related visibility processes provided with SAP EM 9.0 are:
Shipper - Freight Order Visibility Process
Shipper - Freight Unit Visibility Process Shipper - Freight Booking Visibility Process
Consignee - Freight Order Visibility Process
Consignee - Freight Unit Visibility Process
Instruction Tracking Visibility Process
The related visibility processes provided with SAP EM 9.0 SP4 are:
Transportation Unit Visibility Process
Resource Tracking Visibility Process
For the details of the Resource Tracking and Transportation Unit Visibility process please see theseparate document SAP_TM_Resource_Tracking_for_EM.
Mutual Updates between freight units and freight orders or bookingsTo avoid redundant messaging or additional manual updates SAP TM supports mutual updates of
events that are implicitly relevant for both types of documents.
An “arrival” event received for the freight booking, for instance, implicitly means that all freight units
assigned to this booking at the point in time of the event are also arrived at the named location. Thisfeature has to be enabled explicitly in the customizing of the freight order/freight booking type (setting
“Propagate Execution Information” has to be checked).
Events that are reported for a freight unit will only be propagated to the related freight order/freight
booking when it has already been reported to all freight units that are assigned to the freight
order/freight booking, e.g. if the departure is reported on freight unit level, it will be automatically
propagated to the freight document when it has been reported for all freight units.
Special cases are here the events “Loading Begin” and “Unloading Begin”. These are already
propagated as soon as the first freight unit receives one of these events. “Loading End” and
“Unloading End” are again propagated only when it is reported for the “last” freight unit.
The following diagram shows, how the events are propagated between the different documents
(freight unit and freight order) and the different systems (in case propagation of execution information
is enabled for the freight order):
EM FU TM FU TM FO
EM FO
TM FO TM FU EM FU
EM FO
TM FU TM FO EM FO
EM FU
EM FO TM FO TM FU
EM FU
Option 1
Option 2 Option 4
Option 3
Event Type
Send Event Message
TM Update
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
1. Event message is reported in SAP EM for the freight unit SAP EM Rule set of freight unit event handler is set up to update TM Event is propagated to the freight unit in SAP TM Automatic propagation to related freight order in SAP TM is done The Event extractor of the freight order in SAP TM propagates the event to the freight
order in SAP EM
2. Event message is reported in SAP EM for the freight order SAP EM Rule set of freight order event handler is set up to update SAP TM Event is propagated to the freight order in TM Automatic propagation to related freight unit in SAP TM is done (if customizing in freight
order type is set to “Propagate Execution Info”) The Event extractor of the freight unit in SAP TM propagates the event to the freight unit
in SAP EM
3. Execution event is reported in SAP TM for the freight unit Automatic propagation to related freight order in SAP TM is done The Event extractor of the freight unit in SAP TM propagates the event to the freight unit
in SAP EM
The Event extractor of the freight order in SAP TM propagates the event to the freightorder in SAP EM
4. Execution event is reported in SAP TM for the freight order Automatic propagation to related freight unit in SAP TM is done (if customizing in freight
order type is set to “Propagate Execution Info”) The Event extractor of the freight order in SAP TM propagates the event to the freight
order in SAP EM The Event extractor of the freight unit in SAP TM propagates the event to the freight unit
in SAP EM
This propagation leads to a situation that the events are always propagated to all relevant documentsif the system is set up correctly:
Event extractors in SAP TM have to be active for the event types that shall be propagated toSAP EM
Freight orders/freight bookings in SAP TM have to be enabled in the type customizing topropagate the execution info
Rule sets in SAP EM have to be configured that events are propagated to SAP TM (activityfunction TM_MAINTAIN_EXEC_INF)
Updating data in TM triggered by new execution event
Standard updates of freight unit, freight order and freight booking
In the standard the updates are done in TM whenever a new execution event is created (e.g. when an
event message from SAP EM is propagated to SAP TM) according to the following rules.
Execution status updates:
Execution status is set to 09 (Loading in Process) when the first loading related execution
event is created (e.g. event code LOADING_BEGIN).
Execution status is set to 03 (In Execution) when the first execution event after the first loading
is created (e.g. event code DEPARTURE )
Execution status is set to 04 (Executed) when an execution event with a customizable event
code is created for the last stop of the freight document. The event code can be maintained in
the type customizing.
Because execution events have a direct impact on the TM execution status, they can also have animpact on the TM lifecycle status. The lifecycle status of a freight order, for which execution tracking is
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
Time References within SAP TM - EM IntegrationDate/TimeReference
Available Remarks
Actual Event Date TM | EM EM: Event Messages TabTM: Execution Tab
Actual Date when the Event has occurred. Do not mix up with EventReporting Date!
Planned Date TM | EM EM: Event Messages TabTM: Execution Tab
Planned date of an expected event.
Expected Event Date EM It’s the planned date of an event. The term Expected Event Date isonly used in EM for the planned dates of an event. This points to theDate when a certain event is planned (expected) to occur.
The Expected Event Date/Time can be found in table:/SAPTRX/EH_EXPEV
- EVENT_EXP_DATE (Date/Time the Event Is Expected toOccur)- MSG_EXP_DATE (Event Message Expected Date/Time)
Estimated Delay Date EM | TM EM: Send Delay Event
The estimated delay date is used in the EM-TM integration scenariosin the context of reporting a delay event.The estimated date is replicated to the TM system for the referencedevent e.g. a Delay Event was reported for the Loading Begin Event.In TM in the Delay Event details the referenced event Loading Beginis displayed with the new estimated date for this event. The actualplanned date for Loading Begin is not updated automatically.
The data related to the delay event (estimated time, date, time zone,delayed event and location) is stored as control parameter in EM(data of last reported delay) and it’s replicated to the TM system where the information is persisted in the EXECUTIONINFORMATIONBO node of the related freight order, freight booking or freight unit.
There is no standard usage of the estimated date/time for expectedevents. In EM-TM integration scenarios it is used for delay events toindicate the new estimated date/time for the related expected event.
The information about the last estimated delay date is stored in thefollowing control parameters:
- ODT20_ESTIM_DELAY_DATE
- ODT20_ESTIM_DELAY_TIME- ODT20_ESTIM_DELAY_TZONE
This information is not displayed in the standard UI but can be usedby customers to display additional information for the Event Handler.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
In SAP EM the planned and actual event dates are display. Again no planned dates for unexpected events are
available. Also in the standard UI no estimated dates are displayed.
Instruction Tracking
Expected Event
Event Event Code
Instruction Execution EXECUTION
Instruction tracking uses a single expected event to monitor the timely execution of the instructions.
For each instruction a separate event handler instance is created in EM. Instructions related to a
specific forwarding order or freight units can be listed by selecting the corresponding forwarding order
number or freight unit number v.v.. The works in the following way: When an instruction is created the
expected event time is set to the value of the “alert date” of the instruction. The alert date is a reminder
that the due date for executing the instruction is close. Once the alert is passed the expected event
date in the expected event EXECUTION is changed to the due date. The instruction status in EM canhave the values “pending”, “in progress”, “completed”, “alert”, “overdue”, and “completed after due
date”.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
The house bill of lading serves as a common reference to retrieve all the different, relevant
transportation documents belonging to a specific transportation case, in cases where a shipment in
planned in different TM system and by different organizations. Once those documents from the
different source organizations are collected in EM, selection by the bill of lading (or in some cases the
master bill of lading) provides complete visibility about all relevant documents. The following diagram
explains all options for navigation between the different business document types and related visibilityscenarios provided for transportation tracking:
Freight Booking – ODT30_TO
Tracking IDs:
TOR_TEC – TOR ID Freight Booking
BO – Booking
TRQ – TRQ ID
Control Parameter:
ODT30_CONTAINER_ID – Container ID
ODT30_MBL – Master Bill of Lading
ODT30_BL – Bill of Lading
Freight Order – ODT30_TO
Tracking IDs:
TOR_TEC – TOR ID Freight Order
TO – Tour
TRQ – TRQ ID
Control Parameter:
ODT30_CONTAINER_ID – Container ID (new)
ODT30_BL – Bill of Lading (new)
Freight Unit – ODT30_FU
Tracking IDs:
FU – Freight Unit
TRQ – TRQ ID
BO –
Booking
TO – Tour
Control Parameter:
ODT30_CONTAINER_ID – Container ID
ODT30_BL – Bill of Lading
CNTR_ODT20_ASSIGNED_FU
ODT20_FO_ID_IN_FU
CNTR_ODT20_ASSIGNED_FU
ODT20_BO_ID_IN_FU
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
Tracking Scenario Details: Freight Unit, Freight Order and Freight
Booking
Expected Events: Generation RulesThe following table provides an overview on how the EE in SAP EM are generated and how the EE
and Message Date is determined.
Freight Unit
Expected Event Sequence Generated from EE Date Event Message Date
SCHEDULED 90 SCHEDULED from Application System EE Date + 24h
LOAD_BEGIN 100 LOAD_BEGIN from Application System EE Date + 24h
LOAD_END 200 LOAD_END from Application System EE Date + 24h
DEPARTURE 300 DEPARTURE from Application System EE Date + 24h
ARRIV_DEST 400 ARRIV_DEST from Application System EE Date + 24h
UNLOAD_BEGIN 500 UNLOAD_BEGIN from Application System EE Date + 24h
UNLOAD_END 600 UNLOAD_END from Application System EE Date + 24h
Freight Order and Freight Booking
Expected Event Sequence Generated from EE Date Event Message Date
LOAD_BEGIN 100 LOAD_BEGIN from Application System EE Date + 24h
LOAD_END 200 LOAD_END from Application System EE Date + 24h
POPU 300 LOAD_END relative to Event with
same Location
(LOAD_END) + 2h
EE Date + 24h
DEPARTURE 400 DEPARTURE from Application System EE Date + 24h relative
to previous Event
(POPU)
CLEAR_CUSTOMS 500 CLEAR_CUSTO
MS
from Application System EE Date + 24h
ARRIV_DEST 600 ARRIV_DEST from Application System EE Date + 24h
UNLOAD_BEGIN 700 UNLOAD_BEGIN from Application System EE Date + 24h
UNLOAD_END 800 UNLOAD_END from Application System EE Date + 24h
POD 900 UNLOAD_END relative to Event with
same Location
(UNLOAD_END) + 2h
EE Date + 24h
NOTE:
If an EE is has a self-reference in the “Generated from” field that means that the information sent from
the Application System is used to create the EE in SAP EM. If e.g. “Generated from” is referring to
another Event, that means that in SAP EM an additional EE will be generated without having theinformation received from the Application system but using an existing event as reference EE
POPU/POD.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
Event DetailsThe following chapter provides a detailed overview on the existing Expected and Unexpected Events
which are supported in the SAP TM – SAP EM tracking scenarios for Freight Unit, Freight Oder and
Freight Booking.
- EE Relevance: what is the pre-requisite that an EE is considered to be sent to SAP EM- Expected Event Date/Time: Which date is assigned to the EE Date/Time for SAP EM
tracking of the corresponding event. This information is used in SAP EM for the overdue
monitoring and therefore the essential information for e.g. follow up activities and alerting if an
EE changes into status overdue
- SAP TM Event Message Trigger : At which point in time is the actual Event Message sent
from SAP TM to SAP EM
- SAP EM Rule Set: Configured Rules in SAP EM when receiving a specific Event Message –
in the corresponding rule set activities are defined which are executed if the Event Message is
processed
Freight Unit
Expected Events
ExpectedEvent
Condition
Scheduled EE Relevance:
- SAP TM Status – relevant for Expected Event Scheduled:- FU Execution Settings -> Execution Tracking or Execution Tracking with
external SAP Event Management- Execution Status in SAP TM is “not started” and not “ready for execution” - At least one Stop must have an assigned start date.
Expected Event Date/Time:
- Date from Requested Start Date of first stop is being used- Expected Event Date = Requested Start Date First Stop minus two days
SAP TM Event Message Trigger:
- The Schedule Event is only sent whenthe planning status has been changed from any other status except "NotPartially Planned" or "Not Ready for Planning" to "Planned"
SAP EM Rule Set:
-
Set Transportation Status to SCHEDULED (Scheduled)
Loading Begin EE Relevance:
- Stop Category = Outbound
Expected Event Date/Time:
- Assignment Start-Date of the corresponding Stop
SAP TM Event Message Trigger:
- Loading Begin Event is sent in case of Execution Information Event
“Loading Begin” status or information was changed- Event update was not initiated from SAP EM
SAP EM Rule Set:
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was reprocessed
Loading End EE Relevance:
- Stop category = outbound
Expected Event Date/Time:
- Assignment End-Date of the corresponding Stop
SAP TM Event Message Trigger:
- Loading End Event is sent in case of Execution Information Event“Loading End” status or information was changed
- Event update was not initiated from SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was reprocessed- Set Transportation Status to LOADED (Loaded)
- Set Transportation Status = ARRIVED (Arrived)- Update EE with Geo Data
UnloadingBegin
EE Relevance:
- Stop Category = inbound
Expected Event Date/Time:
- Assignment Start-Date of the corresponding Stop
SAP TM Event Message Trigger:
- Unloading Begin Event is sent in case of Execution Information Event“Unloading Begin” status or information was changed
- Event update was not initiated from SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was re-processed- Set Transportation Status to UNLOADED (Unloaded)
Unloading End EE Relevance:
- Stop Category = inbound
Expected Event Date/Time:
- Assignment End-Date of the corresponding Stop
SAP TM Event Message Trigger:
- The Unloading End Event is sent in case of Execution InformationUnloading End status or information was changed
- Event update was not initiated from SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was re-processed- Set Transportation Status to ARRIVED (Arrived)
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- SAP TM Execution information for the Loading Begin Event changed andthe Event Source was not SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
the Sender System was not SAP TM
Loading End EE Relevance:
- Stop Category = outbound
- Loading activity at this Stop
Expected Event Date/Time:
- Loading activity End Date/Time
SAP TM Event Message Trigger:
- SAP TM Execution information for the Loading End Event changed and theEvent Source was not SAP EM
SAP EM Rule Set:
- Set Transportation Status to LOADED (Loaded)- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
the Sender System was not SAP TM
Proof of Pickup EE Relevance:
- Proof of Delivery (POPU) Event is related to the Loading End Event fromSAP TM. The POPU Expected Event is generated in SAP EM based on theinformation sent with the Loading End Event. Without Loading End Eventno Expected Event for POPU is generated.
Expected Event Date/Time:
- Generated in EM from Loading End Expected Event Add 2h to ExpectedEvent Date/Time of Loading End.
SAP TM Event Message Trigger:
- LOADING_END Event as pre-requisite for POPU generation in SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
the Sender System was not SAP TM- Set Transportation Status to LOADING_CHECKED 'Loading Checked'
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- Planned Transportation Date/Time set on corresponding Stop
SAP TM Event Message Trigger:
- SAP TM Execution information for the Departure Event changed and theEvent Source was not SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed- Set Transportation Status to IN_TRANSIT (In Transit)
Clear Customs EE Relevance:
- Document is customs relevant
SAP TM Event Message Trigger:
- Clear Customs Event will not be reported out of SAP TM- Event reporting is expected e.g. via external Customs System
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
the Sender System was not SAP TM- Set Transportation Status to CUSTOMS_CLEARED_IMP (Customs
Cleared Import)
Arrival atDestination
EE Relevance:
- Stop Category = inbound
Expected Event Date/Time:
- Planned Transportation Date/Time set on corresponding Stop
SAP TM Event Message Trigger:
- SAP TM Execution information for the Arrival at Destination Event changedand the Event Source was not SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed- Set Transportation Status to ARRIVED (Arrived)
UnloadingBegin
EE Relevance:
- Stop Category = inbound
- Unloading activity at this Stop
Expected Event Date/Time:
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- SAP TM Execution information for the Unloading Begin Event changed and
the Event Source was not SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
Sender System was not SAP TM- Set Transportation Status to ARRIVED 'Arrived'
Unloading End EE Relevance:
- Stop Category = inbound - Unloading activity at this Stop
Expected Event Date/Time:
- Unloading activity End Date/Time
SAP TM Event Message Trigger:
- SAP TM Execution information for the Unloading End Event changed andthe Event Source was not SAP EM
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message
- Update Execution Information in SAP TM if EH was not re-processed and
Sender System was not SAP TM- Set Transportation Status to UNLOADED 'Unloaded'
Proof ofDelivery
EE Relevance:
- Proof of Delivery (POD) Event is related to the Unloading End Event fromSAP TM. The POD Expected Event is generated in SAP EM based on theinformation sent with the Unloading End Event. Without Unloading EndEvent no Expected Event for POD is generated.
Expected Event Date/Time:
- Generated in EM from Unloading End Expected Event Add 2h to
Expected Event Date/Time of the UNLOADING_END Event
SAP TM Event Message Trigger:
- SAP TM Execution information for the Unloading End Event changed andthe Event Source was SAP TM or change was propagated from successordocument
SAP EM Rule Set:
- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed and
the Sender System was not SAP TM- Set Transportation Status to DELIVERED (Delivered)
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- EVM Parameter Update- Update EH with Geo Data from the Event Message- Update Execution Information in SAP TM if EH was not re-processed- Create Alert- Set Delivery Status to DELAYED (Delayed)
Cancel EE Relevance:
- Document Lifecycle Status = cancelled or Document deleted in SAP TM
SAP TM Event Message Trigger:
- Document has been cancelled or deleted in SAP TM
SAP EM Rule Set:
- Set Transportation Status to CANCELLED (cancelled)- Deactivate EH EH deletion Flag is set in SAP EM
Block forExecution
Relevance:
- If an execution block on FO or BO exists the event is relevant in case it’s a
new block or one existing block reason has changed - Following Blocks are supported:
Block Reason CategoryEM Control ParameterReason Code
Execution Blocked by Air Cargo Security Check ODT30_BRC_ACS_CHK
Execution Blocked by Capacity Check ODT30_BRC_CAPA_CHECK
Execution Blocked by Compliance Check ODT30_BRC_COMPL_CHK
Execution Blocked by Customs Relevance Check ODT30_BRC_CUST_REL
Execution Blocked by Dangerous Goods Check ODT30_BRC_DG_CHECKFO
Execution Blocked by Discrepancy Report ODT30_BRC_DISCR_REP
Execution Blocked by Incompatibilities Check ODT30_BRC_INC_CHECK
Execution Blocked by Discrepancy Report ofPredecessor Document ODT30_BRC_PCS_DISCR
Execution Blocked by Execution Block ofPredecessor Document ODT30_BRC_PCS_DOC_E
Execution Blocked by Planning Block ofPredecessor Document ODT30_BRC_PCS_DOC_P
Execution Blocked by Manual Execution Block ODT30_BRC_MAN_EXEC
Execution Blocked by Manual Planning Block ODT30_BRC_MAN_PLAN
SAP TM Event Message Trigger:
- New Block on FU, FO or BO
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
The Enhancement of the Event Messages with the additional Parameter for the Geo Coordinates is
the prerequisite for the Geo Map Usage in SAP EM 9.0.
Expected EventsEvent Event Code SAP TM Event Type SAP TM 9.0 SP 2 Enhancement
LoadingBegin
LOAD_BEGIN ODT20_TO_LOAD_BEGIN Yes – TM & Web UI
LoadingEnd
LOAD_END ODT20_TO_LOAD_END Yes – TM & Web UI
Proof ofPickup
POPU ODT20_TO_POPU Yes
Departure DEPARTURE ODT20_TO_DEPART Yes
ClearCustoms
CLEAR_CUSTOMS
na Clear Customs is not supportedfrom SAP TM or via Web UI.
The Clear Customs EventMessage can be e.g. receivedfrom an external CustomsSystem. If the Geo Coordinatesare included the information isconsidered in SAP EM.
Arrival atDestination
ARRIV_DEST ODT20_TO_ARRIVAL Yes
UnloadingBegin
UNLOAD_BEGIN
ODT20_TO_UNL_BEGIN Yes – TM & Web UI
UnloadingEnd
UNLOAD_END ODT20_TO_UNL_END Yes – TM & Web UI
Proof ofDelivery
POD ODT20_TO_POD Yes – TM & Web UI
Unexpected Events
Event Event Code SAP TM Event Type SAP TM 9.0 SP 2 Enhancement
Damage DAMAGE na via Web UI
Delay DELAYED na via Web UI
DelayFreightUnit
DELAYED_FU na via Web UI
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- An Instruction is always relevant for SAP EM tracking if Due Date, Status
and Description are not initial and Instruction is of type “Task” (Type“Information” is ignored for SAP EM tracking)
EE Relevance and EE Date/Time:
- Due Date must be available in order to transmit an instruction record toSAP EM
- Each instruction sent to SAP EM will always has the EE “EXECUTION” - Depending if the Alert Date has been set which is before the Due Date
o Alert Date set: EE Date is set to the Alert Dateo Alert Date cannot be determined: EE Date is set to Due Date
NOTE: In SAP TM it’s not possible to set the Due and Alert Date before the currentDate. The Alert Date must always be equal to or before the Due Date.
SAP TM Event Message Trigger:
- New instruction has been created or the status for an existing Instructionhas been changed
SAP EM Rule Set:
- Event Message with Status PENDING, IN_PROGRESS will reset the EEExecution in SAP EM to indicate that a final status from SAP TM has notyet been reported – Status Attribute will be updated via Update Activity 2
- Event Messages which report the status ALERT will reset the EE Executionand update the EE Date/Time with the Instruction Due Date set in SAP TM(Status Alert should normally only be set in SAP EM in the overduemonitoring process)
- Event Messages reporting status COMPLETED andCOMPLETED_AFTER_DUEDATE will update the EE (reported EE Event).In case of status COMPLETED there will be an additional check if thecompletion date is before the Due Date – if this is not the case the systemwill also update the Status Attribute to COMPLETED_AFTER_DUEDATE.The Instruction Tracking process is at the moment only supported with SAPTM. If the status in SAP TM is set to COMPLETED the system checks
automatically if the Completion Date is before the Due Date and determinethe appropriate Completion status
NOTE: Only an Event Message reporting the status COMPLETED will change theEE Status to Reported EE.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
- Instruction EH with status parameter PENDING = 1 and IN_PROGRESS =2 will update the Status Attribute ODT30_INS_EXECUTION with the
appropriate Status value- For Instruction EH with status parameter COMPLETED = 3 the status
attribute value is set to COMPLETEDo There is an additional check if the Completion Date is after the Due
Date the status attribute value is set toCOMPLETED_AFTER_DUEDATE (Status Completed after DueDate should normally automatically determined in SAP TM)
- For Instruction EH with status parameterCOMPLETED_AFTER_DUEDATE = 6 the status attribute value is set toCOMPLETED_AFTER_DUEDATE
- For Instruction EH with status parameter ALERT = 4 the EH status attributeis set to ALERT and the EE Date/Time is set to the Instruction Due Datefrom SAP TM (Status Alert should normally only be set in SAP EM in the
overdue monitoring process)- For Instruction EH with status parameter OVERDUE = 5 the status attribute
value is set to OVERDUE (Status Overdue should normally only be set inSAP EM in the overdue monitoring process)
SAP EM Overdue Monitoring:
- Monitoring Activity is used for all EE with Event Code „EXECUTION” - If the EE Date is already set to the Instruction Due Date the Status Attribute
and the Instruction status in SAP TM is set to OVERDUE- If the EE Date was set to the Alert Date (Check will only be performed if EE
Date is not Due Date) the Instruction Status Attribute and the Instructionstatus in SAP TM is set to Alert. Afterwards the EE Date is updated with the
Instruction Due Date in the next run of the Overdue Monitor when theEE is captured the status will then set to Overdue
NOTE: Only in case the EE status changes to Overdue the status is set to OverdueEE.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
SAP Transportation Management Transportation Management Planning Freight Unit
Define Freight Unit Types
Overview Deletion and Deactivation in SAP EM
The following table describes the different process in SAP EM in regards of EH deactivation and soft
deletion depending on the customizing settings in SAP TM.
NOTE:
In case obsolete documents in SAP TM are canceled the above described customizing settings
determine if the document is being deleted physically or if only the lifecycle status is set to “canceled”.
SAP TM BasicSetting
DeletionSetting
SAP EM Behavior
Booking Can BeDeleted
No 1.) Rule Set: ODT30_TO_CANCEL
EH will be deactivated /SAPTRX/EH_HEADER-EH_ACTIVE = “ “
Freight Order CanBe Deleted
No 1.) Rule Set: ODT30_TO_CANCEL
EH will be deactivated
/SAPTRX/EH_HEADER-EH_ACTIVE = “ “
2.) EH Update Activity 2: ODT20_TO_UPDATE_ACT
Activity: TM_DELETE_FU_EH AO Type: ODT30_FUFU ID: <CNTRL-ODT20_FU_ID_TO_BE_DELETED>
Control Parameter “FU_ID_TO_BE_DELETED” is only set forFreight Orders “Direct Shipment Options”. The Control Parameter isused to determine the related Freight Units for deletion in SAP EM.
The Freight Unit in SAP TM will be converted into a Freight Order incase of a direct shipment option. The Freight Unit in SAP TM doesnot exist anymore and therefore the SAP EM EH for the Freight Unitmust be deleted when the new EH for the Freight Order is created inSAP EM.
EH will be deleted (Soft deletion) /SAPTRX/EH_HEADER-EH_DELETED = “X“
Freight Unit CanBe Deleted
No 1.) Rule Set: ODT30_FU_CANCEL
EH will be deactivated /SAPTRX/EH_HEADER-EH_ ACTIVE = “ “
Booking Can BeDeleted
Yes 1.) Deletion information is sent from SAP TM:
Function Module: /SAPTRX/BAPI_EH_POSTTable: APPLOBJECTS /SAPTRX/BAPI_APPLOBJ_IDENT-
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management
Examples of application objects are a shipment , delivery , handling unit of delivery , or equipment . The
application object type defines this character. You may, for example distingush between standard euro
pallets and special pallets for shipping larger items and define different application object types for it.
4. Last Exp. Event
Last Expected Event for Execution of a Document
Last expected event for a document, for example, the expected event Unload_End .
Use
If this expected event is sent from the destination stop of a document, the document is finished from
an execution perspective.
Dependencies
The system changes the execution status of the document to Executed .
Freight Booking: Settings for SAP EM
Execution Tracking:
1. Execution Tracking Relevance
Indicator for controlling the tracking of documents.
Use
If you want to track certain types of documents, choose 2 (Execution Tracking) or 3 (Execution
Tracking with External Event Management). The system then sets the initial document execution
status Not Started.
If you do not want to track certain types of documents, choose 1 (No Execution Tracking).The system
then sets the initial document execution status Not Relevant.
2. Propagate Execution Info
Propagate Execution Information to Predecessor Document
Indicates if an event that is reported for a freight order, a freight booking, or a transportation unit is tobe propagated to the predecessor documents.
Use
1.
3 .
4.
2.
7/21/2019 SAP Event Management - Scenarios for SAP Transportation Management