Mobile Add-On For S/4HANA Installation Guide

PUBLIC
SAP S/4HANA Mobile Add-On

Document Version: 1.0 SP08 – 2021-08-25
Mobile Add-On for S/4HANA Installation Guide

© 2021 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 SAP Mobile Add-On Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
4 SAP Mobile Add-On Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5 Installing the SAP Mobile Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5.1 Preparing for Installation of the SAP Mobile Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2 Installing the SAP Mobile Add-On Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3 Post Installation - Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
5.4 Post Installation - Optional. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6 Backing up the SAP Mobile Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 PUBLIC Content
1 Document History
Before you begin reading this guide, be sure that you have the latest version. Find the latest version at SAP S/
4HANA Mobile Add-On.
The following table provides an overview of the most important document changes.
Document Version Date Description of Changes
1.0 NOV 2020 Original release of the Mobile Add-On

for S/4HANA Installation Guide, version
1.0 SP08
1.0 AUG 2021 Added number ranges in Step 7 of the

Post Installation - Required [page 12]
procedure.

Document History PUBLIC 3
2 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 Asset Manager application. It is assumed that the
personnel performing the installation and setup are aware of SAP S/4HANA installation. SAP S/4HANA and
SAP setup knowledge is helpful while carrying out the steps for the mobile setup of SAP S/4HANA.
Use this installation guide along with appropriate SAP documentation, as it covers only setting up and enabling
the SAP Asset Manager application. Configuration procedures described in the guide are effective only if done
on top of the configuration procedures documented in the Administration Guide for the Implementation of SAP
Best Practices for SAP S/4HANA.
Leveraging SAP Conversion Agent Capabilities
The following functional areas are handled using standard SAP conversion agent processes and functionality:
● High availability concept

● Starting and stopping
● Software maintenance
● Support desk management
Additional functionality includes:
● System administration and monitoring for mobile

● Mobile application configuration
● Custom development
● Troubleshooting
For detailed information on these items, refer to the appropriate topics of the SAP Asset Manager Configuration
Guide.

4 PUBLIC Before You Begin
3 SAP Mobile Add-On Installation Overview
Mobile Add-On for SAP on premise systems support integration to the SAP S/4HANA and SAP ERP systems,
configuration, system administration, and monitoring.
SAP Mobile Add-On includes the following components:
● Mobile integration foundation for SAP S/4HANA

● Mobile application integration services for SAP S/4HANA
The SAP Mobile Add-On supports SAP NetWeaver ABAP 7.51 and above based systems (for a full list, see SAP
note 2471345 : Release Strategy for SAP Mobile add-on for SAP S/4HANA). The application add-on supports
standard business processes provided by the SAP S/4HANA system.
The following complex mobile applications from SAP are supported by the SAP Mobile Add-On:
● SAP Work Manager releases: 6.3, 6.4, 6.5

● SAP Inventory Manager releases: 4.2, 4.3
● SAP Asset Manager release 2.0, 3.0, 4.0, 1911, 2005, 2010
 Note
S4MISU packages are only required for ISU functionality.
The following synchronization applications from SAP are supported by the SAP Mobile Add-On:
● Asset Central integration
The mobile add-on is backwards-compatible. Older releases of the SAP Work Manager, SAP Inventory Manager,
or SAP Asset Manager applications are supported by the latest SAP Mobile Add-On.
Installation Tasks
The installation of the SAP Mobile Add-On includes the following main tasks:
1. Verify the system requirements.

2. Prepare for installation, including downloading the software and support packages to install.
3. Install the SAP Mobile Add-On software and support packages.
4. Activate the Administration Component in the target client for the SAP S/4HANA system.
5. Define and schedule background jobs that maintain the synchronization components within the
Integration Framework.
Once the installation of the SAP Mobile Add-On, as well as the other software components within the SAP
S/4HANA-based mobile solution is complete, the standard functionality as provided by SAP is available.

SAP Mobile Add-On Installation Overview PUBLIC 5
4 SAP Mobile Add-On Requirements
The following software and support package requirements are the minimum versions of the listed items
required for the SAP Mobile Add-On Administration Component installation to the SAP S/4HANA system.
Verify that these minimum software versions are met before installing the SAP Mobile Add-On. Later versions
of these components are fully supported; these items represent only the minimum versions.
Software Requirements
Software Component Release Support Package
SAP_ABA 75B SP01
SAP_GWFND 751 SP01 or higher
SAP_BASIS 751 SP01
S4CORE 101 SP01
IS_UT* 801 SP01 or higher
*Component is only required if you are using the Utilities industry functionality
Software Component Release Support Package
SAP S/4HANA on-premise edition 1610 Feature Pack Stack (FPS) 01 or higher
SAP S/4HANA on-premise edition 1709 1709
SAP S/4HANA on-premise edition 1809 1809
SAP S/4HANA on-premise edition 1909* 1909*
* Running SAP Asset Manager in SAP S/4HANA on-premise edition 1909 or later does not require SAP Mobile
Add-On installation. The Mobile Add-On Integration Framework used by SAP Asset Manager is included as part
of SAP S/4HANA 1909 on-premise edition

6 PUBLIC SAP Mobile Add-On Requirements
5 Installing the SAP Mobile Add-On
Prerequisites
● An SAP NetWeaver ABAP-based system is required to install the SAP Mobile Add-On
 Note
We recommend performing an embedded deployment for your SAP Gateway system when you install
the SAP Mobile Add-On.
● Ensure that you have the current versions of kernel, TP, and R3trans
● Current SPAM / SAINT update: Compare the short text of the last SPAM / SAINT update you imported
with the SPAM / SAINT update in the SAP Service Marketplace. If the version of the SPAM / SAINT update
in the SAP Service Marketplace is more recent, import the update.
● Verify that the required software components have been installed, as listed in the system requirements for
the SAP Mobile Add-On Administration Component
● Ensure that your security settings to trust the Cloud Connector certificate are configured properly. For
more information, see Configure Principal Propagation to an ABAP System for HTTPS.
● No SAP password is required
SAP Mobile Add-On Additional Information
 Note
For SAP S/4HANA on-premise edition 1909 or higher systems, no ABAP SAP Mobile Add-On installation is
required.
If you are running SAP Asset Manager 2005, upgrade your 1909 system to FPS02.
● Space required in the transport directory: Approximately 35 MB

● Total runtime: Approximately 0.5 hours
S4MFND Installation and Upgrade Package Information

● S4MFND 100 installation and upgrade package:
○ <SAPK-100AHINS4MFND.SAR>
● S4MFND 100 SP01:
○ <SAPK-10001INS4MFND.SAR>
● S4MFND 100 SP02:
● S4MFND 100 SP03:

Installing the SAP Mobile Add-On PUBLIC 7
● S4MFND 100 SP04:
● S4MFND 100 SP05:
● S4MFND 100 SP06:
● S4MFND 100 SP07:
● S4MFND 100 SP08:
S4MERP Installation and Upgrade Package Information
● S4MERP 100 installation and upgrade package:

○ <SAPK-100AHINS4MERP.SAR>
● S4MERP 100 SP01:
○ <SAPK-10001INS4MERP.SAR>
● S4MERP 100 SP02:
● S4MERP 100 SP03:
● S4MERP 100 SP04:
● S4MERP 100 SP05:
● S4MERP 100 SP06:
● S4MERP 100 SP07:
● S4MERP 100 SP08:
S4MISU Installation and Upgrade Package Information
 Note
SMISU packages are only required for installations using the Meter Management component.
● S4MISU 100 installation and upgrade package:

○ <SAPK-100AHINS4MISU.SAR>
● S4MISU 100 SP01 upgrade package:
○ <SAPK-10001INS4MISU.SAR>

8 PUBLIC Installing the SAP Mobile Add-On
Language Support
The SAP Mobile Add-On supports the following languages for the SAP Asset Manager application:
● zhCN - Simplified Chinese

● csCZ - Czech Republic
● enUS - English
● frFR - French
● deDE - German
● huHU - Hungarian
● itIT - Italian
● jaJP - Japanese
● koKR - Korean
● nlNL - Netherlands
● nbNO - Norwegian
The SAP Mobile Add-On supports the following languages for the SAP Work Manager, SAP Inventory Manager,
and SAP Service Manager applications:
● ar001 - Arabic
● bgBG - Bulgarian (new for 2005)
● zh_hans - Simplified Chinese
● zh_hant - Traditional Chinese
● hrHR - Croatian (new for 2005)
● csCZ - Czech Republic
● daDK - Danish
● nlBE - Dutch
● enUS - English
● frFR - French
● deDE - German
● huHU - Hungarian
● itIT - Italian
● jaJP - Japanese
● koKR - Korean
● nlNL - Netherlands
● nbNO - Norwegian
● plPL - Polish
● ptBR - Portugese

● roRO - Romanian
● RuRU - Russion (new for 2005)
● srRS - Serbian
● skSK - Slovak
● slSL - Slovenian
● esES - Spanish
● ukUK - Ukrainian (new for 2005)
Relevant SAP Notes
● SAP Note 2495578 : Release Information Note - Mobile Add-On for S/4HANA 1.0 and Support Packages
● SAP Note 2493602 : SAP Asset Manager Mobile Add-On for SAP S/4HANA Installation Master Note
Support
For any support-related inquiries for the Mobile Add-on for SAP S/4HANA Administration Component
integration, open a message at https://support.sap.com/incident using the Mobile Add-On General: MOB-
SYC-SAP component.
Procedure Overview
The following tasks comprise the installation procedure for the SAP Mobile Add-On. When this procedure has
been completed, the mobile add-on is installed to the SAP S/4HANA system and activated. This procedure also
includes the following post-installation changes or additions:
● Activation of the B/C Set in the SAP target client

● Activation of the service for the Web Dynpro ABAP application
● Definition of the background jobs for system operation, including exchange data processing and optional
push processing
5.1 Preparing for Installation of the SAP Mobile Add-On
Procedure
1. Log on to your SAP system as client 000 and as a user that has system administrative privileges. Do not
use the SAP* or DDIC users.
2. Import the required user language or multiple languages for all components that are already installed.
Perform the language import before the installation of the SAP Mobile Add-On.

5.2 Installing the SAP Mobile Add-On Software
Context
Deploying the Mobile add-on in an SAP S/4HANA system:
 Note
Running SAP Asset Manager in SAP S/4HANA on-premise edition 1909 or later does not require SAP
Mobile Add-On installation. The Mobile Add-On Integration Framework used by SAP Asset Manager is
included as part of SAP S/4HANA 1909 on-premise edition.
If you are using SAP S/4HANA on-premise edition 1909 or later, you do not need to complete the following
procedures:
● Post Installation - Required [page 12]

● Post Installation - Optional [page 18]
● Install and configure the SAP S/4HANA system with release 1610, minimum of FPS01. Refer to the
appropriate documentation on the S4/HANA on-premise 1610 FPS01 page.
● Install and configure the mobile add-on software component on the related SAP S/4HANA system. The
software is available for download at https://support.sap.com/en/my-support/software-downloads.html
, Release, Upgrade, and Maintenance Product Availability Matrix . Then search for your product.
Procedure
1. Load the software package into your system through the add-on manager, using the transaction code
SAINT.
For more information about loading software packages, see the online documentation for the add-on
installation tool. Select the help function in the application toolbar and navigate to Online Documentation
Loading Installation Packages .
2. Start the installation of the SAP Mobile Add-On using the add-on installation tool, accessed from the
transaction SAINT.
For more information about the add-on installation tool, see the online documentation by selecting the
Help function on the toolbar.
The add-on installation tool imports the ABAP add-on installation packages from your DVD or the SAP
Service Marketplace into your SAP system landscape. For more information, see the following SAP note:
○ 2471345 : Release Strategy for SAP Mobile add-on for SAP S/4HANA
3. Required support packages for each mobile application are found in the documentation for the
corresponding mobile application.

5.3 Post Installation - Required
Prerequisites
We recommend that you run the SAP Mobile Add-On on an embedded deployment of the SAP Gateway for
performance reasons. However, the SAP Mobile Add-On is available for both embedded deployment and
gateway hub deployment landscapes.
Meet the following requirements to access the SAP Mobile Add-On on-premise from the gateway OData
services for SAP S/4HANA 1610 FPS 01+ installations with the SAP Gateway activated in an embedded
deployment:
● The SAP Gateway is activated (see Configurations on SAP Gateway Hub).

● The SAP system has idempotent services configured (see Settings for Idempotent Services).
Meet the following requirements to access the SAP Mobile Add-On for ERP from the gateway OData services
for SAP ERP 6.0 EHP 7 SP14 installations with the SAP Gateway activated in a Gateway hub deployment:
● The SAP Gateway is activated (see Configurations on SAP Gateway Hub)

● The SAP Gateway system aliases are configured (see Configurations on SAP Gateway Hub)
● The SAP system has idempotent services configured (see Settings for Idempotent Services).
Context
As a part of the post installation procedure, there are both required and optional tasks. The following procedure
covers the required tasks, which include activating both the BC set and the service for the Web Dynpro ABAP
application, the definition of intervals for certain number objects, and the configuration of the exchange table
purge background job, and the activation of gateway OData services.
 Note
If the SAP Gateway is an embedded deployment, begin the following procedure at Step 1. If the SAP
Gateway is activated as a hub deployment, begin the following procedure at Step 2.
Procedure
1. Activate the relevant OData service for your application:

a. Log on to the target client for the SAP system application as a user with administrative privileges.
b. Start the transaction /IWFND/MAINT_SERVICE
c. Add a service from the local system alias, adding services with the following properties as necessary:

Technical Service Name Service Description External Service Name Namespace
/MERP/ SAP Asset Manager 1.0 SAP_ASSET_MAN /MERP/

SAP_ASSET_MAN AGER_10
AGER_10

AGER_20
/MISU/ SAP Asset Manager 2.0 - SAP_ASSET_MAN /MISU/

SAP_ASSET_MAN ISU extension AGER_20
AGER_20*

AGER_30

AGER_30*

AGER_40

AGER_40*
/MERP/ SAP Asset Manager 1911 SAP_ASSET_MAN /MERP/

AGER_1911
/MISU/ SAP Asset Manager 1911 - SAP_ASSET_MAN /MISU/

AGER_1911*

AGER_2005

AGER_2005*

AGER_2010


AGER_2010*
/ACI/ Asset Central data change ASSET_CEN /ACI/

ASSET_CEN notification TRAL_CHANGE_NOTIF
TRAL_CHANGE_NOTIF
/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

LINE_LOOKUP_EXT_01 lookup extension 01 LINE_LOOKUP_EXT_01



*If meter readings are enabled in the back-end system and ISU components are available, the MISU
service replaces the existing MERP SAP Asset Manager service.
d. Once you’ve added the appropriate services, set the proper system aliases.
e. Ensure that you have updated the offline oData settings. See Updating Offline Settings for SAP Asset
Manager Overview and associated topics for more information.
f. Ensure that you perform Step 7 to set the SAP Business Technology Platform Cloud Connector system
mapping.
g. Continue to Step 5.
2. Ensure that the system alias pointing to the back-end SAP system from the Gateway hub has a correct RFC
configuration in the back end. See the Configurations on SAP Gateway Hub topic for more information.
3. Ensure that trust relationships are correctly established between the Gateway hub and the SAP ERP back
end. See the Configurations on SAP Gateway Hub topic for more information.
4. Activate the relevant OData service for your application:
a. Log on to the target client for the SAP S/4HANA Gateway system as a user with administrative
privileges.
b. Start the transaction /IWFND/MAINT_SERVICE.
c. Add a service from the system alias with the mobile add-on installed, adding services with the following
properties as necessary:

AGER_10


AGER_20

AGER_20*

AGER_30

AGER_30*

AGER_40

AGER_40*

AGER_1911

AGER_1911*

AGER_2005

AGER_2005*

AGER_2010

AGER_2010*




/ACI/ Asset Central data change ASSET_CEN /ACI/

ASSET_CEN notification TRAL_CHANGE_NOTIF
TRAL_CHANGE_NOTIF
*If meter readings are enabled in the back-end system and ISU components are available, the MISU
service replaces the existing MERP SAP Asset Manager service.
5. Activate the relevant BC (Business Configuration) set for your application.

a. Log on to the target client for the SAP S/4HANA application as a user with administrative privileges.
b. Start the transaction. SCPR20.
c. Activate the appropriate BC set from the following options:
SAP Asset Central BC set options:
○ /ACI/ASSET_CENTRAL_INTEGRATION
SAP Asset Manager 2010 BC set options:
○ Base SAP Asset Manager 2010 standard configuration:

○ /MERP/SAP_ASSET_MANAGER_2010_REF
○ SAP Asset Manager 2010 with the Meter Management component running the IS-Utility solution:
○ /MISU/SAP_ASSET_MANAGER_2010_REF


SAP Asset Manager 4.0 BC set options:
○ Base SAP Asset Manager 4.0 standard configuration:


○ SAP Asset Manager 4.0 with the Meter Management component running the IS-Utility solution:



6. Activate the services for the Web Dynpro ABAP applications.
a. Start transaction SICF.
b. Activate all services under the node default_host/sap/bc/webdynpro/Syclo.
7. For installs (not upgrades): Define intervals for the following number range objects when relevent:
a. Start transaction SNRO.
b. Enter the number range for object /MFND/CS1.
Interval 01, Value 0000000001 ~ 0199999999: Client State record number (required for SAP Asset
Manager implementation)
c. Enter the number range for object /MFND/DQ1.
Interval 01, Value 0000000001 ~ 0199999999: Dependent Object Queue record number (required for
SAP Asset Manager implementation)
d. Enter the number range for object /SMFND/SY1.
Interval 01, Value 0000000001 ~ 0199999999: Synchronization Object Link record number (required
for Asset Central integration)
e. Enter the number range for object /SMFND/DS1.
Interval 01, Value 0000000001 ~ 0199999999: Data Staging record number

f. Enter the number range for object /SYCLO/C_2.
○ Interval 01 Value 0000000001 ~ 0099999999: Push Instance Record number (required for SAP
Asset Manager installation)
○ Interval 03 Value 0200000000 ~ 0299999999: Inbound Transaction record number (required for
SAP Asset Manager and Asset Central installation)
○ Interval 04 Value 0300000000 ~ 0399999999: Subscription Queue record number (required if
any Push Scenario has a Subscriber Type configured for Subscription Queue)
8. Define the background job: Exchange table purge
a. Define a variant for the program /SYCLO/CORE_EXCH_PURGE_PROG with the Mobile Application
attribute set to the application you’re installing. For example, SAP_ASSET_MANAGER_2005.

b. Define a periodic background job for the /SYCLO/CORE_EXCH_PURGE_PROG program with transaction
code SM36, using the variant defined in the previous step. Set the frequency so purges are performed
daily.
9. Create OData offline configuration settings:
a. Start transaction SE38
b. Execute report /MERP/CORE_OFFLINE_CONFIG_PROG with variant SAP&SAM_2005
c. Download the resulting .ini file to a local folder. Then upload the .ini to the offline feature of SAP
Business Technology Platform mobile services.
10. Create OData offline configuration settings:
11. For additional information, see the following:
○ SAP Note 2493602 : SAP Asset Manager Mobile Add-On for S/4HANA 1.0 Installation Master Note
○ SAP Note for SAP Asset Manager: 2471345 : Release Strategy for SAP Mobile Add-On for SAP S/
4HANA
○ SAP Note for 2977434 : SAP Asset Manager: Mobile Application Integration Framework for S/
4HANA OP Installation Master Note
○ Updating Offline Settings for SAP Asset Manager Overview
5.4 Post Installation - Optional
Context
The following post installation tasks cover the definition of background jobs and are optional based on the
desired functionality for the implementation. Following is a list of these optional tasks and the situations in
which they should be defined:
● Define Background Job: Push Scenario

● Define Background Job: Server Side Paging Purge:
● Define Background Job: Client State Purge
● Define Background Job: Dependent Object Queue Purge
The details on defining each of these jobs is provided the following procedure. You do not need to define all of
the background jobs, and you can skip the background jobs not applicable to your implementation.
Procedure
1. Define Background Job: Push Scenario

a. Define a variant for program /SYCLO/CORE_PUSH_PROC_PROG with the Mobile Application attribute
set to the mobile application you are installing.
b. Define a job for /SYCLO/CORE_PUSH_PROC_PROG as either a periodic job or a trigger by event job with
transaction SM36, using the variant from the previous substep. For a periodic job, set the frequency
according to the requirements of the push processing. This interval defines the frequency for object
pushes to the client applications. For a trigger by event job, the event is /SYCLO/

BACKGROUND_JOB_EVENT with a parameter value of EXCHOBJ_PUSH_EVENT. If the event does not
exist in the system, define a custom event of /SYCLO/BACKGROUND_JOB_EVENT using transaction
code SM64.
 Note
○ If you are using the SAP Mobile Add-On for the SAP Asset Manager application, see the procedure
Activating Push Services for SAP Asset Manager.
○ If you are using the SAP Mobile Add-On for the SAP Asset Manager application, see the Push
Scenario Definition topic.
○ If you are using the SAP Mobile Add-On for the SAP Work Manager application, see the procedure
Configuring Push and the related subprocedures.
2. Define Background Job: Server Side Paging Purge

a. Define a variant for program /MFND/CORE_SVR_PAGE_PURGE_PROG with the Mobile Application
attribute set to the application you are installing.
b. Define a periodic background job for program /MFND/CORE_SVR_PAGE_PURGE_PROG with transaction
code SM36, using the variant defined in the previous substep.
3. Define Background Job: Client State Purge
a. Ensure that you have implemented SAP Note2660262 : Client State Purge Utility Does Not Support
Purging Inactive Records Only.
b. Define a variant for program /MFND/CORE_CLNT_ST_PURGE_PROG with the options Active Client State
Only, All Client States and Test Run deselected.
c. Define a job for /MFND/CORE_CLNT_ST_PURGE_PROG as either a periodic job or a trigger by event job
with transaction SM36 using the variant from the previous substep. For a periodic job, set the
frequency according to the requirements of the client state purge. The interval defines the frequency
with which previously processed client states are removed from the database.
4. Define Background Job: Dependent Object Queue Purge
a. Define a variant for program /MFND/CORE_DEPOBJ_Q_PURGE_PROG with the option Test Run
deselected.
b. Define a job for /MFND/CORE_DEPOBJ_Q_PURGE_PROG as either a periodic job or a trigger by event job
with which previously processed dependent object queues are removed from the database.
5. Define Background Job: Inbound Transaction Queue Purge
a. Define a variant for program /SMFND/IBQ_TRANS_PURGE_PROG with the option Test Run deselected.
b. Define a job for /SMFND/IBQ_TRANS_PURGE_PROG as either a periodic job or a trigger by event job
with which previously processed dependent object queues are removed from the database.

6 Backing up the SAP Mobile Add-On
Use standard SAP backup and restore procedures for the SAP Mobile Add-On. Specific procedures vary
depending on the database for the SAP system. For information, refer to the SAP Help Portal manual under
Technical Operations for SAP NetWeaver Administration of Databases . For example:
Database Administration.

20 PUBLIC Backing up the SAP Mobile Add-On
Important Disclaimers and Legal Information
Hyperlinks
Some 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.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental 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 Code
Any 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 Language
We 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.

Important Disclaimers and Legal Information PUBLIC 21
www.sap.com/contactsap
© 2021 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.
THE BEST RUN

Mobile Add-On For S/4HANA Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Add-On For S/4HANA Installation Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP S/4HANA Mobile Add-On

Mobile Add-On for S/4HANA Installation Guide

THE BEST RUN

2 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 SAP Mobile Add-On Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

4 SAP Mobile Add-On Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5 Installing the SAP Mobile Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

6 Backing up the SAP Mobile Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Mobile Add-On for S/4HANA Installation Guide

Document Version Date Description of Changes

1.0 NOV 2020 Original release of the Mobile Add-On

1.0 AUG 2021 Added number ranges in Step 7 of the

Mobile Add-On for S/4HANA Installation Guide

Leveraging SAP Conversion Agent Capabilities

● High availability concept

Additional functionality includes:

● System administration and monitoring for mobile

Mobile Add-On for S/4HANA Installation Guide

SAP Mobile Add-On includes the following components:

● Mobile integration foundation for SAP S/4HANA

● SAP Work Manager releases: 6.3, 6.4, 6.5

S4MISU packages are only required for ISU functionality.

● Asset Central integration

1. Verify the system requirements.

Mobile Add-On for S/4HANA Installation Guide

Software Component Release Support Package

SAP_ABA 75B SP01

SAP_GWFND 751 SP01 or higher

SAP_BASIS 751 SP01

S4CORE 101 SP01

IS_UT* 801 SP01 or higher

Software Component Release Support Package

SAP S/4HANA on-premise edition 1709 1709

SAP S/4HANA on-premise edition 1809 1809

SAP S/4HANA on-premise edition 1909* 1909*

Mobile Add-On for S/4HANA Installation Guide

SAP Mobile Add-On Additional Information

● Space required in the transport directory: Approximately 35 MB

S4MFND Installation and Upgrade Package Information

Mobile Add-On for S/4HANA Installation Guide

S4MERP Installation and Upgrade Package Information

● S4MERP 100 installation and upgrade package:

S4MISU Installation and Upgrade Package Information

● S4MISU 100 installation and upgrade package:

Mobile Add-On for S/4HANA Installation Guide

● zhCN - Simplified Chinese

Mobile Add-On for S/4HANA Installation Guide

Relevant SAP Notes

● Activation of the B/C Set in the SAP target client

5.1 Preparing for Installation of the SAP Mobile Add-On

Mobile Add-On for S/4HANA Installation Guide

Deploying the Mobile add-on in an SAP S/4HANA system:

● Post Installation - Required [page 12]

Mobile Add-On for S/4HANA Installation Guide

● The SAP Gateway is activated (see Configurations on SAP Gateway Hub).

● The SAP Gateway is activated (see Configurations on SAP Gateway Hub)

1. Activate the relevant OData service for your application:

Mobile Add-On for S/4HANA Installation Guide

/MERP/ SAP Asset Manager 1.0 SAP_ASSET_MAN­ /MERP/

/MERP/ SAP Asset Manager 2.0 SAP_ASSET_MAN­ /MERP/

/MISU/ SAP Asset Manager 2.0 - SAP_ASSET_MAN­ /MISU/

/MERP/ SAP Asset Manager 3.0 SAP_ASSET_MAN­ /MERP/

/MERP/ SAP Asset Manager 1.0 SAP_ASSET_MAN /MERP/

/MERP/ SAP Asset Manager 2.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 3.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 3.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 4.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 4.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 1911 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 1911 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 2005 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2005 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 2010 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2010 - SAP_ASSET_MAN /MISU/

/ACI/ Asset Central data change ASSET_CEN /ACI/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP Asset Manager 1.0 SAP_ASSET_MAN /MERP/

/MERP/ SAP Asset Manager 2.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 3.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 3.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 4.0 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 4.0 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 1911 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 1911 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 2005 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2005 - SAP_ASSET_MAN /MISU/

/MERP/ SAP Asset Manager 20010 SAP_ASSET_MAN /MERP/

/MISU/ SAP Asset Manager 2010 - SAP_ASSET_MAN /MISU/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/MERP/ SAP_ON SAP Asset Manager online SAP_ON /MERP/

/ACI/ Asset Central data change ASSET_CEN /ACI/