Upgrade and Maintenance 
This section contains documentation related to the activities that you carry out for further upgrades and maintenance of mobile client applications. You need to refer to this section once you have completed the standard implementation of mobile client applications. However, to accomplish upgrade or maintenance activities, you need to refer to the standard implementation activities such as transports, generation and deployment of mobile client applications. For more information about how to continue after upgrading or maintaining CRM components, see Ongoing Implementation Tasks.
You carry out further upgrade and maintenance activities depending on the business need. These activities are referred to as business scenarios in this section. These scenarios are different from the field application scenarios such as Field Quotation and Order Management with Mobile Sales, Field Territory Management with Mobile Sales and so on.
The table below indicates the business needs and the corresponding business scenarios to be accomplished
Business need |
Business scenario |
You have received an SAP upgrade and have to upgrade mobile client components and applications. |
|
You need to add new fields to a mobile client application. |
|
You have to apply an SAP patch. |
|
You found discrepancies in the mobile client application and therefore need to check whether the Mobile Application Repositories (MARs) in the typical landscape contain the same baseline versions of development objects. |
|
You need to resolve collisions that have occurred while upgrading MARs. |
|
You need to develop or customize the Mobile Client Companion. This is done using Mobile Application Studio with required references from the standard mobile client application. |
|
Translate the mobile client application into a language other than English (EN) and German (DE). |
|
Facilitate controlled access to a mobile client application by application users. |
CRM Integration
Step-by-StepSee also: