SAP EM How to Display the Planned Route on the Geo-Map

Transcription

1 SAP EM How to Display the Planned Route on the Geo-Map Author: Marco Freischlag Document Date:

2 TABLE OF CONTENTS SUMMARY... 3 PREREQUISITE:... 3 SOLUTION:... 3 SAMPLE Coding:... 3 GEO-MAP DISPLAY:... 6

3 SUMMARY The Standard EM Geo-Map functionality works at the moment only for reported events (event message parameter) and event handler parameter which is described in the following document Depending on the various uses cases it might be interesting to be able to see the planned route on the Geo- Map. The planned route is derived from the expected events that have not been reported yet. Using the expected event location it s possible to retrieve the geographical data (longitude and latitude) from any connected system in which location master data are maintained. PREREQUISITE: The visibility scenario is enabled for the Geo-Map usage SOLUTION: BAdI /SAPTRX/BADI_EH_S: Create or modify BAdI Implementation The Interface method which is called for displaying the event handler and event message data on the UI /SAPTRX/IF_EX_BADI_EH_S~AFTER_GET_DATA_DISP must be implemented SAMPLE Coding: METHOD /saptrx/if_ex_badi_eh_s~after_get_data_disp. DATA: ls_eh_expev TYPE /saptrx/eh_expev, lt_eh_expev TYPE TABLE OF /saptrx/eh_expev, ls_eh_status TYPE /saptrx/bapi_eh_disp_status, lv_timestamp TYPE timestamp, lv_tzone TYPE ttzz-tzone, lv_date TYPE d, lv_time TYPE t, lv_index LIKE sy-tabix. FIELD-SYMBOLS: <fs_eh_header_ext> <fs_eh_header> TYPE LINE OF /saptrx/bapi_eh_hdrext_tab, TYPE /saptrx/bapi_eh_disp_hdr. DATA: lr_consolidatedevents TYPE REF TO /saptrx/bapi_eh_consolidate, lt_geo_loc TYPE zmf_tt_geo_loc, ls_geo_loc TYPE zmf_s_geo_loc, ls_geo_loc TYPE lty_geo_loc, lv_evt_guid TYPE /saptrx/ev_guid, lv_ao_system TYPE /saptrx/appsyst. LOOP AT eh_headers ASSIGNING <fs_eh_header> WHERE bus_proc_type = 'TMS_TOR' AND ao_type = 'Z_TEST'. CHECK consolidatedevents IS NOT INITIAL. * for now take first AO system to lookup geo data for locations IF sy-tabix = 1. lv_ao_system = <fs_eh_header>-ao_system. ENDIF. * Check for Consolidated Events for which no Evt Msg has been received LOOP AT consolidatedevents REFERENCE INTO lr_consolidatedevents WHERE evt_guid IS INITIAL AND eh_guid = <fs_eh_header>-eh_guid. APPEND lr_consolidatedevents->location_id_part1 TO lt_geo_loc. CHECK lt_geo_loc IS NOT INITIAL. SORT lt_geo_loc BY locid ASCENDING. DELETE ADJACENT DUPLICATES FROM lt_geo_loc. * Check function is exsit or not. CALL FUNCTION 'FUNCTION_EXISTS' 3

4 * funcname = /saptrx/if_odt30_constants=>co_em_geo_loc_func funcname = 'ZMF_GET_LOC_GEODATA' EXCEPTIONS function_not_exist = 1 OTHERS = 2. CHECK sy-subrc = 0. * for each location id read geo data from source sap tm system * CALL FUNCTION /saptrx/if_odt30_constants=>co_em_geo_loc_func CALL FUNCTION 'ZMF_GET_LOC_GEODATA' iv_ao_system = lv_ao_system CHANGING ct_geo_loc = lt_geo_loc. IF lt_geo_loc IS NOT INITIAL. * temporarily assign longitude and latutude value * to consolidated events in oder to display the planned route LOOP AT consolidatedevents REFERENCE INTO lr_consolidatedevents WHERE evt_guid IS INITIAL AND eh_guid = <fs_eh_header>-eh_guid. READ TABLE lt_geo_loc INTO ls_geo_loc WITH KEY locid = lr_consolidatedevents->location_id_part1. CALL FUNCTION 'SYSTEM_UUID_C22_CREATE' IMPORTING uuid_c22 = lv_evt_guid. lr_consolidatedevents->evt_guid ls_evm_hdrext-evt_guid ls_evm_hdrext-ext_field_name ls_evm_hdrext-ext_field_value = lv_evt_guid. = lv_evt_guid. = 'RES30_LONGITUDE'. = ls_geo_loc-longitude. APPEND ls_evm_hdrext TO evmheaderextension. ls_evm_hdrext-evt_guid ls_evm_hdrext-ext_field_name ls_evm_hdrext-ext_field_value = lv_evt_guid. = 'RES30_LATITUDE'. = ls_geo_loc-latitude. ENDIF. APPEND ls_evm_hdrext TO evmheaderextension. ENDMETHOD. "/SAPTRX/IF_EX_BADI_EH_S~AFTER_GET_DATA_DISP FUNCTION zmf_get_loc_geodata. *"*"Local Interface: *" IMPORTING *" REFERENCE(IV_AO_SYSTEM) TYPE /SAPTRX/APPSYST *" CHANGING *" REFERENCE(CT_GEO_LOC) TYPE ZMF_TT_GEO_LOC DATA: lv_queue_name ls_appsyst TYPE trfcqnam, TYPE /saptrx/appsyst. SELECT SINGLE * FROM /saptrx/appsyst INTO ls_appsyst WHERE app_system_id = iv_ao_system. CHECK sy-subrc = 0. lv_queue_name = 'EM_LOC_GEO'. CALL FUNCTION 'TRFC_SET_QUEUE_NAME' "#EC * qname = lv_queue_name EXCEPTIONS invalid_queue_name = 1 OTHERS = 2. * CALL FUNCTION /saptrx/if_odt30_constants=>co_tm_geo_loc_func CALL FUNCTION 'ZMF_GET_TM_LOC_GEODATA' DESTINATION ls_appsyst-rfcdest 4

5 CHANGING ct_geo_loc = ct_geo_loc. ENDFUNCTION. Sample Implementation of RFC Module in SAP TM: FUNCTION zmf_get_tm_loc_geodata. *"*"Local Interface: *" CHANGING *" VALUE(CT_GEO_LOC) TYPE ZMF_TT_GEO_LOC DATA: lv_loc_key lr_em_geo_loc lt_locid ls_geo_loc ls_loc_geo lt_loc_geo ls_loc_root lt_loc_root TYPE /bobf/conf_key, TYPE REF TO zmf_geo_loc, TYPE /scmtms/t_loc_alt_id, TYPE /scmtms/s_bo_loc_geoinfo_k, TYPE /scmtms/s_bo_loc_geoinfo_k, TYPE /scmtms/t_bo_loc_geoinfo_k, TYPE /scmtms/s_bo_loc_root_k, TYPE /scmtms/t_bo_loc_root_k. LOOP AT ct_geo_loc REFERENCE INTO lr_em_geo_loc. APPEND lr_em_geo_loc->locid TO lt_locid. IF lt_locid IS NOT INITIAL. * Get Location descriptions & geo information CALL METHOD /scmtms/cl_pln_bo_data=>get_loc_data it_loc_id = lt_locid CHANGING ct_loc_root = lt_loc_root ct_loc_geo = lt_loc_geo. ENDIF. LOOP AT ct_geo_loc REFERENCE INTO lr_em_geo_loc. CLEAR: ls_loc_root, ls_loc_geo. READ TABLE lt_loc_root INTO ls_loc_root WITH KEY location_id = lr_em_geo_loc->locid TRANSPORTING root_key. READ TABLE lt_loc_geo INTO ls_loc_geo WITH KEY root_key = ls_loc_root-root_key TRANSPORTING longitude_value latitude_value. lr_em_geo_loc->longitude lr_em_geo_loc->latitude = ls_loc_geo-longitude_value. = ls_loc_geo-latitude_value. CONDENSE lr_em_geo_loc->longitude. CONDENSE lr_em_geo_loc->latitude. ENDFUNCTION. 5

6 GEO-MAP DISPLAY: The route for the reported expected event is displayed in blue. The planned route is displayed in purple with an open padlock as display icon. 6

7 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, 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..