Expand +



Installing and configuring SAP Sales Manager on SAP Mobile Platform: Q&A with CRM 2014 speaker Sandeep Raina

by Sandeep Raina

February 12, 2014

Sandeep Raina of Fujitsu America joined us for an online chat to answer questions on SAP Mobile Sales 2.5 integration and technical requirements with SAP Mobile Platform.

To review the discussion, you can view the entire chat replay or the edited transcript below. Thanks to everyone who joined us for some great questions looking at the move from SAP CRM Mobile Sales, security, and configuration, among other topics.

Sandeep Raina is a principal working with Fujitsu America, and has more than a decade of experience in SAP CRM, ECC, SRM, and mobile platforms. Sandeep had worked on multiple global implementations, upgrades, and rollouts and has played lead role in designing and delivery CRM solutions for various customers across multiple industries including Chemicals, Automobile, Electronics, and Healthcare. Sandeep’s current focus is on CRM with HANA and enterprise mobility.

Sponsored by CRM 2014 Las Vegas, April 1-4






Charlotte Christy, Moderator: Thanks to everyone for joining us today! I’m pleased to have Sandeep   Raina of Fujitsu America joining us. Sandeep is a CRM expert and has presented on SAP CRM Mobile Sales at past SAPinsider conferences. This year, he’ll be talking about SAP Sales Manager, and accelerating the sales cycle with mobility and the SAP Mobile Platform. Welcome, Sandeep!

Sandeep Raina, Fujitsu America: Thanks Charlotte for the introduction and welcome to everyone on the Q&A.



Charlotte Christy: Could we start with a quick overview of the basics for today’s Q&A? What is SAP Sales Manager? How does it compare to past releases of SAP Mobile Sales?

Sandeep Raina: Sales Manager is a mobile application developed on SAP's Syclo platform and is now part of SMP. This application is designed to provide the most flexible and robust design for a better user experience. Functionality wise, Release 1 of SAP Sales Manager and SAP Mobile Sales are almost the same. SAP Sales Manager is better in terms of customization and overall flexibility. You can perform changes on applications without changing the frontend. This was a big challenge in the previous version of the CRM Sales application. Also with SAP Sales Manager, one more system is removed that was a required component in the CRM Sales application.



Charlotte Christy: Any new features in SAP Sales Manager that you’d like to focus on?

Sandeep Raina: New features include better push notifications on your transactions from the CRM backend. Users will be sent a notification if new opportunities, leads or activities are assigned. Users are advised immediately. You also have multiple versions of applications running based on the requirements. With the new transmit functionality, users can receive new configurations without changing anything on the device.



Charlotte Christy: And what are the technical requirements for installing and configuring Sales Manager? I know your session focuses on some benefits of SAP Mobile Platform with Sales Manager — can you mention one or two of these? 

Sandeep Raina:

1) You need a Windows/Linux server to install the CRM Manager server (a combination of an Agentry server and other components). Also a server/system to load and setup the Sales Manager client.

2) There are additional add-ons that are required in CRM and ECC (optional): 2 in CRM, and 1 in ECC.



Comment From Anders Hansen: I have a question regarding a system refresh. Consider the following scenario. The productive CRM and ECC are copied down to the test CRM and ECC. In this way, there is alignment between the productive system and the test/quality system. The RFC connections are set correctly to the test DOE environment and the DOE environment is cleaned from master data. How do I get the master data to replicate from the refreshed CRM environment to the test DOE environment? The initial load does not work. And the SDOE_LOAD (delta load) does not work for opportunities.

Sandeep Raina: Once your CRM and ECC systems are refreshed, you can push the data into DOE. Technically, your DOE must also be refreshed. If your DOE system is not refreshed, it will still contain old data. You can still perform a full load data by using the programs that are in CRM. This will push all new data to DOE. This has worked and I have done this in past. You can unsubscribe the device and then subscribe again to see new data.



Comment From Ken: What is the realistic testing timetable when integrating SAP Sales Manager on the SAP mobile platform?

Sandeep Raina: Hi Ken. It takes 4-6 weeks to have your application up and running in the development system. Realistically, Sales Manager can be applied in production within 3-4 months with SAP Syclo (part of SMP now). This all depends upon if you are looking to do more customizations and changes inside the application. Most of the customizations are configurable and can be done within a short duration.



Comment From Guest: What is the migration path and effort involved for moving from the old Mobile sales to CRM Sales Manager?

Sandeep Raina: SAP has provided a migration path to move from the old Mobile Sales to CRM Sales Manager. Some of the steps have to be done manually. There are a few ABAP programs and prerequisites available to perform the migration, such as copying the existing configuration, custom fields, distribution models, etc. into the Sales Manager configuration. All of these ABAP programs are available in OSS Notes and can be downloaded. There is a migration guide available on the service marketplace that has all the details. It has limited steps for the migration.



Comment From Guest: Any advice about security testing and ensuring security between the Sales Manager app and the backend CRM?

Sandeep Raina: Security can be tested based on the individual data for each sales rep. If you are doing modelling based on the territory management, data can be tested on the device to make sure security rules are applied. You can also turn off automatic device registration to make sure no devices can be registered without manual intervention from the administrator. There are additional security roles that can be applied if a user no longer wants to receive data. This can also be tested. You can monitor logs for your security objects.



Comment From Dave: How much customization is available in this app and do most users do a lot of customization or stick with the out-of-the box app?

Sandeep Raina: Hi Dave. SAP has redesigned the CRM Sales application to be highly customizable without changing frontend or backend code. You can add new screens, add new fields, add buttons, make fields mandatory, set up filter rules, etc. With SAP CRM, users typically want changes on the CRM mobile app. This is a common scenario that I have observed across all clients. Most of the requirements are around validation, new fields, new screens, etc.



Comment From Guest: How does Sales Manager tie into our running CRM processes? Should we plan for disruption/downtime in CRM during configuration?

Sandeep Raina: Sales Manager will run like any CRM internal process. During first-time setup, the installation of CRM/ECC add-ons will require downtime for 1-2 hours. These add-ons can be applied easily in the system without much disruption. This is a one-time activity for the first time setup.



Charlotte Christy: Thanks again, everyone, for all your great questions. And thanks again Sandeep, for joining us today. For more on this topic, I invite you to join us at CRM 2014 in Las Vegas April 1-4. Sandeep Raina will be presenting a session on this topic — part of our CRM   “Mobility” track, and there will also be sessions on mobile sales force automation and a panel on mobile strategies for CRM. We hope to see you in Vegas this spring!

Sandeep Raina: Thanks everyone for joining the Q&A session. See everyone at CRM 2014!

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!