How-To - Enhance Visibility Processes for GeoMap Usage

How-To - Enhance Visibility Processes for GeoMap Usage Applies to: SAP Event Management 9.0 Summary This document is not an official SAP publication...
Author: Arnold Sharp
1 downloads 1 Views 2MB Size
How-To - Enhance Visibility Processes for GeoMap Usage

Applies to: SAP Event Management 9.0

Summary This document is not an official SAP publication. It provides information on one possible solution of how to enhance an existing visibility process for SAP EM 9.0 to track and trace objects on a Geo Map. Author:

Marco Freischlag

Company: SAP AG Created on: 12 December 2012

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 1

How-To - Enhance Visibility Processes for GeoMap Usage

Table of Contents Introduction ......................................................................................................................................................... 3 1

Pre-requisite Map Integration in SAP EM .............................................................................................. 5 1.1

Visual Business 2.0 Runtime installation ............................................................................................... 5 New Event Handler Parameter – Multiple EH Display .......................................................................... 8

2 2.1

Define Control Parameters .................................................................................................................... 8

2.2

Define Parameter Mapping .................................................................................................................... 9

2.3

Configure Fields for User Profiles .......................................................................................................... 9

2.3.1

Configure Fields for Display ........................................................................................................................... 9

Adding new Event Message Parameter – Single EH Display ............................................................. 10

3 3.1

EVM Header Extension ....................................................................................................................... 10

3.1.1

Extension Table ........................................................................................................................................... 10

3.2

Define Event Message Parameters ..................................................................................................... 11

3.3

Define Parameter Mapping for Event Messages ................................................................................. 11

3.4

Configure Fields for User Profiles ........................................................................................................ 12

3.4.1

Configure Fields for Display ......................................................................................................................... 12

3.4.2

Configure Fields for Event Messages .......................................................................................................... 12

3.5

Define User Profiles ............................................................................................................................. 14

3.5.1

Event Display Details ................................................................................................................................... 14

3.5.2

Event Reporting Details ............................................................................................................................... 14

3.5.3

Event Confirmation Details ........................................................................................................................... 16

4

Extend SAP EM User Profile with GeoMap Profile ............................................................................. 18 4.1

Maintain geomap profile ...................................................................................................................... 18

4.2

Assign Geomap Profile to User Profile ................................................................................................ 21

5

EH Type Customizing .......................................................................................................................... 22 5.1

6

Rule Set – Update EH Geo Data ......................................................................................................... 23 Additional Information .......................................................................................................................... 30

6.1

Event Message for multiple Event Handler ......................................................................................... 30

Copyright........................................................................................................................................................... 31

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 2

How-To - Enhance Visibility Processes for GeoMap Usage

Introduction With SAP EM 9.0 SAP has introduced the functionality to display the geographical data which is either related to an Event Handler (EH) or to an Event Message (EVM) on a map which is integrated into SAP EM. The following two use cases are implemented with SAP EM 9.0: -

Display a Single Event Handler: When displaying a single EH on the map only the geographical data of the select EH is displayed. Geographical data is normally sent via Event Messages which is then used for visualization. Each Event Message enriched with geographical data sorted by actual event date is displayed on the map  Latitude and Longitude information is retrieved from the EVM (Events with invalid or no geographical information will not be displayed on the map)

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 3

How-To - Enhance Visibility Processes for GeoMap Usage

-

Display multiple Event Handler If more than one EH is selected from the search results only the latest position of the EH is displayed on the map.  Latitude and Longitude information is retrieved from the EH (EH with invalid or no geographical information will not be displayed on the map)

The basis for using the map functionality within SAP EM is SAP Visual Business. SAP Visual Business is an interactive user interface (UI) technology that enables users to visualize data  both SAP and non-SAP data from various sources on a single screen. SAP Visual Business is a toolbox that allows the rapid building of interactive graphics. SAP Visual Business graphically displays any combination of content in various ways, including as a geographic information system (GIS), a 3D model, or in the form of analytics. The visual relationship to reality allows users to navigate intuitively through business data, manipulating the level of detail in which the information is displayed by zooming in or out. SAP Visual Business was first released with SAP Transportation Management 8.0. Using the Solution with SAP Transportation Management allows logistics processes to be visualized on a map and provides an alternative starting point for transportation planning and optimization

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 4

How-To - Enhance Visibility Processes for GeoMap Usage

1

Pre-requisite Map Integration in SAP EM

1.1

Visual Business 2.0 Runtime installation

Download SAP Visual Business from the SAP Support Portal  http://service.sap.com/support  SAP Software Download Center  Installation and Upgrades  A – Z Index  “V” SAP VISUAL BUSINESS  SAP VISUAL BUSINESS 2.0

Don't forget to set the checkbox. Unfortunately the SAP Frontend Installer does not inform you in case nothing is selected.

ACF White-list certificate installation For each system you need to install an ACF white-list certificate on your local PC: Run transaction WDR_ACF_WLIST and Press 'Install Certificate' from the toolbar.

In case the ACF white-list certificate is not installed, the Transportation Network looks like this:

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 5

How-To - Enhance Visibility Processes for GeoMap Usage

In case the ACF white-list certificate is not available in your system, you can create it manually:

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 6

How-To - Enhance Visibility Processes for GeoMap Usage

ACF Whitelist Certificate Generation (for admins) Currently the ACF whitelist certificate has to be generated manually in each system once by the adminsitrator (transport connection is in progress). So in case the above described ACF white-list installation transaction does not show a Visual Business certificate, execute the following action: Run transaction WDR_ACF_GEN_CERT, select "Generate New Certificate" and press "Execute" (F8). A transport request may be needed for the certificate generation, depending on your system setup.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 7

How-To - Enhance Visibility Processes for GeoMap Usage

2

New Event Handler Parameter – Multiple EH Display

The geographical information will normally be received via EVM in SAP EM. Therefore to show the latest position of an EH on the map this information has to be updated on the EH level. The following parameters are used for multiple EH display:

Parameter Name

Parameter Type

Comment

RES30_GEO_ACT_DATETIME

Control Parameter

Latest Actual Event Time Stamp of the EH – only events which take place after the latest

one

received

will

update

the

geographical data of the EH to update the latest position RES30_EH_LONGITUDE

Control Parameter

Latest Longitude position of the EH – must be referenced in the User Profile  Geomap Maintenance  Longitude EH Param.

RES30_EH_LATITUDE

Control Parameter

Latest Latitude position of the EH – must be referenced in the User Profile  Geomap Maintenance  Latitude EH Param.

EVTTST (SAP EM Standard

Event Message Parameter

Parameter)

Actual Event Time Stamp is used to determine if the event received has to update the Longitude/Latitude on EH level

2.1

Define Control Parameters

Event Management  Event Handlers and Event Handler Data  Parameters  Define Control, Info, and Rule Processing Parameters

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 8

How-To - Enhance Visibility Processes for GeoMap Usage

2.2

Define Parameter Mapping

Not required  the geographical Information is sent via EVM therefore the update of the EH Longitude and Latitude is done in the Rule Set. If these parameters can also be updated via EH update the parameter mapping would be required. 2.3

Configure Fields for User Profiles

Event Management  Event Messages, Status Queries, and Web Interface  Web Interface  Configure Fields for User Profiles 2.3.1

Configure Fields for Display

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 9

How-To - Enhance Visibility Processes for GeoMap Usage

3

Adding new Event Message Parameter – Single EH Display

3.1

EVM Header Extension

Event Management  Event Messages, Status Queries, and Web Interface  Event Message Parameters  Define Extension Table for Event Message Header

Enter a new entry if no extension table for your scenario exists. Enter the extension table which should be created and save the entry. 3.1.1

Extension Table

Extend your extension table for Event Messages  add new fields for the Longitude and Latitude value.

Note: The Longitude and Latitude fields must be referenced in the User Profile  Geomap Maintenance  Lon. EVM Param. and Lat. EVM Param.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 10

How-To - Enhance Visibility Processes for GeoMap Usage

3.2

Define Event Message Parameters

Event Management  Event Messages, Status Queries, and Web Interface  Event Message Parameters  Define Event Message Parameters

Create new parameters for Longitude and Latitude and select the previously created fields from the Event Message header extension table. 3.3

Define Parameter Mapping for Event Messages

Event Management  Event Messages, Status Queries, and Web Interface  Event Message Parameters  Define Parameter Mapping for Event Messages

Cerate or extend the mapping profile for the event message parameters.

Map the Application System Parameter to the Event Message Parameter in SAP EM.

Assign the Mapping Profile and Extension Table to corresponding Tracking ID for which it should be used.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 11

How-To - Enhance Visibility Processes for GeoMap Usage

3.4

Configure Fields for User Profiles

Event Management  Event Messages, Status Queries, and Web Interface  Web Interface  Configure Fields for User Profiles 3.4.1

Configure Fields for Display

Note: Configured Field for Event Messages required with the same Name as created for Configured Fields for Display. Used for Event Display Details.

3.4.2

Configure Fields for Event Messages

These are the fields the Longitude and Latitude information on Event Message level is mapped to.

Configured Field

EM Attribute ID

Display Mode

RES30_EVM_LATITUDE

PARAMETER VALUE

Write

RES30_EVM_LONGITUDE

PARAMETER VALUE

Write

Default Value

Note: Configured Field for Event Messages required with the same Name as created for Configured Fields for Display. Used for Event Confirmation Details.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 12

How-To - Enhance Visibility Processes for GeoMap Usage

These fields will be used when reporting an Event Message via WebUI.

Configured Field

EM Attribute ID

Display Mode

Default Value

LATITUDE_ACT

PARAMETER ACTION

Hidden

M

LATITUDE_NAME

PARAMETER NAME

Hidden

LATITUDE

LATITUDE_TYPE

PARAMETER TYPE

Hidden

LATITUDE_VAL

PARAMETER VALUE

Write

LONGITUDE_ACT

PARAMETER ACTION

Hidden

M

LONGITUDE_NAME

PARAMETER NAME

Hidden

LONGITUDE

LONGITUDE _TYPE

PARAMETER TYPE

Hidden

LONGITUDE_VAL

PARAMETER VALUE

Write

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 13

How-To - Enhance Visibility Processes for GeoMap Usage

3.5

Define User Profiles

Event Management  Event Messages, Status Queries, and Web Interface  Web Interface  Define User Profiles 3.5.1

Event Display Details

3.5.2

Event Reporting Details

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 14

How-To - Enhance Visibility Processes for GeoMap Usage

Note: Latitude and Longitude Parameters must be grouped via “Row Number”  for each Event Message Parameter assign a different row number.

Note: In the Mapping Profile the Parameter will be mapped to RES30_EVM_LONGITUDE / RES30_EVM_LATITUDE used for the Event Display Details.

PARAM_NAME  Default Value of the Configured Fields LONGITUDE_VALUE and LATITUDE_VALUE

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 15

How-To - Enhance Visibility Processes for GeoMap Usage

3.5.3

Event Confirmation Details

Note: When reporting Events via “Report All Expected Events” the Parameters in the Event Confirmation Details Customizing must have the same Name as used in the Display Profile  Event Display Details. Therefore the Configure Fields for Display and Configure Fields for Event Messages have been created with the same name. Latitude and Longitude Parameters must be grouped via “Row Number”  for each Event Message Parameter assign a different row number

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 16

How-To - Enhance Visibility Processes for GeoMap Usage

Note: In the Mapping Profile the Parameter will be mapped to RES30_EVM_LONGITUDE / RES30_EVM_LATITUDE used for the Event Display Details.

PARAM_NAME  Default Value of the Configured Fields LONGITUDE_VALUE and LATITUDE_VALUE

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 17

How-To - Enhance Visibility Processes for GeoMap Usage

4

Extend SAP EM User Profile with GeoMap Profile

4.1

Maintain geomap profile

-

Choose Geomap Profile  New Entries

-

Specify a name for the Geomap profile, a description and a configured field. The configured field is used in the map as a caption for the corresponding map spot

-

Save the entries

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 18

How-To - Enhance Visibility Processes for GeoMap Usage

-

Choose the Geomap profiles created in the previous step, then select Geomap Event Handler Details, and New Entries.  These settings are required for displaying a multiple EH on the map (EH Parameter)

-

Select the configured fields which should be displayed as tooltip or in the quick info window

-

Specify the display level on the selection screen. There are three choices - Tooltip, QuickInfo or Both o o

Tool Seq. sets the Tooltip sequence - the order in which the tooltips are listed on the ma Win. Seq. sets the Quick Info Window sequence

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 19

How-To - Enhance Visibility Processes for GeoMap Usage

-

Choose the Geomap profiles created in the previous step, then select Geomap Event Message Details, and New Entries  These settings are required for displaying single EH on the map (EVM Parameter)

-

Save the entries

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 20

How-To - Enhance Visibility Processes for GeoMap Usage

4.2

Assign Geomap Profile to User Profile

-

Choose the User Profile to be extended with the Geomap Profile

-

Select Geomap Maintenance and New Entries

-

Choose the EvtHandler Type which should be displayed using the Geomap Profile

-

Choose a Map Object Role which is used to display the EH on the map

-

Choose the Parameter Type in which geographical information is stored

-

Choose a Latitude EH Parameter - this specifies the latitude on EH level – refer to New Event Handler Parameter – Multiple EH Display

-

Choose a Longitude EH Parameter - this specifies the longitude on EH level – refer to New Event Handler Parameter – Multiple EH Display

-

Select a Geomap profile created

-

Select Latitude EV Param to specify the event message header extension field that holds the latitude information of the received event message – refer to EVM Header Extension

-

Select Longitude EV Param to specify the event message header extension field that holds the longitude information of the received event message – refer to EVM Header Extension

-

Save your entries

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 21

How-To - Enhance Visibility Processes for GeoMap Usage

5

EH Type Customizing

Event Management  Event Handlers and Event Handler Data  Event Handlers  Define Event Handler Types

Adjust or create the Rule Set to create and update the geographical data.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 22

How-To - Enhance Visibility Processes for GeoMap Usage

5.1

Rule Set – Update EH Geo Data

Sample Processing Logic:

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 23

How-To - Enhance Visibility Processes for GeoMap Usage

1. Check if the Longitude value is populated

2. If Longitude is provided - Check if the Latitude value is populated

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 24

How-To - Enhance Visibility Processes for GeoMap Usage

3. Geographical Data is provided - Check if Event Date is after last Event Date which updated the EH Parameter

= Event UTC TimeStamp  for the date and time fields use a “!” within the parameter name to store the date/time information in raw format. This is required for the comparison of the timestamps.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 25

How-To - Enhance Visibility Processes for GeoMap Usage

4. IF return value is not true – check if the relevant parameter is still initial

5. IF Parameter are initial – Create Parameter

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 26

How-To - Enhance Visibility Processes for GeoMap Usage

6. IF Parameter are initial – Create Parameter

7. IF Parameter are initial – Create Parameter

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 27

How-To - Enhance Visibility Processes for GeoMap Usage

8. IF Event date is after latest Update Event date – change Parameter value

9. IF Event date is after latest Update Event date – change Parameter value

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 28

How-To - Enhance Visibility Processes for GeoMap Usage

10. IF Event date is after latest Update Event date – change Parameter value

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 29

How-To - Enhance Visibility Processes for GeoMap Usage

6

Additional Information

6.1

Event Message for multiple Event Handler

When receiving Event Messages for Resource Tracking from SAP TM the Event Message can have more than one Tracking ID e.g. multiple Container assigned to a BO. Only one Event Message will be sent from SAP TM but must update several EH in SAP EM. In the Extraction Function Module for the respective Events the TRXID will be set to a dummy value. The relevant Tracking IDs will be appended to table CT_TRACKREFERENCES.

Sample Coding: IF lt_res_tu_root IS NOT INITIAL. LOOP AT lt_res_tu_root ASSIGNING . " Tracking ID Code Set 'RES_ID' ls_trackingheader-trxcod = /scmtms/cl_scem_int_c=>sc_trackid_codesets-resource. " Tracking ID – RES " Event Message relevant for multiple Event Handler -> multiple TURES_IDs " Fill trackreferences with all relevant tracking IDs ls_trackingheader-trxid = 'dummy'. CLEAR ls_trackreferences. ls_trackreferences-evtcnt = gv_evtcnt. ls_trackreferences-refcod = /scmtms/cl_scem_int_c=>sc_trackid_codesets-resource. ls_trackreferences-refid = -tures_id. APPEND ls_trackreferences TO ct_trackreferences. ENDLOOP. ENDIF.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 30

How-To - Enhance Visibility Processes for GeoMap Usage

Copyright © Copyright 2012 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, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 S.A. in the United States and in other countries. Business Objects 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.

SAP COMMUNITY NETWORK © 2012 SAP AG

scn.sap.com 31