Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

xApp Mobile Sales for handheld Client Frequently Asked Questions

What is the latest version of Mobile Sales for handheld and what do I need to run it?

Valid For: xMSA HH 5.0

The latest version is xMSA HH 5.0 SR02, which can be downloaded from Service Market Place. Mobile Sales for handheld is an application based on Mobile Infrastructure that retrieves its business data from SAP CRM (Customer Relationship Management). The requirements are as follows:

  • Backend: SAP CRM 4.0 SP09 till SP11/SAP CRM 5.0 SP04
  • Middleware: WebAS 640/WebAS 700
  • Client: SAP Mobile Infrastructure 2.5 SP18/ SAP Mobile Infrastructure 7.0 SP09, IBM DB2 Everyplace 8.2.1A, Creme JVM 3.2.7a

back to top

Where and how can I download the xMSA handheld application?

Valid For: xMSA HH all

Providing that you have the necessary license for the application, you can download it from Service Market Place. Please follow this path to access the download of the application:

http://service.sap.com/swdc -> Download Support Packages and Patches OR Installations and Upgrades -> Entry by Application Group -> SAP xApps -> SAP xApps for Mobile Business -> SAP xMSA, handheld.

If you do not have access to this page, please contact your SAP Account Manager to obtain the authorization for the download.

back to top

Where can I learn more on xMSA handheld?

Valid For: xMSA HH all

The official learning maps for the application can be found on Service Market Place by following the Mobile Field Applications Link (CRM 2005).

back to top

What are the collective notes for the xMSA handheld application?

Valid For: xMSA HH 5.0

The collective notes for xMSA handheld 5.0 are:

966556 for CRM4.0>=SP11
966940 for CRM5.0>=SP05

back to top

What are the main functionalities offered by xMSA HH?

Valid For: xMSA HH 5.0

  • Accounts/Business Partners: View, update, create orgnaizations, persons and contact types of business partners. You can also view and assign marketing attributes for business partners. Other business partner related information include activity and order history, promotions and fact sheets.
  • Activities: View, update, create activities with business partners. Activity journals are not part of the standard application. Built-in "My Calendar" shows activities in different views. Can complete customer surveys that are linked to an activity.
  • Opportunities: View, update, create opportunities with business partners. In the standard application there is no line items (specific products assigned to an opportunity).
  • Sales Orders: View, update, create sales orders for business partners by selecting products from the product list. Pricing is displayed on handheld as the price before special business partner discounts and rules. Once an order is created and synched, the special conditions are applied and calculated in CRM and the total updated price is sent to the device. Bar code scanning integration is supported.
  • Tasks: View, update, create tasks for the sales representative.
  • Complaints and Service Orders: Create customer complaints and service orders (for repair for example) at customer sites and send to CRM for processing.

back to top

What are the supported devices for xMSA HH?

Valid For: xMSA HH 5.0

The xMSA HH 5.0 application is designed for handheld devices running Windows Mobile 2003 and Windows Mobile 5.0. It will also run on desktop and laptop PCs. If installing on a PC, the Creme JVM will not be needed and a desktop version of the Mobile Infrastructure Client should be installed instead.

back to top

What is the synchronization mechanism for xMSA HH?

Valid For: xMSA HH 4.0, 5.0

xMSA HH is a generic sync application. Contrary to Mobile Asset Management (smart sync), xMSA HH does not make use of Sync BOs and no data is stored on the middleware (MI Server). All data is filtered through a delta mechanism on the CRM side and sent in "containers" via the MI server component.

back to top

What is the enhancement concept for xMSA HH?

Valid For: xMSA HH 5.0 SR01+

xMSA HH on the client side is a JSP application which follows the mCAF enhancement concept, that is also used in xMAM and xMTT. For more details on mCAF please take a look at Karsten Strothmann's blog on SDN. On the server side, a variety of configurations can be performed using the IMG (transaction SPRO in CRM) as well as enhancements via the SAP standard BAdis. Please refer to the xMSA HH 5.0 Enhancement Guide on Service Market Place for details and examples.

back to top

What is the maximum number of users that xMSA HH supports?

Valid For: xMSA HH 5.0

The maximum recommended number of concurrent users is 500. This means that no more than 500 users should be attempting a synchronization with CRM at the same time. It is highly recommended that expert sizing is performed when the total number of users approaches 500.

back to top

What is the maximum size of the upsync container and how can I estimate it?

Valid For: xMSA HH 5.0

The maximum recommended size of the data container should not exceed 1126KB. The calculations are performed using the Client Data Calculator available on Service Market Place by entering the number of business objects.

back to top

What are the supported client databases for xMSA HH?]

Valid For: xMSA HH 5.0

Currently, only IBM DB2e is supported. The recommended version is 8.2.1a.

back to top

When I attempt to perform an initial sync to get data from CRM, I get a Synchronization password not set up error.

Valid For: xMSA HH 5.0

Open the file MobileEngine.config file located in your "Mobile Infrastructure installation\settings\" folder. Add the following line to the end of this file:

MobileEngine.Security.SynchronizationPasswordHandlingOption=local

Restart Mobile Infrastructure.

back to top

What is the Service Order functionality in xMSA HH?

In the standard application the following fields are part of the Service Order component:

  • Ref. Object: This is the base object(product) on which the service order is created. For example, vending machine could be the ref object which needs to be repaired.
  • Ref. Date: This is the date which appears in the order, this could be the date on which the order is created.
  • Req. Start and Req. End: This is the requested start and requested end date of the service order.
  • Subject: This is the action to be carried out. Maintenanace or regular repair etc.
  • Products: These are the components of the base product (which was selected in Ref. Object). Vending machine will have components which will need to be repaired or maintained. Based on this the assignments are created.

Other fields include the business partner name, contact name and date and time fields.

It should be noted that the functionality is limited to creating service orders only. Service orders created in the CRM system or on the device will not be downloaded to the device after synchronizing.

back to top

  • No labels