SAP PM Overview
SAP PM Overview
SAP PM Overview
4 How SAP Service and Asset Manager Works in a Cloud Foundry Environment. . . . . . . . . . . . . . 17
9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1 Using Logs in SAP Service and Asset Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
SAP OData Service Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Cloud Connector Log and Trace Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
SAP Cloud Platform mobile services Logs and Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
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_ASSET_MANAGER/p/en-US.
The following table provides an overview of the most important document changes.
You can submit your improvement request for SAP Service and Asset Manager to the SAP Customer Influence
site, a central place for all product improvement requests.
You can browse all improvement requests, submit improvement requests, comment, vote, receive updates, and
see who has voted at the SAP Customer Influence site.
Note
Before you submit your improvement, check if a similar improvement hasn't already been submitted. If a
similar improvement is already in the system, vote for it instead of submitting a new improvement request.
Procedure
1. Access the SAP Customer Influence site from the following link:https://influence.sap.com/sap/ino/#/
campaign/2665
2. Log in with your S-user ID.
3. Choose Improvement Request on the left panel.
4. Enter the details for your improvement request:
Field Notes
Title Enter a title that clearly states your request and area of
improvement.
Tags (Optional) Add tags that can help others find your request.
You can find a complete high-level installation process overview in the SAP Service and Asset Manager
Installation Guide.
● https://help.sap.com/viewer/20f0559b29974bc9b7b069b41176ca17/latest/en-US/
acd3742938b74528aa1b3d8a35c1a3dc.html [https://help.sap.com/viewer/
20f0559b29974bc9b7b069b41176ca17/latest/en-US/acd3742938b74528aa1b3d8a35c1a3dc.html]
● https://help.sap.com/viewer/product/IDENTITY_PROVISIONING/Cloud/en-US [https://help.sap.com/
viewer/product/IDENTITY_PROVISIONING/Cloud/en-US]
● https://help.sap.com/viewer/38dbd9fbb49240f3b4d954e92335e670/Cloud/en-US/
d2a9afc1681c4e57a4a0f2039274d250.html [https://help.sap.com/viewer/
38dbd9fbb49240f3b4d954e92335e670/Cloud/en-US/d2a9afc1681c4e57a4a0f2039274d250.html]
The SAP Service and Asset Manager requires a compatible environment to operate in. Requisite components
include:
SAP Service and Asset Manager leverages the digital core with SAP S/4HANA as well as the SAP Business
Technology Platform as an IoT platform.
SAP Service and Asset Manager manages work orders, notifications, condition monitoring, material
consumption, time management, and failure analysis.
The Mobile Development Kit provides a runtime and full customization framework for SAP Service and Asset
Manager. Users can easily customize SAP Service and Asset Manager by adding and editing actions, business
logic, screens, and styling.
The SAP Service and Asset Manager application supports the following languages:
● ar001 - Arabic
● zh_hans - Simplified Chinese
● zh_hant - Traditional Chinese
● csCZ - Czech Republic
● daDK - Danish
● nlBE - Dutch
● elGR - Greek
● enUS - English
● frFR - French
● deDE - German
● heIL - Hebrew
● hrHR - Croatian
● huHU - Hungarian
● itIT - Italian
● jaJP - Japanese
● koKR - Korean
● nbNO - Norwegian
● plPL - Polish
● ptBR - Portugese
● roRO - Romanian
● RuRU - Russian
● srSP - Serbian
● skSK - Slovak
● slSL - Slovenian
● esES - Spanish
● svSE - Swedish
● thTH - Thai
● trTR - Turkish
Note
See the following topics and guides for detailed information on the Mobile Development Kit and the SAP
Web IDE:
● SAP Web IDE: See the Getting Started chapter of the SAP Web IDE Full-Stack guide.
● Mobile Development Kit: See the Using SAP Cloud Platform Mobile Services, mobile development kit
guide.
● If a custom SAP Service and Asset Manager build is needed for Cloud Foundry, see the Creating a Build
Job for Customized MDK Clients procedure.
The Mobile Development Kit lets you customize, deploy, and manage SAP Service and Asset Manager in the
cloud. The Mobile Development Kit editor lets you edit your various aspects of your application using the
Mobile Development Kit editor. It also provides native client support and consumes mobile services such as
onboarding, offline OData, life cycle management, and supportability through the SAP Business Technology
Platform using the Mobile Development Kit client.
The Mobile Development Kit allows business process experts to customize SAP Service and Asset Manager in a
cloud-based editor using SAP Web IDE, and developers to code directly in the metadata files.
SAP Business Technology Platform enables customers and partners to rapidly build, deploy, and manage
cloud-based enterprise applications that complement and extend your SAP or non-SAP solutions, either on-
premise or on-demand.
Note
For more information on prerequisites and procedures for setting up customer accounts on SAP Business
Technology Platform, see the topic Getting Started with a Customer Account: Workflow in the Neo and
Cloud Foundry environment.
SAP Business Technology Platform is an in-memory cloud platform based on open standards. It provides
access to a feature-rich, easy-to-use development environment in the cloud. The platform includes a
comprehensive set of services for integration, enterprise mobility, collaboration, and analytics.
As a Platform-as-a-Service operated by SAP, our product frees your administrators from any infrastructure and
IT costs and offers state-of-the art quality of service.
Application development
You can use the following programming models to build highly scalable applications:
● Java - SAP Business Technology Platform is Java EE 6 Web Profile certified. You can develop Java
applications just like for any application server. You can also easily run your existing Java applications on
the platform.
● SAP HANA - you can use the SAP HANA development tools to create comprehensive analytical models and
build applications with SAP HANA programmatic interfaces and integrated development environment.
● HTML5 - you can easily develop and run lightweight HTML5 applications in a cloud environment.
● SAPUI5 - use the UI Development Toolkit for HTML5 (SAPUI5) for developing rich user interfaces for
modern Web business applications.
In the context of SAP Business Technology Platform, a solution is comprised of various application types and
configurations created with different technologies, and is designed to implement a certain scenario or task
flow. You can deploy solutions by using the Change and Transport System (CTS+) tool, the console client, or by
using the cockpit, where you can also monitor your solutions. To describe and technically realize the solutions,
SAP Introduces the multi-target application (MTA) model. It encompasses and describes application modules,
dependencies, and interfaces in an approach that facilitates validation, orchestration, maintenance, and
automation of the application throughout its lifecycle.
Applications developed on SAP Business Technology Platform run in a modular and lightweight runtime
container. The platform provides a secure, scalable runtime environment with reusable platform services.
Virtual Machines
Virtual machines allow you to install and maintain your own applications in scenarios not covered by the
platform. A virtual machine is the virtualized hardware resource (CPU, RAM, disk space, installed OS) that
blends the line between Platform-as-a-Service and Infrastructure-as-a-Service.
Services
You can consume a set of services provided by SAP Business Technology Platform according to the technology
you prefer and the use cases of your scenarios.
SAP Business Technology Platform facilitates secure integration with on-premise systems running software
from SAP and other vendors. Using the platform services, such as the connectivity service, applications can
establish secure connections to on-premise solutions, enabling integration scenarios with your cloud based
applications.
In-memory persistence
SAP Business Technology Platform includes persistence powered by SAP HANA, taking full advantage of its
real-time, in-memory computing technology and built-in analytics.
Comprehensive, multilevel security measures have been built into SAP Business Technology Platform. This
security is engineered to protect your mission critical business data and assets and to provide the necessary
industry standard compliance certifications.
Free trial
You can start by getting a free SAP Business Technology Platform developer license on SAP Business
Technology Platform Developer Center that also gives you access to our community and all the free technical
resources, tutorials, blogs, support you need.
SAP Business Technology Platform Mobile Services, or SAP BTP services, provides services to mobile
applications, such as application analytics, app resources, onboarding, and HTTP/HTTPS configuration.
● Application analytics: Usage statistics that are displayed graphically in the SAP BTP cockpit
● App resources: Containers of dynamic configurations, styles, or content that are downloaded by native
applications
● Onboarding: Authentication of users who are registering through SAP Mobile Place
● HTTP/HTTPS configuration: Open standards for client communications
● Life cycle management: Managing and deploying multiple versions of an application
● Offline oData service: Optimizes data transport between the back end and the client offline store
● Push notifications: Native notifications sent from back-end systems to the server, which forwards them on
to the clients
● SAP BTP cockpit: Deploys, manages, and monitors applications
SAP BTP services can expose on-premise back end services through Cloud Connector, and on-demand back
end services directly.
SAP BTP services security enables you to use an on-premise identity management system for on-demand
applications. You can use basic authentication using LDAP, or form-based application authentication using
SAML.
The SAP Business Technology Platform SDK includes well defined layers (SDK frameworks, components, and
platform services) that simplify development of enterprise-ready mobile native apps that take full advantage of
the mobile platform features.
The SAP Business Technology Platform SDK is tightly integrated with the SAP Business Technology Platform
Mobile Services Cockpit to provide the following:
For more information about the SAP Business Technology Platform SDK see the following topics, depending on
your mobile client platform:
Note
The following information details setting up subaccounts on Neo environments for use with SAP Service
and Asset Manager. For informaion on how to set up Cloud Foundry subaccounts with SAP Service and
Asset Manager, see the topic How SAP Service and Asset Manager Works in a Cloud Foundry Environment
[page 17].
These components work in concert to continuously synchronize data from the back end SAP on-premise
database onto the SAP Service and Asset Manager application on mobile devices through the following flow:
1. The SAP Service and Asset Manager application requests authorization from the SAP Business Technology
Platform to authenticate against an identity provider defined by the SAP Business Technology Platform
using an oAuth2.0 Service.
2. SAP Service and Asset Manager uses the authorization grant from the oAuth 2.0 service to access the
remote data sync feature on the mobile service of the SAP Business Technology Platform using the
retrieved authentication.
Additionally, another set of components work in concert to ensure that the SAP Service and Asset Manager
application itself is up-to-date and behaves as intended through the following flow:
1. Users can use the SAP Web IDE on the SAP Business Technology Platform uses the SAP Business
Technology Platform Mobile Services development tools plug-in to update the SAP Service and Asset
Manager application or install additional components onto the application.
2. The SAP Web IDE can perform an MDK Deploy and Activate of the updated application definitions for SAP
Service and Asset Manager to the AppUpdate feature from SAP Business Technology Platform Mobile
Services.
3. SAP Service and Asset Manager periodically checks the AppUpdate feature for new definitions of SAP
Service and Asset Manager, and retrieves the updates on demand.
Note
The following information details setting up subaccounts on Cloud Foundry environments for use with SAP
Service and Asset Manager. For informaion on how to set up Neo subaccounts with SAP Service and Asset
Manager, see the topic How SAP Service and Asset Manager Works in a Neo Environment [page 15].
These components work in concert to continuously synchronize data from the back end SAP on-premise
database onto the SAP Service and Asset Manager application on mobile devices through the following flow:
1. The SAP Service and Asset Manager application requests authorization from the SAP Business Technology
Platform to authenticate against an identity provider defined by the SAP Business Technology Platform
using an oAuth2.0 Service.
2. SAP Service and Asset Manager uses the authorization grant from the oAuth 2.0 service to access the
remote data sync feature on the mobile service of the SAP Business Technology Platform using the
retrieved authentication.
Additionally, another set of components work in concert to ensure that the SAP Service and Asset Manager
application itself is up-to-date and behaves as intended through the following flow:
1. Users can use the SAP Web IDE on the SAP Business Technology Platform uses the SAP Business
Technology Platform Mobile Services development tools plug-in to update the SAP Service and Asset
Manager application or install additional components onto the application.
2. The SAP Web IDE can perform an MDK Deploy and Activate of the updated application definitions for SAP
Service and Asset Manager to the AppUpdate feature from SAP Business Technology Platform Mobile
Services.
3. SAP Service and Asset Manager periodically checks the AppUpdate feature for new definitions of SAP
Service and Asset Manager, and retrieves the updates on demand.
The inventory clerk persona enables an inventory clerk to receive, issue, or transfer materials. The inventory
clerk persona also supports batch-managed materials and serialized parts.
Note
Persona support is available starting with the SAP Service and Asset Manager 2110 release.
Goods receipt (Ad hoc) Goods recipe other 501 X Support for multiple
(501 w/o PO) material per document
Goods issue (Ad hoc) Cost center 201 X Support for multiple
material per document
Goods issue (Ad hoc) Work order 261 X Support for multiple
material per document
Goods issue (Ad hoc) Network operation 281 X Support for multiple
material per document
Goods issue (Ad hoc) WBS element 221 X Support for multiple
material per document
● A plant must be assigned to the logon user. Use the user parameter WRK.
● You must assign the inventory clerk persona to the user. See the Configuring Personas procedure in the
SAP Asset Manager Configuration Guide for details.
● The user must have the authorization to create a material document.
Note
As of SSAM 2205, special postings for stocks and transfers are not supported.
The following functions are supported as part of the goods receipt process:
The following functions are supported as part of the goods issue process:
Note
Please verify the filters on the plants and storage location OMDOs to ensure the appropriate filters are
configured. For example: the PLANT filter on SAM2205_PLANT is not restricted to the user parameter
WRK.
Note that OMDO is shared across personas, so consider the impact on other personas and the
performance implications when changing filters. You can use user attributes or the filter handler for special
handling.
A mobile user can perform the following functions from the results of a stock lookup:
● Stock transfer
● Goods issues for cost center, WBS element, work order, or network
Note
As of 2205, the stock lookup only supports unrestricted stocks at a storage location. Special or batch
stocks are not supported.
● Downloading a physical inventory document and performing counts on the mobile client
● Creating a physical inventory document on the mobile client
Note
As of 2205, physical inventory counts are limited to the company’s own stock and counting special stocks
is not supported.
As of 2205, creating a physical inventory document with a group type or with a special stock indicator is not
supported.
In order to connect to an SAP back end, a compatible on-premise environment with the SAP Mobile Add-On
must be available.
The SAP back end communicates with the SAP Business Technology Platform via the Cloud Connector. You
can find more information on the Cloud Connector in the SAP Business Technology Platform Connectivity
manual.
Add the SAP Mobile Add-On for SAP ERP systems alongside the requisite service packs in order to provide the
required OData services for specific versions of SAP Service and Asset Manager.
Depending on the version of SAP Service and Asset Manager, the following versions of the SAP Mobile Add-On
are available for compatible SAP ECC 6.0 EHP7 SP14 systems and newer:
Add-On Component SAM 2.0 SAM 3.0 SAM 4.0 SAM 1911
SMFND 630_740 SP01 Supported Not supported Not supported Not supported
Ensure that the corresponding SAP Mobile Add-On and service packs are installed for the SAP Service and
Asset Manager application you wish to run. For detailed information and instructions regarding the installation
of the SAP Mobile Add-On for ECC 6.0 Systems, see the Mobile Add-On for ERP Installation Guide, or check
primary note 2577248 .
After downloading the files for the SAP Mobile Add-On desired support packages from the SAP Software
Download Center, load the mobile add-on onto your system through the add-on manager, using the transaction
code SAINT. Once the add-on is installed, load the support packages into your system through the Support
Package Manager (accessed through transaction code SPAM).
1. Ensure that the requisite Web Dynpro that controls the behavior of the SAP Mobile Add-On are properly
activated.
1. Transactions /SYCLO/CONFIGPANEL and /SYCLO/ADMIN open the Mobile Application Integration
Framework Configuration Panel and Administration Panel for the desired back end SAP ERP system.
2. Ensure that the requisite B/C sets related to the desired version of the SAP Mobile Add-On are installed
and activated.
1. If these B/C sets have been properly activated, application configuration for the desired SAP Service
and Asset Manager version appears in the transaction /SYCLO/CONFIGPANEL under Mobile
Application Parameters.
3. Ensure that the OData service for the desired SAP Service and Asset Manager application is activated and
assigned to the Mobile Application OData Service Assignment.
1. The requisite OData service appears in the Mobile Application OData Service Assignment in the
transaction /SYCLO/CONFIGPANEL and is assigned to the mobile application.
2. The requisite OData service will also appear in the listing of OData services provided by the SAP
Gateway system, found in transaction /IWFND/MAINT_SERVICE.
1. Configure the alias assignment in the /IWFND/MAINT_SERVICE transaction. By selecting the
desired OData service, the bottom-right panel informs administrators which back end connection
alias is used for the connection to the backend SAP Mobile Add-On services.
2. Perform a quick test of the OData service to ensure the proper OData service document is being
returned by the service:
After selecting the OData service, the bottom-right panel includes a link to an internal test using
the gateway client. By using the internal gateway client tool with the HTTPS connection option,
system administrators can ensure that their connections are properly reaching the correct back-
end system from the SAP gateway and retrieving data for the proper data service providers for
SAP Service and Asset Manager.
3. Ensure that the idempotency jobs are set up from the SPRO configuration of the SAP gateway system,
as SAP Service and Asset Manager relies on idempotency in HTTP OData services to ensure data
integrity.
4. Ensure that the SAP back-end system is set up to allow authentication of HTTPS calls from the Cloud
Connector via principal propagation.
When the SAP Mobile Add-On has been set up correctly, the OData service starts returning data in the SAP
Gateway client, accessible from transaction /IWFND/GW_CLIENT.
Add the SAP Mobile Add-On for SAP S/4HANA systems alongside the requisite service packs in order to
provide the required OData services for specific versions of SAP Service and Asset Manager.
The following versions of Mobile Add-On for SAP S/4HANA are available for compatible SAP S/4HANA 1610
FPS01 systems and newer:
Add-On Com
ponent SAM 1.0 SAM 1.1 SAM 2.0 SAM 3.0 SAM 4.0 SAM 1911
S4MFND 100 Supported Not supported Not supported Not supported Not supported Not supported
S4MERP 100
S4MFND 100 Not supported Supported Not supported Not supported Not supported Not supported
SP01
S4MERP 100
SP01
S4MFND 100 Not supported Supported Supported Not supported Not supported Not supported
SP02
S4MERP 100
SP02
S4MISU 100
S4MFND 100 Not supported Supported Supported Supported Not supported Not supported
SP03
S4MERP 100
SP03
S4MISU 100
SP01
S4MFND 100 Not supported Supported Supported Supported Supported Not supported
SP04
S4MERP 100
SP04
S4MISU 100
SP02
Ensure that the corresponding SAP Mobile Add-On and service packs are installed for the SAP Service and
Asset Manager application you wish to run. For detailed information and instructions regarding the installation
of the SAP Mobile Add-On for 1610 FPS01 systems, see the Mobile Add-On for S/4HANA Installation Guide, or
check primary note 2493602 .
After downloading the files for the SAP Mobile Add-On desired support packages from the SAP Software
Download Center, load the mobile add-on onto your system through the add-on manager, using the transaction
Once the SAP Mobile Add-On and requisite support packages have been installed, follow the Post Installation -
Required topic to fully configure the Mobile Add-On for SAP S/4HANA. Ensure that the OData Service is
assigned in /IWFND/MAINT_SERVICE and the B/C set is activated for the given version of SAP Service and
Asset Manager. After following the topic, use thefollowing checklist to ensure that the mobile application
integration framework is properly installed and configured:
1. Ensure that the requisite Web Dynpro that controls the behavior of the SAP Mobile Add-On are properly
activated.
1. Transactions /SYCLO/CONFIGPANEL and /SYCLO/ADMIN open the Mobile Application Integration
Framework Configuration Panel and Administration Panel for the desired back end SAP S/4HANA
system.
2. Ensure that the requisite B/C sets related to the desired version of the SAP Mobile Add-On are installed
and activated.
1. If these B/C sets have been properly activated, application configuration for the desired SAP Service
and Asset Manager version appears in the transaction /SYCLO/CONFIGPANEL under Mobile
Application Parameters.
3. Ensure that the OData service for the desired SAP Service and Asset Manager application is activated and
assigned to the Mobile Application OData Service Assignment.
1. The requisite OData service appears in the Mobile Application OData Service Assignment in the
transaction /SYCLO/CONFIGPANEL and is assigned to the mobile application.
2. The requisite OData service will also appear in the listing of OData services provided by the SAP
Gateway system, found in transaction /IWFND/MAINT_SERVICE.
1. Configure the alias assignment in the /IWFND/MAINT_SERVICE transaction. By selecting the
desired OData service, the bottom-right panel informs administrators which back end connection
alias is used for the connection to the backend SAP Mobile Add-On services.
2. Perform a quick test of the OData service to ensure the proper OData service document is being
returned by the service:
After selecting the OData service, the bottom-right panel includes a link to an internal test using
the gateway client. By using the internal gateway client tool with the HTTPS connection option,
system administrators can ensure that their connections are properly reaching the correct back-
end system from the SAP gateway and retrieving data for the proper data service providers for
SAP Service and Asset Manager.
3. Ensure that the idempotency jobs are set up from the SPRO configuration of the SAP gateway system,
as SAP Service and Asset Manager relies on idempotency in HTTP OData services to ensure data
integrity.
4. Ensure that the SAP back-end system is set up to allow authentication of HTTPS calls from the Cloud
Connector via principal propagation.
When the SAP Mobile Add-On has been set up correctly, the OData service starts returning data in the SAP
Gateway client, accessible from transaction /IWFND/GW_CLIENT.
The SAP Business Technology Platform is an essential component of the end-to-end landscape for the SAP
Service and Asset Manager application. You can manage all of the separate components and features used by
the SAP Service and Asset Manager from the SAP Business Technology Platform. These components and
features are easily configured, including offline OData services, APNs or GCP push services, SAP on-premise
OData connections, Mobile Development Kit customization and deployment options, and others.
For more details regarding purchasing access licenses to the SAP Business Technology Platform, contact your
SAP account representative.
Before continuing, ensure that you have access to an SAP Business Technology Platform global account, as
well as licenses and access for SAP Mobile Services, the Mobile Development Kit, and the SAP Web IDE full
stack edition. Once you obtain the licenses and access for these items, create a subaccount on the region of
your choice under the NEO environment. Check to ensure that all of these services are provisioned to the
subaccount. If you’re unable to establish a connection to Mobile Services or the SAP Web IDE with the Mobile
Development Kit plug-in, contact your SAP Business Technology Platform support representative to determine
how to request these features.
For more information, see the SAP Business Technology Platform portal page at SAP Cloud Platform.
Your SAP Service and Asset Manager installation needs either a Cloud Foundry or a Neo SAP Business
Technology Platform Mobile Services (SAP BTP services) installation and configuration.
For more information regarding what services are required for your Cloud Foundry setup, see the official
installation documentation for the SAP BTP services.
Establish an SAP Business Technology Platform Neo account with the requisite services.
Connecting the SAP Business Technology Platform to SAP BTP services Neo
1. Navigate to the Services tab of the SAP Business Technology Platform subaccount with Mobile Services
provisioned on it.
2. Enter the configuration for mobile services by selecting the Mobile Services, Users service. Ensure that the
status is set to Enabled.
3. Once the service is enabled, select the Configure Mobile Servies, Users option. Navigate to the Roles tab in
the configuration.
4. Add users that need access to the connection settings of the mobile application to the Administrator role to
allow them to manage the connection between the SAP Service and Asset Manager application and the
requisite components that it uses on the SAP Business Technology Platform.
For more information on setting up the SAP Service and Asset Manager application with the SAP Business
Technology Platform, see the official documentation for the SAP BTP Neo Environment.
To quickly get connected in SAP BTP services, some preset templates are provided for apps built on the Mobile
Development Kit, including SAP Service and Asset Manager:
1. In SAP BTP services, create a destination that utilizes the Cloud Connector to create a connection to the
SAP on-premise environment.
1. In the default metadata that is shipped with SAP Service and Asset Manager, the destination names
that the mobile application is looking for are DEST_SAM<version number>_PPROP. Therefore, use this
naming convention for destinations used with standard installations of the SAP Service and Asset
Manager application.
2. The SAP Service and Asset Manager application currently only supports connections to on-premise
environments. Ensure that the Cloud Connector is properly configured by creating the connection
based on the virtualhost information in the Cloud Connector.
3. The SAP Service and Asset Manager application has different performance and timing requirements
depending on the on-premise system being used:
1. For SAP ERP back ends and landscapes using the Gateway hub environment, set the timeout
settings for the connection to at least 20 minutes.
2. For SAP S/4HANA back ends with embedded SAP Gateways, set the timeout settings for the
connection to 10 minutes at a minimum.
4. In the custom header section, include the header sap-client = <on-premise gateway client
#> to prevent potential issues from a misconfigured default client configuration.
5. Manually configure URL rewriting only if the Cloud Connector is set with a virtualhost that differs from
the internal host. To manually configure URL rewriting, set the inbound and outbound rewrite rules to
Establish an SAP Business Technology Platform Cloud Foundry account with the requisite individual services.
For detailed information on Cloud Foundry, see the SAP Cloud Platform Mobile Services page.
1. Navigate to the SAP Cloud Platform Cockpit portal page. The SAP Business Technology Platform portal
page is the home page where you access your listing of global accounts. You must be logged on to access
your accounts.
2. Click your desired global account, for example, SAP Service and Asset Manager.
You’re taken to Global Account Cockpit page.
3. Click the Subaccounts tab. Your subaccounts appear. If you don't have any subaccounts created, use the
following substeps to create a subaccount:
○ Click the New Subaccount button.
○ In both the Display and the Subdomain fields, type a short, meaningful name.
○ In the Provider field, select either AWS or Microsoft Azure. Currently, Google Cloud Platform isn’t
supported.
○ Click Create.
A new subaccount is created.
4. Click the Subaccounts Assignment tab.
5. Select your desired subaccount.
6. Click the Configure Entitlements button, then click the Add Service Plant button.
The Entitlements window displays.
7. Select Mobile Services on the left to bring up the Mobile Services panel on the right.
8. Click the Standard checkbox to add it to your plan.
9. Click Application Runtime on the left. Then check the MEMORY checkbox on the right.
Application Runtime and Mobile Services appear at the bottom of the panel.
10. Click the Add [Number] Service Plans.
You’re returned to the Subassignment Accounts page.
Note
The amount of application runtime memory required is based on the number of applications you’re
setting up in the subaccount. For every 5 applications, you need at least 1 GiB of quota. For example, 10
mobile applications require 2 GiB of runtime. See the SAP Asset Manager Sizing Guide for detailed
information.
2. Create a space.
4. Select the Instances tab. Create a new instance with a meaningful name and no parameters.
5. Select the instance. Select Open Dashboard to open the mobile services. Create an application
following the Using the SAP Business Technology Platform Mobile Services App Creator to Create an
Application [page 33] procedure.
16. By default, apps made in SAP BTP services on Cloud Foundry are oAuth secured. To build the onboarding
link to connect the application, navigate to the Security section and configure the following:
○ oAuth Token
○ Authorization
○ Redirect URLs
○ Client ID
Prerequisites
● Ensure you have followed the steps in SAP Business Technology Platform Mobile Services - Setting Up a
Cloud Foundry Environment, Single Instance [page 30], up to Step 15e before starting the following
subprocedure.
● Read and follow 2978807 : MAIF to CPms Multi-Virtualhost Support
Context
Note
Procedure
Your SAP Service and Asset Manager application is automatically created on SAP Business Technology
Platform Mobile Services.
Postrequisites
Continue to Step 6 of the Creating an Application in SAP Business Technology Platform Mobile Services - Cloud
Foundry procedure in the SAP Asset Manager Installation Guide.
The SAP on-premise landscape communicates with the SAP Business Technology Platform via the Cloud
Connector.
Find more information on the Cloud Connector in the SAP Business Technology Platform Connectivity
documentation.
During the installation of the Cloud Connector, take the following steps:
1. Ensure that the system certificate is trusted by the back-end SAP Gateway. You can add a certificate via
transaction STRUST.
2. For principal propagation, ensure that the local CA certificate is set up and the back end accepts the x.509
principal propagation certificate sent from the Cloud Connector. The back-end SAP Gateway needs to
allow authentication via principal propagation in order to properly determine data distribution for a given
mobile application user. Therefore, define the subject pattern that the x.509 certificates are sent with from
the Cloud Connector in the SAP Gateway system, either explicitly though transaction EXTID_DN or via a
certificate rule through transaction CERTRULE.
3. In addition, the subject and issuers of all certificates need to be trusted in the ICM system.
1. Add the parameter <icm/HTTPS/trust_client_with_issuer = <Subject of CA
Certificate on Cloud Connector> and <icm/HTTPS/trust_client_with_subject =
<subject pattern of the x.509 certificate from the cloud connector> into the
System Profile Parameters using transaction RZ10.
2. Restart the ICM framework using transaction SMICM under the option Administration Hard
Shutdown Global .
Once the on-premise connection to the Cloud Connector is established and configured, establish the
connection to the SAP Cloud Platform account.
1. Ensure that the Cloud Connector has its trust configuration and proxy configuration set properly to
communicate with the SAP Business Technology Platform region that you would like to connect to.
2. Create a connection to a valid subaccount with the previous checklist in this topic accomplished. Use the
subaccount ID and a user account that has been added to that subaccount with the role Cloud Connector
Admin or Administrator.
1. Add the mapping from the virtual to the internal system of an HTTPS connection to the on-premise
Gateway. Ensure that all resources are available for the URL path and all subpaths for /sap/opu/odata.
2. Ensure that the trust configuration accepts all hanamobileprod based trusts in the Principal Propagation
tab.
Note
When using the Cloud Connector with SAP BTP services on a Neo subaccount, configure
hanamobileprod:mobilejava as Trusted in the following location: Sub-account configuration
Cloud-to-on-Premise section Principal Propagation tab .
See 2660862 : SAP Cloud Platform Mobile Services (SCPms) Setup Info for SAP Asset Manager with
SAP ERP System for detailed information.
If the extension or installation of additional components onto SAP Service and Asset Manager is required, then
the SAP Web IDE is a required deployment.
Find more information at the documentation for the SAP Web IDE Full-Stack.
To deploy an application from the SAP Web IDE to the SAP BTP services instance:
1. Ensure that the mobileservices destination in the SAP Business Technology Platform subaccount has the
value mobile added to the WebIDEUsage property.
2. Ensure that the Mobile Services App Development Tools is enabled by checking the Settings tab in the
Extensions section in the SAP Web IDE.
3. Download the SAP Service and Asset Manager metadata from the SAP Marketplace. Import the application
into the SAP Web IDE.
4. Once the metadata is imported, load the metadata to the MDK perspective.
Right-click on the app, and select MDK Deploy and Activate. Deploy the app to the mobile application.
5. Once the app is loaded, use the connection link builder in the SAP Web IDE to build an onboarding link for
the mobile device using the information retrieved from the building of the mobile application.
6. Once the link is built, send the link to the mobile device with SAP Service and Asset Manager installed.
7. Connect to the mobile app, sign in, and update the mobile application when prompted.
You can find more information regarding the installation of SAP Service and Asset Manager in the SAP Service
and Asset Manager Installation Guide.
You can find more information regarding the configuration of SAP Service and Asset Manager in the SAP
Service and Asset Manager Configuration Guide.
Error logs provide detailed context information about errors that have occurred at runtime.
Use the following logs and traces to help diagnose issues with your SAP Service and Asset Manager installation
and performance after installation:
Error logs provide detailed context information about errors that have occurred at runtime, enabling you to
perform root cause analysis, as well as reproducing and correcting errors.
You can launch the error log with transaction /IWFND/ERROR_LOG in Gateway Hub systems. Launch the error
log with transaction /IWBEP/ERROR_LOG in your back-end system.
The SAP Gateway error logs reveal basic details about errors and show errors from all users for a given client.
Business logic errors are often displayed in this error log due to improper business logic. Other errors displayed
include the HTTP code to indicate the type of error.
Note that based on the security level setting, advanced details or the replay function may be hidden or
disabled. Note also that these error logs will not show generic authorization errors if users fail to properly
authenticate.
Use option SAP Gateway Client to reproduce runtime situations that led to a particular error without accessing
the application from the actual mobile client, and to simulate a service at runtime to identify and resolve
potential issues.
For more information about how to configure the error log, see Configuration Settings for the Error Log in the
SAP Gateway Technical Operations Guide.
In addition, use the Application Log Viewer to display more technical error details by using transaction /
IWFND/APPS_LOG.
The SAP Gateway provides tracing tools (transaction code: /IWFND/TRACES) to trace on a particular user for
both performance and payload.
Performance trace enables you to monitor performance at service call level for both the SAP Business Suite
and the SAP Gateway. Payload trace enables you to monitor the service calls with request and response data,
and to replay and simulate the service calls without accessing the application from the mobile client.
Traces display detailed request and response data coming into the SAP Gateway. Traces are active for only a
short time, and are purged on a regular basis.
For information about how to configure and activate the payload trace tool, see Tracing Tools: Configuration in
the SAP Gateway Technical Operations Guide.
Use transaction SMICM to reveal client certificates and information sent alongside HTTP requests.
An internet communications trace can reveal issues with principal propagation. You can use the incoming
forwarded client certificate to determine if certificate-mapping rules are properly established.
Trace levels are set through an administration menu. You can also restart the ICM using SMICM.
The SAP back-end performance tracing tools display a trace log of processes that ran as well as detailed
performance information regarding those processes.
Use transaction code: SMICM to reveal client certificates and other information sent alongside HTTP requests.
Trace files can reveal potential issues with principal propagation. Use the incoming forwarded client certificate
to determine if your certificate-mapping rules are properly established.
Set trace levels through the Administration menu. You can also restart the ICM through transaction SMICM.
Cloud Connector logs show all traffic that passes through your Cloud Connector.
You can set your Cloud Connector settings with or without payload information.
SAP Business Technology Platform Mobile Services technical logs contain grouped logs by correlation ID for
easier readability of log data.
The SAP Business Technology Platform Mobile Services aren’t enabled by default. Enable the logs using Log
Settings.
You can set the individual log levels for each component of SAP Business Technology Platform Mobile Services
through the log settings. You can also set the consistency of log purging through the settings.
SAP Business Technology Platform Mobile Services network traces trace calls that route through mobile
services.
Download network trace files in either ZIP or HAR format. Note that SAP Business Technology Platform Mobile
Services are best read in HAR format by programs like Fiddler or Charles.
You can also set the consistency of log purging on the Network Traces screen.
Use the built-in logger of the Mobile Development Kit client so that it turns on when it connects to the SAP
Business Technology Platform Mobile Services application based upon the log policy set on the Client Policies
screen.
You can set the log level from the Client Policies screen in the SAP Business Technology Platform Mobile
Services. Log levels are brought into the logging page through the Analytics section of SAP Business
Technology Platform Mobile Services.
Procedure
1. Install the Mobile Development Kit VS Code extension via the menu item of VS Code Extensions Viewer
Install from VSIX .
A new language mode, MDK, is attached to any opened Mobile Development Kit metadata file.
3. Add a new launch configuration called MDK for the first time launch in Debug view.
● Doesn’t support offline features, including navigation links, expands, and others
● Doesn’t retrieve records with dependent objects
Procedure
4. Use the Gateway trace logs found on your back-end system. See SAP Gateway Tracing Tools [page 40] for
more information.
If your Android device uses an OEM-specific (non-Google) software keyboard, it may prevent you from entering
decimals and negative numbers in fields where you're entering a reading value, such as measuring point
screens.
If you or your mobile device users are unable to enter decimal points and negative values on their Android
devices, take the following steps to install Gboard on your Android device:
1. Search for and install the Gboard app from the Google Play store onto Android mobile devices running SAP
Service and Asset Manager (https://play.google.com/store/apps/details?
id=com.google.android.inputmethod.latin ). Gboard is the default, Google-provided, Android keyboard.
2. Enable Gboard as the default keyboard input. See the following substeps and screenshots for examples of
how to install Gboard. Note that your Android screens may not look exactly like the screenshots due to
manufacturer differences in design.
1. Open the Gboard app after you’ve installed it. Gboard displays a message requesting you to enable
your language and input settings. Tap the Enable in Settings button to continue.
A pop-up window displays, allowing you to select which keyboard you wish to enable.
Note
If a pop-up window doesn’t display during the Gboard set up wizard, continue to the Manually
Setting Gboard Defaults subsection in this topic to manually apply the Gboard settings.
3. Tap the Language and input selection on the General Management screen. Select Gboard as the default
keyboard.
4. Tap the Default keyboard selection on the Language and input screen. Select Gboard as the default
keyboard.
5. After performing these steps on your Android device that you use for the SAP Service and Asset Manager
application, ensure that you can enter measuring point or reading values that include decimal points and a
negative number value.
You can get the following error when activating and deploying the Mobile Development Kit:
Build failed
- Right-click the project folder, select "Clean npm Folder", and build again.
- Delete the "package-lock.json" file from the project and build again..
To resolve the error, right-click the MDKWebpackFactory folder and select Clean npm Folder. If cleaning the
npm folder doesn’t resolve the issue, delete the MDKWebpackFactory folder and redeploy your project.
If the SAP Service and Asset Manager application is removed from a mobile device or stops working, you can
recover your data that was stored in the application.
Use the following solutions to reinstall the SAP Service and Asset Manager client and recover the user data:
If the application stops running or is removed from the mobile device, reinstall the client.
Reinstall the application onto the mobile device. See Installing the SAP Asset Manager Client topic in the SAP
Asset Manager User Guide.
If the SAP Service and Asset Manager app was deleted and reinstalled, the data from the app is lost, including
any data that was not synced to the back end.
1. Reinstall the application onto the mobile device. See Installing the SAP Asset Manager Client topic in the
SAP Asset Manager User Guide.
2. Onboard through the SAP BTP services app.
3. Once the onboarding is complete, download data onto the mobile device by performing an initial sync.
If the SAP Service and Asset Manager app stops running and doesn’t restart, use the following steps:
1. Save the database files from the app to a location you choose on a PC or a Mac.
1. iOS: Use Finder on Mac or iTunes on Windows
As of the 2005 release of the application, you can also use the Files application.
The app launches and reads the saved files. You don't need to perform an initial sync. The application state is
restored.
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.
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.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
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.