sap inventory manager configuration guide

CUSTOMER

SAP Inventory ManagerDocument Version: 4.3.2 – 2018-04-26

SAP Inventory Manager Configuration Guide

Content

1 SAP Inventory Manager Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 SAP Inventory Manager Functionality Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 SAP Inventory Manager on the SAP Mobile Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Setting Up the SAP Mobile Platform Server to Support Multiple Languages. . . . . . . . . . . . . . . . . . . . . . .81.5 Multiple Country Support for Address and Phone Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2 Mobile Add-On for ERP Configuration Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.1 Accessing the Mobile Add-On for ERP ConfigPanel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 ConfigPanel Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Standard Operations in the Configuration Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Mobile Add-On Configuration Panel Functional Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1 ConfigPanel - Mobile Application Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2 ConfigPanel - Geospatial Service Definitions Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 ConfigPanel - oData Channel Integration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 ConfigPanel - Change Detection Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

ConfigPanel - EFI Assignment Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29ConfigPanel - Exchange Object Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5 ConfigPanel - Inbound Transaction Queue Definition Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.6 ConfigPanel - Data Staging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Data Agent Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Data Store Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.7 RFC Channel Integration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Mobile Data Object Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45BAPI Wrapper Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.8 Push Framework Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Push Scenario Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Outbound Trigger Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Subscription Agent Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

3.9 ConfigPanel - Technical Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.10 ConfigPanel - Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4 Mobile Add-On for ERP for SAP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .604.1 Accessing Administrative Functions in SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2 Mobile Add-On for ERP Push Instance Purge Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.3 Mobile Add-On for ERP Data Cache Purge Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .624.4 Mobile Add-On for ERP Generic Purge Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

2 C U S T O M E RSAP Inventory Manager Configuration Guide

Content

4.5 Mobile Add-On Exchange Table Purge Utility Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4.6 Mobile Add-On Log Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.7 Mobile Add-On Log Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

4.8 Enable SAP Solution Manager to Diagnose Agentry Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5 Mobile Add-On for ERP Administration Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.1 Mobile Add-On for ERP Administration Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.2 Accessing the Administration and Monitoring Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5.3 Administration Portal - Mobile Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Mobile Solution Overview - Operation Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.4 Administration Portal - Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Administration - User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Administration - Server Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Administration - Runtime Logging Level Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Administration - Parameter Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.5 Administration Portal - Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Administration Portal - Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

User Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Push Instance Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Communication Session Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Object Mobile Status Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

5.6 Sending Email Using the Administration & Monitoring Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

5.7 Administration Portal - Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Retrieving and Recalculating Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Statistics - Communication Session Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Statistics - Application BAPI Wrapper Call Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Statistics - Push Scenario Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

6 Agentry Application Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256.1 Global Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

7 Common Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297.1 Activating the Warehouse Management Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

7.2 Disabling an Old Version of the SAP Inventory Manager Application. . . . . . . . . . . . . . . . . . . . . . . . . . .129

7.3 Disabling the Material Master UOM View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7.4 Enabling Data Staging for Materials Complex Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7.5 Assigning Responsible Locations to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

8 Data Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358.1 SAP ERP Transaction Codes for SAP Inventory Manager Components. . . . . . . . . . . . . . . . . . . . . . . . . 137

9 Using the Mobile Application Comparison Report Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

SAP Inventory Manager Configuration GuideContent C U S T O M E R 3

Document History

Before you begin reading this guide, be sure that you have the latest version. Find the latest version at https://help.sap.com/viewer/product/SAP_Inventory_Manager/latest/en-US.

The following table provides an overview of the most important document changes.

Version Date Description

4.3.2 MAR 2018 Original release


Document History

https://help.sap.com/viewer/product/SAP_Inventory_Manager/latest/en-US

https://help.sap.com/viewer/product/SAP_Inventory_Manager/latest/en-US

1 SAP Inventory Manager Overview

1.1 Before You Begin

This document is intended for system administrators, technical architects, and IT personnel involved in the installation, setup, and configuration of software for the SAP Inventory Manager application. It is assumed that the personnel performing the installation and setup are aware of SAP installation. SAP setup knowledge is helpful while carrying out the steps for the mobile setup of SAP.

This document is intended to be used along with appropriate SAP documentation and covers only setting up and enabling the SAP Inventory Manager mobile application.

1.2 SAP Inventory Manager Functionality Overview

SAP Inventory Manager is a complete wireless inventory management solution. It provides the tools to improve and manage inventory levels, efficiently fill customer orders, and track the movement of materials using mobile devices with scanning functionality. The mobile application accesses the SAP Enterprise Asset Management (EAM) solution and empowers you to provide your technicians and warehouse management staff with the ability to execute stockroom operations in an automated and seamless way. The ease of operation ensures that you keep your valuable parts and spares under control and ready to respond.

The Mobile Add-On for ERP extends the following functionality to a mobile device:

● Physical Inventory Count: Physical counts of materials are recorded using Mobile Add-On for ERP on a mobile device are applied to the SAP database without the need for data entry.

● Materials Movement: A material movement is a change in stock such as an issue, transfer, or a return. SAP Inventory Manager extends the issues and transfers recording functionality of SAP to a mobile device. Movement in stock can be recorded directly as it occurs using SAP Inventory Manager. These changes are applied to the SAP database without the need for data entry.

● Materials Receipt: A material receipt is an increase in stock. For example, when the receipt of materials from a vendor or production is posted. SAP Inventory Manager extends the material receipt functionality of SAP to a mobile device. The receipt of materials can be recorded to the SAP database without the need for data entry.

● Check availability of materials while on the job● Accept and distribute incoming materials by purchase order● Prepick materials based on work orders● Speed receipt and back-order reporting to and from shipping and receiving

SAP Inventory Manager Configuration GuideSAP Inventory Manager Overview C U S T O M E R 5

1.3 SAP Inventory Manager on the SAP Mobile Platform

SAP Inventory Manager is deployed on the SAP Mobile Platform as an Agentry application. The application is built with the Agentry Toolkit within the SAP EAM and service mobile app SDK.

NoteFor detailed information on the Agentry Toolkit and the SAP EAM and service mobile app SDK, see Agentry App Development.

There are numerous components to the Agentry Toolkit, including the following:

● Runtime environment● Agentry Editor● Agentry client● Agentry test environment (ATE)● Development server (optional installation)

General overview information on each of these components is provided in this topic. For information the components, including usage, configuration, and other technical details, see the documentation provided with the SAP Mobile Platform and SDK.

Runtime Environment

The runtime environment is a production server system. Within this component, you can define one or more applications of different archetypes. An archetype refers to the different types of mobile applications, including the development paradigms, under which mobile applications are developed and deployed. The SAP Inventory Manager application is developed and deployed under the Agentry archetype. Therefore, it requires the definition of an Agentry application within the runtime environment into which it is deployed. You can modify the application by configuring options within the administration interface, the SAP Mobile Platform Cockpit.

Additionally, you can develop changes to out-of-the-box behavior of the application by using components of the Agentry toolkit within the SAP EAM and service mobile SDK.

SAP Mobile Platform Server

The server is provided within the SAP EAM and service mobile app SDK. It provides the same runtime functionality as the Agentry server component within the SAP mobile runtime environment. It is provided in the Agentry toolkit to allow you to install the server without the need to install the entire runtime environment for development work. The development server is not intended for production use.


SAP Inventory Manager Overview

https://help.sap.com/doc/d9c75eebcfa840c8a4aa4b0e6a8136de/latest/en-US/7c1c8bd1700610148278be00e002816b.html


Agentry Editor Plug-in to Eclipse

The Agentry Editor plug-in to Eclipse provides a 4GL, point-and-click interface that allows developers to modify the SAP Inventory Manager application. The Agentry Editor is provided in the SAP EAM and service mobile app SDK as a part of the Agentry toolkit. Agentry applications are stored within the Agentry Editor in the Eclipse workspace as Agentry application projects.

Both the Agentry application project and the Java packages and projects are all managed within a single Eclipse workspace. The developer is presented with a single IDE in which the mobile application as a whole can be maintained and modified. See the document Agentry App Development in the SAP Mobile Platform documentation for details on working within this toolset.

SAP Inventory Manager Client

The SAP Inventory Manager client is provided for each of the client device types supported by the SAP Inventory Manager application. An installer for the SAP Inventory Manager client build is provided for Windows operating systems. For devices running iOS, the application is installed from the App store, or from your Apple Enterprise Server site. For Android devices, the .apk file is provided. You can install the .apk file from a Web server by navigating to its location within the local network of your environment.

The SAP Inventory Manager client is an executable run on the client device by the end user. The overall architecture of the Agentry toolkit allows for the development of a single application project, which can be deployed on multiple device types. The client processes the business logic developed in the Agentry Editor and is deployed to the runtime environment. The client displays the user interface according to the native operating system of the device on which the SAP Inventory Manager is running.

The Agentry Test Environment

The Agentry Test Environment (ATE) is among the development tools provided in the Agentry Toolkit within theSAP EAM and service mobile app SDK. It is a highly useful tool for developers during the development cycle used for testing the client-side behavior and functionality of your mobile application. It includes numerous debugging and inspection tools to provide insight into the data, action execution, rule evaluation, and other aspects of the behavior of the client at runtime.

The ATE is not an emulator. However, it does posses the capability to mimic the behavior of all the supported client device types. Within the ATE is a full Agentry client. Part of the features of the ATE is the ability to select from a list of supported client platforms from within the Agentry archetype development paradigm. Once you select a platform, the Agentry client tells the SAP Inventory Manager server that it is a client of that type. The client then receives the user interface components for that platform.



1.4 Setting Up the SAP Mobile Platform Server to Support Multiple Languages

Context

English is the default language for SAP Inventory Manager, so you do not need to do anything for English.

The language pack .zip file for SAP Inventory Manager is named SAPInventoryMgr432LanguagePacks.zip.

Procedure

1. Unzip all of the translated .ini files to the directory where you installed the SAP Mobile Platform server.

2. Edit the agentry.ini file.

a. In the Configuration section, add the following line if it does not exist:

"localizations="

b. After the equal ( = ) sign, add the languages used in your application (English is the default language, so you do not need to add it). For example, to add German and Spanish, type localizations=de;es;.

NoteIt is recommended that you add only required languages:○ ar - Arabic○ cs - Czech○ de - German○ es - Spanish○ fr - French○ he - Hebrew○ hu - Hungarian○ it - Italian○ ja - Japanese○ ko - Korean○ pl - Polish○ pt - Portuguese○ ro - Romanian○ ru - Russian○ sh - Serbian○ sk - Slovakian○ sv - Swedish○ tr - Turkish○ zh-CN - Simplified Chinese



Results

All languages that you defined in the Localizations line of the Configuration section are supported on the SAP Mobile Platform server.

1.5 Multiple Country Support for Address and Phone Formats

Address Format

You can view, add, or edit addresses based on country specifications. SAP ERP sets up and globally controls the default country format for the application.

SAP Inventory Manager automatically adapts address layouts to country-specific formats, based on the selected country chosen. Depending on your selection, for instance, you may enable a State dropdown or a Province dropdown. For example, Spain uses Province while the United States uses State. Having a country specification enables your users to select a province from the address dropdown if Spain is the selected country, whereas the dropdown contains states if the United States is the selected country.

Address and Phone Formats List

The supported countries and their printed address formats and phone formats include:

Country Printed Address Format Phone Number Format

Argentina (AR) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

REGION

COUNTRY

N/A - the phone number is displayed without formatting

Austria (AT) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Australia (AU) HOUSE_NO STREET

LOCATION

CITY REGION POSTL_COD1

COUNTRY

04xx xxx xxx

0x xxxx xxxx



Belgium (BE) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Brazil (BR) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY REGIO

COUNTRY

0 (xx) xxxx-xxxx

Canada (CA) HOUSE_NO STREET

LOCATION


COUNTRY

xxx-xxx-xxxx

Switzerland (CH) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY

0800 xxx xxx

0900 xxx xxx

0xx xxx xx xx

China (CN) HOUSE_NO STREET

LOCATION

POSTL_COD1 CITY REGION

COUNTRY


Germany (DE) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Denmark (DK) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY

xx xx xx xx

Spain (ES) STREET HOUSE_NO

LOCATION


COUNTRY

06xx xxx xxx

0xxx xx xx xx




France (FR) HOUSE_NO STREET

LOCATION

POSTL_COD1 CITY

COUNTRY

0 8xx xxx xxx

0x xx xx xx xx

Greece (GR) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Hong Kong (HK) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

REGION

COUNTRY


Hungary (HU) POSTL_COD1 CITY

STREET HOUSE_NO

LOCATION

COUNTRY

06 1 xxx-xxxx

06 xx xxx-xxx

Italy (IT) STREET HOUSE_NO

LOCATION


COUNTRY


Japan (JP) POSTL_COD1

REGION CITY

STREET HOUSE_NO

LOCATION

COUNTRY


South Korea (KR) POSTAL_COD1

COUNTRY

REGION CITY

STREET HOUSE_NO

LOCATION




Luxembourg (LU) HOUSE_NO STREET

LOCATION

POSTL_COD1 CITY

COUNTRY

6x1 xxx xxx

40 xxxx

42 xxxx

43 xxxx

45 xxxx

47 xxxx

48 xxxx

49 xxxx

4 xxx xx

xxxx xxxx

xx xxxx

Mexico (MX) STREET HOUSE_NO

LOCATION


COUNTRY


Netherlands (NL) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Norway (NO) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY

4xx xx xxx

9xx xx xxx

xx xx xx xx

New Zealand (NZ) HOUSE_NO STREET

LOCATION

REGION

CITY POSTL_COD1

COUNTRY


Portugal (PT) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY





Sweden (SE) STREET HOUSE_NO

LOCATION

POSTL_COD1 CITY

COUNTRY


Singapore (AR) HOUSE_NO STREET

LOCATION

CITY POSTL_COD1

COUNTRY


United Kingdom (UK) HOUSE_NO STREET

LOCATION

CITY

REGION

POSTL_COD1

COUNTRY

See the following table for UK phone number formats

USA (US) HOUSE_NO STREET

LOCATION


COUNTRY

(xxx) xxx-xxxx

The following are the phone number formats for the UK:

0800 xxxx (015395) xxxxx (01xxx) xxxxxx

0845 46 4x (015396) xxxxx (02x) xxxx xxxx

(016977) 2xxx (016973) xxxxx 03xx xxx xxxx

(016977) 3xxx (016974) xxxxx 055 xxxx xxxx

(01xxx) xxxxx (016977) xxxxx 056 xxxx xxxx

0500 xxxxxx (017683) xxxxx 070 xxxx xxxx

0800 xxxxxx (017684) xxxxx 076 xxxx xxxx

(013873) xxxxx (017687) xxxxx 07xxx xxxxxx

(015242) xxxxx (019467) xxxxx 08xx xxx xxxx

(015394) xxxxx (011x) xxx xxxx 09xx xxx xxxx

(01xxx) xxxxxx


2 Mobile Add-On for ERP Configuration Panel

2.1 Accessing the Mobile Add-On for ERP ConfigPanel

Context

Use the following procedure to access the Configuration Panel, also known as the ConfigPanel.

Procedure

1. Log into SAP.2. Type the command /n/syclo/configpanel into the command box and click the green check mark or click Enter.

A Web page opens with the Agentry SAP Framework Configuration page, or ConfigPanel, for the Mobile Add-On for ERP.


Mobile Add-On for ERP Configuration Panel

2.2 ConfigPanel Overview

All configuration activities for the Mobile Add-On for ERPare performed through the ConfigPanel.

Changes you make through the ConfigPanel can significantly impact the behavior of the Mobile Add-On for ERP and the SAP Inventory Manager application. Make and test changes in a development environment first before migrating them to the rest of the SAP system landscape.

The following screenshot shows the home page of the ConfigPanel:

2.2.1 Standard Operations in the Configuration Panel

While each mobile application is unique, certain buttons in the Configuration Panel are standard and are available for all applications.

Filtering by Mobile Application

If more than one mobile application is available on the same system, you can use the filter function to only view items for a specific application. Find the filter option on any page where multiple applications are displayed.

To filter by application, click the arrow to the right of the Defined Mobile Applications field and select the appropriate mobile application. To remove the selection and view all items for all mobile applications on the system, click in the field again and select the asterisk ( * ) symbol.

SAP Inventory Manager Configuration GuideMobile Add-On for ERP Configuration Panel C U S T O M E R 15

Creating, Copying, Deleting, and Changing Items

The following standard actions are available to configure different components and items within your mobile application setup:

● Create: Creates a new item. All modifiable fields are empty.● Copy: Copies the item that was highlighted and creates a new item. Information fills in all modifiable fields

from the existing item. You can change that information before saving.● Delete: Deletes the highlighted item.● Change: Allows you to change the highlighted item in the modifiable fields.

Saving or Canceling Changes for an Item

Once you click the Create, Copy, or Change button, the Save and Cancel buttons display. After you change the configuration of the item, click Save to save the changes or Cancel to discard the changes.

NoteIf the Save and Cancel buttons are active, the Home link for the ConfigPanel is not available. Either save your changes or cancel out of the changes to return to the main Configuration Panel page

Message List

Certain actions can generate system messages. These messages can be error messages or informational messages. If you perform an action that prompts a system message, a message bar appears above the main panel with a brief description of the message.

Click the Show List button to display the detailed view of the message list.


Mobile Add-On for ERP Configuration Panel

3 Mobile Add-On Configuration Panel Functional Overview

3.1 ConfigPanel - Mobile Application Configuration SettingsThe Mobile Application Configuration page allows you to configure general settings for the entire mobile application.

Use the Mobile Application Configuration page to set general settings for the entire SAP Inventory Manager mobile application.

The Mobile Application Configuration screen is comprised of the following tabs:

● General● Mobile Status Setting● Conversion Exit Setting● System Components● Parameters● Client Globals● User Attributes

General Tab

Use the General tab to create or change basic information about a mobile application.

SAP Inventory Manager Configuration GuideMobile Add-On Configuration Panel Functional Overview C U S T O M E R 17

● Basic Data fields:○ Mobile Application: For this required field, enter the name of the mobile application, limited to 40

characters.○ Description: For this required field, enter a brief, easy to understand description of the mobile application,

limited to 60 characters.○ Release: Release number of the mobile application○ Type: Type of application

● User Management Setting:Disable Automatic User Creation: When checked, a new user GUID is not automatically created when a new mobile client is detected in the system. The system administrator must manually create and maintain mobile users through the Administration portal.

● Server Management Setting:Disable Automatic Server Registration: When checked, a new server GUID is not automatically created when a new server is detected in the system. The system administrator must manually create and maintain servers through the Administration Portal.

● Life-cycle management fields:○ Application Blocked: If set (checked), this mobile application is disabled. The mobile user can no longer

connect to the back-end system for this mobile application. The xchange process is also disabled for this mobile application.

○ Effective Date and Time: The date and time this block flag takes effect.● Inbound Transaction Management fields:

○ Inbound Transaction Active: If set (checked), you enable inbound transaction management on the back end.

○ Standard Inbound Queue ID: If you are using asynchronous inbound transaction, you can select one queue as the primary queue from the <Standard Inbound Queue ID> dropdown. Selecting a primary queue means that all transactions have the same properties and are used for simple mappings. However, out of the box, the selection dropdown is blank. Further customization is needed in the object type assignment of the primary type queue for BAPI wrapper settings, cross references, key mappings, and other settings not detailed in this guide.

● Multi Back End Setting fields:○ Multi Back End Enabled: When checked, enables a specific mobile application to connect to multiple SAP

systems, consisting of one host server and one or more satellite servers.○ System Role: Dropdown menu listing Host or Satellite.

A host system is the connection between SAP and the Agentry application in the SAP Mobile Platform server. The host server provides the logic to the Agentry application and functions as a bridge to the satellite servers. There can only be one host server per system.Satellite servers communicate with SAP through the host server.To complete multi back end enabled configuration, configure the host and satellite servers on the System Components tab.

Mobile Status Setting Tab

Use the Mobile Status Setting tab to map the available mobile statuses that a mobile data object (MDO) supports on the client side. If a user status also exists for the same object type, you can link it to the mobile status and the system status through this tab.


Mobile Add-On Configuration Panel Functional Overview

● Mobile Application Info fields:○ Mobile Application: (Read Only) The name of the mobile application○ Mobile Application Description: (Read Only) A brief, easy to understand description of the mobile

application○ Release: (Read Only) The release number of the mobile application

● Mobile Status Mapping fields:○ Add Status button: Click Add Status to create a new mobile status mapping.○ Delete Status button: Click Delete Status to delete an existing mobile status mapping. To delete a mobile

mapping status, click the rectangle to the left of the Object Type column in the row you want to delete and click Delete.

○ Object Type: Object type from the Mobile Status Detail section○ Mobile Status: Mobile status from the Mobile Status Detail section○ System Status: System status from the Mobile Status Detail section○ User Status: User status from the Mobile Status Detail section

● Mobile Status Details fields:○ Object Type: The specific object in a mobile application, ex., NOTIFICATION○ Mobile Status: Status defined by the mobile application○ Label on Mobile: Not used○ System Status: Standard SAP status code○ User Status: SAP user status code as defined in SAP (note that the status code should be language-

independent codes)○ Mobile Status Alias List: Language-specific mobile status aliases can be defined

In the following example screen, the highlighted row in the mapping table indicates that if a user sets a work order to completed, the application sets the work order system status to 10072 in SAP.


If there is no system status or user status, the mobile status only affects the mobile device and does not affect the backend SAP system.

If there is a user status specified but no status profile when the mobile user sets the mobile status, the app sets that user status for the object, disregarding the status profile of that object.

If there is a user status and status profile specified when the mobile user sets the mobile status, the app sets that user status if the object uses that status profile.

Conversion Exit Setting Tab

A conversion exit is a function module that converts a value from an external format to an internal, SAP format. A conversion exit can also convert an internal SAP value to a readable, external, value, that is then displayed on a mobile device. However, you may want to completely exclude some conversion routines from your mobile application altogether. Configure those specific conversion exit settings using the Conversion Exit Setting tab.





● Conversion Exit List fields:○ Add button: Click Add to create a new conversion exit detail. Fill in the fields in the Conversion Exit Detail

section to automatically fill in the fields in this table.○ Delete button: Click Delete to delete an existing conversion exit detail. To delete a conversion exit detail,

click the rectangle to the left of the Conversion Exit column in the row you want to delete and click Delete.○ Conversion Exit: (Read Only) Conversion exit from the Conversion Exit Detail section.○ Active Flag (column 1): (Read Only) When checked, the Skip Conversion box is checked in the Conversion

Exit Detail section○ Skip Conversion (column 2): (Read Only) When checked, the Skip on Initial box is checked in the

Conversion Exit Detail section○ Skip On Initial (column 3): (Read Only) When checked, the Setting Scope box is checked in the

Conversion Exit Detail section○ Setting Scope: (Read Only) Conversion exit scope from the Conversion Exit Detail section

● Conversion Exit Detail fields:○ Conversion Exit: Name of the conversion exit as found in SAP○ Setting Scope: Choose from the dropdown menu choices:

○ All Conversion Exit: Both input and output conversion exit routines are excluded○ Input Conversion Exit: Conversion routines are exited when data is sent to SAP


○ Output Conversion Exit: Conversion routines are exited when data is pulled out of SAP○ Skip Conversion: When checked, the conversion routine is always exited. When you check this box, it

automatically checks the box in the first Active flag column in the table above.○ Skip on Initial: When checked, the conversion routine is only excluded when the initial field does not

contain a value. If the initial field contains any value, the conversion routine runs. When you check this box, it automatically checks the box in the second Active flag column in the table.

○ Setting Enabled: When checked, the settings configured for the conversion exit are enabled and the exit is active. When you check this box, it automatically checks the box in the third Active flag column in the table.

System Components Tab

Use this tab to define system components in a multi back-end system. Configuration in this tab is not necessary if the application does not require a multi back-end system.

NoteCheck the Multi Back-End Enabled box in the General tab of the Mobile Application Configuration pane in order for system component configuration to function.




application○ Release: (Read Only) The release number of the mobile application○ Multi back end Enabled: (Read Only) When checked, the multi back end is activated on the General tab.

● System Component List fields:○ Add button: Click Add to create a new system component detail. Fill in the fields in the System

Component Detail section to automatically fill in the fields in this table.○ Delete button: Click Delete to delete an existing system component detail. To delete a system component

detail, click the rectangle to the left of the System Component column in the row you wish to delete and click Delete.

○ System Component: (Read Only) System component from the System Component Detail section○ System Role: (Read Only) System role from the System Component Detail section○ RFC Destination: (Read Only) RFC destination from the System Component Detail section○ Active Flag: (Read Only) When checked, the Active Flag box is also checked in the System Component

Detail section


○ Component Mobile App: In multi back end scenarios, when different back end names are used, the component mobile app is the application name that can tie all applications together

● System Component Details fields:○ System Component: For this required field, enter a descriptive name of the component.○ RFC Destination: Define in SAP before configuration in Mobile Add-On for ERP. Use transaction code

SM59 in SAP to create or change the RFC destination.○ Host: (Read Only) Identifying host name, defined in SAP○ System Number: (Read Only) Identifying server number, defined in SAP○ Client: (Read Only) Number of the client that the system component connects to, defined in SAP○ System Role: Determines if the system component is a host or a satellite. There can only be one host per

multi back-end system.○ Active Flag: When checked, the system component is activated in the multi back-end system○ Component Mobile App: Common application name for multi back-end systems

Parameters Tab

Use this tab to define system parameters.





● Parameter List fields:

NoteThe columns in the Parameter List table are read only. Use the Parameter Detail section to make any additions or edits to the table.

○ Add button: Click Add to create a new parameter detail. Fill in the fields in the Parameter Detail section to automatically fill in the fields in this table.

○ Delete button: Click Delete to delete an existing parameter detail. To delete a parameter detail, click the rectangle to the left of the Parameter Group column in the row you want to delete and click Delete.

○ Parameter Group: Parameter group from the Parameter Detail section○ Param. Name: Parameter name from the Parameter Detail section○ Param. Value: Parameter value from the Parameter Detail section○ Param. Scope: Parameter scope from the Parameter Detail section○ Active Flag: When checked, the Active Flag box is checked in the Parameter Detail section○ No Runtime Change: When checked, the No Runtime Change box is checked in the Parameter Detail

section○ Comment: Comments from the Parameter Detail section

● Parameter Detail fields:○ Parameter Group: The group to which the parameter belongs. Groups are a means of organizing

parameters. References to a parameter include both the group name and the parameter name.○ Param. Name: The unique name of the parameter○ Param. Scope: The scope of the parameter value. There are two options:

○ Mobile Application: Value for all users of the application○ Mobile User: Value that can be overridden for individual users. To override a parameter value of a user,

see the Administration & Monitoring portal information on parameters.○ Param. Value: The currently configured value of the parameter. References to this parameter return the

parameter value○ Rule ID: If enabled, the ID is the rule used at runtime○ Use Rule: When checked, you can define a rule to be used at run time○ Rule Input Param: If the specified rule has optional parameters, define them here○ Active Flag: When checked, the parameter is used by the mobile application. Inactive parameters are not

available to the mobile application.○ No Runtime Change: When checked, the value of the parameter cannot be overridden. The configured

value is always the value. If not checked, parameter values can be overridden at runtime through synchronization processing.

○ Comment: Any comments applicable to the parameter that describe its purpose or value. Comments have no effect on the behavior of the parameter and are provided for reference purposes only.

Client Globals Tab

Use this tab to define client globals.




● Client Global List fields:

NoteThe columns in the Client Global List table are read only. Use the Client Global Detail section to make any additions or edits to the table.

○ Add button: Click Add to create a new global. Fill in the fields in the Client Global Detail section to automatically fill in the fields in this table.

○ Delete button: Click Delete to delete an existing global. To delete a global, press the rectangle to the left of the Global Group column in the row you wish to delete and click Delete.

○ Global Group: Global group from the Client Global Detail section○ Global Name: Client global group name from the Client Global Detail section○ Global Value: Client global value from the Client Global Detail section○ Global Scope: Global scope from the Client Global Detail section○ Active Flag: When checked, the Active Flag box is checked in the Client Global Detail section○ No Runtime Change: When checked, the No Runtime Change box is checked in the Client Global Detail

section○ Comment: Comments from the Client Global Detail section

● Client Global Details fields:○ Client Global Group: The group to which the global belongs. Groups are a means of organizing globals.

References to a global include both the group name and the global name.



○ Client Global Name: The unique name for the global○ Global Scope: The scope of the global value. There are two options:

○ Mobile Application: Value for all users of the application○ Mobile User: Value that can be overridden for individual users

○ Client Global Value: The currently configured value of the global. References to the global return this value.

○ Rule ID: Name of the ABAP class○ Use Rule: When checked, the rule listed in the Rule ID field is active. If this value is active, then the Client

Global Value field is not used.○ Rule Input Param: Parameters to use with the rule. Examples include a key value pair, a user parameter, or

a table.○ Comment: Displays any comments added to the global to describe its purpose or current value.

Comments have no effect on the behavior of the global and are provided for reference purposes only.○ Active Flag: When checked, the client global is activated in the system. Inactive globals are not available

to the mobile application.○ No Runtime Change: When checked, the value of the global cannot be overridden. The configured value in

the ConfigPanel is always the value. Globals without this setting can be overridden at runtime through synchronization processing.

User Attributes Tab

Use this tab to create new user attributes.




● User Attribute Settings - Attribute List fields:You can define any number of user attributes. Add them in the Attribute Detail section to populate the attributes in the list. The fields in the Attribute List are read only.○ Attribute Name: (read only) This is the user attribute name.○ Reference Structure Name: (read only) If you assigned this attribute to a reference structure, the name is

displayed here.○ Reference Field Name: (read only) If you assigned the attribute to a single field, it is displayed here.○ ValueSet Provider Class: (read only) Each field in the structure can have a lookup table. This is the

valueset associated with this attribute.● User Attribute Settings - Attribute Detail fields:

Add the attributes here. The only required field is the Attribute Name.By default, the Attribute Name field is a single field, with up to 255 characters. You can define a smaller, single field. For instance, if you want to define a three-character only field, you can define a reference structure and a field. The user attribute can also be a record reference structure.○ Attribute Name: Add a name for the attribute you are defining.○ Description: (Optional) Enter a short description of what this attribute is to be used for.○ Reference Structure Name: (Optional) You can assign the attribute to a structure instead of a single field.○ Reference Field Name: (Optional) You can assign the attribute to a single field.○ ValueSet Provider Class: (Optional) This is the lookup value table. Each field in the structure can have a

lookup table.

3.2 ConfigPanel - Geospatial Service Definitions Settings

Use the Geospatial Service Definitions screens to define your geospatial service provider and set object type assignments.

NoteGeospatial Service Definitions are not currently used by the SAP Inventory Manager application.



3.3 ConfigPanel - oData Channel Integration Settings

oData, or Open Data Protocol, is an open data access protocol that allows the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way.

NoteNone of the offerings under the oData Channel Integration Settings section are currently used by the SAP Inventory Manager application.

3.4 ConfigPanel - Change Detection Settings

Change detection settings define and configure how the mobile application communicates with SAP and the object tables within SAP.

Two areas are used in the ConfigPanel to configure change detection:

● EFI Assignment: Change detection rules for SAP data objects, such as master data and transaction data, defined for each mobile application

● Exchange Object Configuration: Enhancement Framework Implementation (EFI) trigger assigned to exchange objects

NoteBefore you create or configure information in the ConfigPanel, create the corresponding tables and objects in both SAP and Agentry, or ensure that they exist.

See the subtopics in this section for more information on change detection settings.

3.4.1 ConfigPanel - EFI Assignment Settings

Enhancement Framework Implementation (EFI) source code plug-ins are implemented by the Mobile Add-On for ERP for each business object where you are implementing change detection. The source code plug-in is provided as an ABAP include file. Each exchange object is assigned to a plug-in to handle the actual change detection process. EFIs are typically available across multiple mobile applications running on the same system.

EFIs collect before and after images of data in an SAP object that has been created, modified, or deleted. The EFI then hands those images to the exchange object, which continues with the data processing. Therefore, you link the EFIs to the appropriate exchange objects.


Enhancement Implementation Includes

The Enhancement Implementation Includes list is a tree of the include file list in the package. Click the arrow to the left of the first item to expand the list:

General Tab

Use the General tab to view and modify the general settings for a chosen EFI file.

● EFI Type: Select one of the following options for EFI type:



○ Standard EFI Include: Traditional way to implement EFI and configure the EFI assignments○ EFI Event Handler Implement EFI using an ABAP class-based approach. If you select EFI Event Handler,

you develop EFI implementation as a subclass of /SMFND/CL_CORE_EFI_EVENT_BASE. Available EFI event handler classes are displayed in the dropdown field. The EFI event handler approach provides a more robust functionality and is recommended for new EFI implementations.

● EFI Include Name: Source code plug-in file name● Description: Short description of the EFI. The field is automatically filled in when you select the EFI Include

Name and is not editable.● Package: Package where the EFI is located. This field is automatically filled in when you select the EFI Include

Name and is not editable.

Assignment Tab

Use the Assignment tab to modify the EFI assignments.

● EFI Info fields:The general EFI information fields in this section are taken from information in the General tab and are not editable.

● EFI Assignment List:The EFI Assignment table displays which plug-ins are assigned to a specific include file. All column information is replicated in the Assignment Detail section directly below the table.To highlight an individual row, click the gray square to the left of the EFI Include Name column in that row.


● Assignment Detail fields:Information in this section changes depending on which row is highlighted in the EFI Assignment List section table.○ Mobile Application: The specific mobile application and its release number. This field is noneditable.○ Exchange Object: Exchange object to which the EFI include file is assigned.○ Exch. Object Desc: A brief, easy to understand description of the exchange object, limited to 60

characters.○ Active Flag: When checked, the exchange object is in an active state. If unchecked, the EFI is not linked to

the assigned mobile data object

3.4.2 ConfigPanel - Exchange Object Configuration Settings

The exchange object defines what object in the exchange table to update in the exchange persistent layer, what class handler to call to update the exchange table, and what fields relate to change detection. Use the Configuration Panel to specify which changes are relevant to your mobile application and what conditions to satisfy to trigger an update action.

The Exchange Object Configuration screen consists of the following tabs:

● Technical Settings● Change Detection Field Selection● Change Detection Condition Filter● Data Segment Settings● Linkage Settings● Push Settings

Technical Settings Tab

Use the Technical Settings tab to configure basic settings for an exchange object.

● General data fields:○ Exchange Object: ID of the exchange object, limited to 40 characters○ Exchange Object Description: Brief description of the exchange object, limited to 60 characters○ Mobile Application: Specific mobile application to which the exchange object belongs using a dropdown

selection field○ Application Area: Classifies the exchange object based on standard SAP application areas using a

dropdown selection field○ Reference Business Object: Standard SAP business object○ Exchange Table Name: Name of the table stored in SAP that contains the technical data○ Exchange Table Description: Brief description of the exchange table○ Exchange Lock Object: SAP lock object used when updating the exchange table○ No Exchange Table Update: When checked, the record is not written to the exchange table in SAP when

the record is changed○ Days to Keep History: Number of days the historical data is kept in the exchange table



● Handler Setting field:Exchange Object Handler: Name of class handler from the repository that is responsible for updating the exchange table

● Collective Run Settings field:Collective Run Mode: Defines conditions to determine if exchange processing can be executed asynchronously as V3 collective run. The mode options are:○ Dynamic: Collective run mode is determined at runtime by the exchange handler method

DETERMINE_EXEC_MODE○ Not Allowed: Not allowed to switch to collective run mode○ Activated: Always execute asynchronously in v3 collective run○ By User Parameter ID: Switch to V3 collective run mode for runtime user with the specified user

parameter value set in the user profile● Activation Setting fields:

○ Active Flag: When checked the exchange object is in an active state. If unchecked, the exchange object performs no actions.

○ Use in Linkage Processing Only: If checked, the exchange object is only allowed during linkage processing. If not checked, the original EFI triggered exchange processing takes place.

Example:

The following screen sample shows that the exchange process is enabled for SIM43_RESERVATION. Any changes to Reservation master data are recorded in the exchange table and transmitted to the client during the next transmit.


Change Detection Field Selection Tab

The Change Detection Field Selection tab allows you to optimize the change detection process for mobile applications. If a value change is detected for any fields within the group, the object identifier is written to the exchange table, indicating that a change has been made. If the Active flag is not checked for a field, any value changes made to that field are not detected or recorded to SAP during the exchange process. By default, all fields are initially checked.

The Exchange Object by Application Area lists all application areas and the exchange objects linked to each application area. Expand the lists by clicking on the arrows to the left of the application area to display the exchange objects associated with it.

● Exchange Object Info fields:○ Exchange Object: A noneditable field that contains the ID of the exchange object.○ Exchange Object Description: A noneditable field that contains a brief description of the exchange object.○ Exchange Object Handler: A noneditable field that contains tha name of class handler from the repository

that is responsible for updating the exchange table.● Exchange Object Field Selector fields:

○ Field Catalog: All fields that can be detected by the class handler when changes are made, grouped by the technical table name of the SAP business object. The field catalog is a noneditable field.

○ Active Flag: When checked, either the table or a field within a table is active. Any value change to the selected field is detected by the class handler.

NoteChecking the Active Flag box on a Table row selects all fields within the table.

○ Short Description: Brief description of the table or the field within the table. The short description is a noneditable field.



● Selection Proposal options:In a typical installation, it is not desirable to have all fields in all exchange tables checked as active for change detection. Rather, only the fields that are active on the mobile data object that are brought down to the mobile device should also be active in the exchange object.Based on mobile data object usage in the mobile application, the Selection Proposal examines the active flags that are checked for the table fields of an exchange object. The Selection Proposal then provides recommendations to the administrator on which fields in the exchange object to check or uncheck.

Change Detection Condition Filter Tab

The Change Detection Condition Filter tab allows you to restrict change detection based on data content. For exchange handlers to support this feature, you first define data filter conditions for which the underlying SAP business object qualifies before the change detection process is triggered. The data filter condition is defined at the table field level and is in the SAP range table format.

● Exchange Object Info fields:○ Exchange Object: A noneditable field that contains the ID of the exchange object.


○ Exchange Object Description: A noneditable field that contains a brief description of the exchange object.○ Exchange Object Handler: A noneditable field that contains tha name of class handler from the repository

that is responsible for updating the exchange table.● Exception Settings fields

:○ Ignore Data Creation: When checked, new records, data, or both are created are not processed to the

exchange table○ Ignore Data Deletion: When checked, deleted records, data, or both are not processed to the exchange

table○ Ignore Data Update: When checked, updated records, data, or both are not processed to the exchange

table● Defined Filters list:

The Defined Filters box lists all data filters supported by the class handlers.● Rule Editor fields:

○ Filter Name: Name of the filter as defined in the class handler method. This information is defined by the class handler developer and is not editable.

○ Reference Table Name: Technical name of the SAP database table where this filter is applied. This information is defined by the class handler developer and is not editable.

○ Reference Field Name: Technical name of the SAP database table field where this filter is applied. This information is defined by the class handler developer and is not editable.

○ Data Filter Rule Key: Internal technical key used by the framework at runtime○ Range Value: Use the following values to set the range:

○ Sign: Value for the SAP range table column SIGN○ Option: Value for the SAP range table column OPTION○ Low Value: Value for the SAP range table column LOW○ High Value: Value for the SAP range table column HIGH○ Active Flag: When checked, the rule is active

● Rule List table:The Rule List table displays a list of rules that have been defined.○ Rule No.: Number of the rule that is defined, in chronological order○ Rule Type: Rule type, automatically assigned by the rule type selected in the DOF Rule Type field○ Rule Value: Internal rule value saved by SAP○ Active Flag: When checked, the rule is active

Data Segment Settings Tab

The Data Segment Settings tab defines data segment requirement details for the specific exchange object. Data segment setting is optional for any given xchange object. If no data segment setting is defined, an exchange object is always called by the EFI event trigger if the exchange object is assigned to the EFI in the EFI Assignment Configuration settings.

By defining data segment settings, additional criteria is applied when determining whether an exchange object is called by an EFI event trigger. Even when an exchange object is assigned to the EFI in the EFI Assignment configuration settings, the exchange object is only called by the EFI event trigger when the data segment requirements are met.



Linkage Settings

The Linkage Settings tab allows the exchange objects that are linked together to communicate with each other. The communication is one-directional, with the exchange object sending information to the object(s) listed in the Linked Exchange Objects List. When there is a value change to the exchange object, that value change information is passed on to the linked exchange objects. The linked exchange objects then go through additional processes related to the value change.


● Exchange Object Info fields:○ Exchange Object: A noneditable field that contains the ID of the exchange object.○ Exchange Object Description: A noneditable field that contains a brief description of the exchange object.○ Exchange Object Handler: A noneditable field that contains tha name of class handler from the repository

that is responsible for updating the exchange table.● Linkage Settings field:

With the Linkage Hierarchy, you can go ‘n’ levels deep with linked objects. Any node changes triggers changes to the lower-level nodes linked to the parent node. These relationships are defined in the Linked Exchange Objects list.For example, the exchange object <APP>_MEASURING_POINT is linked to the following exchange objects:○ <APP>_FLEET○ <APP>_EQUIPMENT○ <APP>_FUNC_LOCATION

If the Measuring Point data changes, then the linked exchange objects also change.Maximum Linkage Hierarchy Level:

● Linked Exchange Objects list:○ Add Linkage button: Use this button to add a new linked exchange object. Click Add Linkage and use the

fields in the Linkage Detail section to add information.○ Delete Linkage button: Use this button to delete a linkage. To highlight the row you want to delete, click

the rectangle to the left of the Target Exchange Object cell and click Delete Linkage.○ Target Exchange Object: Displays the target exchange object selected in the Linkage Detail section.○ Linkage Type: Displays either an A for asynchronous or an S for synchronous, selected in the Linkage

Detaill section.○ Active Flag: When checked in the Linkage Detail section, the linkage between exchange objects is active.

● Linkage Detail fields:○ Target Exchange Object: The exchange objects that are linked to the exchange object listed in the

Exchange Object Info section.○ Linkage Type: Currently, Synchronous is the only option available. When a value change occurs to the

exchange object, notification to the linked exchange object is performed in real-time.○ Exclude Data Creation / Update / Deletion: The linkage for a source exchange object to a target

exchange may be limited by the action done on the source object. The possible actions are Create, Update, and Delete. By checking any of these three ‘exclude’ boxes, the linkage is not triggered for that action.

○ Active Flag: When checked, the linkage between the exchange object and the target exchange object is active.

Push Settings Tab

If the exchange object is part of a push instance, you must configure the object in the Push Settings tab before the object can appear in the Source Object dropdown menu of the push scenario definition.



● Exchange Object Info fields:○ Exchange Object: A noneditable field that contains the ID of the exchange object.○ Exchange Object Description: A noneditable field that contains a brief description of the exchange object.○ Exchange Object Handler: A noneditable field that contains the name of class handler from the repository

that is responsible for updating the exchange table.● Push Settings field:

Push Relevant: When checked, the exchange object is listed as a selection in the Source Object dropdown list in the Push Scenario Definition screen.

3.5 ConfigPanel - Inbound Transaction Queue Definition Settings

Transaction management settings are used to define and configure how the mobile application handles the inbound transaction queue.

NoteInbound transaction queue definitions are not currently used by the SAP Inventory Manager application.

3.6 ConfigPanel - Data Staging Settings

By default, data staging is off out of the box, as staged data is stale. Using data staging is only recommended for more static data.

See the topic Enabling Data Staging for Materials Complex Tables [page 130] for a procedure on how to configure data staging for your application.


3.6.1 Data Agent Definition

Use this page to define the data store supplying agent settings. Using the Data Agent Definition fields, you define a data staging framework data agent. A data agent defines the technical routine that populates a data store. The technical routine definitions include class, function, module, and so on.

3.6.2 Data Store Definition

Use the data store definition screens to define data store settings, data storage, data agent assignment, schedules, and mapping information. In this IMG activity, you define the data staging framework data stores. A data store is a data storage that can provide data to a Mobile Data Object. A data store can consist of multiple data segments, which are related data sets. A data store is populated by assigned data agents and schedules.

For example, you can define a data store and load it with a precalculated data set for a complex table with a large data set for initial download. A defined data store can improve the runtime performance of your mobile client during initial synchronization.

Data Store Definition has the following tabs:

● General Data● Data Segment● Agent Assignment● Field Mappings● Schedule



General Data Tab

Use the General Data tab for basic data information, including the Data Store ID, Store Type, and Data Store Description.

Select the Reserved for Mobile Data Object ID field if you want to tie the data store to a single MDO.

Data Segment Tab

Use the Data Segment tab to define the Data Supplier Detail information, such as Data Segment ID, Table Name, and Segment Alias.


Agent Assignment Tab

Use the Agent Assignment tab to define the Mapping Table Detail, including the Data Agent ID, Data Segment ID, and the Agent Parameter Name.



Field Mappings Tab

Use the Field Mappings tab to provide Field Mapping Detail, such as Table Mapping Assignment, Data Agent ID, Source Field Name, Parameter Name, and Target Field Name.


Schedule Tab

Use the Schedule tab to define the Scheduling Detail, such as Schedule ID, Data Agent ID, Start Date and Start Time, as well as End Date and End Time. You can also define a Frequency for the schedule as well as an eCATT Variant Name and eCATT Variant Container.

To execute the loading for the data store, schedule the data store loading utility program /SMFND/CL_DSF_LOADER as an optional background job.



3.7 RFC Channel Integration Settings

RFC, or Remote Function Call, enables you to call and execute predefined functions in a remote system or in the same system. RFCs manage the communication process, parameter transfer, and error handling.

3.7.1 Mobile Data Object Configuration

A mobile data object, or MDO, represents a mobile semantic view of data and activity combination for an SAP business object.

Mobile data objects are data repositories in the namespace that can get, create, update, and delete information in SAP. They encapsulate the business logic of mobile applications by defining transactions, data structures, and business rules.

There are three types of MDOs:

● Data Table (DT): A simple representation of SAP BusinessObjects KEY and VALUE.● Complex Table (CT): A two-dimensional representation of a business object with a single table of multiple

columns.● Standard Data Object (DO): A multi-dimensional representation of a business object with multiple tables

representing different subsets of the business object.

CautionOnly administrators or mobile application developers should create, copy, or change mobile data objects.


Use the ConfigPanel to modify MDO properties such as object type, class handlers, data filters, and other settings. For example, instead of modifying BAPIs to change what information is retrieved from SAP and pushed out to mobile devices, administrators use the ConfigPanel to modify MDOs and set up data filter rules.

The Mobile Data Object Configuration screen has the following tabs:

● General Setting● ResultSet Field Selection● Data Filter● Data Staging● Proxy Setting

General Setting Tab

Use the General Setting tab to modify the general settings for a chosen mobile data object.



● Basic Data: The Basic Data section provides general information about the specific mobile data object. The basic data information is used in tabs of the Mobile Data Object screen.○ Mobile Data Object ID: Required field. Enter the name of the MDO, limited to 40 characters○ Description: Required field. Enter a brief, easy to understand description of the MDO, limited to 60

characters


○ Data Object Type: A dropdown list of the three MDO types:○ Data Table: A simple representation of the SAP BusinessObjects KEY and VALUE○ Complex Table: A two-dimensional representation of the business object with a single table of

multiple columns○ Standard Data Object: A multi-dimensional representation of a complete business object. It can have

multiple tables representing different subsets of the SAP BusinessObjects.○ Mobile Application: Name of the mobile application. Choose the mobile application from the dropdown

list.○ Reference Business Object: SAP business object for which the MDO is being created.

● Data Object Handler Settings: Use the Data Object Handler Settings section to configure the methods of the MDO.○ Data Object Handler: Name of the ABAP OO class handler from the class repository of SAP. The ABAP OO

class handler is developed by the application developer with predefined business logic and scope to perform fetch, create, delete, or update activities for an SAP business object.

○ Get Method: Method defined in the class handler that fetches data for the underlying SAP business object (optional)

○ Create Method: Method defined in the class handler that creates data for the underlying SAP business object (optional)

○ Update Method: Method defined in the class handler that updates data for the underlying SAP business object (optional)

○ Delete Method: Method defined in the class handler that deletes data for the underlying SAP business object (optional)

○ Skip Exception Processing: When checked, the exception processing step is not invoked if an exception occurs during MDO handling

● Exchange Object Settings: Allows you to associate the MDO with an exchange object. Configure the exchange object using the Exchange Object Configuration screen in the ConfigPanel.○ Exchange Object: Name of the exchange object as defined in the SAP mobile exchange persistent layer.

Specify an exchange object from the dropdown menu if the selected class handler uses the mobile exchange persistent layer to determine data exchanges to the mobile application.

○ Enable Conv. Exit Overwrite: When checked, you can define specific internal and external conversion settings in the Technical Settings screen of the ConfigPanel.

● Localization Settings: When you enable localization in the MDO configuration, you can assign a localization language to an MDO, which is used for language related distribution. For example, a complex table MDO with localization language enabled returns language relevant descriptions in the specified localization language instead of the user logon language.○ Enable Localization Setting: Check to allow localization○ Language: Assign the localization language to the MDO

● Middleware Reference Info: If the middleware is specified, the MDO performs the standard exchange process as well as a lookup in the client object register table to determine what information the client contains. If data was removed from the client that still exists in the SAP table, the data is readded to the client during the transmit.○ Reference Middleware Object Type: Middleware objects are set through the Administration portal

(optional)● Activation: Use the checkbox to enable or disable an MDO in the application without deleting the MDO.

○ Data Object Active: When checked, the MDO is in an active state. If unchecked, the MDO performs no actions



ResultSet Field Selection Tab

When you enable a field selector function for a class handler, you can then select fields for the GET method to populate. The class handler is mobile application neutral. It supplies more data than the mobile application needs. Therefore, to preserve system performance, customize field usage settings to only retrieve required data for the mobile application. The ability to customize prevents the need to develop a new class handler for each mobile application.

● Handler Info fields:○ Mobile Data Object ID: Name of the MDO○ Description: Description of the mobile data object, limited to 60 characters. Required field.○ Data Object Handler: Name of the ABAP OO class handler from the class repository of SAP. The ABAP

OO class handler is developed by the application developer with predefined business logic and scope to perform fetch, create, delete, or update activities for an SAP business object.

○ Get Method: Name of the GET method set in the General Setting tab.


● Field Selection Detail fields:○ Field Catalog column: Lists all the fields that can be returned by the class handler method, grouped in the

order of the name of the class handler method, SAP table name, and field name. To display all information in this column, click the arrows to the left of a name to expand the row.

○ Field Active column: When checked, the data for the selected field is returned by the class handler method

○ Field Description column: Description of the specific field in the SAP table○ Data Format column: How data is presented○ Sort Options: When a large amount of information is presented, use the sort options to find the

information required easily. When you select a different radio button, the rows collapse. Expand them again to display the new field sorting.

Data Filter Tab

When a data filter function is enabled for a class handler, the option exists to define various types of filter rules to control what data a user can view on the mobile application based on the business process of the customer. In an SAP environment, each user is assigned a role-based profile with authorization restrictions for what data is viewed and which activities performed.

For example, a user who works for a specific plant should not be able to view data for another plant. Data filter rules allow you to restrict data access for mobile applications. Data filters can be user-dependent or applied to the entire mobile application.





● Defined Filters list:The Defined Filters tree lists all data filters supported by the class handlers defined in the Data Object Handler Settings field in the General Setting tab. To expand the tree, click the arrows to the left of the class handler methods to display the filters associated with the methods.

● Rule Editor fields:○ Method Name: Name of the class handler method where the data filter is defined. The data filter function

is only supported for the GET method○ Filter Name: Name of the filter as defined in the class handler method. The filter name is defined by the

class handler developer and is not editable.○ Reference Table Name: Technical name of the SAP database table where this filter is applied. The

reference table name is defined by the class handler developer and is not editable.


○ Reference Field Name: Technical name of the SAP database table field where this filter is applied. The reference field name is defined by the class handler developer and is not editable.

○ Data Filter Rule Key: Internal technical key used by the framework at runtime○ DOF Rule Type: Type of rule

Each rule set has different settings options:○ User Profile Parameter rule

○ Parameter ID: Memory parameter ID as defined in SAP and specified in the user profile. Click the icon to the right of the field box to perform a search on all available parameter IDs.

○ Description: Description of the memory parameter ID. The description field is not editable and is automatically filled in when the parameter ID is selected.

○ Active Flag: When checked, the rule is active○ Static Value in Range Format rule

○ Sign, Option, Low Value, and High Value are the values for the applicable columns in the SAP Range Table.

○ Syclo Filter Class Handler rule○ Syclo Data Filter Handler: Name of the handler class as defined in the system○ Parameter: Additional processing information that is passed to the class handler. The parameters are

entered as free text, and the syntax of the parameter stream is defined by the developer.○ Active Flag: When checked, the rule is active

○ Runtime Session Data rule○ Runtime Session Data Name: Session ID within the specified group○ Runtime Session Data Group: Name of the session group○ Active Flag: When checked, the rule is active

● Rule List table: The Rule List table displays a list of rules that have been defined○ Rule No.: Number of the rule that is defined, in chronological order○ Rule Type: Rule type, automatically assigned by the rule type selected in the DOF Rule Type field○ Rule Value: Internal rule value saved by SAP

Data Staging Tab

If an application processes a large amount of objects, data staging of the objects can assist with processing times. If an object is configured for data staging, the data within the object is stored as a package and is split into packets. The data can contain metadata and tagging for easy life-cycle management and data lookup. Standard APIs are provided for package management.





● Data Staging Setting fields:Get, Create, Update, and Delete Method Setting: When a checkbox is marked for a specific method, data staging is active for that method

Proxy Setting Tab

Use the Proxy Setting tab to define any proxy settings.




● Proxy Settings fields: The following fields are available for each of the methods:○ System Component: Identifies the remote system○ Proxy Type: BAPI Proxy is the only supported proxy type○ Proxy Name: BAPI name of the remote system○ Proxy Active: When checked, proxy settings are active for the specific method

3.7.2 BAPI Wrapper Configuration

A BAPI wrapper is created by the application developer to expose SAP data and business logic to the mobile application. By design, the BAPI wrapper does not contain any business logic. Each BAPI wrapper is assigned to a specific method type (GET, CREATE, UPDATE, or DELETE) of an MDO to perform the required business logic. By decoupling the business logic from the BAPI wrapper, it is possible to switch MDOs without affecting the underlying mobile application definition.



The BAPI wrapper Configuration screen contains the following tabs:

● General● Assignment

General Tab

Use the General tab to modify general settings for a selected BAPI wrapper.

● BAPI Wrapper Info fields:○ BAPI Wrapper Name: Technical name of the Remote Function Call (RFC) function module defined in the

system○ Description: Description of the BAPI wrapper, limited to 60 characters (required)○ Function Group: Function group to which the BAPI belongs○ Function Group Description: Description of the function group, limited to 60 characters○ Package: SAP group to which the function group and the BAPI wrapper both belong

● Technical Info: The Technical Info, or BAPI wrapper list, provides an expandable tree of the available BAPI wrapper function groups and the BAPI wrapper names associated with each function group. Use the arrows to the left of the function name to display all BAPI wrapper names under the function group.


Assignment Tab

Use the Assignment tab to hook up BAPI wrapper assignments to mobile data objects. In this tab, you can change the assignment of a BAPI wrapper to specific mobile data objects, assign a new mobile data object to the BAPI wrapper, or delete a mobile data object assignment from the BAPI wrapper.

● BAPI Wrapper Info fields:○ BAPI Wrapper Name: Technical name of the Remote Function Call (RFC) function module defined in the

system○ Description: Description of the BAPI wrapper, limited to 60 characters (required)

● Mobile Data Object Assignment List:○ Mobile Data Object Assignment table: Table that displays which mobile data objects are assigned to

each BAPI wrapper. All column information is replicated in the Assignment Detail section below the table.To highlight an individual row, click the gray square to the left of the Mobile Application column in that row.

● Assignment Detail fields: Information in these fields changes depending on which row you highlight in the Mobile Data Object Assignment List table○ Mobile Application: The specific mobile application and its release number. This field is noneditable○ Mobile Data Object ID: The name of the mobile data object in a dropdown field○ Description: A brief, easy to understand description of the mobile data object, limited to 60 characters.

This field is noneditable○ Method Type: Mobile data object method (GET, CREATE, UPDATE, or DELETE) that is assigned to the

BAPI wrapper○ Active Flag: When checked, the mobile data object is in an active state. If unchecked, the mobile data

object performs no actions○ Default Assignment: When checked, the specific mobile data object assigned to that BAPI wrapper is

primary. If no mobile data object ID is specified in the standard BAPI wrapper input parameter <IS_BAPI_INPUT-DO_ID>, then the primary mobile data object is used during runtime.It is possible to assign multiple MDOs to the same BAPI in a single mobile application.



To override the default MDO assignment at runtime and to specify the desired MDO, define the <DO_ID> field in <IS_BAPI_INPUT>.

3.8 Push Framework Settings

Use the following topics to understand how to configure different push scenarios in your system.

3.8.1 Push Scenario Definition

Use the Push Scenario Definition link on the ConfigPanel to configure what data is pushed from the SAP back end to the mobile device, and the triggers that initiate a push.

NotePush Scenario Definitions are not currently used by the SAP Inventory Manager application.

3.8.2 Outbound Trigger Configuration

An outbound trigger allows a mobile application to interface with external systems such as Agentry middleware server from SAP. You can integrate outbound triggers into standard mobile application processes, such as push processing. You can define different types of outbound triggers, including HTTP triggers, file triggers, and web service triggers.

NoteOutbound trigger configuration is not currently used by the SAP Inventory Manager application.

3.8.3 Subscription Agent Definition

Subscription Agent Definitions allow you to define how subscription requests for back-end system data are handled.

On Demand subscriptions allow you to define push options. For instance, some accounts, or activities have attachments, which are not automatically pushed down. If subscribed, however, a sales manager can get those attachments on demand, based on the settings configured in the subscription agent.

NoteSubscription Agent Definitions are not currently used by the SAP Inventory Manager application.


3.9 ConfigPanel - Technical SettingsThe Technical Settings screen in the ConfigPanel is used to change the framework technical settings for application logs viewable in SAP. These application logs are logging levels and conversion exit logs.

The following fields make up the Technical Settings screen:

● Application Logging Level: Defines the logging level for all framework components. Logging entries are recorded in the SAP application log database under the object </syclo/>.The logging levels are:○ No logging○ Abort○ Error○ Warning○ Info○ Debug○ Trace

● Enqueue Wait Time (Sec): If an SAP object is locked and inaccessible during an update by a mobile device, this parameter controls the number of seconds the underlying component continues to attempt to access the locked object in intervals of one second. If accessing the locked object is still unsuccessful after the wait time, the update process aborts.

● Internal Conversion Exit Active: When checked, the framework runtime data manager performs standard SAP external-to-internal format conversion exit for all inbound BAPI parameters. The option is enabled by default. Only an application developer should change the Internal Conversion Exit Active setting, as changing it directly impacts the mobile application.

● External Conversion Exit Active: When enabled, the framework runtime data manager performs standard SAP internal-to-external format conversion exit for all outbound BAPI parameters. The option is enabled by default. Only an application developer should change the External Conversion Exit Active setting, as changing it directly impacts the mobile application.

● Range Parameter Check Active: When enabled, the framework runtime data manager performs checks on all SAP range parameters of inbound BAPI parameters. The SAP range parameter has the structure of SIGN, OPTION, LOW and HIGH. The check routine sets the SIGN value to I and the OPTION value to EQ if not specified. The option is enabled by default. Only an application developer should change the Range Parameter Check Active setting, as changing it directly impacts the mobile application.

● Collection Mode: Determines how system statistic records are written to the database. Two modes are supported currently: Synchronously and Asynchronously. When Synchronously is selected, the statistics



record is written to the database in real-time during BAPI calls. However, selecting Synchronously incurs a performance penalty. Selecting Asynchronously means that statistics are collected in-memory and written asynchronously to the database at the end of the BAPI call.

● Statistic Collection Active: When enabled, the framework records all runtime statistics associated with the BAPI calls between the middleware server and SAP. The statistic collection provides data for the KPI statistics collections found in the Administration Portal. Only an application developer should change the Statistic Collection Active setting, as changing it directly impacts the mobile application.

● Created By, Creation Time Stamp, Last Changed By, Changed Time Stamp: The user ID and time stamps are automatically logged when a record is created or changed.

3.10 ConfigPanel - Security Settings

Security settings are used to provide additional rules and roles on top of the standard SAP-provided rules and roles.

For detailed information on required and essential authorizations, and procedures on enabling mobile-specific authorization checks, see the SAP Inventory Manager Security Guide.


https://help.sap.com/viewer/a7adaf055a824eeaaba4e1da1ede33c2/latest/en-US/952497700ffa47b38b42d492ad5e6c58.html

4 Mobile Add-On for ERP for SAP Systems

All components of the Mobile Add-On for ERP administration in SAP, such as BAPI wrappers and mobile data objects support logging. Activity logs generated by theMobile Add-On for ERP are integrated into the standard SAP application log database.

The following are administration and monitoring functions available in the Mobile Add-On for ERP:

● Push Instance Purge Utility● Data Cache Purge Utility● Generic Purge Utility● Exchange Table Purge Utility● Subscription Queue Purge Utility● Log Deletion● Log Display● Statistics Log Purge Utility

The manual process of purging data is important during configuration and modification in a development environment. Be sure to purge data after each test, after reviewing it, and before starting the next test. This way, the data found in the logs is applicable to the newest test activities and will not cause confusion. Periodic purging of data also contributes to an optimum running environment.

Exchange table histories can be set to automatically delete after a set period of days through the ConfigPanel. Perform all other data purges and log deletions through SAP.

4.1 Accessing Administrative Functions in SAP

Procedure

1. Log into SAP.2. Type /n/syclo/smart into the command field and click the green checkmark to the left of the field, or press

Enter.

60 C U S T O M E RSAP Inventory Manager Configuration GuideMobile Add-On for ERP for SAP Systems

The Mobile Add-On Administration window displays. Click the arrows to the left of the menu items to expand the SAP menu tree. Expand as follows: SAP menu System Administration Operation . The available administrative functions display:

3. Double-click on the desired administrative function to open the SAP window for that function.

4.2 Mobile Add-On for ERP Push Instance Purge Utility

The push instance purge utility is used to purge exchange table information that is used during the push processing. Once the push data is pushed to client devices, the exchange information is no longer needed and can be purged.

The purge utility in SAP performs a manual purge. Configure automatic purges of push instances in the Push Scenario Definition panel of the ConfigPanel.

SAP Inventory Manager Configuration GuideMobile Add-On for ERP for SAP Systems C U S T O M E R 61

When desired fields are filled, click the clock icon in the upper left to execute the purge.

Runtime Settings

● Mobile Application: Click the box icon to bring up a window displaying all mobile application choices.● Push Instance GUID: Select GUIDs contained within the push instance table in SAP ERP to purge.● Push Status: Select statuses contained within the push instance table in SAP ERP to purge. By default, all

statuses are included if the fields are not filled in. The push statuses include:○ NEW○ PROCESS○ SRV_COMP○ COMPLETED○ CANCEL

● Scenario ID: Select scenario IDs contained within the push instance table to purge.● Record ID: Select record IDs contained within the push instance table to purge.● Expiration Date: Choose a date when the purge utility operation expires. The expiration date is automatically

filled with the current date.● Expiration Time: Choose a time when the purge utility operation expires.● Maximum No. of Instances: Type in the maximum number of instances to purge from the instance table.● Test Run: When this box is checked, records are not purged upon execution. Rather, a list of the records

selected for purging displays, and you can determine that the purge parameters are correct. Once records are purged, you cannot recover them.

4.3 Mobile Add-On for ERP Data Cache Purge UtilityUse the data cache purge utility to manage and purge packages associated with messages and the outbound message queue from SAP. The outbound message queue is the only way SAP communicates with the client device.


Packages are the data attached to outbound messages. In this way, an administrator can send a message to multiple users while referencing only one data package, rather than an individual data package for each outbound message.

Runtime Settings

● Mobile Application: Select the desired mobile application with which the outbound messages or packages are associated.

● Expiration Date: Choose a date when the purge utility operation expires. When used with Expiration Time, the maximum expiration timestamp from which to purge messages from the cache. If an expiration date or time are provided, they are converted into a timestamp. The utility only deletes the messages where the expiration date or time is less than or equal to the provided timestamp. If a timestamp is not provided, deletion occurs without respect to the expiration timestamp of the messages.

● Expiration Time: Choose a time when the purge utility operation expires. When used with Expiration Date, the maximum expiration timestamp from which to purge messages from the cache. If an expiration date or time are provided, they are converted into a timestamp. The utility only deletes the messages where the expiration date or time is less than or equal to the provided timestamp. If a timestamp is not provided, deletion occurs without respect to the expiration timestamp of the messages.

● Data Handler Name: Select data handler names contained within the data cache to purge. Data handlers are responsible for messages within packages to purge. It limits the purge to the class handler responsible for handling the message.


● Data Handler Method: Select data handler methods contained within the data cache to purge. Data handlers are responsible for messages within packages to purge. It limits the purge to the method of a class handler responsible for handling the message.

● Configuration Object Name: Select configuration object names contained within the data cache to purge. Limits the purge to the configuration object that owns, or is the source of, the message.

Package Deletion Settings

Select the Delete Packages option to purge packages stored in SAP.

NoteIf a data package is associated with a message GUID, you cannot delete it.

● Storage Unit GUID: Each package is associated with a unique storage unit GUID

Message Deletion Settings

Select the Delete Outbound Messages option to purge outbound messages stored in SAP.

NoteAll packages associated with outbound messages are also deleted when you select the Delete Outbound Messages option.

● Message GUID: Each outbound message is associated with a unique message GUID● Message Status: Select message statuses contained within the data cache to purge. Use the following

available message statuses:○ NEW○ SEND○ RECEIVED○ CANCEL○ CONFIRMED

● Message Counter: Select message counters contained within the data cache to purge.

Test Run

When you check the Test Run box, packages or messages are not purged upon execution. Rather, a list of the packages or records selected for purging appears. Then, you can determine that the purge parameters are correct. Once packages or records are purged, you cannot recover them.


4.4 Mobile Add-On for ERP Generic Purge UtilityUse the generic purge utility to delete records in SAP that pertain to specific user IDs or middleware server records.

When you check a box in the Middleware Data Selection field, additional fields for the selection appear, allowing you to set specific purging criteria for the selection.

● Mobile Application: Select the desired mobile application with which the middleware server records are associated

● User GUID: Select user GUIDs contained within the middleware server records to purge

User Registry

When you check the User Registry box, all records pertaining to that user ID, such as session and object records, are also purged. Each mobile user ID is a user GUID in SAP. Mobile users need a separate user GUID for each mobile application they use.


Check the User Registry box to purge user records according to the following criteria:

● User Date Earlier Than: Highlight the field to use the calendar to select a date to purge user records existing before the date selected

● User Time Earlier Than: Highlight the field to use the time display window to select a time to purge user records existing before the time selected

Session Registry

Every time a user ID connects to SAP, a session record is created. Each session record has a GUID, a start time stamp and an end time stamp.

Check the Session Registry box to purge session records according to the following criteria:

● Session Date Earlier Than: Highlight the field and use the calendar to select a date to purge session records created before the date selected

● Session Time Earlier Than: Highlight the field and use the time display window to select a time to purge session records created before the time selected

● Session GUID: Either type in the GUID or use the Multiple Selection icon to select a range of GUIDs

Object Registry

Each object on each client device has a unique GUID contained within the object registry table. The object registry is used by the fetch process to calculate what data is needed by each client device based on change detections since last transmit.

Check the Object Registry box to purge object records according to the following criteria:

● Object Date Earlier Than: Highlight the field and use the calendar to select a date to purge object records created before the selected date


● Object Time Earlier Than: Highlight the field and use the time display window to select a time to purge object records created before that time

● Object GUID: Either type in the GUID or use the Multiple Selection icon to the right of the field to select a range of GUIDs

User Push History

When push history is enabled, every time an object is pushed to a user it is recorded to a history table. The user push history purge utility removes old history records, or specific history records, by specifying a date, time, or record GUIDs from which to purge.

NoteIn order for history records to appear, the push (distribution) handler has to support the history function.

Check the User Push History box to purge object records according to the following criteria:

● Update Date Earlier Than: Highlight the field and use the calendar to select a date to purge user push history created before the selected date.

● Update Time Earlier Than: Highlight the field and use the time display window to select a time to purge user push history created before that time.

● Push History Record GUID: Either type in the GUID or use the Multiple Selection icon to the right of the field to select a range of GUIDs.

Cross Reference

The reference tables contained within SAP facilitate the key mapping process for Agentry applications. When a user creates a local object with a temporary ID and transmits to the system, the object is assigned an object GUID. Agentry can also break down a document into smaller chunks of information, each with its own reference GUID mapped to the object GUID.

Generic Purge Utility - Cross Reference


Check the Cross Reference box to purge cross references according to the following criteria:

● Ref. Obj. Date Earlier Than: Highlight the field and use the calendar to select a date to purge reference object records created before the selected date.

● Ref. Obj. Time Earlier Than: Highlight the field and use the time display window to select a time to purge reference object records created before that time.

● Reference GUID: Either type in the GUID or use the Multiple Selection icon to the right of the field to select a range of GUIDs.

Server

A system can contain multiple middleware servers within the system. Each server has a unique GUID associated with it.

Generic Purge Utility - Server

Check the Server box to purge server records according to the following criteria:

● Server Date Earlier Than: Highlight the field and use the calendar to select a date to purge server session records created before the selected date.

● Session Time Earlier Than: Highlight the field and use the time display window to select a time to purge server session records created before that time.

● Server GUID: Either type in the GUID or use the Multiple Selection icon to the right of the field to select a range of GUIDs.

● Only Delete Locked Server: Check this box if you only want to purge server records on the locked server.

Mobile Status

Whenever a technician changes the status of an object and transmits from the mobile device, the status management tables in SAP are updated. Each object has a unique object key associated with that object.

Generic Purge Utility - Status Selections


Check the Mobile Status box to purge mobile object records according to the following criteria:

● Status Date Earlier Than: Highlight the field and use the calendar to select a date to purge mobile status records created before the selected date.

● Status Time Earlier Than: Highlight the field and use the time display window to select a time to purge mobile status records created before that time.

● Object Key: Either type in the object key or use the Multiple Selection icon to the right of the field to select a range of object keys.

Test Run

Check the Test Run box in order to have SAP display another window that shows in table format the records that will be deleted based on the criteria selected in the Purge Utility Program screen. Once records are purged from the system, they cannot be recovered.

Generic Purge Utility - Deleted Session Table Entries Table

4.5 Mobile Add-On Exchange Table Purge Utility Program

Use the purge utility for the exchange tables to purge obsolete exchange objects from one or more mobile applications in SAP. Obsolete records are determined based on the purge frequency configured in the Configuration Panel.

To determine the purge frequency in the Configuration Panel, navigate to the Exchange Object Configuration menu item under the Mobile Application Settings section. In the Technical Settings tab, set the Days to Keep History field to the desired number of days and click the Save button.

When field selection is complete, click on the Clock icon at the top left of the screen to execute the exchange table purge.


SAP Administration - Exchange Table Purge Utility Program

Selection Criteria

● Mobile Application: Use the mobile application range fields to select one or more mobile applications from which to purge objects from the exchange tables.

NoteSelection choices may vary depending on which mobile applications are available on the system. If there is only one mobile application, this field does not apply.

● Exchange Object: Use the exchange object range fields to select one or more exchange objects from which to purge tables.

● Last Changed By: Use the range fields to select one or more user names who made changes from which to purge tables.

● Object Key: Key of the exchanged object. This ID is governed by how the field OBJKEY is populated in the relevant exchange table. The keys will vary from object to object.

● Exchange Action: Use I for Insert, U for Update, and/or D for Delete.● Record Status: Use [blank] for the standard purge, D for Delete, and S for Skip.● Delete All Entries: Select this checkbox to purge all obsolete records from the exchange tables, regardless of

the application or exchange objects.

4.6 Mobile Add-On Log Deletion

Use the log deletion function to delete expired logs from SAP. When desired fields are filled, click on the Clock icon to execute the deletion.


SAP Administration - Delete Expired Logs

Expiry Date

Click the first radio button to only delete logs which have reached their expiry date. Click the second radio button to delete logs that have reached their expiry date as well as logs that can be deleted before their expiry date has passed.


Selection Conditions

● Object: Select the desired object by either typing it in the field or clicking on the selection icon. The object is usually set to /syclo/.

● Subobject: Select from the following subobjects:○ ADMIN - Administration portal logs○ BAPI - Client application logs○ CONFIG - Configuration portal logs○ DEFAULT - All logs not covered through the rest of the subobjects○ EXCHANGE - Exchange and transaction process logs

● External ID: Each log entry has an external ID, depending on what the log is for.● Transaction Code: Not used● User: SAP user ID that created the logs● Log Number: Each log entry has a log number associated with it. If the log number or range of numbers is

known, enter them here.● Problem Class: The problem class of the logs● From (date/time): To select the beginning start date and time of the logs to delete, click in the fields and use

the calendar and the time window display to choose the correct date and time.● To (date/time): Select the end date and time of the logs to delete by clicking in the fields and using the

calendar and the time window display to choose the correct date and time.

Options

● Only calculate how many: Click this radio button to generate a popup window with the number of table logs that fit the criteria for deletion. Selecting this option does not result in any log deletion.

● Generate list: Click this radio button to generate a list of which table logs fit the field criteria for deletion. This list opens a different SAP window with multiple options for working within the list, including individual selection of table logs to delete. Selecting this option does not result in any log deletion.

● Delete immediately: Click this radio button to delete all table logs immediately. The system still confirms the deletion of logs in a popup window before permanently deleting them.

Delete by Number of Logs

COMMIT Counter: Enter the number of logs you want to delete.

4.7 Mobile Add-On Log Display

Use the log display utility to view activity logs based on the criteria selected on the main screen. When you have selected all desired criterion, click the Clock icon at the top of the screen to execute the request and display the desired logs.


SAP Administration - Analyze Application Log

● Object: To select the desired object, either type it in the field or click on the selection icon to the right of the field. The object is usually set to /syclo/ to view logs.

● Subobject: Select from the following subobjects:○ ADMIN - Administration portal logs○ BAPI - Client application logs○ CONFIG - Configuration portal logs○ DEFAULT - All logs not covered through the rest of the subobjects○ EXCHANGE - Exchange and transaction process logs

● External ID: Type the external ID into the field.


Time Restriction

● From (Date/Time): Click on the white square icons to the right of the date and time fields to select a start date and time of the beginning of the logs chosen for display. The date and time are automatically set for the current date at 00:00:00 hours.

● To (Date/Time): Click on the white square icons to the right of the date and time fields to select an end date and time of the final logs chosen for display. The date and time are automatically set for the current date at 23:59:59 hours.

Log Triggered By

● User: SAP user ID● Transaction Code: Standard SAP transaction codes● Program: Standard SAP programs

Log Class

Select the appropriate standard SAP log class. Log classifications are based on the implementation by the developer.

Log Creation

Select the appropriate log creation setting. These are standard SAP settings based on the implementation by the developer.

Log Source and Formatting

Select the appropriate log source and formatting setting. These are standard SAP settings based on the implementation by the developer.

4.8 Enable SAP Solution Manager to Diagnose Agentry Issues

You can use the SAP ERP Solution Manager to diagnose issues with the Mobile Add-On.

To enable this, SAP Solution Manager 7 EhP 1 must be installed.


OSS Note 1371097 "Diagnostics Setup for Agentry Servers End-To-End Root Cause Analysis System Landscape Setup Guide" is available here:

https://service.sap.com/~sapidb/011000358700000074392009E

Reporting Issues Using SAP Service Marketplace

You can report issues with the obile Add-On using the SAP Service Marketplace. Customer issues entered into the SAP Service Marketplace are automatically sent to the appropriate Technical Support team.


5 Mobile Add-On for ERP Administration Portal

5.1 Mobile Add-On for ERP Administration Portal

All components of the Mobile Add-On for ERP Administration, such as BAPI wrappers, mobile data objects and exchange objects, support logging. Activity logs generated by the Mobile Add-On for ERP are integrated into the standard SAP Application Log database.

The recommended time frame for keeping the logs is:

● Customization Table logs - Do not delete.● Exchange Table logs - Keep no more than 6 months (180 days).● System logs - Keep no more than 30 days.

Viewing the Mobile Application Log

To view the application logs:

1. Start the Mobile Administration Menu by running the command /n/syclo/smart from the command field of SAPGUI session.

2. Select the transaction /SYCLO/SLG1 - Application Log: Display Logs to launch the start screen of the log

display.


Mobile Add-On for ERP Administration Portal

3. Enter the desired the selection criteria. Make sure Object is set to /SYCLO/. Execute the transaction to view log details.

SAP Inventory Manager Configuration GuideMobile Add-On for ERP Administration Portal C U S T O M E R 77

Deleting an SAP Mobile Application Log

You should purge these logs every 30 days. To delete an application log:

1. Select transaction /SYCLO/SLG2 - Application Log: Delete Logs to launch the selection screen.

2. Enter selection criteria, and execute the transaction to purge the log database. The system will confirm deletion of logs in a popup window before deleting them.

Purge Utility for Exchange Persistent Layer

The purge utility for the exchange persistent layer is a tool that allows the system administrator to purge the content of the exchange tables. Exchange tables are not intended to be history tables. They should be purged periodically to maintain the exchange performance with the mobile application. It is recommended that you keep these tables no longer than every six months (180 days).



To purge the exchange table online:

1. Select transaction /SYCLO/EX_PURGE - Exchange Table Purge Utility to launch the selection screen.

2. Specify the list of Mobile Applications to be included. Leave this blank to include all applications installed.3. Specify the list of Exchange Objects to be included. Leave this blank to include all exchange objects.4. Enable the option Delete All Entries to delete all records in the exchange tables. If the delete all option is not

chosen, check the Value of Days To Keep History in the exchange object settings to determine what data should be purged.

5. Use the program /SYCLO/CORE_EXCH_PURGE_PROG to schedule a background job to carry out a periodic purge automatically.

5.2 Accessing the Administration and Monitoring Portal

Prerequisites

The person performing this procedure must log into the SAP ERP system as a user with the following authorizations:

● Authorization object - S_ICF● Authorization field - ICF_FIELD - SERVICE● Authorization field - ICF_VALUE - SYCLOADM● Authorization object - S_TCODE● Authorization field - TCD - /SYCLO/ADMIN

Procedure

1. Log into SAP ERP under an account with one of the authorizations provided in the prerequisites to this procedure.


2. Type /n/syclo/smart into the command field and click the green check mark to the left of the field, or press Enter.

The SAP Easy Access Agentry SAP Framework window displays.

3. Expand the SAP menu tree by clicking the arrows to the left of the menu items. Expand as follows: SAP menu System Administration Administration & Monitor .

The available administrative functions display.

4. Double-click on the Administration & Monitoring Portal menu item.

The SAP NetWeaver Web Application Server logon screen opens in a browser window.



NoteDepending on your configuration, the log on screen may be different than what is shown.

5. Fill in any necessary fields for your specific implementation and click Log On.

The System Administration & Monitoring Portal opens in the browser window.


5.3 Administration Portal - Mobile Solution Overview

An administrator can monitor the current system status through the main overview panel.

Mobile Solution Overview Panel

Today’s Date: The date is automatically set to the current date when the Administration portal is first accessed. To view system status for past dates: click the calendar icon to the right of the date field and choose the desired date.

1. Click the calendar icon to the right of the date field and select the desired date.



Mobile Solution Overview - Date Selection 2. Click Refresh to refresh the Operation Status statistics for the chosen date.3. To revert back to the current date, select the calendar icon again and select the current date, highlighted by

the blue box. Then, click Refresh to refresh the Operation Status statistics.

Current System Status (Checks of critical framework settings): Brief overview of the current system status through use of an icon and status text. Click the View Detail hyperlink to view the System Status Detail table.

Current System Status Detail

The System Status Detail table displays when you click the View Detail hyperlink to the right of the Current Systems Status (Checks of critical framework settings) line. This table provides an account of the framework and its status during the selected date.

Mobile Solution Overview - System Status Detail

● Seq. No.: Row number of the system tests performed● Status: Icon display of the system status● System Status Message: Text message giving a status description. There are three main system tests

performed:○ Configuration framework system setting - If this setting does not exist, or returns an error status message,

applications will not be able to run on the framework.○ Syclo number range interval - Automatic number counter. If this is not set up during the system

installation, the counters will not work. See the installation guide for more details.


○ Connection test - This test is dynamic and only appears if the system is multi-back end enabled. For the system to post a Success value for this test, the RFC destinations must be defined.

● Value: Text status of the system test

Click Close Message List to close the table view.

5.3.1 Mobile Solution Overview - Operation Status

The Operation Status panel of the Mobile Solution Overview provides a high-level status of activity on the system. Clicking on the View Detail link to the right of each status displays a more detailed status table below the Operation Status panel.

To access operation status details for a different date, choose a different date using the calendar icon at the top of the panel. Be sure to click Refresh in order to refresh the panel statistics to the newly-selected date.

NoteIf statistics collection is not enabled in SAP, some operation status details will not be available through the Administration & Monitoring portal.

Mobile Solution Overview - Operation Status

Total Number of Mobile Applications

Lists the number of mobile applications in use on the system.



Mobile Solution Overview - Mobile Application Count Detail

● Seq. No.: Row number in the table● Status: Not used in this table● Mobile Application: Name and release of the mobile application● Value: Number of specific mobile applications in use on the system

Total Number of Mobile Users

Lists the total number of mobile users on the system on the date chosen.

Mobile Solution Overview - Mobile User Count Detail

● Seq. No.: Row number in the table● Status: Not used in this table


● Mobile Application: Name of the mobile application● Value: Number of active users on the specific mobile application

Number of Active Users

Lists the total number of active users on the system on the date chosen.

Mobile Solution Overview - Active User Count Detail

● Seq. No.: Row number in the table● Status: Not used in this table● Mobile Application: Name of the mobile application● Value: Number of active users on the mobile application

Number of Push Instances

Lists the total number of pushes initiated on the system on the date chosen.



Mobile Solution Overview - Push Instance Count Detail

● Seq. No.: Row number in the table● Status: Not used in this table● Mobile Application, Scenario ID, Push Status: Name of the mobile application, name of the push instance, and

status of the push instance● Value: Number of push instances initiated on each mobile application

Total Number of Middleware Servers

Lists the total number of middleware servers present on the system.

Mobile Solution Overview - Middleware Server Count Detail

● Seq. No.: Row number in the table


● Status: Not used in this table● Server: Port, Serial Number: Name of the middleware server, the port it uses to connect to the framework, and

the serial number assigned to it in SAP.● Value: Number of middleware servers with that server name, port and serial number. This number will always

be 1.

Total Number of Communication Sessions

Lists the total number of communication sessions for the date chosen.

Mobile Solution Overview - Communication Session Count Detail

● Seq. No.: Row number in the table● Status: Not used in this table● Server: Port, Mobile Application: Name of the server, the port it uses to connect to the framework, and the

mobile application used on the server for the communication sessions● Value: Number of communication sessions on the specific server listed

Number of Users with Exception

If a user encounters issues during a transmit, the user ID, the mobile application, and the application ID is logged.



Mobile Solution Overview - User Exception Count Detail

● Seq. No.: Row number in the table● Status: Visual indicator showing the severity of the exception● Mobile Application: Name of the mobile application, GUID of the mobile application, and user name causing

the exception● Value: Number of exceptions the listed user has on the listed mobile application

5.4 Administration Portal - Administration

The Administration panel is used to create and manage the following areas:

● User Management - System administrators can create new mobile user IDs, as well as manage all settings associated with specific user IDs.

● Server Management - System administrators can create new connections to new servers, as well as manage all settings associated with specific servers.

● Runtime Logging Level Setting - System administrators can create or modify new logging parameters associated with specific user GUIDs.

● Mobile Application Parameters - Use the Mobile Application Parameter Management panel to override parameter settings in a production environment for a specific user or for the whole application, depending on the selection you make for the parameter scope.

Administrative Info

Each management panel contains a section at the bottom of the page called Administrative Info. Expand the section by clicking on the white box icon to the right of the Administrative Info heading.


Administration Portal - Administrative Info

● Created By: User ID of the person who created the information● Creation Time Stamp: Time and date the information was created● Last Changed By: User ID of the person who modified information in the panel● Changed Time Stamp: Time and date the information was modified

5.4.1 Administration - User Management

The Middleware User Management panel is used to create and manage mobile client user IDs. These IDs are layered on top of the user’s SAP user ID.

A user must have an SAP user ID before being able to access any mobile applications. A user must also have a separate user GUID for each mobile application they access. In this way, the system can track and calculate exchange episodes for each application a user accesses while keeping the exchanges separated by mobile application.

Basic Search Parameters

Use this field to search for users on a specific mobile application, or refine the search even further by the user ID or last activity time. Once specific user(s) are found, their information can be changed if necessary.

● Mobile Application: Name of the mobile application. Use the drop-down menu to choose the correct mobile application. This is a required field to enable the Search function.

● User: SAP user ID● Last Activity Time: Use the drop-down menu to select a window of time. The default is set to All, which is equal

to selecting no specific time period.● Search: Click Search once after you have entered all required and additional search parameters. If the search

returns results, they are displayed in the Search Result section. If the search parameters are not fulfilled, a message stating “No data found” displays in the Search Result section.

When you click Search in the Basic Search Parameters section, the Search Result table is populated, based on the parameters you selected. To create a new user in this section, click the Create button. In this case, it is not necessary to search for an existing user.

Basic Info Tab

When a user is selected in the Search Results table, the fields are populated in the Basic Info tab.



Click Change to modify editable fields. Click Create in the Search Result section to create a new user through the editable fields. Fields with a red asterisk beside them are mandatory.

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each

mobile application assigned in SAP.● User Name: User ID chosen from the table in the Search Result section● SAP Personnel Number: User ID number assigned to the user in SAP● Middleware License Number: Server serial number of the middleware server that is running the chosen mobile

application● Device ID: If a user is assigned to a mobile device connected to the chosen application and the mobile device

has an ID, the field is populated.● Device User ID: User ID assigned to the mobile device● Group ID: Allows you to define additional information about a user, such as a crew number or team name. This

is a free-text field.● Email Address: Email address of the user. Email are sent through the Push Scenario Definition panel in the

Configuration portal. Email are also used in the User Monitor panel under Monitoring in the Administration portal.

● HTTP Address: Web address or site links that users can access, such as a Twitter feed● Default Address Type: Select either Email Address or HTTP Address from the drop-down menu for the default

email sending method● Source System: Originating SAP system of the user ID. This is useful in multi-backend systems.● Lock Flag: If checked, user is unable to access the mobile application from the mobile device. This is used if a

mobile device is lost or stolen and the application data must be made inaccessible.

User Attributes Tab

This is where you define the values for user attributes. First, you must create the user attributes in the Mobile Application Configuration section of the Configuration Panel. Once you have defined one or more user attributes, use this tab to define the values for the attribute and turn it on.


Click Change to enter change mode, then click Add to set the details for a selected user attribute.

● Attribute Name: The drop-down menu for this field displays a list of all user attributes that you created in the ConfigPanel. Select the user attribute you want to define.

● Reference Structure: This drop-down menu is populated based on the user attribute you select. Select the appropriate field.

● Active Flag: Select this checkbox to activate the attribute.

You can set multiple user attributes. To do this, go back to the top and click Add again and select another user attribute to define and activate.

NoteYou can use the same user attribute more than once, defining different values.

Once you have defined all applicable user attributes, click Save.

Cross Reference List Tab

The Cross Reference List is used in systems that contain multi-back ends. When a user is created or modified, that user’s information will need to be replicated across the systems. This detail view provides statistics and information for each user on a multi-back end system.



Mobile User Detail - Cross Reference List

● System Component: System where the user ID resides● Reference User GUID: SAP user GUID● Sync Required: If box is checked, synchronization is required● Last Sync Time: Time and date of last synchronization● Sync Status: Descriptive text detailing the synchronization status● Created By: SAP ID of the user who created the new user ID● Creation Time Stamp: Time and date the user ID was created● Last Changed By: SAP ID of the user who made the change● Changed Time Stamp: Time and date of last change

Client Registration Info Tab

The Client Registration Info tab is used for RIM products only.

Mobile User Detail - Client Registration Info

5.4.2 Administration - Server Management

The Middleware Server Management panel is used to create and manage the middleware servers on the system.


Administration - Middleware Server Management


Use this field to search for users on a specific mobile application, or refine the search even further by the user ID or last activity time. Once specific user(s) are found, their information can be changed if necessary.


● Server Name: Name given to the middleware server either through SAP or when creating a new server configuration in this panel.

● Server Port: Port on the server assigned to the selected mobile application● Serial Number: The serial number of the server assigned to the mobile application● Search button: Click Search once all required and additional search parameters are filled. If the search returns

results, they are displayed in the Search Result section. If the search parameters are not fulfilled, a message stating “No data found” displays in the Search Result section.

When you click Search in the Basic Search Parameters section, the Search Result table is populated. To create a new server in this section, use Create. In this case, it is not necessary to search for an existing server.



Basic Info Section

When you select a server in the Search Results table, the fields are populated in the Basic Info section. Click Change to modify editable fields. Click Create in the Search Result section to create a new server by populating the editable fields. Fields with a red asterisk beside them are mandatory.

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● Server GUID: Server GUID for the specific mobile application chosen. Each server has a different GUID for each

mobile application assigned in SAP.● Server Name: Server name chosen from the table in the Search Result section● Port: Port the Agentry application in the SAP Mobile Server has assigned to the specific mobile application

chosen● Middleware Svr (Server) SerNo (Serial Number): Customer license number● Server URL (FQDN): Fully qualified domain name that can identify the Agentry application defined in the SAP

Mobile Server. In this way, SAP can identify and broadcast to the middleware server without using an IP address. If the IP address of the middleware server changes, use this method as the preferred way to communicate.

● Target Host: If a target host is specified, a broadcast of push notification is sent to the IP or URL specified in the Target Host field, instead of to the middleware server’s own IP or URL. Use this if a dedicated middleware or server should receive the broadcast from SAP.

● Local Outbound Trigger Port: By default, each middleware server running the same mobile application use the same port number to receive push notification broadcasts from SAP. This is the default in the outbound trigger setting Target Host Port Number. If, for some reason, individual middleware servers listen to push notifications on a different port, specify the port number here. The listed port number in this field will then supercede the port number set in Outbound Trigger Settings.

● Outbound Trigger URL Type: Use either the IP address or server URL when broadcasting push notifications.● Lock Flag: If checked, the server will no longer accept users attempting to connect. Set the lock flag to

temporarily lock down a server without deleting it from the system.● Disabled for Outbound Trigger: If checked, the Outbound Trigger is unavailable for the selected server.

5.4.3 Administration - Runtime Logging Level Setting

The Runtime Logging Level Setting panel is used to create and manage logging levels for specific mobile applications and user GUIDs. These settings override the logging level setting defined in the Technical Settings panel of the Configuration Panel. The logging level setting defined in the Configuration Panel applies to all applications running on the framework. However, at times more detail on a specific user or mobile application is desired without making changes to the entire framework.

With the runtime logging level setting, administrators can make dynamic adjustments to the logging level settings. Overrides to the framework settings can be made in two different areas: an individual mobile application or individual users running a specific mobile application. When troubleshooting of the user or the mobile application is complete, the administrator can uncheck the active flag to reset the logging levels back to the default settings specified in the Configuration Panel.


Administration - Runtime Parameter Management


Use these fields to search for logging parameters on a specific mobile application, or refine the search even further by the user ID. Once specific logging parameters are found, their information can be changed if necessary.

● Mobile Application: Name of the mobile application. Use the drop-down menu to choose the correct mobile application. This is a required field to enable the search function.

● User GUID: User GUID associated with the selected mobile application● Param Name: Name of the selected parameter. Parameters are set and configured in the Configuration portal.● Search button: Click Search once all required and additional search parameters are set. If the search returns


When you click Search in the Basic Search Parameters section, the Search Result table is populated. You can also click Create to create a new runtime parameter in this section. In this case, it is not necessary to search for an existing runtime parameter.



Basic Info Section

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each

mobile application assigned in SAP.● SAP User ID: User ID assigned in SAP● Param. Name: Name assigned to the logging parameter● Parameter Group: A read-only field that displays the system category of the parameter group● Param. Value: A numerical value corresponding to logging levels:

○ 0 - No logging○ 1 - Abort○ 2 - Error○ 3 - Warning○ 4 - Info○ 5 - Debug○ 6 - Trace

● Active Flag: Check this box in order to enable the logging levels set through this panel. Uncheck to disable the logging levels set through this panel and to return to the logging levels set through the Technical Settings panel in the Configuration Panel.

● Effective Date / Time: Date and time the logging level change will take affect● Duration (Hrs): Duration, in hours, of the logging level change

5.4.4 Administration - Parameter Management

NoteParameters are set and configured in the Parameters tab in the Mobile Application Configuration section of the Configuration Panel.

The Parameter Management panel replaces the parameters found within the JavaBE.ini file in previous releases of the application. Parameters control the application runtime behavior of the Java back end component. Parameter management works in conjunction with back end support and provides remote diagnostic capabilities and configuration of the application at a user level.

Use the Parameter Management panel to override parameter settings in a production environment for a specific user or for the whole application, depending on the selection you make for the Parameter Scope. This will not change application settings, but rather user settings for the selected parameter and the selected user. In this way, you can diagnose issues and troubleshoot without the need for users to reset their Client when problems occur.


Administration - Parameter Management


Use these fields to search for mobile application parameters on a specific mobile application, or refine the search even further by the user ID. Once specific parameters are found, you can change them if necessary.


● User GUID: User GUID associated with the selected mobile application● Parameter Type: Drop-down menu to select the type of parameter● Parameter Scope: Drop-down menu to select the parameter scope● Parameter Name: Drop-down menu to select the name of the parameter● Search button: Click Search once all required and additional search parameters are filled. If the search returns


When you click Search in the Basic Search Parameters section, the Search Result table is populated. You can click Create to create a new runtime parameter in this section. In this case, it is not necessary to search for an existing runtime parameter.



Runtime Parameter Detail - Basic Info

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● Parameter Type: Type of parameter, selected from a drop-down list.● Parameter Scope: Scope of parameter, selected from a drop-down list.● User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each

mobile application assigned in SAP.● SAP User ID: User ID assigned in SAP● Parameter Group: Identifies the system category of the parameter group. Parameter groups are set and

configured in the Configuration portal.● Parameter Name: Identifies the name assigned to the parameter. Parameter names are set and configured in

the Configuration Panel.● Comment: Any comments entered about the parameter● Parameter Value: The value assigned to the parameter through the Configuration portal.● Active Flag: Check this box in order to enable the parameter. Uncheck to disable.● Effective Date / Time: Effective date and time of the parameter change● Duration (Hrs): Duration, in hours, of the parameter change

5.5 Administration Portal - Monitoring

Use the Monitoring panel to monitor the following areas:

● User Monitor● Push Instance Monitor● Communication Session Monitor● Object Mobile Status Monitor● Mobile Transaction History Monitor● Subscription Queue Monitor

The Monitoring panels are only used for monitoring users and activity. An administrator cannot create new information or change existing information through these panels. To create or modify information, navigate to the appropriate panel in the Admin Portal and save the changes.

5.5.1 Administration Portal - Settings

All of the screens in the Administration Portal contain a Settings link in the Search Result section. Configuring the settings for results display can assist in filtering and sorting user data, especially if there are many user results returned in a search.

To access the Settings section, click Settings at the top right of the Search Result section. This opens the Settings view.


NoteEach of the portal screens requires individual setup of the settings.

● View: If multiple views are saved, use the drop-down menu to select the appropriate view to change.● Save As button: Use this button to save the particular configuration created or modified with a descriptive title.

Use the View drop-down menu in the Search Result section to select the desired view. The created view is available in all Settings tabs.

● Delete button: If a view is no longer needed, select the view in the drop-down menu and click Delete.● Properties button: Click this button to display view properties or to rename the view.● OK button: When done with configuration in the tabs, click OK to change the settings in the Search Result table

or test the printing configuration. When you click OK, the changes are not yet committed permanently.● Cancel button: Click this to cancel any changes made during the configuration session.● Apply button: Click Apply when all configuration is finished and tested. When you click Apply, the changes are

committed so they are available from session to session.

Column Selection Tab

The Column Selection tab allows you to configure the columns and the results that are displayed in the search result table.

Management Settings - Column Selection



Sort Tab

At times, a search performed by using the standard Basic Search Parameters can result in a large amount of information displayed. Use the Sort tab to determine which columns are used to sort the information, depending on the needs of the administrator. The sorting function works in that the first row in the Sorted Columns is the primary source for sorting. Each additional row refines the sorting further. For instance, if a user is active on more than one server, sort by User Name and then Server Serial No to display that user’s activity in order of the serial number.

Filter Tab

Administrators can create different filters in order obtain a more detailed view from the search results. When the filter is no longer needed on the search results table, click Delete Filter.

Display Tab

Use the Display tab to control how the table in the Search Result section displays. You can define the following items:

● Displayed Rows● Displayed Columns● Table Design● Grid Lines

Print Version Tab

Use the Print Version tab to configure basic print settings, such as margins, paper size, orientation, and so on.

5.5.2 User Monitor

The User Monitor panel allows an administrator to locate and view specific users and mobile application use. An administrator can also send specific users’ email to their mobile devices or HTTP addresses through this panel.

NoteThe Client Registration Info tab is for RIM products only and will not be covered in this manual.


Monitoring - Mobile User Monitoring


● Mobile Application: Name of the mobile application. Use the drop-down menu to choose the correct mobile application.

● User: SAP user ID. Manually type in the SAP user ID or click the white box icon to the right of the field for optional search methods.

● Last Activity Time: Use the drop-down menu to select a window of time. The default is set to All, which is equal to selecting all activity times. All times are available unless the historical logs have been purged in SAP.

● User GUID: User GUID assigned to their mobile device.● Search: Click Search to initiate the search process. If no results are valid in the search parameters, the

message No Data Found displays in the Search Results table. If valid data is returned, it displays in the Search Results table according to the Settings and Filter setup configured by the administrator.

● Send Email: Press to start the Send System Emails action.

When you click Search in the Basic Search Parameters section, the Search Result table is populated based on the parameter settings you selected..



General Info Tab

The General Info tab displays detailed information about the specific user highlighted in the Search Results table.

Mobile User Detail - General Info

● User Name: SAP User ID● User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each

mobile application assigned in SAP.● Personnel Number: User ID number assigned to the user in SAP● Middleware User Group ID: Group ID assigned to the specific user through the User Management panel in the

Administration portal● Lock Flag: If checked in the User Management panel, the user is unable to access the mobile application from

the mobile device. This is used if a mobile device is lost or stolen and the application data must be made inaccessible.

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● Middleware Svr SerNo: Server serial number of the middleware server that is running the chosen mobile

application

Client Object Info Tab

The Client Object Info tab displays everything that is contained on the client device associated with a specific mobile user GUID as of the last transmit.


Mobile User Detail - Client Object Info

● Object GUID: Internal identifier of the record● Middleware Object Ty: Type of object, such as notification or work order● Middleware Object Ky: Object key, or ID of the object● Changed Time Stamp: Time and date the object was entered into the system

NoteFor details on how to disable and re-enable items, see the topic “Disabling and Re-enabling Contacts, Transactions, and FactSheets” in the “Common Changes” chapter.

Cross Reference List Tab

When a user creates an object on their mobile device, that object generates a local key. Upon the next transmit, SAP assigns a key to the object and maps the newly-assigned object key to the old local object key that was generated by the client device. The cross reference list displays the object GUIDs for a mobile application on a mobile device and their local object keys mapped to their SAP object keys.




● MDW Reference GUID: Standard internal ID of the record● Middleware Object Ty: Object type, such as work order or notification● Source Object Ky: Object key originating from the client device, which is then mapped to the key assigned to

the object by SAP● Target Object Ky: Key that SAP assigns to the object, which is then mapped to the key originating from the

client device

Outbound Message Queue Tab

The Outbound Message Queue tab displays all messages in the SAP outbound message queue sent through the client device associated with the user and their mobile application highlighted in the Search Results table.

Mobile User Details - Outbound Message Queue

● Message GUID: GUID assigned to the message when it was created● Channel ID: Channel for the outbound message that identifies the source of the message● Message No.: Readable identifier of the message as an incremental integer● Data Package ID: The data package identifier, if a data package is associated with the outbound message● Expiration Time: Time set for the message to expire● Message Status: Status of the message. Statuses include New, Read, Send, and Confirm.● Confirmation Time: Time the message was successfully received on the device


● Read Time: Time the message was opened, or read, on the device● Send Time: Time message is sent from the mobile device● Creation Time Stamp: Time message was created, or started, on the system

Communication Sessions Tab

The Communication Sessions tab displays all transmissions associated with the user and the mobile application highlighted in the Search Results table.

Mobile User Detail - Communication Sessions

● Session GUID: Internal identifier of the session● Server GUID: Identifier of the server on which the user initiated the session● Active Flag: Indicator that a user stayed connected to the server throughout the session. If a client remains

connected, the active flag is shown as 1.● Close Time Stamp: Time and date the session was ended● Creation Time Stamp: Time and date the session was initiated

Client Registration Info Tab

The Client Registration Info tab is only used by legacy applications with Blackberry devices.

5.5.2.1 Mobile User Detail - General Info

The General Info tab displays detailed information about the specific user highlighted in the Search Results table.



Mobile User Detail - General Info

● User Name: SAP User ID● User GUID: User GUID for the specific mobile application chosen. Each user has a different GUID for each

mobile application assigned in SAP.● Personnel Number: User ID number assigned to the user in SAP● Middleware User Group ID: Group ID assigned to the specific user through the User Management panel in the

Administration portal● Lock Flag: If checked in the User Management panel, the user is unable to access the mobile application from

the mobile device. This is used if a mobile device is lost or stolen and the application data must be made inaccessible.

● Mobile Application: Name of the mobile application chosen in the Basic Search Parameters section● Middleware Svr SerNo: Server serial number of the middleware server that is running the chosen mobile

application

5.5.2.2 Mobile User Detail - Client Object Info

The Client Object Info tab displays everything that is contained on the client device associated with a specific mobile user GUID as of the last transmit.

Mobile User Detail - Client Object Info


● Object GUID: Internal identifier of the record● Middleware Object Ty: Type of object, such as notification or work order● Middleware Object Ky: Object key, or ID of the object● Changed Time Stamp: Time and date the object was entered into the system

NoteFor details on how to disable and re-enable items, see the topic “Disabling and Re-enabling Contacts, Transactions, and FactSheets” in the “Common Changes” chapter.

5.5.2.3 Mobile User Detail - Cross Reference List

When a user creates an object on their mobile device, that object generates a local key. Upon the next transmit, SAP assigns a key to the object and maps the newly-assigned object key to the old local object key that was generated by the client device. The cross reference list displays the object GUIDs for a mobile application on a mobile device and their local object keys mapped to their SAP object keys.


● MDW Reference GUID: Standard internal ID of the record● Middleware Object Ty: Object type, such as work order or notification● Source Object Ky: Object key originating from the client device, which is then mapped to the key assigned to

the object by SAP● Target Object Ky: Key that SAP assigns to the object, which is then mapped to the key originating from the

client device

5.5.2.4 Mobile User Detail - Outbound Message Queue

The Outbound Message Queue tab displays all messages in the SAP outbound message queue sent through the client device associated with the user and their mobile application highlighted in the Search Results table.



Mobile User Details - Outbound Message Queue

● Message GUID: GUID assigned to the message when it was created● Channel ID: Channel for the outbound message that identifies the source of the message● Message No.: Readable identifier of the message as an incremental integer● Data Package ID: The data package identifier, if a data package is associated with the outbound message● Expiration Time: Time set for the message to expire● Message Status: Status of the message. Statuses include New, Read, Send, and Confirm.● Confirmation Time: Time the message was successfully received on the device● Read Time: Time the message was opened, or read, on the device● Send Time: Time message is sent from the mobile device● Creation Time Stamp: Time message was created, or started, on the system

5.5.2.5 Mobile User Detail - Communication Sessions

The Communication Sessions tab displays all transmissions associated with the user and the mobile application highlighted in the Search Results table.

Mobile User Detail - Communication Sessions

● Session GUID: Internal identifier of the session● Server GUID: Identifier of the server on which the user initiated the session● Active Flag: Indicator that a user stayed connected to the server throughout the session. If a client remains

connected, the active flag is shown as 1.● Close Time Stamp: Time and date the session was ended


● Creation Time Stamp: Time and date the session was initiated

5.5.2.6 Mobile User Detail - Client Registration Info

The Client Registration Info tab is only used by legacy applications with Blackberry devices.

5.5.3 Push Instance Monitor

The Push Instance Monitor panel allows an administrator to search for and view details of push instances by specific mobile applications.

Monitoring - Push Instance Monitor



● Scenario ID: Type of push, selected from the drop-down menu, to search for in the pushes in the application● Time Limit: Use the drop-down menu to select a window of time. The default is set to All, which is equal to

selecting all push instances. All instances are available unless the historical logs have been purged in SAP.● Recipient User ID: User ID receiving the push● Status Included: Status of the push instance on the middleware server. Choosing no status returns all push

instances on the mobile application. Multiple statuses can be chosen for the search. The following are the different status levels and their meanings:



○ NEW - Set when data in SAP has changed and the system configuration indicates that a push process is needed. No other information is available or set when status is in the NEW stage.

○ ENQUEUE - Set when the push process program is running on the data that triggered the push process. During this time, the data is locked so that it cannot be changed during the push process.

○ PROCESS - Standard status. The push process agent processes the instance in the push register and determines the proper recipients of the push data. The push data have been prepared for each recipient in the outbound queue in order for Agentry to pick it up.

○ CANCEL - Set for a push instance if there are subsequent newer push instances in the push register for the same work order. In this case, only the last push instance is processed in order to prevent multiple pushes for the same work order sent to the same mobile device.

○ COMPLETED - Set when either no recipient is determined or all push recipients for the push have CLNT_CONF status with respect to the recipient’s push message.

○ SRV_COMP - Set for a push instance when all recipients have SRV_CONF status with respect to the individual push recipient’s push message. If there are multiple push messages for the same work order and the recipients are waiting for Agentry to pick up the work orders, only the latest push event is sent to Agentry and the rest are set to SRV_CONF automatically by the push fetch BAPI. This prevents multiple copies of the same work order sent to each client.

● Max. No. of Records: Default is set to 2,000. Type in maximum number of records returned.● Search: Click Search to initiate the search process. If no results are valid in the search parameters, the

message No Data Found displays in the Search Results table. If valid data is returned, it displays in the Search Results table according to the Settings and Filter setup configured by the administrator.

When you click Search in the Basic Search Parameters section, the Search Result table is populated, based on the parameter settings you selected.

Subscriber View Tab

The Subscriber View tab on the Push Instance Monitor panel provides a recipient list containing all users and detailed information about the push instance associated with their user IDs.

Push Instance Detail - Subscriber View

● User Name: Name of user who received the push instance● Current Status: Status of the push instance at the time the search was performed● Creation Time: Time the push instance was created● Client Confirmation Time: Time and date that the client confirms it has received the push


● Server Confirmation Time: Time and date when the middleware server confirmed it received the push in its cache

● Cancellation Time: Time and date of a manual or automatic cancellation of a push. For example, if a new push is created, the old pushes can be manually cancelled, as they are now out of date.

● Expiration Time: Time and date of a push expiration. If a client does not pick up a push before it expires, it is shown here.

● Middleware Server Connection By User: Name of the Agentry server that the user is connected to.● Outbound Message ID: Message ID● Internal Package ID: Data package ID● OTrigger Proc. Time: Time and date when the outbound trigger was processed

Push Scenario Info Tab

The Push Scenario Info tab on the Push Instance Monitor panel provides technical information about the selected push instance highlighted in the Search Result table. Information displayed in this tab is created and configured using the Configuration portal, Push Scenario Definitions panel.

Push Instance Detail - Push Scenario Info

● Scenario ID: Name of the push instance scenario● Validity (Hr): Hours that the push scenario remains valid after the initial push to clients● Mobile Application: Name of the mobile application where the push instance resides● Source Type: Type of source object associated with the push scenario● Source Object: Name of the mobile data object that contains the push scenario. The source object is created

or modified in the Mobile Data Object configuration panel in the Configuration portal.● Source Handler: Class handler associated with the source object for the push scenario● Subscriber Type: Corresponds to the Subscriber Type in the Subscriber Settings section of the Push Scenario

Definition panel in the Configuration portal.● Distribution Type: Corresponds to the Distribution Type in the Distribution Settings section of the Push

Scenario Definition panel in the Configuration portal. MDO, or mobile data object, is the only setting available.● Distribution Object: Name of the distribution object that is set in the Distribution Settings section of the Push

Scenario Definition panel in the Configuration portal.● Distribution Handler: Name of the distribution handler associated with the mobile data object contained in the

push instance. The distribution handler is selected or changed in the Mobile Data Object Configuration panel, General Setting tab in the Configuration portal.



5.5.3.1 Push Instance Monitor - Subscriber ViewThe Subscriber View tab on the Push Instance Monitor panel provides a recipient list containing all users and detailed information about the push instance associated with their user IDs.

Push Instance Detail - Subscriber View

● User Name: Name of user who received the push instance● Current Status: Status of the push instance at the time the search was performed● Creation Time: Time the push instance was created● Client Confirmation Time: Time and date that the client confirms it has received the push● Server Confirmation Time: Time and date when the middleware server confirmed it received the push in its

cache● Cancellation Time: Time and date of a manual or automatic cancellation of a push. For example, if a new push

is created, the old pushes can be manually cancelled, as they are now out of date.● Expiration Time: Time and date of a push expiration. If a client does not pick up a push before it expires, it is

shown here.● Middleware Server Connection By User: Name of the Agentry server that the user is connected to.● Outbound Message ID: Message ID● Internal Package ID: Data package ID● OTrigger Proc. Time: Time and date when the outbound trigger was processed

5.5.3.2 Push Instance Monitor - Push Scenario InfoThe Push Scenario Info tab on the Push Instance Monitor panel provides technical information about the selected push instance highlighted in the Search Result table. Information displayed in this tab is created and configured using the Configuration portal, Push Scenario Definitions panel.

Push Instance Detail - Push Scenario Info


● Scenario ID: Name of the push instance scenario● Validity (Hr): Hours that the push scenario remains valid after the initial push to clients● Mobile Application: Name of the mobile application where the push instance resides● Source Type: Type of source object associated with the push scenario● Source Object: Name of the mobile data object that contains the push scenario. The source object is created

or modified in the Mobile Data Object configuration panel in the Configuration portal.● Source Handler: Class handler associated with the source object for the push scenario● Subscriber Type: Corresponds to the Subscriber Type in the Subscriber Settings section of the Push Scenario

Definition panel in the Configuration portal.● Distribution Type: Corresponds to the Distribution Type in the Distribution Settings section of the Push

Scenario Definition panel in the Configuration portal. MDO, or mobile data object, is the only setting available.● Distribution Object: Name of the distribution object that is set in the Distribution Settings section of the Push

Scenario Definition panel in the Configuration portal.● Distribution Handler: Name of the distribution handler associated with the mobile data object contained in the

push instance. The distribution handler is selected or changed in the Mobile Data Object Configuration panel, General Setting tab in the Configuration portal.

5.5.4 Communication Session Monitor

The Communication Session Monitor panel provides an administrator a detailed history of communications on a specific mobile application. The communications monitor can provide a history for everything in the system, unless the history has been purged from SAP.

Monitoring - Communication Session History Monitor





● Server ID: Name of the middleware server● Time Limit: Use the drop-down menu to select a window of time. The default is set to All, which is equal to

selecting all communication sessions. All sessions are available unless the historical logs have been purged in SAP.

● User: SAP user ID. Manually type in the SAP user ID or click the white box icon to the right of the field for optional search methods.

● Online Session Only: Select from True or False:○ True - Picks up online-only communication sessions○ False - Picks up both online and offline communication sessions

● User GUID: User GUID assigned to their mobile device.● Max. No. of Records: Default is set to 2,000. Type in maximum number of records returned.


5.5.5 Object Mobile Status Monitor

The Data Object Mobile Status Monitor provides the administrator a history of SAP objects affected by a mobile user’s actions. The actions are recorded in SAP and the monitor panel provides a user-friendly way to access the information.

Monitoring - Data Object Mobile Status History Monitor




● Last Changed Time: Use the drop-down menu to select a window of time. The default is set to All, which is equal to selecting all mobile object change times. All logs are available unless the they have been purged in SAP.

● Object Type: Type of object defined in the mobile application definition.● Mobile Status: Historical view of status changes for the mobile object● Sort Field: Additional information about the object, if any is provided● Object Key: Internal ID of the object● Max. No. of Records: Default is set to 2,000. Type in maximum number of records returned.


5.6 Sending Email Using the Administration & Monitoring Portal

Context

At times, administrators may need to broadcast system messages or other information to a group of users or all users on the system. The Administration portal provides a way to communicate with users through email or text messages rather than through the mobile device, which may not be connected and available.

NoteUser email or HTTP addresses and preferences are set in the Administration portal, Administration menu, User Management panel.

Procedure

1. Access the Administration & Monitoring portal.2. Click on the Monitoring hyperlink at the top of the screen, and then click the User Monitor menu option in the

navigation panel.3. Click Send Email .

The Send System Emails screen displays.



4. Check or uncheck the Selected boxes for all desired mobile user GUIDs.5. Fill out the title, or header of the email.6. Type in the body of the email in the Email Content box.7. Click Send to send the email to all marked user GUIDs or Close to cancel out of the screen and discard

changes.

If the email is sent successfully, a message displays.

5.7 Administration Portal - Statistics

The Statistics panel is used to view statistics in the following three areas:

● Communication Session Statistics● Application BAPI Wrapper Call Statistics● Push Scenario Statistics

The statistics panels display graphical views of various key performance indicator (KPI) data. The Statistics panels are view-only. An administrator cannot create new information or change existing information through these panels.

There are three tabs for each statistic, each allowing a different graphical view: Daily, Weekly, and Monthly. The following examples depict a representation of each type of graph.


The Daily Chart tab shows a graphical representation of the chosen statistics broken down into hours.

Daily KPI Chart

The Weekly Chart tab shows a graphical representation of the chosen statistics broken down into days, with a total of seven days.

Weekly KPI Chart



The Monthly Chart tab shows a graphical representation of the chosen statistics broken down into days, with a total of the amount of days in the selected month.

Monthly KPI Chart

5.7.1 Retrieving and Recalculating Statistics

Context

Each panel in the Statistics section automatically displays the current date’s statistics. If statistics are needed for prior dates, use the following procedure.

Procedure

1. Click the calendar icon to the right of the date field and choose the desired date.


2. Click Refresh to refresh the statistics for the chosen date.

The new statistics graph displays in the KPI table.3. If the current date is selected, to check if the statistics have changed, click Re-calculate Statistics to

recalculate.

5.7.2 Statistics - Communication Session Statistics

The KPIs available through the Communication Session Statistics panel display information on the system operation status for the chosen date.

Statistics - Communication Session Statistics

Daily KPI Summary

● View: If the administrator sets up different views using the Settings link, the drop-down menu will display those view names. Select a different view for specific data needs.

● Print Version: If enabled, creates a PDF version of the data in the Search Results table.● Export to Microsoft Excel: Exports all data in the Search Results table to an Excel spreadsheet● Statistics Category/Characteristic Name/Characteristic Value: Use to filter statistics further. Select from the

choices available through the dropdown menus. If the field is blank, no choices are available.



● Filter/Delete Filter: If the Filter tab is utilized in the Settings window accessed by the Settings link, click Filter to display filter choices in order to further filter the data displayed. If a filter is in use, click Delete Filter to remove the filter and display all data returned by the initial search performed.

● Settings: Click this link to display a Settings panel in order to modify how search results are displayed. See the section on changing Administrator settings for more details.

● Daily KPI Summary table: Contains rows that display which statistics are available for the selected date. Highlight a row to display that graph. The graphs available are as follows:○ KPI - COMM_SESSION_LOAD: The KPI - COMM_SESSION_LOAD is a graphical representation of the

system load for the date chosen. The more sessions there are per hour, the heavier the load on the system, which could cause performance issues. Session load statistics are based on the number of sessions connecting; it does not take into account duration of the sessions.

○ KPI - CONNECTING_USER_COUNT: The KPI - CONNECTING_USER_COUNT is a graphical representation of the total users connecting to the system for the date chosen. Data gathered for this graph does not take into account a single user logging into multiple sessions; it only counts unique user IDs connecting to the system.

5.7.3 Statistics - Application BAPI Wrapper Call Statistics

The KPIs available through the Application BAPI Wrapper Call Stats panel display information on the number of BAPI calls for the chosen date. This statistical information can be useful in troubleshooting end user behaviors and use of the mobile application(s).

Statistics - Application BAPI Wrapper Call Statistics

Daily KPI Summary



choices available through the drop-down menus. If field is blank, no choices are available.


● Filter/Delete Filter: If the Filter tab is utilized in the Settings window accessed by the Settings link, click Filter to display filter choices in order to further filter the data displayed. If a filter is in use, click Delete Filter to remove the filter and display all data returned by the initial search performed.


● Daily KPI Summary table: Contains rows that display which statistics are available for the selected date. Highlight a row to display that graph. The graphs available are as follows:○ KPI - CRT_BAPI_CALL_COUNT: The KPI - CRT_BAPI_CALL_COUNT is a graphical representation of how

many BAPI calls were detected. The more calls there are per hour, the heavier the load on the backend system, which could cause performance issues. BAPI call statistics are based on the number of calls; it does not take into account what is called during the transaction process.

○ KPI - ERROR_BAPI_CALL_COUNT: The KPI - ERROR_BAPI_CALL_COUNT is a graphical representation of how many BAPI calls returned with an error message. These statistics can provide a good indicator to begin troubleshooting performance issues with the system, if necessary.

○ KPI - GET_BAPI_CALL_COUNT: The KPI - GET_BAPI_CALL_COUNT is a graphical representation of how many GET BAPI calls were made.

○ KPI - DEL_BAPI_CALL_COUNT: The KPI - DEL_BAPI_CALL_COUNT is a graphical representation of how many DELETE BAPI calls were made.

○ KPI - UPD_BAPI_CALL_COUNT: The KPI - UPD_BAPI_CALL_COUNT is a graphical representation of how many UPDATE BAPI calls were made.

○ KPI - INITSYNC_BAPI_CALL_COUNT: The KPI - INITSYNC_BAPI_CALL_COUNT is a graphical representation of initial synchronizations (i.e., all data is transmitted to a mobile device, not just data changed since last transmit) on the system. If a large amount of initial synchronization transmissions are present on the system for a specific time period, it could indicate issues with the system.

○ KPI - ALL_BAPI_CALL_COUNT: The KPI - ALL_BAPI_CALL_COUNT is a graphical representation of all BAPI calls made during the time period.

5.7.4 Statistics - Push Scenario Statistics

The KPIs available through the Push Scenario Statistics panel display the amount of pushes that occurred for the chosen date on an hourly basis. This statistical information can be useful in determining peak loads and to assess factors that drive push scenarios.



Statistics - Push Scenario Statistics

Daily KPI Summary



choices available through the drop-down menus. If field is blank, no choices are available.● Filter/Delete Filter: If the Filter tab is utilized in the Settings window accessed by the Settings link, click Filter to

display filter choices in order to further filter the data displayed. If a filter is in use, click Delete Filter to remove the filter and display all data returned by the initial search performed.


● Daily KPI Summary table: Contains rows that display which statistics are available for the selected date. Highlight a row to display that graph. The graphs available are as follows:○ KPI - PUSH_INSTANCE_LOAD: The KPI - PUSH_INSTANCE_LOAD is a graphical representation of total

number of pushes on the system.○ KPI - PUSH _INST_CANCEL_COUNT: The KPI - PUSH_INSTANCE_CANCEL_COUNT is a graphical

representation of total number of push instances with a CANCEL status.○ KPI - PUSH _AVG_TIME_CMPLETE: The KPI - PUSH_AVG_TIME_CMPLETE is a graphical representation of

the average time between when a push instance is created and when it reaches a COMPLETE status.


○ KPI - PUSH _AVG_TIME_PROCESS: The KPI - PUSH_AVG_TIME_PROCESS is a graphical representation of the average time between when a push instance is created and when it is processed by the push processor.

○ KPI - PUSH _AVG_TIME_SVR_CONF: The KPI - PUSH_AVG_TIME_SVR_CONF is a graphical representation of the average time between when a push instance is created and when it reaches SVR_CONF status.

○ KPI - PUSH _AVG_TIME_CLNT_CONF: The KPI - PUSH_AVG_TIME_CLNT_CONF is a graphical representation of the average time between when a push instance is created and when it reaches CLNT_CONF status.

○ KPI - PUSH _CLNTCNF_TIME_TOPRANK: The KPI - PUSH_CLNTCNF_TIME_TOPRANK is a graphical representation of the shortest time between when a push instance is created and when it reaches CLNT_CONF status.

○ KPI - PUSH _CLNTCNF_TIME_LOWRANK: The KPI - PUSH_CLNTCNF_TIME_LOWRANK is a graphical representation of the longest time between when a push instance is created and when it reaches CLNT_CONF status.



6 Agentry Application Project

6.1 Global Definitions

Information is provided here on the Globals defined within the Agentry application project for the SAP Inventory Manager application.

A global definition defines a constant value, including data type, for the application. This value can be referenced throughout the application, both by the attributes of other definition types and for use in synchronization components. A global value cannot be changed on the client at run-time but can be overridden during synchronization.

Globals List

Name Group Default Value Description

Counted Defaults X The default value to indicated items have been counted. Override if a different character is in use.

Decimals Defaults 2 The default precision for decimal values. Change if a different number of digits after the decimal should be kept.

DetailPanePosition Defaults Bottom The default location for detail panes on list screens displayed on the Client. Change this value to set a different position for all list screen detail panes.

DetailPaneSize Defaults 50 The default size for list screen detail panes. Change this value to change the size of all list screen detail panes.

DetailPaneWordWrap Defaults True The default word wrap behavior for all list screen detail panes. Change to false to suppress word wrap behavior in all list screen detail panes.

EnableReceipts Defaults True Flag to enable or disable receipts functionality. Set to false to disable this functionality in the application.

EnableReversals Defaults True Flag the enable or disable reversals functionality. Set to false to disable this functionality in the application.

SAP Inventory Manager Configuration GuideAgentry Application Project C U S T O M E R 125


False Defaults false The default string value for false. Change to set a different false text value. This global is provided primarily to support localization and will normally be overridden via application localization settings on the Server.

HideBin Defaults False Flag to hide or show bin information related to material locations. Set to true to hide this information on the Client.

InvalidDate Defaults 01/01/0000 The default invalid date value. Note that this default is the Agentry system default to indicate invalid or unset dates within values with a data type of date and should rarely be changed.

InvalidNumericField Defaults -1 The default invalid numeric value. This should only be changed if the default of -1 can be a valid numeric value for a specific implementation.

InvalidStringField Defaults -1 The default invalid string value. This should only be changed if the default of -1 can be a valid string value for a specific implementation.

LocalPrefix Defaults LOCAL_ The default prefix for ID values created on the Client when new object instances are added. This global is provided primarily to support localization and will normally be overridden via application localization settings on the Server.

None Defaults null The default empty value for the system. Should only be modified if null is an unacceptable empty value.

POOrderType Defaults PO The default order type value for purchase orders.

StockType Defaults F The default stock type value for material items.

True Defaults X The default string value to represent true. Change this if a differ-ent value from X is desired.


Agentry Application Project


UseDetailPane Defaults True A flag value to enable or disable the display of detail panes. Set this value to false to hide all defined detail panes.

DeliveryNote FieldLength 16 The maximum length of delivery note text.

FiscalYear FieldLength 4 The number of characters to represent year values in dates.

HeaderText FieldLength 25 The maximum number of characters for header text values.

MatNr FieldLength 18 The maximum number of characters for MatNr fields.

Plant FieldLength 4 The maximum length for plant values.

StorageLocation FieldLength 4 The maximum length for the storage location values.

UnloadingPoint FieldLength 25 The maximum length for the unloading point values.

GoodsIssue GMCode 03

GoodsReceiptForOrder GMCode 02

GoodsReceiptForPurchaseOrder GMCode 01

OtherGoodsReceipt GMCode 05

ReversalOfGoodsMovement GMCode 06

SubContractingSubsequentAdjustment GMCode 07

TransferPosting GMCode 04

OrderReceipt MovementIndicator F

POReceipt MovementIndicator B

All MovementType 291

Asset MovementType 241

CostCenter MovementType 201

InterPlantTransfer MovementType 311

IntraPlantTransfer MovementType 301

Issue MovementType 201

IssuePrefix MovementType Issue

Network MovementType 281

Order MovementType 261

OtherReceipt MovementType 501

OtherReceiptNoProdOrder MovementType 521

SAP Inventory Manager Configuration GuideAgentry Application Project C U S T O M E R 127


OtherReceiptPrefix MovementType AdHocReceipt

POReceipt MovementType 101

PoReceiptIntoBlockedStock MovementType 103

POReversal MovementType 102

ProdReceipt MovementType 111

Project MovementType 221

ReceiptPrefix MovementType Receipt

ReceiptReturnPrefix MovementType ReceiptReturn

ReturnDelivery MovementType 122

Sales MovementType 251

SalesOrder MovementType 231

Transfer MovementType 301

TransferPrefix MovementType Transfer


Agentry Application Project

7 Common Changes

This section covers the most common configuration changes necessary for SAP Inventory Manager installations.

The SAP application can be modified in several ways from the default configuration provided by the installers. Any modifications can require changes to the application project using the Agentry Editor, the Java synchronization logic in the Eclipse Java project, or the configuration panel in the Mobile Add-On for ERP. Changes are made to add or enable additional functionality, to disable or remove functionality, or to alter the behavior of default features and functionality.

During implementation, there will be changes made in almost all environments. The default implementation of SAP Inventory Manager includes the common functionality required of most implementation environments. During implementation it will likely be necessary to change certain configuration options to match the needs of the specific implementation.

In most cases, modifications are made prior to moving into a production environment. These changes can also be made post-production. Post-production modifications should be migrated to the production system only after significant testing and according to the standard migration process at the implementation site.

7.1 Activating the Warehouse Management Component

If you intend to use the Warehouse Management component, ensure that you have activated the correct B/C set:

● </SMERP/SAP_WAREHOUSE_MAN_12_REF>

After activating the B/C set, mobile application <SAP_WAREHOUSE_MANAGER_12> becomes available in the ConfigPanel.

7.2 Disabling an Old Version of the SAP Inventory Manager Application

If you are upgrading your SAP Inventory Manager application and not performing a new installation, we recommend that you disable the old application, if you no longer need it.

To disable the application:

1. In the ConfigPanel, navigate to Mobile Application Configuration General tab .2. In the Lifecycle Management section, check the Application Blocked option.3. Add an Effective Date. The effective date is the cutover date for the upgraded SAP Inventory Manager

application.

SAP Inventory Manager Configuration GuideCommon Changes C U S T O M E R 129

7.3 Disabling the Material Master UOM View

The complex table for the material master UOM can contain a large number of records. If this complex table is not required in your specific implementation, disable the complex table to improve application performance gains.

By default, the material master UOM view is on in the out of box application. However, the full material master table can take much time to load. For many customer needs, the unit of measure is found in the posted document, or from the base UOM on the material.

Disable the material master UOM view in one of following ways:

● Navigate to the Configuration Panel Mobile Data Object Configuration CT - Complex Table<Application>_MATERIAL_UOM . From the General Setting tab, uncheck the Data Object Active box.

● Navigate to the Configuration Panel Mobile Application Configuration Parameters tab . Select your application in the Defined Mobile Applications list. Find CTMaterialUOM in the parameter list (<Parameter Group:> CT_SAPOBJECT). Enter a 0 in the <Param Value> field.

7.4 Enabling Data Staging for Materials Complex Tables

Data staging provides performance gains during the initial sync for complex tables with large datasets.

There are preconfigured data staging tables delivered for the out-of-box SAP Inventory Manager application for material complex tables. Consider enabling or activating these data staging tables in the Warehouse Management component.

To activate the out-of-box configuration for data staging, take the following steps.

1. Enable the data store. Using the ConfigPanel, access the Data Store Definition screen, and find the data store definition for the required data you want to activate. Check the Active Flag checkbox for the following:○ SIM43_STORE_MATERIAL_PLANTVIEW○ SIM43_STORE_MATERIAL_SLOCVIEW○ SIM43_STORE_MATERIAL_UOMVIEW

2. Activate the supply MDOs to supply data for data store loading. Navigate to Mobile Data Object Configuration CT - Complex Table (select your MDO) General Setting tab and check the Data Object Active checkbox for the following:○ SIM43_DSTORE_MATERIAL_SLOC_VIEW○ SIM43_DSTORE_MATERIAL_PLANT_VIEW○ SIM43_DSTORE_MATERIAL_UOM

3. Activate data staging for consumer MDOs. Go to Configuration Panel Mobile Data Object ConfigurationData Staging tab for the following:○ SIM43_MATERIAL_PLANT_VIEW○ SIM43_MATERIAL_SLOC_VIEW○ SIM43_MATERIAL_UOM

For each MDO, perform the following steps:1. Check the Data Staging Supported checkbox.


Common Changes

2. Check the Activate Staging checkbox.3. Check the Enable Data Store checkbox and specify the corresponding Data Store ID.4. Set the Package Size.

7.5 Assigning Responsible Locations to Users

The User Attribute feature assigns responsible locations to users in theSAP Inventory Manager application. The feature is enabled by default.

Follow these core configuration steps to implement the user attribute feature:

1. Create the user attribute through the ConfigPanel2. Assign attribute values through the Admin Portal3. Define how to consume the data in the MDO through the ConfigPanel

Create the User Attribute through the ConfigPanel

Use the User Attributes tab of the Mobile Application Configuration section in the ConfigPanel to create new user attributes. To access the tab, navigate to ConfigPanel Mobile Application Configuration and select the User Attributes tab.


Define the Data Consumption in the Mobile Data Object (MDO)

Once you create, define, and activate the user attributes, you can then define how the data is consumed in the MDO.

1. If not already there, navigate to ConfigPanel Mobile Data Object Configuration Data Filter tab .2. Select the SAP Inventory Manager application in the Mobile Application Filter box.

3. Select Mobile Data Object CT - Complex Table <APP>_SLOC_USER in the Data Object Navigation Tree.

4. Select Get Method - GET Data Segment Filter - USER_RULE_ENABLED from the Defined Filters list.

NoteOut of the box, the USER_RULE_ENABLED filter is active for the <APP>_SLOC_USER user rule.

The complex table associated with user attributes is <APP>_SLOC_USER, and is enabled by default. You can define how the user attribute data is consumed in the MDO in any of the following ways:

1. Define the USER_RULE_ENABLED filter. For the DOF Rule Type, select Mobile User Attribute to define data that is specific to a user. The data comes from the Administration Portal. The static data defined with the other options (Syclo Filter Class Handler, Static Table Rules, and Runtime Session Data) are applicable to all users as it is application-specific, not user-specific.Check the Active Flag and populate the Rule List.

2. Define the USER_LOCATION filter. For the Table Rule Category, select Non-Static Table Rules. For the Table Filter Rule Type, select Mobile User Attribute. In the <User Attribute> field, select USER_LOCATION - User Assigned LocationsChoosing these selections checks the USER_LOCATION - User Assigned Locations rule. If TRUE (the default), the user rule is enabled and active.


Common Changes

3. Define your own class handler using the Syclo Filter Class Handler filter. You can define your own class handler for any MDO.

NoteThe following MDOs are restricted by the User Attribute feature:

● SIM43_GOODSMVT_GENERIC● SIM43_INBOUND_GOODSMVT_GENERIC● SIM43_OUTBOUND_GOODSMVT_GENERIC● SIM43_PHYSICAL_INVENTORY_GENERIC● SIM43_PO_OUTB_STOCK_TRANSFER_ORDER● SIM43_PO_STOCK_TRANSFER_ORDER● SIM43_PRODUCTION_ORDER_GENERIC● SIM43_PURCHASE_ORDER_GENERIC● SIM43_PURCHASE_REQ_GENERIC● SIM43_RESERVATION_GENERIC● SIM43_MATERAL_SLOC_VIEW● SIM43_MATERIAL_ACCOUNTING_VIEW● SIM43_MATERIAL_PLANT_VIEW● SIM43_MATERIAL_STORAGETYPE_GENERIC● SIM43_MATERIAL_UOM● SIM43_MATERIAL_WHSE_GENERIC

Assign Attribute Values to Users

Once you have defined your user attributes in the ConfigPanel, you then define the values for the attributes, and activate the attributes you plan to use. Accomplish this through the User Attributes tab of the Administration section in the Admin Portal.

Navigate to the Admin Portal Administration User Management . Select the User Attributes tab in the Mobile User Detail section of the screen.


Here, take the following steps to define and activate any applicable user attributes.

1. Select a user from the Search Result table.2. Click Change in the Mobile User Detail section.3. Click Add in the Attribute Settings area.4. Select an attribute from the Attribute Name dropdown menu. This list is populated from the list of attributes

you created in the ConfigPanel. Based on your selection, the Reference Structure field and Reference Field Name fields are populated with the appropriate data.

NoteOut of the box, the only attribute you need to define is the USER_LOCATION assignment.

Optionally, select a Plant and Storage Location from the dropdown menus, as appropriate.5. Check the Active Flag checkbox to activate the selected user attribute.

NoteYou can go back and set more user attributes to Active. You also have the option to use the same user attribute with different values for the same user.

6. When you have finished defining and activating the user attributes, click Save.


Common Changes

8 Data Distribution

This topic describes how the user parameters are set for filtering to get the most out of the data distribution for the SAP Inventory Manager application.

Data distribution defines how and what back end data is downloaded to the mobile devices. It considers various factors and criteria when determining what back end data should be downloaded to the mobile client and to the mobile user. Some common criteria include:

● Relevant business processes and business rules● User business roles in the organization● Last mobile client synchronization time with the back-end system● Back end data changes and the time of the changes● Current state of data objects on the mobile device

For the initial synchronization from the mobile device to the back-end system, the first two bullet points are considered when determining what data should be downloaded to the mobile device and for the requesting user.

For subsequent delta synchronizations from the mobile device to the back-end system, all bullet points are considered when determining what data should be downloaded to the mobile device for the requesting user.

Useful Filters for Complex Tables with Large Data Sets

Some complex tables can download large number of records to the mobile device, and therefore can impact synchronization performance. Review and take advantage of the data filters available in the ConfigPanel to restrict the dataset required to download to the device. Configuration Panel restrictions are global restrictions, then device-specific restrictions take place. Out of the box, the application is set to use the user parameters for filtering.

Some of the most common parameters are:

● Plant● Storage Location● Warehouse

NoteIf no restrictions are set, the user receives everything and user parameter settings are ignored.

SAP Inventory Manager Configuration GuideData Distribution C U S T O M E R 135

SAP Inventory Manager Feature Matrix

Mobile App Features SAP Back End Comments

Inbound

● GR purchase order● GR production order● GR for inbound delivery● GR STO

MIGO (Movement types 101, 103, 501, 521, etc.)

● Supports batch managed and serialized materials

● Supports consignment stocks

Outbound

● GI production order● GI reservations● GI outbound delivery / STO

MIGO (Movement types 351, 201, 261, 601, 631, etc.)



Goods reversals / returns MIGO (Movement types 102, 122, 352, 202, etc.)

Reversals are done by material documents

Transfers MB1B (Movement types 201, 311, etc.) SLOC to SLOC

Physical inventory M101, M104

Purchase requisition ME51N

SAP Inventory Manager with Warehouse Component Feature Matrix


Inbound

● GR purchase order● GR production order● GR for inbound delivery● GR STO

MIGO (Movement types 101, 103, 501, 521, etc.)

● Supports warehouse managed materials for putaway



Outbound

● GI production order● GI reservations● GI outbound delivery / STO

MIGO (Movement types 351, 201, 261, 601, 631, etc.)

● Supports warehouse management materials for putaway



Transfers LT01 Bin to bin

Physical inventory M101, M104 Only bin count


Data Distribution


Purchase requisition ME51N

SAP Inventory Manager and Warehouse Component Feature Matrix

Mobile App Feature SAP Back End Comments

Stock overview MMBE ● Supports warehouse managed materials


8.1 SAP ERP Transaction Codes for SAP Inventory Manager Components

Use the following table as a reference for SAP transaction codes specific to the Warehouse Management component functions.

Transaction Codes Definition

MIGO PO receipt

Goods issue for production order and service order

Goods movement for reservation

MIGO / MB1B Transfer posting

MIGO / MB1A Miscellaneous goods issue

MB23 Reservation

VL02 Picking

VL36 Display pick list

VL02N Delivery PGI

LT01 Transfer order creation

Transfer order difference

LT01 / LT10 Bin to bin transfer



LT11 / LT12 Transfer order confirmation

LT1B / LT1C Transfer order confirmation - picking

LT1C / LT1E Transfer order confirmation - transfer

LS24 / LS26 Warehouse Management stock overview

LX26 Warehouse Management cycle ad hoc document

LI11N Warehouse Management cycle count

Warehouse Management cycle recount

LI20 Warehouse Management count - clear difference

Use the following table as a reference for SAP transaction codes specific to the Material Management component functions.


CO03 Display production order

ME21N Create purchase order

Create STO

ME23N Display purchase order

Display STO

MIGO Goods movement

GI goods movement

GR goods movement

TR material transfer

STO movement

STO transfer

MI01 Create physical inventory

MI02 Change physical inventory

MI03 Display physical inventory

MI04 Enter inventory count

MI05 Change inventory count

MI06 Display inventory count


Data Distribution


MI24 Display physical inventory documents


9 Using the Mobile Application Comparison Report Utility

The Mobile Application Comparison Report Utility allows you to compare configuration differences between two mobile applications, two mobile application BC sets, or a mobile application and a BC set. It also allows you to compare across clients.

Use tcode SA38 to program ‘/SYCLO/CORE_MAPP_COMPARE_PROG’.


Using the Mobile Application Comparison Report Utility

The following is a sample selection screen for the report:

In the sample selection screen above, you are comparing the configuration difference between mobile applications "SAP_WORK_MANAGER_61" and "SAP_WORK_MANAGER_62". The reference patterns SWM61 and SWM62 are

SAP Inventory Manager Configuration GuideUsing the Mobile Application Comparison Report Utility C U S T O M E R 141

considered equal during comparison, as shown below.


Using the Mobile Application Comparison Report Utility

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP Inventory Manager Configuration GuideImportant Disclaimers and Legal Information C U S T O M E R 143

go.sap.com/registration/contact.html

© 2018 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. The information contained herein may be changed without prior notice.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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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.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. All other product and service names mentioned are the trademarks of their respective companies.Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/about/legal/trademark.html

sap inventory manager configuration guide

Documents