Setting up Visual Enterprise Integration (WM6)

Transcription

1 SAP Mobile Platform 3.0 June 2015 English Setting up Visual Enterprise Integration (WM6) Building Block Configuration Guide SAP SE Dietmar-Hopp-Allee Walldorf Germany

2 Copyright 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SAP SE Page 2 of 8

3 Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP SE Page 3 of 8

4 Content 1 Purpose Release Limitations Prerequisites Work Manager 6.2 Mobile Application Configuration Client Global Configuration Mobile Data Object (MDO) Configuration Work Order Document Attachment Configuration Notification Document Attachment Configuration Restart Agentry Server (Deployed on SMP) Adding the VE Viewer Control to the Agentry WPF Client... 8 SAP SE Page 4 of 8

5 Setting up Visual Enterprise Integration: Configuration Guide 1 Purpose The purpose of this document is to describe the general configuration steps required for the integration of SAP s 3D Visual Enterprise Viewer (VE) with SAP Work Manager 6.2.It should be noted SAP Mobile Platform 3.0 and the SAP Work Manager 6.2 mobile application can be configured to support the display of native VE files (type CGM or VDS); the mobile application is not intended to be used for the creation/maintenance of such files. Further, no VE files are delivered as part of the SMP3.0/WM6.2 solution. Finally, support for the VE Viewer in the Work Manager mobile application is limited to tablet-type mobile devices and excludes Smart Phones. 2 Release Limitations It should be noted support for native viewing of VE files in the WM6.2 Mobile Application is limited to files attached to Work Orders and/or Notifications using the Generic Object Services (GOS) SAP Document Management Technology. 3 Prerequisites It is assumed the customer will have procured the needed SAP VE software licenses required for the use of the VE Viewer with SAP Work Manager 6.2. Additionally, it is the customer s responsibility for the creation and maintenance of the native VE files to be displayed in the mobile application. Finally, it is also the customer s responsibility to have attached the VE files to the appropriate Work Orders and/or Notifications in the SAP ERP back-end system as a prerequisite for their display in the mobile application. Before you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for SAP Work Manager rapiddeployment solution. You can find this document in the content library, attached to the Stepby-Step Guide. This building block is configured by the configuration panel user created by the system administrator. SAP Work Manager rapid-deployment solution supports two flavor of the Work Manager 6.1 application: 1. Base Work Manager 6.2 without LAM (Linear Asset Management) and Inspection Rounds 2. Work Manager 6.2 with LAM (Linear Asset Management) and Inspection Rounds. Integration of the SAP Work Manager 6.2 mobile application with the SAP VE Viewer is supported in both Work Manager 6.2 application flavors. 4 Work Manager 6.2 Mobile Application Configuration 4.1 Client Global Configuration Use SAP SE Page 5 of 8

6 In this activity, you change the default mobile application configuration criteria for enablement of VE Viewer integration. Procedure 1. Logon to the SAP ERP back-end system with your user id and password 2. Access the SAP Work Manager Mobile Application Configuration Panel using the following SAP transaction or navigation path: Transaction Code IMG Menu /n/syclo/configpanel SAP Customizing Implementation Guide -> Agentry SAP Framework Configuration -> System Settings -> Define Mobile Applications 3. On the home page, go to Mobile Application Configuration. In the Defined Mobile Applications section, choose SAP_WORK_MANAGER_ Choose the Client Globals tab and choose Change. 5. In the Client Global List table, in column Global Group enter VE in the empty row. Choose Filter icon on the left. 6. Choose the Global Name PREF_VE_ENABLED. 7. In the Client Global Detail section, modify the value of the field Client Global Value: to TRUE. By default the value is set to FALSE. 8. Choose Save. You are prompted for the transport request and choose Continue after specifying the transport request. 4.2 Mobile Data Object (MDO) Configuration Use In this activity, you validate the OOB Mobile Application Document Management configuration to ensure support for Generic Object Services (GOS) is active for both Work Orders and Notifications Work Order Document Attachment Configuration This section is applicable only if the customer has attached native VE files to Work Orders in their SAP ERP system using Generic Object Services and wish to view these files on a mobile device. Otherwise, this configuration section can be skipped. Procedure 1. On the home page, go to Mobile Data Object Configuration. Set the Mobile Application Filter to SAP Work Manager with LAM or SAP Work Manager depending on the application flavor activated in your system. 2. Expand DO Standard Data Object and choose SWM62_WORKORDER_GENERIC. 3. Go to Data Object Detail (Display Mode), Choose Change. 4. Navigate to Data Filter tab. 5. Under Data Object Filter Rule Definition, expand the GET method and expand the Data Segment section. 6. Choose the filter DOC_GOS_ACTIVE and ensure that the Low Value is set to True as shown below. Field Name Field Value SAP SE Page 6 of 8

7 Field Name Sign Field Value Inclusive Option = Low Value True 7. Choose Save. You are prompted for the transport request. Choose Continue after specifying the transport request Notification Document Attachment Configuration This section is applicable only if the customer has attached native VE files to Notifications in their SAP ERP system using Generic Object Services and wish to view these files on a mobile device. Otherwise, this configuration section can be skipped. Procedure 1. On the home page, go to Mobile Data Object Configuration. Set the Mobile Application Filter to SAP Work Manager with LAM or SAP Work Manager depending on the application flavor activated in your system. 2. Expand DO Standard Data Object and choose SWM62_NOTIFICATION_GENERIC. 3. Go to Data Object Detail (Display Mode), Choose Change. 4. Navigate to Data Filter tab. 5. Under Data Object Filter Rule Definition, expand the GET method and expand the Data Segment section. 6. Choose the filter DOC_GOS_ACTIVE and ensure that the Low Value is set to True as shown below. Field Name Sign Field Value Inclusive Option = Low Value True 7. Choose Save. You are prompted for the transport request. Choose Continue after specifying the transport request. 4.3 Restart Agentry Server (Deployed on SMP) After the completing the mobile application configuration changes, it is recommended to stop the Agentry server (which is deployed on SAP Mobile Platform) and start it again. Contact your System Administrator to execute this step. SAP SE Page 7 of 8

8 5 Adding the VE Viewer Control to the Agentry WPF Client Use The default, Work Manager 6.2 WPF Agentry client does not support the display of native VE file types (VDS and CGM). Therefore, this section of the configuration guide for integration of the VE Viewer, defines the steps required to add the VE Viewer Control to the WPF Agentry client. Procedure 1. Download and install the latest Agentry WPF Client on the Windows device 2. Download and install the latest Work Manager Mobile Apps OpenUI SDK bundle 3. Copy the VE relevant contents for WPF from the Mobile Apps OpenUI SDK bundle into the folder where the Agentry WPF Client is installed (where the AgentryClient.exe is located). This includes the VEClientControls.dll file from the VE folder in the OpenUI SDK bundle as well as the CustomControls folder and AgentryClientCommon.dll file from the Common folder in the OpenUI SDK bundle. 4. Download and unzip the latest SAP Visual Enterprise Applications SDK from SAP SCN. ( 5. Copy the VE DLLs to the folder where the Agentry WPF Client is installed. The following four specific VE DLL files are required: DVL_x64.dll DVL_Win32.dll SAP.VE.DVL.dll SAP.VE.DVL.Interop.dll 6. Start the Agentry WPF Client The Rapid Deployment Solution explains the steps for Agentry WPF Client. However, they can be leveraged to a greater extent for Agentry ios or Android client with some additional efforts. SAP SE Page 8 of 8