crm mobile sales config guide

Sybase Mobile Sales 1.2.1 / SUP 2.0

SAP CRM 2007/ 7.0/ 7.0 EHP1

June 2011

English

CRM Mobile Sales and Gateway to SAP NW Mobile (C19)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices CRM Mobile Sales and Gateway to SAP NW Mobile (C19) – Configuration Guide

Copyright© Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP

© SAP AG of 39


Group 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.

Copyright © 2011 by Sybase, Inc. All rights reserved.

This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845.

Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc.

Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase and the marks listed are a trademark of Sybase, Inc. ® indicates registration in the United States of America.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world.

Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.

All other company and product names mentioned may be trademarks of the respective companies with which they are associated.

Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.

Sybase, Inc., One Sybase Drive, Dublin, CA 94568.

© SAP AG of 39


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 39


Content

1 Purpose........................................................................................................................................ 6

2 Preparation................................................................................................................................... 7

2.1 Prerequisites......................................................................................................................... 7

2.2 SAP Notes............................................................................................................................. 7

2.3 User Requirements...............................................................................................................8

2.4 RFC requirement...................................................................................................................8

3 Setting up the SAP CRM System.................................................................................................9

3.1 Business Function Settings (Only for CRM 7.0 EHP1)..........................................................9

3.2 General Customizing.............................................................................................................9

3.2.1 Defining Mobile Languages............................................................................................9

3.2.2 Defining Mobile Currencies..........................................................................................10

3.3 Defining the Date and Organization Filter...........................................................................11

3.3.1 Defining the Mobile Date Filter.....................................................................................11

3.3.2 Defining Mobile Organizations.....................................................................................12

3.4 Defining Upload and Download Parameters for Transaction Data......................................13

3.4.1 Downloading Parameters.............................................................................................14

3.4.2 Status Exclusion Filters................................................................................................15

3.4.3 Notes............................................................................................................................ 16

3.4.4 Updating Parameters...................................................................................................16

3.5 Defining Technical Settings.................................................................................................19

3.5.1 Create an RFC Destination to SAP NetWeaver Mobile 7.1..........................................19

3.5.2 Defining Mobile RFC Destinations...............................................................................20

3.5.3 Mapping the Mobile Data Object to the Back-End Business Object (BO)....................21

3.6 MBDOC Settings for the Delta Download............................................................................22

3.6.1 Activating the MBDOC Flow.........................................................................................23

3.6.2 Registering Queues.....................................................................................................25

4 Setting Up SAP NetWeaver Mobile 7.1......................................................................................26

4.1 Post-Installation Steps.........................................................................................................26

4.1.1 Configuring SAP NetWeaver Mobile 7.1......................................................................26

5 Setting Up the Gateway 1.1 to SAP NetWeaver Mobile.............................................................28

5.1 Configuring ICF Services....................................................................................................28

5.2 Configuring the Mobile Sales Application............................................................................28

5.3 Configuring Parameters for Message Monitoring................................................................31

5.4 Setting Up Users in the Data Orchestration Engine............................................................32

5.5 Assigning the Necessary Roles to the User........................................................................33

5.6 Setting Up Mobile Sales Customizing for Authorization......................................................33

6 Triggering the Initial Load from SAP CRM..................................................................................36

6.1 Report Execution for the Initial Download of Business Partners..........................................36

6.2 Executing the Initial Download of Transaction Data............................................................37

6.3 Executing the Initial Download for Other Data Objects from SAP Netweaver system.........38

7 References................................................................................................................................. 39

© SAP AG of 39


CRM Mobile Sales and Gateway to SAP NW Mobile

1 Purpose

This document provides information on how to set up the landscape for the CRM Mobile Sales application using the gateway 1.1 to SAP NetWeaver Mobile. The document provides links to various guides, installation sources, and the customizing information that is required to make the entire landscape functional. It includes setup information for SAP CRM, SAP NetWeaver Mobile 7.1, and Gateway 1.1 to SAP NetWeaver Mobile.

© SAP AG of 39


2 Preparation

2.1 PrerequisitesSAP Landscape and Version Verification

Verify that the SAP landscape has the required components and versions installed including SAP CRM, SAP NetWeaver Mobile, and the gateway to SAP NetWeaver Mobile.

SAP Product Supported Versions

SAP Customer Relationship Management (CRM) 2007 SP06 and later

7.0 SP05 and later

7.0 EHP1 SP04 and later

SAP NetWeaver Mobile 7.1 SP11

gateway to SAP NetWeaver Mobile 1.1 SP05

Entity Set Definitions for Mobile Applications (ESDMA) for CRM

MAS_SMARTPHONE_SALES_V00; version V9G001

Currently, the Gateway 1.1 to SAP NetWeaver Mobile is not supported on Enhancement package 1 of SAP NetWeaver Mobile 7.1.

2.2 SAP NotesRefer to following critical notes before proceeding further with the configurations.

SAP Note Short Text Comment

1574343Rapid deployment of Sybase Mobile Sales for SAP CRM

Refer to this note before you start implemention.

1497826NetWeaver Mobile 7.10 Composite Note for SP11

Make sure to implement all notes as mentioned in this note

1589289Release Information Note: SPS05 Gateway1.1 to NW Mobile 710

1449498 CRM 7.0 - Mobile Sales Analytics fixes

1600189CRM Mobile Sales - Missing relationship data on the device

1604174CRM Mobile Sales SP05 : Distribution Rules

Informatory Note on intended behavior of Distribution Rule

1504273Generation of Distribution Model fails with error

© SAP AG of 39


2.3 User Requirements1. All Mobile users in SAP CRM (Users to be subscribing) needs to also exist in DOE.

2. All CRM Mobile Users should also be Employees in SAP CRM system.

3. The “Employee Responsible” relationship must be set for all objects that need to be pushed

to the device with Default distribution model.

2.4 RFC requirement1. Between DOE and CRM, we should have trusted relationship set to current user.

2. Between CRM and DOE, we should have trusted relationship set to a fixed RFC user.

3. Fixed RFC user should exists with all regular user roles and RFC roles in DOE and CRM

system.

4. All Mobile Users need to be assigned RFC roles in DOE system.

© SAP AG of 39


3 Setting up the SAP CRM System

For installation information regarding the various versions of SAP CRM, see https://websmp108./instguides → SAP Business Suite Applications → SAP CRM.

3.1 Business Function Settings (Only for CRM 7.0 EHP1)

For Enhancement package 1 for SAP CRM 7.0, you must NOT activate the business function Sales and Service for Gateway to SAP NetWeaver Mobile (CRM_SLS_SRV_MOBILE_1).

Procedure1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu IMG ® Activate Business Functions

2. Ensure that the business function Sales and Service for Gateway to SAP NetWeaver Mobile (CRM_SLS_SRV_MOBILE_1) is NOT activated.

3.2 General Customizing

3.2.1 Defining Mobile Languages

Use

In this activity, you define languages. These settings can be used by SAP CRM applications for Smartphone.

This setting allows the administrator to maintain the languages needed for the smartphone scenario. One language is specified as the default language. If no languages are maintained, then English (EN) is the default language. The general customizing data that is downloaded to SAP NetWeaver Mobile 7.1 (SP11) for master and transaction data is always a subset of the core SAP CRM data.

Multilanguage tables contain data in the languages (other than the default language) you have maintained here.

The following languages are supported for the Sybase Mobile Sales rapid-deployment solution for SAP CRM: English (EN), German (DE), Spanish (ES), and French (FR).


© SAP AG of 39



SAP CRM IMG menu (CRM 7.0 or 2007)

Customer Relationship Management ® Mobile solutions for Smartphone ® Define General Customization

SAP CRM IMG menu (CRM 7.0 EHP1)

Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Technical Settings ® Define General Customization

2. Select Define Mobile Languages, and choose New Entries.

3. Enter the following values:

Field Name Field Entry

Language English, German, French, and so on

Description Description is automatically picked

Default Language Select Default language

4. Choose Save, and select a transport request if required.

ResultYou have created languages needed for your smartphone application.

3.2.2 Defining Mobile Currencies

UseIn this activity, you define currencies. These settings can be used by SAP CRM applications for Smartphone. The currencies you maintain here can form the dropdown values for a currency field on the client device.

The currencies maintained here are downloaded to the device as part of the initial download. This list is provided as a dropdown to the user on the smartphone device during creation of one-order documents.




Customer Relationship Management ® Mobile solutions for Smartphone ® Define General Customization


Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Technical Settings ® Define General Customization

2. Select Define Mobile Currencies, Choose New Entries



Currency USD, EUR, INR, and so on

Description Description is automatically picked

4. Choose Save, and select a transport if required.

© SAP AG of 39


ResultYou have maintained currencies for your smartphone.

3.3 Defining the Date and Organization Filter

3.3.1 Defining the Mobile Date Filter

UseIn this activity, you define the date range as filter for data to be sent from the back-end SAP CRM server to the middleware. Applications developed for smartphone devices can access this filtered data. This is required because all the data in the SAP CRM server database may not be required by smartphone users. You can define the date range (number of days in the past and in the future) filter for the following points:

Activities

Opportunities

Leads

The date filter is one of the criteria that can be used for the initial download of transaction data to SAP NetWeaver Mobile 7.1. If no date filter is maintained, then all data is downloaded to SAP NetWeaver Mobile 7.1. You can maintain separate date filters for each transaction object.

If values for Days Back and Days Ahead are zero, then data is not filtered based on date range.




Customer Relationship Management ® Mobile solutions for Smartphone ® Define Date and Organization filter for initial download


Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Sales ® Define Date and Organization filter for initial download

2. Choose Define Mobile Date Filter, and choose New Entries.



Activity Date Filter <Values for Days Back & Days Ahead>

Lead Date Filter <Values for Days Back & Days Ahead>

Opportunities Date Filter <Values for Days Back & Days Ahead>

© SAP AG of 39


If you want to see all your activities created in past one month and future two months, you can maintain Days back (30) and Days ahead (60).


ResultYou have successfully defined the date range for Lead/Activities/Opportunities, and so on, either for the past or/and the future for your smartphone.

3.3.2 Defining Mobile Organizations

UseIn this activity, you define organization parameters as filters for data to be sent from the back-end SAP CRM server to the middleware. Applications developed for smartphone devices can access this filtered data. This is required because all the data in the SAP CRM server database may not be required by smartphone users. You can define organizational filters based on any of the following parameters:

Sales Organization

Distribution Channel

Sales Office

Sales Group

In addition to the date filter, transaction data can also be filtered based on the sales organization data. The administrator can maintain the mobile-specific sales organizations here. If nothing is maintained, then all organizations are taken into consideration for the initial data download from SAP CRM to SAP NetWeaver Mobile 7.1.

Once maintained, the data filtering is done based on the combination of sales organization, the distribution channel, the sales office, and the sales group. Multiple combinations can be maintained here.

If values for organizational parameters have not been maintained, then data is not filtered based on organizational parameters.




Customer Relationship Management ® Mobile solutions for Smartphone ® Define Date and Organization filter for initial download


Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Sales ® Define Date and Organization

© SAP AG of 39


filter for initial download

2. Choose Define Mobile Organizations, and choose New Entries.



Sales Organization <Values - Organization ID>

Distribution Channel <Values for your distribution channel>

Sales Office <Values for your sales office>

Sales Group <Values for your sales group>

4. Choose save and select a transport if required.

ResultYou have successfully created the organization filter for your smartphone.

3.4 Defining Upload and Download Parameters for Transaction Data

UseIn this activity, you define the parameters based on which data is uploaded or downloaded for the following business transactions:

Activities

Opportunities

Leads

The above parameters are used by function modules to filter data during download, and for defaulting values during upload. Applications, which make use of these customizing settings, can be developed on smartphone devices for information exchange with the back-end SAP CRM server.

For each of the above business transactions, you can define the following download criteria:

The download criteria based on which business transaction data can be downloaded from the SAP CRM server to the middleware. You can further filter the data by defining a transaction status as the criterion for excluding transactions from being downloaded. Business transactions having the status defined by you are not downloaded.

To download the transactional data, it is mandatory to customize download parameters on the SAP CRM system.

If upload parameters are configured, it is mandatory to maintain download parameters.

The parameters or criteria, such as relevant transaction types, are customer-specific; below, only an example is described. See the Scoping Questionnaire to find customer-specific information.

© SAP AG of 39


You can maintain a set of partner functions for the download of each transaction type. If nothing is maintained, then the partner functions maintained as upload parameters is used.

3.4.1 Downloading Parameters

UseOnly the transactional data belonging to transaction types maintained in customizing is downloaded to SAP NetWeaver Mobile 7.1. There are four partner functions that are downloaded for each transaction object, except for opportunities, which has eight partner functions. The partner functions configured in the download parameters are downloaded to the device for any one-order document.

The following table shows one way of configuring the partner functions for the different transaction objects (for both upload and download parameters):

Partner Function ->

PF1 PF2 PF3 PF4 PF5 PF6 PF7 PF8

Activities Activity partner

Contact person

Can be any partner function (usually Attendees partner function).

Employee responsible

NA NA NA NA

Leads Prospect Contact person

Can be any partner function (usually Sales representative partner function).


NA NA NA NA

Opportunity Prospect Contact person

Can be any partner function (usually Sales representative partner function).


Sales team

Sales team

Sales team

Competitor




Customer Relationship Management ® Mobile solutions for Smartphone ® Define Upload and Download Parameters for Transaction Data


Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Sales ® Define Upload and Download Parameters for Transaction data

For example, if you want to define Lead Download Criteria, proceed as follows:

© SAP AG of 39


1. Select Lead Download Criteria.2. Choose New Entries.3. Choose the required transaction types and partner functions.

To define Download criteria for other transaction types (Opportunities/Activities), repeat the steps 1 to 3.



Transaction Type <LEAD/Activities etc.>

Description Values are automatically picked

Partner Function 1/2/3/4 <Values >


ResultYou have successfully defined download criteria for your transactions.

3.4.2 Status Exclusion Filters

UseFor each transaction type that is maintained in the download parameters, there is an associated exclusion status.

For example, you maintain a filter for the status LOST in the exclusion filter for the LEAD transaction type. As a consequence, the system does not send any objects of transaction type LEAD with the status LOST to the device. If you do not maintain anything, then the system sends objects of all statuses to the device, there would be no filtering according to the status.






Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Sales ® Define Upload and Download Parameters for Transaction Data



Status Profile <CRMLEAD for LEAD>

Status <E004 for Lost Leads>

Status Description Automatically picked

© SAP AG of 39



ResultYou have successfully created an exclusion filter for your LEAD transaction type. Similarly, you can set it up for other one-order objects like activities or opportunities, and so on.

3.4.3 Notes

UseIn this activity you define the note type to be downloaded.

This note type is also the default note type for business transactions created on the smartphone devices and uploaded to the SAP CRM server.

You can maintain a maximum of one note type in the IMG customizing for all the transaction objects. This note type is only supported during creation and download of transaction data.







2. Choose Lead Notes/Activity Notes/Opportunity Notes, select New entries



Text Object CRM_ORDERH

Description Automatically picked

Text ID <Example – Note A002>



ResultYou have successfully created the note type to be defaulted while creating and viewing any one-order, for example LEAD/Activity, and so on.

© SAP AG of 39


3.4.4 Updating Parameters

UseYou define the default parameters to be used when creating a business transaction on the smartphone.

The partner functions configured here are used during the creation of the one-order document. These parameters are mandatorily to be maintained for the creation scenario. The business partner IDs passed from the client is mapped to the corresponding partner function slots.

Customers can add the partner functions according to the business requirements.

When a transaction application is created, the system reads the parameters from the upload parameters customizing table. The partner function values are read from the upload parameters customizing table. If the user enters a business partner ID while creating the transaction, the business partner ID is stored in the role of the corresponding partner function maintained during customizing.

For example, in the case of an opportunity, partner function 00000021 (Sales Prospect) is maintained as Partner Function1 in the upload parameter customizing. If the user enters a business partner ID in the Main Partner 1 field, then the business partner is saved as the sales prospect for that opportunity.







2. Select the parameter you want to update:

Activity Update parameter

Opportunity Update parameter

Lead Update Parameter

3. Choose New Entries.

4. Enter the following values for Activities:


Activity Type <Send Email/Receive Email, and so on>

Transaction Type <Transaction type>

Category <Values for categories>

Status <Values for status>

Priority <Values for priority>

© SAP AG of 39



Goal <Values for Goal>

Partner function 1/2/3.. <Values of Partner functions>

Date Type <Values of Date type>

You must maintain default values as part of the customizing for the creation of activity transactions. The values that must have a default value are as follows:

• Activity type

• Process type

• Category

• Status

• Priority

• Goal

• Partner functions

• Date type

Whenever the user creates a new activity on the client, these default values are used. When the activity is passed back to the device after creation in SAP CRM, the download customizing parameters are taken into consideration.

Only the following activity transaction types are supported during activity creation from the client:

Send Mail

Receive Mail

Outgoing Phone Call

Incoming Phone Call

Appointment

Task

Activity with Invitation to Internal Colleagues

5. Enter the following values for Opportunities:


Transaction Type <Values>

Description <Values >

Status <Values >

Partner function 1/2/3.. <Values >

Date Type <Values >

© SAP AG of 39


You must maintain default values as part of the customizing for the creation of opportunities. Only one transaction type is supported during creation. The values that must have a default value are as follows:

• Transaction type

• Status

• Date type

• 8 partner functions

Among the 8 partner functions, partner function slots 5, 6, and 7 are for the Sales Team and slot 8 is for Competitor.

6. Enter the following values for Leads:


Transaction Type <Values>

Status <Values >

Partner function 1/2/3.. <Values >

Date Type <Values >

You must maintain default values as part of the customizing for the creation of leads. Only one transaction type is supported during creation. The values that must have a default value are the following:

• Transaction type

• Status

• Date type

• 4 partner functions


ResultWhenever the user creates a new activity, opportunity or lead on the client, these default values are used. When the activity is passed back to the device after creation in SAP CRM, the download customizing parameters are taken into consideration.

3.5 Defining Technical Settings

3.5.1 Create an RFC Destination to SAP NetWeaver Mobile 7.1

UseTo allow the back-end to exchange data with SAP NetWeaver Mobile 7.1, you must create an RFC destination.

© SAP AG of 39


Procedure1. Access the activity in CRM system using the following transaction:

CRM Transaction code

SM59

2. To create an RFC destination, choose Create.



RFC Destination <RFC destination of the server>

Connection Type 3 (ABAP Connection)

Description 1 <Description>

4. Choose the Technical Settings tab. Specify the Target Host, System Number. Other fields are not mandatory.

5. Choose the Logon & Security tab page.

a. Select Yes for Trusted Relationship.

b. Enter the Client and User details.

The User specified in RFC destination should be created in CRM and SAP NetWeaver Mobile system with S_RFCACL authorization assigned.

6. If you are using the Unicode format for representing the data, in the MDMP & Unicode tab, select the Unicode indicator.

7. Save your entries and confirm the message that appears.

8. To test the RFC connection, choose Connection Test.

ResultOn choosing Remote Logon, the SAP NetWeaver Mobile 7.1 system is displayed with the current user login.

3.5.2 Defining Mobile RFC Destinations

UseYou can maintain multiple SAP Netweaver Mobile 7.1 middleware destinations in this customizing

setting. The active flag indicates which connections are currently enabled.

.




Customer Relationship Management ® Mobile solutions for Smartphone ® Define Technical settings


Customer Relationship Management ® Gateway to SAP

© SAP AG of 39


NetWeaver Mobile ® Technical Settings ® Define Technical settings

10. Select Define Mobile RFC destinations, and choose New Entries.



RFC Destination <RFC destination of the server>


Active Should be checked as active

Date Type <Values>


ResultYou have successfully defined the RFC destination.

3.5.3 Mapping the Mobile Data Object to the Back-End Business Object (BO)

UseIn this activity, you define the mapping of the mobile data objects to backend BOs.

These settings ensure that back-end data is correctly mapped when it is downloaded to the middleware.

For the initial data download and also for the delta scenarios, back-end business object names are needed to be mapped to the mobile data objects in SAP NetWeaver Mobile 7.1. The back-end BO names mentioned below are the values present against the Backend BO Names of the respective data objects in the SAP NetWeaver Mobile 7.1.




Customer Relationship Management ® Mobile solutions for Smartphone ® Define Technical settings


Customer Relationship Management ® Gateway to SAP NetWeaver Mobile ® Technical Settings ® Define Technical settings

2. Select Map Mobile Data Object.

© SAP AG of 39


Sales Orders and Service Orders are not part of the Sybase Mobile Sales rapid-deployment solution for SAP CRM.



Mobile Data Object 01 – Business Partner

03 – Activity

04 – Lead

05 – Opportunity

08 – Customization

09 – Interaction History

Backend BO name

For 01 - MAS_PARTNER_14

For 03 – MAS_ACTIVITY_14

For 04 – MAS_LEAD_14

For 05 – MAS_OPPORTUNITY_14

For 08 – MAS_CUSTOMIZATION_14

For 09 – MAS_HISTORY_14


ResultYou have successfully mapped back-end objects with mobile sales objects.

3.6 MBDOC Settings for the Delta Download

UseTo enable the delta download, the following entries need to be enabled in the table SMW3FDCUST. The first entry is for transaction related data such as activities, opportunities, and leads. The second and the third one are for the business partner, for the changes at the header and child level respectively.

Procedure1. Access the activity using the following transaction code:

Transaction code SM30

Table SMW3FDCUST

2. Enter the Following Values:

1st Entry:

© SAP AG of 39



BDOC type BUS_TRANS_MSG

Context MOA

Sequence 0025

Service Function CRM_1ORDER_DELTA_MOBILE_MBDOC

Entry Active Check the flag

2nd Entry:


BDOC type BUPA_MAIN

Context MOA

Sequence 0011

Service Function CRM_BUPA_DELTA_MOBILE_MBDOC


3rd Entry:


BDOC type BUPA_REL

Context MOB

Sequence 0011

Service Function CRM_BUPA_REL_DELTA_MOB_MBDOC


3. Remove the Active flag against all the Bdoc Type: BUPA_REL and Service Function: BP_REL_CRM_TO_CDB.


ResultYou have successfully entered values for data replication for transactions and business partners.

3.6.1 Activating the MBDOC Flow

3.6.1.1 MBDOC Components to Activate

ProcedureYou must activate the following MBDOC components:

Data synchronization

Adapters

Generation service

© SAP AG of 39


Middleware

Replication and realignment

3.6.1.2 Activation Check for MBDOC Components

UseIn this activity, you check different middleware parameters:

Transaction: CMWC_SMW.

Data Sync Active entry is available and selected.

Transaction: SE16. Table: SMW3FDCUST.

Entries are present and active (Active field value is X for some of the entries).

Transaction: GENSTATUS.

Status of periodic job is green.

SAP system is green (waiting/running).

Transaction: MW_MODE.

Message processing: On is selected.

Transaction: SMOHQUEUE.

Status of Queue Daemon is: Released or Running.

When you choose Start Queue Daemon, the system displays the message Starting queue daemon not necessary. Already started.

Procedure

1. Go to following transaction code:

Transaction code CMWC_SMW

2. If the Data Sync Active entry is available, but not selected, select it. Otherwise, create a new entry for Data Sync Active and select it.

If working in a client other than 000, you must copy the data for table SMW3FDCUST from client 000 to the current working client.


Transaction code GENSTATUS

4. If the status of the SAP system is Error (Red), and the errors are memo conversion errors, then run the report CMW_LOB_MIGRATION in transaction SE38.

5. If the Status of periodic job is not green, then choose Start Generation Job.


Transaction code MW_MODE

7. To activate the middleware, select On for message processing. Save your change.

8. Go to transaction code:

Transaction code SMOHQUEUE

© SAP AG of 39


Logical destination should have been setup for starting the queue daemon in transaction SMOHQUEUE. In transaction SM59, under Logical Connections, you may find the required entry, SAPCRM_MW_RR_000.

9. Choose Start Queue Daemon. 10. Check if the Status of Queue Daemon is Released or Running.

When you choose Start Queue Daemon, the system displays the message Starting queue daemon not necessary. Already started.

ResultYou have successfully enabled the middleware for replicating data

3.6.2 Registering Queues

UseIn this activity, you register queues for data replication to NetWeaver Mobile 7.1.

Procedure 1. Access the activity using the following transaction code:

Transaction code SMQR

2. Register the following queue patterns:

MAS*

INT*

BP_QUEUE

HISTORY_QUEUE

ACTIVITY_QUEUE

OPPT_QUEUE

LEAD_QUEUE

CUST_QUEUE

SO_QUEUE

SRV_QUEUE

© SAP AG of 39


4 Setting Up SAP NetWeaver Mobile 7.1 You can find both the software and the Installation Guides on the SAP Service Marketplace.

4.1 Post-Installation Steps Once you have installed SAP NetWeaver Mobile 7.1, follow the following steps to make it ready for use.

4.1.1 Configuring SAP NetWeaver Mobile 7.1Before users can work with SAP NetWeaver Mobile, you must perform a number of configuration and setup tasks. You must configure various technical components, upload data from the back–end system, and edit master data to enable applications for occasional connections. For more information about the possible configurations, see System Configuration and Administration ® Configuration Guide on the SAP Help Portal.

There are a lot of configurations mentioned in the above link target, but you do not need to maintain them all for the SAP CRM Sales scenario. This section contains a step-by-step guide to the steps that are required. These steps have been taken straight from the configuration guide itself and all the following links refer to one of the subsections of the main guide.

You must complete all the configuration steps that apply to your newly installed AS ABAP system for SAP NetWeaver Mobile. This topic contains all the steps that you have to perform after installation.

4.1.1.1 Creating an Administrator ProfileOnly an administrator profile for the Data Orchestration Engine allows you to perform all the configuration activities that are listed below.

For more information, refer to Creating an Administrator Profile and Mobile.

4.1.1.2 Log On to SAP NetWeaver Mobile AdministratorAll administration-related activities for SAP NetWeaver Mobile 7.1 are accessible through the SAP NetWeaver Mobile Administrator. The administration activities include the configuration of the SAP NetWeaver Application Server.

Fo more information, see Logging on to SAP NetWeaver Mobile Administrator.

4.1.1.3 Creating an RFC Destination to the Back-End SAP CRMTo allow SAP NetWeaver Mobile 7.1 to exchange data with the back-end, you must create an RFC destination. This RFC destination ensures that the DOE can process the back-end data.

© SAP AG of 39

http://help.sap.com/saphelp_nwmobile71/helpdata/en/c9/44ca6dd5404574bf919445ace4bc1c/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/17a790d8000064e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/de/14/82e0ff49414164a2cc5da54d9a9b0e/frameset.htm

http://help.sap.com/nwmobile71/

https://websmp202.sap-ag.de/operationsnwmobile71

https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000696241&


Procedure1. Access the activity in NW system using the following transaction:

NW Transaction code SM59

2. To create an RFC destination, choose Create.



RFC Destination <RFC destination of the CRM server>

Connection Type 3 (ABAP Connection)

Description 1 <Description>

4. Choose the Technical Settings tab. Specify the Target Host, System Number. Other fields are not mandatory.

5. Choose the Logon & Security tab page.

a. Select Yes for Trusted Relationship.

b. Enter the Client.

c. Select Current User checkbox.

6. If you are using the Unicode format for representing the data, in the MDMP & Unicode tab, select the Unicode indicator.

7. Save your entries and confirm the message that appears.

8. To test the RFC connection, choose Connection Test.

ResultOn choosing Remote Logon, the SAP CRM system is displayed with the current user login.

© SAP AG of 39


5 Setting Up the Gateway 1.1 to SAP NetWeaver Mobile

You must go through the following steps after installing the add-on Gateway 1.1 to SAP NetWeaver Mobile 7.1.

5.1 Configuring ICF ServicesThe Gateway 1.1 to SAP NetWeaver Mobile provides default ICF services as follows:

No Service Name Description

1 DOE_ESDMA_SOAP Used for the DOE connector entry point

2 DOE_XSD_DATATYP Used for referencing the SDOE data types while setting up the enterprise tool for each of the WSDL files

3 SDOE_ESDMA_APPLN_SETUP Used for setting up the ESDMA application

You must activate the above mentioned ICF services in the system.

Procedure1. Access the activity using the following transaction code:

Transaction code SICF

2. Choose Execute.

3. Enter the Service Name (provided in the table above) in the Service field, and choose Apply.

4. Right-click on the service which was displayed in the Services list displayed in the table above.

5. Select Activate Service from the list of options.

6. Repeat the same steps for the rest of the services listed in the table.

5.2 Configuring the Mobile Sales Application

UseTo streamline the configuration of the Gateway to NetWeaver Mobile, you use the ESDMA application setup wizard.

Prerequisites

© SAP AG of 39


You need to assign the role SAP_SDOE_ESDBR_DWLD to access the setup wizard.

You need to perform the application setup after applying all the mandatory notes as mentioned in the Release and Information Note of corresponding SP Release (eg 1589289 for SP05). Refer to SAP Notes section for all mandatory notes before proceeding. If you have already setup and configured the application before performing an upgrade to the latest SP release, it is recommended that you configure the application again by performing the steps as described below.

Refer to Note 1604174 (CRM Mobile Sales SP05 : Distribution Rules) for understanding the intended behaviour of the underlying distribution rule.

You need to have all the DOs generated successfully. Some of the DOs may not be generated correctly. For manual generation:

1. Log on to the SAP NetWeaver Application Server.

2. Go to the Workbench (transaction: sdoe_wb).

3. Select Object Name ‘MAS_SMARTPHONE, 1.4 of SAP’, go to Data Object Category > Standard > Data Objects and generate (if the status is not GREEN) the DO’s: MAS_SURVEY & MAS_FACTSHEET.

4. Select Object Name ‘MAS_SMARTPHONE_DMSCV,1.4 of SAP’, go to Distribution Model and generate (if the status is not GREEN) the DM’s: DM_PARTNER & DM_SURVEY.

The RFC destination for CRM System must have been setup correctly in Netweaver. To check the RFC Destination:

1. Log on to the SAP NetWeaver Application Server.

2. Go to transaction: SM59

3. Under ABAP Connections, Select the RFC Destination for CRM System.

4. Click on Remote Logon. It should take you to the CRM system.

Procedure 1. Log on to the SAP NetWeaver Application Server.

2. Choose ESDMA Application Setup.

3. Choose the following ESDMA application for which the setup process should be performed:

ESDMA Name Version Number

MAS_SMARTPHONE_SALES_V00 V9G001

4. Choose Start Setup.

5. On the Backend Destination Configuration screen, enter the following values:

Software Component Version RFC Destination

MAS_SMARTPHONE , 1.4 of SAP <RFC Destination name to the CRM system>

SAP BASIS 7.10 NONE

© SAP AG of 39


Software Component Version

Data Object RFC Destination

Configure RFC Destination for Data Object

MAS_SMARTPHONE, 1.4 of SAP

MAS_ANALYTICS_GRAPH NONE


MAS_SALESTEAM NONE


MAS_USER_POSITION NONE

The RFC destination for the rest of the data objects displayed should be left blank. If you see any pre-existing RFC Destination for the rest of data objects, delete that entry and make it blank.

6. To perform the data load during the Application Setup, select Enable data load along with Application Setup

7. Choose Next.

8. On the ESDMA Configuration screen, select MAS_SMARTPHONE_DMSCV, 1.4 of SAP from the list.

9. Choose Next.

10. On the Backend Search Function Configuration screen, verify the RFC destinations for the data objects. Please note that only 2 RFC destinations are set to NONE.

Data Object Backend Search BAPI RFC Destination

MAS_ACTIVITY CRM_ACTIVITY_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_ANALYTICS_GRAPH CRM_ANALYTICS_GRAPH_SEARCH NONE

MAS_HISTORY CRM_INTERACTION_MOB_SEARCH <RFC Destination to CRM system>

MAS_LEAD CRM_LEAD_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_OPPORTUNITY CRM_OPPT_MOBILE_RISK <RFC Destination to CRM system>

MAS_OPPORTUNITY CRM_OPPT_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_OPPORTUNITY CRM_OPPT_MOBILE_TOP <RFC Destination to CRM system>

MAS_PARTNER CRM_BUPA_MOB_SEARCH_GETLIST <RFC Destination to CRM system>

MAS_PRODUCT CRM_PRODUCT_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_SALESTEAM CRM_ANALYTICS_SALES_BE_CALL NONE

MAS_SALES_ORDER CRM_SO_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_SALES_ORDER CRM_SO_MOBILE_TOP <RFC Destination to CRM system>

MAS_SERVICE_ORDER CRM_SRV_MOBILE_SEARCH <RFC Destination to CRM system>

MAS_USER_POSITION CRM_ANALYTICS_USR_POS_GET <RFC Destination to CRM system>

© SAP AG of 39


11. Choose Next.

12. On the Rule Activation screen, select all rules.

13. Choose Activate.

14. Choose Next.

15. On the Synchronous Extract Configuration screen, enable all the data objects listed in the table.

16. Choose Finish.

17. Use transaction SMQ2 to monitor the queue SDOE_APPSETUP_Q. It usually takes long time (at least few hours) to clear the queue.

18. Once the queue is clear, On SAP Easy Access Menu, click on ESDMA Design Time. Select the following ESDMA Name depending on the CRM Release Version. Click on Display. The ESDMA Generation State must be GREEN.

ESDMA Name Version Number

MAS_SMARTPHONE_SALES_V00 V9G001

19. Click on Download Bundles. Save the ESDMA Bundle for use during Sybase Installation.

ResultOnce the configuration is complete, the status of the application changes to green. You can use transaction SMQ2 to monitor the queue SDOE_APPSETUP_Q.

The ESDMA Generation State must be GREEN to suggest a successful generation of Data Objects.

ESDMA Bundle is used during Sybase Installation.

The initial setup of the mobile sales application is configured when the queue entries have been executed successfully.

Refer to Note 1604174 (CRM Mobile Sales SP05 : Distribution Rules) for understanding the intended behaviour of the underlying distribution rule.

5.3 Configuring Parameters for Message Monitoring

You use this procedure to specify values for the monitoring parameters.

Procedure

© SAP AG of 39


1. Choose transaction SDOE_PARAM to open the parameter configuration table.

2. Select the row that contains the DOE_CONNECTOR parameter key.

3. Double-click the Parameter Names node.

4. Select the row that contains the parameter name (for each parameter listed below).

5. Double-click the Parameter Values node.

6. Choose Display -> Change.

7. Enter the values for Text Value and Num Value columns as mentioned below for each of the Parameter Name (& Validity Subarea) combination:

Parameter Name Description Validity Subarea Num Value

Text Value

ENABLE_LOGGING Set this parameter to X to enable logging.

X

LOG_SOAPS_MSGS Set this parameter to X to log the SOAP messages exchanged between the client and the server.

X

PROXY_HOST

Specify the name of the proxy server that you use to connect to the Internet.

<Proxy server name>

PROXY_PORT Specify the port of the proxy server to use.

<Proxy port>

BE_SEARCH_RFC Specify RFC destination name to the CRM system for BE Search Function Modules

CRM_ANALYTICS_GRAPH_SEARCH

<RFC destination to CRM system>

BE_SEARCH_RFC Specify RFC destination name to the CRM system for BE Search Function Modules

CRM_ANALYTICS_SALES_BE_CALL

<RFC destination to CRM system>

5.4 Setting Up Users in the Data Orchestration EngineTo set up users in the Data Orchestration Engine (DOE), you must follow the standard SAP authorization concept. You must use the SAP Identity Management tools to create users and authorizations. These tools must be available either in the back-end or in the system on which SAP NetWeaver Mobile 7.1 is installed.

Once you have created users and their authorizations, you must have this data available in SAP NetWeaver Mobile 7.1; SAP NetWeaver Mobile 7.1 stores the information in the User Details and User Authorizations data objects.

Procedure 1. Create users in the back-end or in the system on which SAP NetWeaver Mobile 7.1 is

installed. For more information, see Creating and Maintaining User Master Records.

The user you create in the current system has to have the same user name as available in the CRM system.

2. Assign roles to users in the back-end, or in the system on which SAP NetWeaver Mobile

© SAP AG of 39

http://help.sap.com/saphelp_banking463/helpdata/en/52/67116a439b11d1896f0000e8322d00/frameset.htm


7.1 is installed. For more information, see Authorizations.

All mobile users must have the authorization object S_RFCACL assigned.

3. Download the user details to the User Details data object. For more information, see Downloading Details into User-Details Data Object.

4. Download the user authorizations to the User Authorizations data object. For more information, see Downloading Details into User Authorizations Data Object.

5.5 Assigning the Necessary Roles to the UserThe additional roles created for Gateway 1.1 to SAP NetWeaver Mobile in addition to the standard roles available in NW Mobile 7.1 are listed below. The system users are mainly categorized as follows:

Users Roles

Administrators SAP_SDOE_ESDBR_DWLD role and the relevant administration roles for SAP NetWeaver Mobile 7.1 access

Developers SAP_SDOE_ESDBR_DWLD role and the developer roles in SAP NetWeaver Mobile 7.1

Synchronization Users SAP_DOE_SYNC_ROLE and SAP_DOE_ADMINISTRATOR

The additional roles required for the Gateway 1.1 to SAP NetWeaver Mobile 7.1 are specified below. Assign the roles to the user as needed.

SAP_SDOE_ESDBR_DWLD: The master role for the SAP NetWeaver Mobile 7.1 connector gives you permissions to perform administration, development, and monitoring. A user with administrator and developer privileges needs this role.

SAP_SDOE_ESDBR_VIEW: This role limits the permission to display of the ESDMA browser tool. You can assign this to a user who needs to search for the details of the various ESDMAs published in the system.

5.6 Setting Up Mobile Sales Customizing for Authorization

Use You have to manually enter the upload and download parameters that are specified during the customizing of Mobile Sales in the SAP CRM system in the SAP NetWeaver Mobile 7.1 system.

Procedure1. Access the activity using following transaction code:

Transaction code SE37

Report Name CRM_AUTH_CUST_INSERTCDS

2. Run the report CRM_AUTH_CUST_INSERTCDS.


© SAP AG of 39

http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/1c230fe9754a8be10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/1c1e9bbdf90066e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/en/f8/b6863f445f4617e10000000a114084/frameset.htm



ET_AUTH_CUST_HEADER <Version>

<Description>

4. Enter the values for the Version and Description fields in the root node ET_AUTH_CUST_HEADER. These values can be anything. You must enter only one row.

Version – 01 and Description – Authorization Customizing Data

The following child nodes should be filled with the specified values. You can enter more than one row, but the key fields should not be duplicated.

ET_AUTH_CUST_ACTIVITY

1. BUS_CAT (K) – Leading business transaction category for activity

2. DIRECTION (K) – D for download parameters, or U for update parameters

3. PROCESS_TYPE (K) – Transaction type for activity

4. ACTIVITY_TYPE (K) – For download parameters, it should be blank, and for update parameters, it should be the values specified on the Activity Update Parameters screen; for example, 01 for Send E-Mail, or 02 for Receive E-Mail

5. DESCRIPTION – Transaction description field on the Activity Download Criteria screen for direction D, and activity type description for direction U; for example, Send E-Mail for 01, or Receive E-Mail for 02

For the rest of the fields, enter the values specified on the Activity Download Criteria or Activity Update Parameters screen. For the fields that are not part of the customizing screens, do not enter values.

ET_AUTH_CUST_OPPT

1. BUS_CAT (K) - Leading business transaction category for opportunity


3. PROCESS_TYPE (K) – Transaction type for opportunity

For the rest of the fields, enter the values specified on the Opportunity Download Criteria or Opportunity Update Parameters screen. For the fields that are not part of the customizing screen, do not enter values.

ET_AUTH_CUST_LEAD

1. BUS_CAT (K) - Leading business transaction category for lead


3. PROCESS_TYPE (K) – Transaction type for lead

For the rest of the fields, enter the values specified on the Lead Download Criteria or Lead Update Parameters screen. For the fields that are not part of the customizing screen, do not enter values.

© SAP AG of 39


For an activity, your entries should be as follows:

BUS_CAT D PROC AC DESCRIPTION ACT ACT_S A ACT ACT_PART ACT_PART ACT_PART

BUS2000126 D Y005 Outbound Email 00000009 00000015 00000014

BUS2000126 U Y005 1 Send Email INT E0001 5 2 00000009 00000015 00000014

4. Execute the report.

5. Check the customizing values that you have entered in step 3.

6. Access the activity using the following transaction code:

Transaction code SDOE_WB

7. Select Component - MAS_SMARTPHONE , 1.4 of SAP.

8. Select the Data Object category.

9. Select standard.

10. Select data objects.

11. Select and expand MAS_AUTH_CUST.

12. Go to the Node Structure.

13. Check the ET_AUTH_CUST_HEADER node. Here, you find a z table created. Check the table for root node entries. Similarly, you have to check all three child nodes and the values in corresponding z tables.

© SAP AG of 39


6 Triggering the Initial Load from SAP CRM

6.1 Report Execution for the Initial Download of Business Partners

PrerequisitesBefore executing this report, the Mobile Sales for Smartphone scenario has already been deployed and configured on the SAP NetWeaver Mobile 7.1 system, and the RFC connections have been maintained between SAP CRM and SAP NetWeaver Mobile 7.1, and also specified as a part of the technical settings described in the step Defining Technical Settings.

The BP download should not be triggered from DOE since it cleans up the existing BP data in the DOE system.

The data downloaded are based on the RFC language configured from the SAP NetWeaver Mobile 7.1 to SAP CRM.

UseYou run this report to download business partner data to the middleware (DOE of SAP NetWeaver Mobile). The customizing settings in Define Technical Settings are also applied when this report is executed. You can define the following filters when executing this report:

Role and category of business partner - When the business partner category is blank, all business partners are downloaded

Relationship category of contact and employee

Other filters - This is not mandatory

Include the interaction history of business partners. When this option is deselected, the interaction history for a business partner is downloaded only when there is a change in data for that business partner or a related interaction

Procedure1. Log on to CRM System.

2. Access the activity using the following transaction code and click on Execute:


SE38

Report Name CRM_BUPA_MOBILE_INITIAL

3. On the selection screen, specify following download criteria:

a. Contact Person Reltyp: BUR001 – Has Contact Person

b. Employee Reltyp: BUR011 – Has the Employee Responsible

© SAP AG of 39


4. Run the report and, based on the download criteria, the system downloads the business partners to SAP NetWeaver Mobile 7.1.

Distribution Model - Business Partner as Leading Object

Business partner distribution is achieved by using a rule which ensures that users get only those business partners for which they are the responsible employees. The Standard Rule to be shipped is

MAS_SMARTPHONE_DMSCV, 1.4 of SAP. Refer to transaction sdoe_wb on the DOE system. Distribution Rule Name - DEV_RULE_USER.

The association between one-order objects (for example Activity, Leads, Opportunity, Sales Order) and Business Partner data objects is used to create a dependency for an efficient distribution of one-order object data. In this distribution model, we have a dependency with contacts and relationship nodes of Business Partner data object, too, so that all contacts and relationships, which are maintained, are downloaded.

By default, this is the active Distribution Model.

6.2 Executing the Initial Download of Transaction Data

UseYou run this report to download transaction data to the middleware (DOE of SAP NetWeaver Mobile). Relevant customizing settings under Mobile Solutions for Smartphone are also applied when this report is executed. You can define the download when executing this report:

Activities

Opportunities

Leads

Customization Data

Procedure1. Log on to CRM System.

2. Access the activity using the following transaction code:


MOBILE_INIT_DOWNLOAD

3. Here, the user can select the required objects such as activity, and then only activity is downloaded to SAP NetWeaver Mobile 7.1 based on the activity download parameters maintained during customizing.

Note that any changes done to the customizing on the back-end after the initial download need a delta download triggered from the SAP NetWeaver Mobile 7.1.

Sales Orders and Service Orders are not in part of the Sybase Mobile Sales rapid-deployment solution for SAP CRM.

Distribution Model - Transactional Data (Activity) as leading object

© SAP AG of 39


The Transactional Data object data can also be distributed based on responsible employee for the object alone. The Standard Rule which is shipped and in which Activity is the leading object and the Business partner object follow it.

MAS_SMARTPHONE_DMSCV_TR_MD , 1.4 of SAP. Refer the transaction sdoe_wb on the DOE system.

Distribution Rule Name –

1. DEV_RULE_USER_CHILD

2. DEV_RULE_USER_TOP

6.3 Executing the Initial Download for Other Data Objects from SAP Netweaver system

For all the data objects specified, the initial download has to be triggered from the SAP NetWeaver Mobile 7.1.

Mandatory Objects:

MAS_EMPLOYEE

Optional Objects:

MAS_EMPLOYEE_SUBGEN

MAS_ORG_SUBGEN

MAS_EMPLOYEE_RECBGEN

Procedure1. Log on to Netweaver System.2. Access the activity using the following transaction code:

Transaction code SDOE_LOAD

3. Execute transaction SDOE_LOAD.4. Enter the following values:


Software Component Name MAS_SMARTPHONE, 1.4 of SAP

Data Object MAS_Employee

Load Type Initial

DOE triggered Adapters only Check

5. Execute.

ResultYou have triggered the load in the back-end.

© SAP AG of 39


On Netweaver SAP Easy Access Menu, click on Data Orchestration Admin and Monitoring Portal > Administration > Distribution Rule Administration and check if all the Distribution Models are in Active(GREEN) state or not. In case some of them are not active (YELLOW), then select and click on Repair to activate them.

Useful Troubleshoot Links on Netweaver SAP Easy Access Menu:

Data Orchestration Admin and Monitoring Portal> Monitoring > Message Monitoring

Data Orchestration Admin and Monitoring Portal> Monitoring > Data Monitoring

Data Orchestration Admin and Monitoring Portal> Monitoring > Logs & Traces

Session Monitoring for DOE Connector

Subscription Monitor for DOE Connector

7 ReferencesYou can find various articles that are useful in the context of this document in the SAP Developer Network .

© SAP AG of 39

http://www.sdn.sap.com/

http://www.sdn.sap.com/

crm mobile sales config guide

Documents