EM TM Integration with Expected Events on Container Level How the data code set and data ID can be used to distinguish between different expected events Author: Daniel Härder Document Date: 31.01.2013
TABLE OF CONTENTS SUMMARY... 3 TECHNICAL PREREQUISITES... 3 CONFIGURATION IN SAP TM... 3 New Application Object Type... 3 New expected event extractor for FCL freight unit... 3 Freight Unit Type Customizing... 5 Freight Order and Freight Booking Type Customizing... 6 Enhance Execution Tab on UI... 6 CONFIGURATION IN SAP EM... 8 New Event Handler Type... 8 Create new EH Type Condition Function... 8 Create new Expected Event Profile... 10 Create new EH Type... 11 Parameter Mapping... 12 New User Profile... 12 New Selection Profile... 13 New Display Profile... 14 New Event Message Profile... 15 New User Profile... 17 TECHNICAL DETAILS... 17 Usage of Data Code Set and Data ID... 17 Propagation Mode for Data Code Set and Data ID in TM... 17 Propagation to successor documents... 18 Propagation to predecessor documents... 18 UI SCREEN SHOTS... 18 TM UI... 18 EM UI... 19 2
SUMMARY This document gives an overview of the configuration that is needed to enhance the standard FCL freight unit tracking scenario for EM TM integration to have expected events on container level. It is then possible to report expected events like LOADING_BEGIN on container level and not only on freight unit level (like in the standard scenario). There are customizing settings on both sides (TM and EM) needed. Additionally new function modules have to be created for the extraction of the expected events for the freight unit (in TM) and the condition to find the desired EH Type (in EM). In general the same approach can be used to have expected events on a more detailed level than freight unit or freight order level (also others than container level). TECHNICAL PREREQUISITES The described scenario can be set-up based on SAP EM 9.0 SP01 and TM 9.0 SP04 (+ note 1814280). If your systems are not already on this SP level, you can alternatively implement note 1797503 in SAP EM 9.0 and notes 1797506, 1804112, 1811642 and 1814280 in SAP TM 9.0. CONFIGURATION IN SAP TM New Application Object Type Create new application object type for business process type TMS_TOR as copy of ODT30_FU (transaction /SAPTRX/ASC0AO). New expected event extractor has to be assigned (see next step). New expected event extractor for FCL freight unit Create new expected event extractor as copy of ODT20_FU. The new function module should be created as copy of FM /SCMTMS/EXTR_EE_FU. In the coding the item data has to be retrieved additionally to have the container information. For all expected events that shall be on container level the fields DATACS (fixed value, e.g. CONTID) and DATAID (= container ID) have to be populated and one entry in table E_EXPEVENTDATA has to be created per container ID as shown in the screen shots below. 3
4
Freight Unit Type Customizing The execution propagation mode of the freight unit type has to be set to Enhanced Propagation and the application object type has to be set to the new one. 5
Freight Order and Freight Booking Type Customizing The execution propagation modes of freight order type and freight booking type have also to be set to Enhanced Propagation. Enhance Execution Tab on UI To display the container ID for the expected events on the execution tab on the freight unit UI a web dynpro component customizing has to be created. This can be done with the web dynpro application CUSTOMIZE_COMPONENT. The field DATAID, which is already available in the field catalog, can be added as new UI element. The header can then be changed to Container ID. 6
7
CONFIGURATION IN SAP EM New Event Handler Type For the new EH type a new EH type condition function and a new expected event profile is needed. Create new EH Type Condition Function Create new entry for EH Type Condition Function as shown in the following screenshots. 8
9
Create new Expected Event Profile Copy existing expected event profile ODT20_FU (transaction /SAPTRX/TSC0EE). For the profile items for the event codes LOAD_BEGIN, LOAD_END, DEPARTURE, ARRIV_DEST, UNLOAD_BEGIN, UNLOAD_END unmark the checkboxes Do Not Set for Data Function and Do Not Check for Check Data. This is shown for LOAD_BEGIN in the screen shot below. 10
Create new EH Type A new EH Type has to be created in EM (transaction /SAPTRX/TSC0TT). Copy existing EH Type ODT30_FU and change the condition and the expected event profile to the ones you created. 11
Parameter Mapping Create new entry for the new application object type for the parameter mapping (transaction /SAPTRX/TSC0PDM). The new application object type has been defined in TM. New User Profile A new user profile has to be created to display the freight unit event handlers on the EM Web UI. The user profile can be created as copy of existing user profile ODT30_SHIPPER_FU (transaction /SAPTRX/UCUP). 12
New Selection Profile The new selection profile can be created as copy of existing selection profile ODT30_SHIPPER_FU. Configured field ODT30_EH_TYPE_FU has to be replaced with a new configured field, that selects the new EH Type (can be created in transaction /SAPTRX/UCCF). 13
New Display Profile The new display profile can be created as copy of existing display profile ODT30_SHIPPER_FU. The event display details should be enhanced with new configured field to display the container ID. 14
New Event Message Profile The new event message profile can be created as copy of existing event message profile ODT30_SHIPPER_FU. In the event reporting details for the event codes LOAD_BEGIN, LOAD_END, UNLOAD_BEGIN, UNLOAD_END two additional configured fields have to be assigned. One is to submit the data code set and the other one to allow the entry of the data code ID (which is used for the container ID) on the UI. 15
16
New User Profile Assign the new profiles to your new user profile. TECHNICAL DETAILS Usage of Data Code Set and Data ID The fields for data code set and data ID are used to distinguish between the same expected events for different container of one freight unit. The combination of event code, location and data code set and data ID is unique for an expected event. Propagation Mode for Data Code Set and Data ID in TM 17
Let s assume we have two freight units with two containers each assigned to an ocean freight booking. Therefore we have two expected events for the LOADING_END on the port of loading location for each container one. This is true as well for all the other expected events of the freight units which were extracted on container level (See section New expected event extractor for FCL freight unit ). The new event propagation mode Enhanced Propagation that is available in the TOR Type customizing works as follows: Propagation to successor documents If an expected event (e.g. LOADING_END at the port of loading) for one container of one of the freight units has been reported, no propagation of the event is done to the ocean freight booking. The propagation of the LOADING_END event to the freight booking is only done, at the time it has been reported for all four containers of the two freight units. Propagation to predecessor documents If an expected event (e.g. DEPARTURE at the port of loading) has been reported for the ocean freight booking, the event is immediately propagated to all four containers of the two assigned freight units. UI SCREEN SHOTS TM UI 18
EM UI 19
20
www.sap.com 2013 SAP AG. All rights reserved. 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 their respective 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 mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks 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 and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.