Sup Sample Sales Force Automation

Sample: Sales Force Automation

Sybase Unwired Platform 2.1ESD #3

DOCUMENT ID: DC01389-01-0213-01LAST REVISED: April 2012Copyright © 2012 by Sybase, Inc. All rights reserved.This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions ortechnical notes. Information in this document is subject to change without notice. The software described herein is furnishedunder a license agreement, and it may be used or copied only in accordance with the terms of that agreement.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 priorwritten permission of Sybase, Inc.Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase andthe marks listed are trademarks 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 registeredtrademarks 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 Oracle and/or its affiliates in the U.S. and othercountries.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 areassociated.Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS52.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.

http://www.sybase.com/detail?id=1011207

Contents

Context Summary ..................................................................1Usage Scenario ......................................................................3Get Started .............................................................................5

Sybase Unwired Platform Prerequisites .........................5SAP System Prerequisites ..............................................5Importing the Sales Force Automation Sample into

Unwired WorkSpace ...................................................6Opening the Sample Project ...........................................7Connecting to the SAP DataSource ...............................9Connecting to Unwired Server ......................................12Deploying the Sample to Unwired Server .....................13

Try It Out ...............................................................................19Exploring Mobile Business Objects ..............................19

Mobile Business Objects .....................................20Running the Field Sales Agent Application ...................21

Setting Up the Field Sales Agent Application inVisual Studio ...................................................21

Using the Field Sales Agent Functions ................26Running the Sales Manager Application .......................33

Setting Up the Sales Manager Application inVisual Studio ...................................................33

Using the Sales Manager Functions ....................38Learn More ...........................................................................45

Related Reference ........................................................45Sample File Reference ........................................45MBO-to-SAP BAPI/RFC Mapping ........................46

Learn More About Sybase Unwired Platform ...............50Getting Help ..................................................................51

Appendix: Configure Your SAP System ............................53Creating Remote Function Calls ...................................53Configuring Business Objects and Sample Data ..........53

Sample: Sales Force Automation iii

Configuring Data Change Notification ..........................84Index ..................................................................................91

Contents

iv Sybase Unwired Platform

Context Summary

The Sales Force Automation sample contains everything you need to explore Sybase®

Unwired Platform features.

The sample is based on this development environment:

• Sybase Mobile SDK• Sybase Unwired Platform Runtime• Microsoft Visual Studio 2008• Windows Mobile 6 Professional SDK Refresh• ActiveSync 4.5

Use the Sales Force Automation sample to explore the interaction of a native Windows Mobileapplication written in C# and mobile business objects (MBOs) in the Sybase UnwiredWorkSpace and Unwired Server.

Use this sample to gain a comprehensive preview of the benefits Unwired Platform can offerwithout having to program the application yourself.

Learn more about Unwired Platform by creating a Windows Mobile application using thetutorial on the Sybase Product Documentation Web site: http://sybooks.sybase.com/sybooks/sybooks.xhtml, then navigate to the most current version.

Context Summary

Sample: Sales Force Automation 1

http://sybooks.sybase.com/sybooks/sybooks.xhtml


Context Summary

2 Sybase Unwired Platform

Usage Scenario

The Sales Force Automation (SFA) sample contains two smart mobile applications: one forfield sales agents and one for sales managers.

The Sales Force Automation sample:

• Contains the Field Sales Agent application for managing customers and orders, includingsmart material selection for order booking, and performing an online availability check formaterials before confirming orders.

• Contains the Sales Manager application for approving or rejecting blocked orders, andviewing Management Information System (MIS) reports, such as sales reports for the salesareas the managers are responsible for, and outstanding reports for the set of dealersbelonging to those sales areas.

• Leverages business processes configured in SAP® ERP Sales and Distribution (ECC 6.0),and the technical capabilities of Sybase Unwired Platform to mobilize the statedprocesses.

Usage Scenario


Usage Scenario


Get Started

Complete the prerequisites, then follow the tasks in order.

Sybase Unwired Platform PrerequisitesBefore you begin, review and complete these prerequisites for the system where you willinstall or have already installed a Developer Edition of Sybase Unwired Platform.

• Unzip the SUP213_SalesForceAutomation.zip into a temporary directory onthe same system as Unwired WorkSpace. For example, unzip the file to C:\temp.

• Install the Personal Developer Edition or Enterprise Developer Edition of Sybase UnwiredPlatform 2.1.Upgrade to Sybase Unwired Platform 2.1 ESD #3.Be sure you have all the requisite Unwired Platform components installed. For completeinstallation instructions, see the Sybase Unwired Platform documentation at http://sybooks.sybase.com/sybooks/sybooks.xhtml:• Release Bulletin for Sybase Mobile SDK• Installation Guide for Sybase Mobile SDK• Release Bulletin for Runtime• Installation Guide for Runtime

• Install the other development environment components:• Microsoft Visual Studio 2008• Windows Mobile 6 Professional SDK Refresh• ActiveSync 4.5

SAP System PrerequisitesBefore you begin, review and complete these prerequisites for the SAP system you will usewith this sample.

• Create supporting Remote Function Calls (RFCs) in the SAP system by copying the codefrom the corresponding text files in the SFA_FunctionModules folder. See CreatingRemote Function Calls on page 53.

• Configure supporting business objects in the SAP system. See Configuring BusinessObjects and Sample Data on page 53.

• Set up the HTTP connection to allow data change notification (DCN) to send automaticupdates to the Unwired Server. See Configuring Data Change Notification on page 84.

Get Started




Importing the Sales Force Automation Sample into UnwiredWorkSpace

In Unwired WorkSpace, deploy the mobile business objects (MBOs) to Unwired Server.

1. Select Start > Programs > Sybase > Unwired Platform > Start Unwired PlatformServices.

2. Select Start > Programs > Sybase > Unwired Platform > Unwired WorkSpace.

3. If prompted to select a workspace, accept the default path and click OK.

4. If the Welcome page appears, click Start Development to go to the WorkSpace Navigatorand Enterprise Explorer tabs.

5. Select File > Import.

6. In the Import wizard, select General > Existing Projects into Workspace, and clickNext.

7. In the Import Projects page, select Select archive file and Browse to the directory whereyou unzipped SUP213_SalesForceAutomation.zip.

8. Select SalesForceAutomation_MBO.zip, and click Finish.

Get Started


The SalesForceAutomation_MBO directory contains the Sales Force Automationsample mobile application project, including the defined mobile business objects (MBOs).

9. In the Projects area, select the SalesForceAutomation project and click Finish to importit.

The project is imported into Unwired WorkSpace and is now available in WorkSpaceNavigator.

When you import the project, errors are generated, as indicated by the red “x” beside thetop-level SalesForceAutomation project folder. These errors resolve as you set upthe project in the environment.

Opening the Sample ProjectBrowse the contents of the Sales Force Automation project, and open it in the MobileApplication Diagram.

1. In WorkSpace Navigator, expand the Sales Force Automation folder to view the projectartifacts.

Get Started


Ignore the errors in the SalesForceAutomation project folder and theSalesForceAutomation.pkg project file. The errors resolve as you set up theproject.

The Mobile Business Objects folder contains the business objects. The otherfolders contain the project artifacts, including generated code.

2. Right-click the SalesForceAutomation project folder and select Open in DiagramEditor.

The Mobile Application Diagram opens and displays the MBOs, including theiroperations and attributes.

The red error icons indicate that the Sales Force Automation connection profile, whichprovides access to the datasource to which the MBOs are bound, does not yet exist yet.These errors resolve after you create a connection profile.

From the Properties view, you can explore other aspects of MBO definition. You configuremost MBOs in this view.

3. Select the Problems tab and expand Errors.

4. In the Problems tab, under Errors, right-click the first Project SalesForceAutomationitem and select Quick Fix.

Get Started


5. In the Quick Fix dialog, under Select a fix, select Configure build path and clickFinish.

6. In the Edit JAR dialog, browse to the sapjco3.jar file and click Open.

The default installation directory is <UnwiredPlatform_InstallDir>\UnwiredPlatform\sapjco\v3\32bit.

7. In the Properties for SalesForceAutomation dialog, under the Libraries tab, select sup-ds.jar, and click Edit.

8. In the Edit JAR dialog, browse to <UnwiredPlatform_InstallDir>\Unwired_WorkSpace\Eclipse\sybase_workspace\mobile\eclipse\plugins\com.sybase.uep.tooling.api_2.1.3.version.

If you installed in the default location, this is C:\Sybase\UnwiredPlatform\Unwired_WorkSpace\Eclipse\sybase_workspace\mobile\eclipse\plugins\com.sybase.uep.tooling.api_2.1.3.version.

9. In the lib folder, select the sup-ds.jar file and click Open.

10. In the Properties for SalesForceAutomation dialog, click OK.

After a few seconds, the Problems tab shows only warnings. You can expand the Warningsitem to show details:

Connecting to the SAP DataSourceFrom the SAP system administrator, obtain the information necessary to connect to the SAPsystem and create a connection profile in Unwired WorkSpace.

1. In Enterprise Explorer, click the New Connection Profile icon:

2. In the Connection Profile page:

a) Select SAP Server.b) For the name, enter My SAP System.

c) Click Next.

3. In the SAP Connection Properties page, enter information for the SAP system.You see sample connection properties similar to those shown below:

Get Started


4. Click Test Connection.

You should see a Ping succeeded! message.

If you instead see Ping failed!, verify the information you entered with the SAPsystem administrator and correct the connection properties. Try again.

5. Click Finish.The new connection profile appears under the SAP Servers folder.

Get Started


6. In Enterprise Explorer, right-click the My SAP System connection profile and selectConnect.

7. Expand the My SAP System connection profile to show the SAP application componentsthat are now accessible.

Get Started


Connecting to Unwired ServerUse the My Unwired Server connection profile to connect to Unwired Server.

Prerequisites

• Start Unwired Platform Services.• Start Unwired WorkSpace.• Import the Sales Force Automation project.

Task

Unwired WorkSpace includes the My Unwired Server connection profile that provides accessto Unwired Server. Use it to connect to Unwired Server, then deploy the mobile businessobjects (MBOs) in the project to Unwired Server.

1. In Enterprise Explorer, expand the Unwired Servers folder.

2. Right-click My Unwired Server and select Connect.

If the connection fails, make sure all Unwired Server services are started: from Windows,select Start > Programs > Sybase > Unwired Platform > Start Unwired PlatformServices.

3. Expand each element in the tree below My Unwired Server.

Get Started


When you connect to the server, all the elements that you can administer appear.

Deploying the Sample to Unwired ServerDeploy the sample to Unwired Server to make the mobile business object (MBO) logicavailable to the two applications in the sample.

Prerequisites

Connect to Unwired Server.

Task

1. Right-click in the Mobile Application Diagram and select Switch Developer Profile >Advanced.

2. In WorkSpace Navigator, right-click the SalesForceAutomation project and selectDeploy Project.

3. Accept the defaults for deploy mode, target version, and package name, then click Next.

Get Started


4. On the Contents page, select all boxes to deploy all MBOs and click Next.

Get Started


5. On the Package User-defined Classes page, click Add JAR.

6. In the JAR Selection dialog, select filters.jar and click OK.

Get Started


On the Package User-defined Classes page, filters.jar appears in the list of JARs.

7. Click Next.

8. On the Target Server page, select My Unwired Server and click Refresh.

9. Accept the default domain and the admin security configuration, then click Next.

10. On the Server Connection Mapping page, under Connection profile, select My SAPSystem.

11. Under Server connection, click New Server Connection.

12. In the Create New Server Connection dialog, click OK.

After the deployment process completes, a Deployment Status message appears,confirming that the deployment succeeded.

13. In the Deployment Status dialog, click OK.

14. Expand My Unwired Server and its subfolders to view the deployed MBOs.

Get Started


Get Started


Try It Out

Use the sample to view customers, create sales orders, approve blocked sales orders, and viewmanagement reports.

Before you can try the Field Sales Agent application and the Sales Manager application, youmust:

1. Meet the prerequisites and complete the tasks in Get Started on page 5.2. Deploy the sample MBOs to Unwired Server.3. Review the MBO attributes and operations.4. Set up each application in Visual Studio.5. Run each application on a Windows Mobile emulator.

Exploring Mobile Business ObjectsReview the existing attributes and operations for mobile business objects (MBOs), viewrelationships among various MBOs, and explore how MBOs are bound to thePurchaseOrder database as the datasource.

1. In WorkSpace Navigator, expand the Mobile Business Objects folder to view theMBOs created for this sample:

Approval Global

Customer Material

CustomerOutstanding Salesorder

ErrorList SalesReport

ET_CUSTOMER StockCheck

Each MBO has an associated object type. You can open and view these object types in theDiagram Editor:• – server MBOs.• – client MBOs.• – SAP structure.

2. To view the relationships among the MBOs and SAP structures, and gain insight into thebusiness logic supporting them, right-click any MBO or structure and select Open inDiagram Editor.

Try It Out


Mobile Business ObjectsMobile business objects form the business logic for mobile applications and workflows.

A mobile business object (MBO) is derived from a datasource, for example, a database server,Web Service, or SAP® server. MBOs form the business logic for mobile workflows that can bedeployed to an Unwired Server and referenced in mobile devices (clients). MBOs include:

• Implementation details – read-only metadata columns that include information about thedata.

• Abstract details – attributes correspond to class properties on the mobile client, and map tocolumns. Parameters correspond to synchronization parameters on the mobile client andmap to arguments. MBOs can also contain operations, which themselves containparameters and arguments, and can be used to update, create, or delete data.For native applications, a database runs on the mobile device. When users make changes,those changes apply only to their local copy of the data. The changes are sent to the SybaseUnwired Platform server, and changes in the actual enterprise database are sent to themobile device.With Mobile Workflow, even though the user exchanges data with the server, there is noclient-side store that is synchronized with the server's consolidated database.

• Relationships – defined between MBOs, link attributes, and parameters in one MBO, toattributes and parameters in another MBO.

Try It Out


You can define MBOs using either a:

• Top-down approach – design attributes and parameters first, and later bind them to adatasource, or a

• Bottom-up approach – specify a datasource, and automatically generate attributes andparameters from it.

A mobile application includes MBOs, role and server mappings, and other artifacts that aredelivered to the Unwired Server during deployment.

Running the Field Sales Agent ApplicationA field sales agent uses the sample application to enter and submit sales orders for customers.

Setting Up the Field Sales Agent Application in Visual StudioUse Visual Studio to deploy the Sales Force Automation client application for field salesagents to the Windows Mobile emulator.

Prerequisites

• Install Visual Studio 2008 with Windows Mobile 6 SDK on the system where UnwiredWorkSpace is running.

• If you previously set up the Field Sales Agent application or the Sales Manager applicationin Visual Studio, close the emulator without saving the state, and then close Visual Studio.

Task

1. In Windows Explorer, go to the directory where you extracted theSUP213_SalesForceAutomation.zip.

2. Open the SalesForceAutomation folder.

If you extracted the ZIP file to C:\temp, the application files are in C:\temp\SalesForceAutomation.

3. Double-click the SalesForceAutomation.sln file.

The two projects in the solution file appear in the Solution Explorer.

Try It Out


4. In Solution Explorer, expand the src\SalesForceAutomation folder, and locatethe SalesForceAutomationDB.cs file.

Try It Out


5. Open the SalesForceAutomationDB.cs file and search for 2480 (port number forUnwired Server).

6. In the line directly above 2480, select the server name.For example, select KPATILXP.

Try It Out


7. Replace the server name with the host name of the machine where Unwired Server isinstalled.For example, replace KPATILXP with myserver.

8. Save the SalesForceAutomationDB.cs file.

9. From Windows, select Start > Programs > Microsoft ActiveSync.

10. From the ActiveSync menu bar, select File > Connection Settings.

11. In the Connection Settings dialog, use the following settings, then click OK.

12. In Visual Studio, verify Windows Mobile 6 Professional Emulator is selected.

Try It Out


13. In Visual Studio, select Tools > Device Emulator Manager.

14. Right-click Windows Mobile 6 Professional and select Connect.

15. Right-click Windows Mobile 6 Professional again and select Cradle.Wait for ActiveSync to indicate that the emulator is connected.

16. Press F5, or select Debug > Start Debugging.

17. If prompted to select a device, select Windows Mobile 6 Professional Emulator andclick Deploy.

The Login Page for the Sales Force Automation Field Sales Agent application appears inthe emulator.

Try It Out


Using the Field Sales Agent FunctionsA field sales agent can view a list of customers and information for individual customers,create sales orders for customers, and assign and check availability of materials while creatingan order.

PrerequisitesLaunch the application on Windows Mobile 6 Professional Emulator.

Task

1. Log in to the Sales Force Automation application.

Enter the administration credentials you indicated during installation for the supAdminuser.

Try It Out


Source details:• RFC – None• MBO – Global (local MBO)• Technical details –

• LDAP authentication• Local MBO

2. Click Login.

The application home page appears.

Try It Out


Source details:• RFC – None• MBO – Global (local MBO)

3. Click Synchronize to update device data from the SAP server.

4. Click Customer.

The Customers screen appears with summary information for the customers listed.

Try It Out


Source details:• RFC – ZTEST_CUSTOMER_PROFILE• MBO – Customer &ET_Customer• Technical details – Comingled MBO

5. Select CUST1 and click Details.

The Customer Profile screen appears with more detailed information for the selectedcustomer.

Try It Out


Source details:• RFC – ZTEST_CUSTOMER_PROFILE• MBO – Customer &ET_Customer• Technical details – Comingled MBO

6. Create a sales order for the customer:

a) Click the Home icon to return to the application home screen.b) Click Create Sales Order.

7. Enter the information for an item:

a) From the Customer list, select CUST1.b) From the Material, select WIN1-AirConditioner.c) Click Live Stock to retrieve the Available Qty number.d) In the Required Qty box, enter 7.

You added information for one item to the new sales order for CUST1.

Try It Out


Source details:• RFC –

• ZWW_MATERIAL_GETLIST• ZWW_STOCK_CHECK• SalesOrder.CreateFromDat2

• MBO –• Material• StockCheck

• Operation – CreateFromDat2• Technical details

• Complex MBO• Load on Demand Cache policy for Stock Check• Personalization Key• Resultset Checker/Filter

8. Click Add to add the item to the new sales order.

The New Sales Order screen appears with the one item that you ordered.

Try It Out



• ZWW_MATERIAL_GETLIST• ZWW_STOCK_CHECK• SalesOrder.CreateFromDat2

• MBO –• Material• StockCheck

• Operation – CreateFromDat2• Technical details –

• Complex MBO• Load on Demand Cache policy for Stock Check• Personalization Key• Resultset Checker/Filter

9. Add more items to the new sales order:

a) Click Add Item.b) Continue with step 7 on page 30.c) When you finish adding items to the sales order, select Menu > Save and Submit.

Try It Out


10. When finished:

a) Close the emulator without saving the state.b) Close Visual Studio.

These steps leave the environment in a state that is ready for you to set up and use the otherapplication.

Running the Sales Manager ApplicationA sales manager uses the sample application to approve blocked sales orders and view MISreports.

Setting Up the Sales Manager Application in Visual StudioUse Visual Studio to deploy the Sales Force Automation client application for sales managersto the Windows Mobile emulator.

Prerequisites

• Install Visual Studio 2008 with Windows Mobile 6 SDK on the system where UnwiredWorkSpace is running.

• If you previously set up the Field Sales Agent application or the Sales Manager applicationin Visual Studio, close the emulator without saving the state, and then close Visual Studio.

Task

1. In Windows Explorer, go to the directory where you extracted theSUP213_SalesForceAutomation.zip.

2. Open the SFAApproval folder.

If you extracted the ZIP file to C:\temp, the application files are in C:\temp\SFAApproval.

3. Double-click the SFAApproval.sln file.

The two projects in the solution file appear in the Solution Explorer.

Try It Out


4. In Solution Explorer, expand the src\SalesForceAutomation folder, and locatethe SalesForceAutomationDB.cs file.

Try It Out


5. Open the SalesForceAutomationDB.cs file and search for 2480 (port number forUnwired Server).

6. In the line directly above 2480, select the server name.For example, select 10.22.118.105.

Try It Out


7. Replace the server name with the name of the server where Unwired Server is installed.

For example, replace 10.22.118.105 with myserver.

8. Save the SalesForceAutomationDB.cs file.

9. From Windows, select Start > Programs > Microsoft ActiveSync.

10. From the ActiveSync menu bar, select File > Connection Settings.

11. In the Connection Settings dialog, use the following settings, then click OK.

Try It Out


12. In Visual Studio, verify Windows Mobile 6 Professional Emulator is selected.

13. In Visual Studio, choose Tools > Device Emulator Manager.

14. Right-click Windows Mobile 6 Professional and select Connect.

15. Right-click Windows Mobile 6 Professional again and select Cradle.Wait for ActiveSync to indicate that the emulator is connected.

16. Press F5, or select Debug > Start Debugging.

17. If prompted to select a device, select Windows Mobile 6 Professional Emulator andclick Deploy.

The Login Page for the Sales Force Automation sales manager application appears in theemulator.

Try It Out


Using the Sales Manager FunctionsA manager can view a list of blocked orders, information for individual blocked orders, a listof outstanding orders, and information for individual outstanding orders.

PrerequisitesLaunch the application on Windows Mobile 6 Professional Emulator.

Task

1. Log in to the Sales Force Automation application.

Enter the administration credentials you indicated during installation for the supAdminuser.

Try It Out


Source details:• RFC – None• MBO – None• Technical details –

• LDAP authentication• DCN

2. Click Login.

The application home page appears.

Try It Out


Source details:• RFC – None• MBO – Global (local MBO)

3. Click Synchronize to update device data from the SAP server.

4. Click Blocked Orders.

Try It Out



• ZWW_SALES_DOCUMENT_LIST• ZWW_SALES_DOCUMENT_RELEASE

• MBO – Approval• Operation – Approve• Technical details –

• Cache Update Policy for Operation• Push implementation

5. Approve a blocked order:

a) Select a blocked order and click Details.

Try It Out


As a sales manager, you have the authority to approve a blocked order.b) Click Approve.

6. Display the MIS reports screen:

a) Click the Home icon to return to the application home page.b) Click MIS to display the MIS reports screen.c) Scroll down to see the tabs at the bottom of the screen to select a report: Sales Register

or Outstanding.

Try It Out


Source details:• RFC – ZWW_SALES_ORDERS_LIST• MBO – Sales Report• Technical details – Object Query

7. View the sales order register report for a customer:

a) From the Customer list, select a customer.b) Set the number of months to report, and click Go.

The sales order register report appears for the selected customer. If the customer has noopen sales orders, the report is blank.

Source details:• RFC – ZWW_SALES_ORDERS_LIST• MBO – Sales Report• Technical details – Object Query

8. View the outstanding MIS report for all customers:

a) Scroll down to the bottom of the screen.b) Click Outstanding.

Try It Out


9. View the outstanding MIS report for a customer:

a) From the Customer list, select a customer.b) Click Go.

The outstanding MIS report screen appears for the selected customer. If the customer hasno outstanding items, the report is blank.

10. When finished:

a) Close the emulator without saving the state.b) Close Visual Studio.

These steps leave the environment in a state that is ready for you to set up and use the otherapplication.

Try It Out


Learn More

For more information about this sample, or to get additional help on using Unwired Platformin your enterprise environment, review these sections as required by your business needs.

Related ReferenceReview the sample files, project artifacts, and database schemas for the sample.

Sample File ReferenceFamiliarize yourself with files provided for this sample.

You extracted all project files into a local directory from theSUP213_SalesForceAutomation.zip.

Folder ZIP File Contents

[root] README.txt file with instructions for setting up

sample files, and SalesForceAutoma-tionSample.pdf (this document).

SalesForceAutomation The SalesForceAutomation.sln Visu-

al Studio solution file, containing two projects thatmake up the Sales Force Automation application forfield sales agents that you deploy to the WindowsMobile emulator.

SalesForceAutoma-tion_MBO.zip

Contains the SalesForceAutoma-tion_MBO folder, which has the Sales Force Au-

tomation sample mobile application project, includ-ing the defined mobile business objects (MBOs)that you deploy to Unwired Server.

SFA_FunctionModules SAP RFC source files that you copy to the SAPsystem.

SFAApproval The SFAApproval.sln Visual Studio solu-

tion file, containing two projects that make up theSales Force Automation application for sales man-agers that you deploy to the Windows Mobile em-ulator.

Learn More


MBO-to-SAP BAPI/RFC MappingDescribes the SAP attributes that are mapped to mobile business objects (MBOs) for the rolesused in the Sales Force Automation sample.

Field Sales Agent

Table 1. Business Operation Mapping

Business Operation MBO SAP BAPI/RFC

Customer Profile Customer ZTEST_CUSTOMER_PROFILE

Stock Check StockCheck ZWW_STOCK_CHECK

Material Master Material ZWW_MATERIAL_GETLIST

Table 2. Function Module: ZTEST_CUSTOMER_PROFILE

SL No. Input Field Name Output Field Name

1 VKORG Sales Organization KUNNR Customer Number 1

VTWEG Distribution Channel NAME1 Name1

SPART Division NAME2 Name2

ORT01 City

STRAS House number and street

LAND1 Country Key

TELF1 First telephone number

TELFX Fax Number

KLIMK Customer's credit limit

SKFOR Total receivables (for creditlimit check)

Table 3. Function Module: ZWW_STOCK_CHECK


2 MATNR Material Number MATNR Material Number

MAKTX Material Description (ShortText)

Learn More



MTART Material Type

WERKS Plant

LGORT Storage Location

LABST Valuated Unrestricted-UseStock

MEINS Base Unit of Measure

Table 4. Function Module: ZWW_MATERIAL_GETLIST


3 WERKS Plant MATNR Material Number

WERKS Plant

MAKTX Material Description (ShortText)

Sales Manager

Table 5. Business Operation Mapping

Business Operation MBO SAP BAPI/RFC

Blocked Order List Approve ZWW_SALES_DOCUMENT_LIST

Released Blocked Order Approval (Operation) ZWW_SALES_DOCUMENT_RE-LEASE

Sales Report SalesReport ZWW_SALES_ORDERS_LIST

Customer OutstandingReport

CustomerOutstanding ZWW_CUSTOMER_OUTSTAND-ING1

Table 6. Function Module: ZWW_SALES_DOCUMENT_LIST

SLNo.

Input Field Name Output Field Name

1 KKBER Credit Control Area VBELN Sales Document

KNKLI Customer's account numberwith credit limit reference

ERDAT Date on Which Record WasCreated

Learn More


SLNo.

Input Field Name Output Field Name

VBELN Sales and Distribution Docu-ment Number

NETWR Net Value in Document Cur-rency

I_SALES-DOC

Sales Order VKORG Sales Organization

I_DELIV-ERIES

Deliveries VTWEG Distribution Channel

SPART Division

VKGRP Sales Group

VKBUR Sales Office

KKBER Credit Control Area




NAME1 Name 1

KWKKC Credit value

KLPRZ Credit limit used in %

Table 7. Function Module: ZWW_SALES_DOCUMENT_RELEASE


2 VBELN Sales Document

Table 8. Function Module: ZWW_SALES_ORDERS_LIST


3 KUNNR Customer Number 1 NAME1 Name 1

F_ERDAT Date on which the RecordWas Created

VKORG Sales Organization

T_ERDAT Date on Which Record WasCreated

VTWEG Distribution Channel

Learn More



SPART Division

VBELN Sales Document

ERNAM Name of Person who Createdthe Object

ERDAT Date on Which Record WasCreated

Table 9. Function Module: ZWW_CUSTOMER_OUTSTANDING1


4 KUNNR Customer Number 1 KUNNR Customer Number 1

BUKRS Company Code BUKRS Company Code

KKBER Credit Control Area KKBER Credit Control Area

GJAHR Fiscal Year GJAHR Fiscal Year

NAME1 Name 1

ORT01 City


VKORG Sales Organization

VKBUR Sales Office

VKGRP Sales Group

VTWEG Distribution Channel

SPART Division



Learn More


Learn More About Sybase Unwired PlatformOnce you have finished, try some of the other samples or tutorials, or refer to otherdevelopment documents in the Sybase Unwired Platform documentation set.

Check the Sybase Product Documentation Web site regularly for updates: http://sybooks.sybase.com/sybooks/sybooks.xhtml, then navigate to the most current version.

TutorialsTry out some of the other getting started tutorials available on the Product DocumentationWeb site to get a broad view of the development tools available to you.

Example ProjectsAn example project is the end results of a finished tutorial without going through the steps.Download example projects from the SAP® Community Network (SCN) at http://scn.sap.com/docs/DOC-8803.

SamplesSample applications are fully developed, working applications that demonstrate the featuresand capabilities of Sybase Unwired Platform.

Check the SAP® Development Network (SDN) Web site regularly for new and updatedsamples: https://cw.sdn.sap.com/cw/groups/sup-apps.

Online HelpSee the online help that is installed with the product, or available from the ProductDocumentation Web site.

Developer GuidesLearn best practices for architecting and building device applications:

• Mobile Data Models: Using Data Orchestration Engine – provides information aboutusing Sybase Unwired Platform features to create DOE-based applications.

• Mobile Data Models: Using Mobile Business Objects – provides information aboutdeveloping mobile business objects (MBOs) to fully maximize their potential.

Use the appropriate API to create device applications:

• Developer Guide: Android Object API Applications• Developer Guide: BlackBerry Object API Applications• Developer Guide: iOS Object API Applications• Developer Guide: Windows and Windows Mobile Object API Applications• Developer Guide: Mobile Workflow Packages

Customize and automate:

Learn More




http://scn.sap.com/docs/DOC-8803

http://scn.sap.com/docs/DOC-8803

https://cw.sdn.sap.com/cw/groups/sup-apps

• Developer Guide: Unwired Server Management API – customize and automate systemadministration features.

Javadoc and HeaderDoc are also available in the installation directory.

Getting HelpEach Sybase installation that has purchased a support contract has one or more designatedpeople who are authorized to contact Sybase Technical Support.

If you cannot resolve a problem using the online help or other technical documents, have thedesignated person contact Sybase Technical Support or the Sybase subsidiary in your area.

Learn More


Learn More


Appendix: Configure Your SAP System

Before you run the sample application, you must set up several Remote Function Calls (RFCs)and configure several business objects on the SAP system that the sample will use.

Creating Remote Function CallsCopy the source code for 10 RFCs into the SAP system for use with the Sales ForceAutomation sample application.

The RFC source files are in the SUP213_SalesForceAutomation.zip. The sourcefor each RFC is in a separate text file. Each text file has the name of the RFC with a .txtextension.

1. Go to the directory where you extracted theSUP213_SalesForceAutomation.zip.

2. Open the SFA_FunctionModules folder to find the RFC source files.If you extracted the ZIP file to C:\temp, the RFC source files are in C:\temp\SFA_FunctionModules.

3. Copy the source code for each RFC into the SAP system.

Configuring Business Objects and Sample DataIn the SAP system that supports the sample application, configure business objects and addsome sample data.

1. Create a Company Code.

Company Code is an organizational unit that accounting uses to structure the businessorganization from a financial accounting perspective.

Path: Enterprise Structure > Definition > Financial Accounting > Edit, Copy, Delete,Check Company Code

T-Code: OX02 [2010 - WinfoWare technologies]



2. Create a Controlling Area.

Controlling Area is an organizational unit that accounting uses to subdivide the businessorganization from a cost accounting standpoint.

Path: Enterprise Structure > Definition > Controlling > Maintain Controlling Area

T-Code: OX06 [2010 – Controlling Area]



3. Create a Credit Control Area.

Credit Control Area is an organizational unit that specifies and checks the credit limit forcustomers.

Path: Enterprise Structure > Definition > Financial Accounting > Define CreditControl Area

T-Code: OB45 [2010 – WT Credit Control Area]



4. Create global parameters for the Company Code.

Chart of Accounts – CAIN, Fiscal Year Variant – K4, Credit Control Area – 2010.

Path: Financial Accounting > Financial Accounting Global Settings > CompanyCode > Enter Global Parameters

T-Code: [OBY6]



5. Assign the Company Code to the Controlling Area.

Path: Enterprise Structure > Assignment > Controlling > Assign Company Code toControlling Area

T-Code: [OX19]



6. Create Plants.

Path: Enterprise Structure > Definition > Logistics-General > Define, Copy, Delete,Check Plant

T-Code: [OX10 – 2010 (Plant 1), 2011 (Plant 2), DE01 (Depot 1), DE02 (Depot 2)]



7. Create Storage locations.

Path: Enterprise Structure > Definition > Materials Management > Maintain StorageLocation

T-Code: [OX09 – 2010 (2010), 2011 (2011), 2012 (DE01), 2013 (DE02)]



8. Assign Plants to Company Code.

Path: Enterprise Structure > Assignment > Logistics-General > Assign Plant toCompany Code

T-Code: [OX18] [2010, 2011, DE01, DE02 – (2010)]



9. Create Purchasing Organizations.

Purchasing Organizations negotiate the conditions of purchase with vendors for one ormore Plants.

Path: Enterprise Structure > Definition > Materials Management > MaintainPurchasing Organization

T-Code: [OX08 – P100, P200]



10. Assign Purchasing Organizations to Company Code.

Path: Enterprise Structure > Assignment > Materials Management > AssignPurchasing Organization to Company Code

T-Code: [OX01] [P100, P200 - 2010]



11. Create Personnel Areas.

Path: Enterprise Structure > Definition > Human Resource Management > PersonnelAreas

T-Code: [SPRO]



12. Assign Personnel Areas to Company Code.

Path: Enterprise Structure > Assignment > Human Resource Management >Assignment of Personnel Areas to Company Code

T-Code: [SPRO]



13. Create Sales Organizations.

Path: Enterprise Structure > Definition > Sales & Distribution > Delete, Copy, CheckSales Organization

T-Code: [OVX5] [2010, 2011]

14. Assign Sales Organization to Company Code.

Path: Enterprise Structure > Assignment > Sales & Distribution > Assign SalesOrganization to Company Code



T-Code: [OVX3] [2010, 2011 - 2010]

15. Create Distribution Channels.

Path: Enterprise Structure > Definition > Sales & Distribution > Define, Copy, CheckDistribution Channel

T-Code: [OVXI] [01, 02]

16. Assign Distribution Channels to Sales Organizations.

Path: Enterprise Structure > Assignment > Sales & Distribution > AssignDistribution Channel to Sales Organization



T-Code: [01, 02 – 2010, 2011]

17. Assign Divisions to Sales Organizations.

Path: Enterprise Structure > Assignment > Sales & Distribution > Assign Division toSales Organization

T-Code:[OVXA] [01 – 2010, 2011]

18. Set up Sales Areas.

Path: Enterprise Structure > Assignment > Sales & Distribution > Set up Sales Area



T-Code: [OVXG] [Sales Organization > Distribution Channel > Division]

19. Create Sales Offices.

Path: Enterprise Structure > Definition > Sales & Distribution > Maintain SalesOffice

T-Code: [OVX1] [2010, 2011]

20. Create Sales Groups.

Path: Enterprise Structure > Definition > Sales & Distribution > Maintain SalesGroup



T-Code: [OVX4] [001, 002, 003, 004]

21. Assign Sales Areas to Sales Offices.

Path: Enterprise Structure > Assignment > Sales & Distribution > Assign Sales Areato Sales Office

T-Code: [SPRO] [Sales Organization > Distribution Channel > Division > Sales Office]

22. Assign Sales Groups to Sales Offices.

Path: Enterprise Structure > Assignment > Sales & Distribution > Assign SalesGroup to Sales Office

T-Code: [OVXJ] [001, 002, 003, 004 – 2010, 2011]



23. Assign Sales Organizations and Distribution Channels to Plants.

Path: Enterprise Structure > Assignment > Sales & Distribution > Assign SalesOrganization, Distribution Channel, Plant Combination

T-Code: [OVX6] [Sales Organization > Distribution Channel > Plant]

24. Define Shipping Points.



Path: Enterprise Structure > Definition > Logistics Execution > Define, Copy, Delete,Check Shipping Point

T-Code: [OVXD] [2010, 2011, 2012, 2013]

25. Assign Shipping Points to Plants.

Path: Enterprise Structure > Assignment > Logistics Execution > Assign ShippingPoint to Plant

T-Code: [OVXC] [2010 – 2010, 2011 – 2011, 2012 – DE01, 2013 – DE02]



26. Create a Loading Point.

Path: Enterprise Structure > Definition > Logistics Execution > Maintain LoadingPoint

T-Code: [SPRO] [Loading Point > Shipping Point] [01 (2010), 02 (2011), 03 (2012), 04(2013)]



27. Create a Transportation Planning Point.

Path: Enterprise Structure > Definition > Logistics Execution > MaintainTransportation Planning Point

T-Code: [OVXT]

28. Define Loading Groups.

Path: Enterprise Structure > Shipping > Basic Shipping Functions > Shipping Point& Goods Receiving Point Determination > Define Loading Groups

T-Code: [SPRO] [0001, 0002]



29. Define Shipping Conditions.

Path: Logistics Execution > Shipping > Basic Shipping Functions > Shipping Point &Goods Receiving Point Determination > Define Shipping Conditions

T-Code: [01 (Standard), 02 (Pick-Up), 03 (Immediately), 04 (Transport Service), RE(Returns)]

30. Assign Shipping Points.



Path: Logistics Execution > Shipping > Basic Shipping Functions > Shipping Point &Goods Receiving Point Determination > Assign Shipping Points

T-Code: [SPRO] [Shipping Conditions > Loading group > Plant > Shipping Point]

31. Define Transportation Zones.

Path: Sales & Distribution > Basic Functions > Routes > Route Determination >Define Transportation Zone

T-Code: [OVR1] [0000000001 (Region South)]



32. Determine Routes.

Path: Logistics Execution > Shipping > Routes > Route Determination

T-Code: [SPRO] [000021 (South-North Route)]

33. Set up Partner Determination for Customer Master.

Path: Sales & Distribution > Basic Functions > Partner Determination > Set upPartner Determination > Set up Partner Determination for Customer Master



T-Code: [SPRO]

34. Set up Partner Determination: Account Groups – Function Assignment.

Path: Sales & Distribution > Basic Functions > Partner Determination > Set upPartner Determination

T-Code: T-Code: [SPRO]

General Data:• Name: Hindustan Lever• Street/House Number: Central Street, Kumara Park West/44• Postal Code: 560020• City: Bangalore• Country: IN (INDIA)• Region: 10 (Karnataka)• Transportation Zone: 0000000001 (Region South)• Telephone: 080-20109777• Fax: 080-20109777• E-mail Id: [email protected]



Company Code Data:• Reconciliation Account: 40001000• Terms of Payment: 0001



Sales Area Data:• Sales District: CENTRE• Customer Group: 01• Currency: INR• Price group: 01 (Bulk Buyer)• Customer Price Group: 1 (Standard)• Delivery Priority: 2 (Normal Item)• Shipping Conditions: 01 (Standard)• Incoterms: CIF (Costs, Insurance & Freight)• Account Assignment group: 01 (Domestic Revenues)



Basic Data 1:• Material Name: Win1 (Air conditioner)• Base Unit of Measure: EA (Each)• Material Group: 01



Sales, General/Plant:• Transportation Group: 0001 (On Pallets)• Loading Group: 0001 (Crane)



Accounting 1:• Currency: INR• Valuation Class: 7900• Price Control: S (Standard Price)



35. Set up Credit Check for Item Category.

Path: Sales & Distribution > Basic Functions > Credit Management / RiskManagement > Credit Management/Risk Management Settings > Determine ActiveReceivables per Item Category

T-Code: [SPRO]



Configuring Data Change NotificationIn the SAP system that supports the Sales Force Automation sample application, set up theHTTP connection to allow data change notification (DCN) to send automatic updates to theUnwired Server.

1. On the SAP system, start the SAPGUI client.

2. In the Systems tab, select winfoware, and click Log on.



3. Enter the user, password, and language. Click the Enter icon:



4. In the Command field, enter: SM59. Press Enter.

SM59 is the transaction code to display and maintain RFC Destinations.

5. In the RFC Connections column, expand HTTP Connections to External Server.



6. To set up an RFC Connection for the first time, use this step. If you already set one up andneed to change the Unwired Server, go to step 7.

a) Double-click ZWW_SALES_DOCUMENT_RELEASE.b) Enter these values:

• RFC Destination – ZWW_SALES_DOCUMENT_RELEASE

• Connection Type – G

• Description 1 – To Connect to URL

c) In the Technical Settings tab, enter the Target Host for the Unwired Server, Service No,and Path Prefix.



d) In the Logon & Security tab, select these values:

• Logon Procedure – No Logon

• SSL – Inactive

• SSL Client Certificate – DFAULT SSL Client (Standard)

• PW Status – is initial

e) In the Special Options tab, select these values and click the Save button:

• Timeout – ICM Default Timeout• HTTP Version – HTTP 1.1



At the bottom of the screen, a message appears:Destination ZWW_SALES_DOCUMENT_RELEASE saved.

.

7. If you already set up an RFC Connection and need to change the Unwired Server:

a) Double-click ZWW_SALES_DOCUMENT_RELEASE.b) In the RFC Destination Page, to change a connection setting, click the Pencil icon:

c) In the Technical Settings tab, enter the Target Host for the Unwired Server.

d) Click the Save button:

At the bottom of the screen, a message appears: DestinationZWW_SALES_DOCUMENT_RELEASE saved.

8. Click Connection Test.

One of the following messages appears:

The messages indicate that the Unwired Server is accessible from the SAP system and theDCN setup is correct.



IndexA

ActiveSync 1configuring to work with emulator 21, 33requirements for sample 5

applicationfield sales agent functions 26sales manager functions 38

B

build path, configuring 7business objects

configure on SAP system 53creating 5

business requirements 3

C

connection profilecreating 9My SAP System 9

context summary 1

D

data change notification 84DCN

See data change notificationdevelopment environment 1

E

errors, resolving 7

F

Field Sales Agent application 3, 26run with emulator 21viewing in emulator 21

H

help, getting 51

HTTP connectionconfiguring 5creating 84

M

MBOs 19mapped to RFCs 46overview 20

Microsoft Visual Studio 2008 1, 5Mobile Application Diagram 7mobile business objects

deploying 6deploying to Unwired Server 13object types 19view diagrams 19

See also MBOsMy Unwired Server connection profile 12

P

prerequisitesSAP 5Sybase Unwired Platform 5

projectsimporting into Unwired WorkSpace 6sample file reference 45

R

referenceMBO-to-SAP BAPI/RFC mapping 46sample files 45

Remote Function Callsconfigure on SAP system 53creating 5creating in SAP system 53

requirements, business 3RFCs

mapped to MBOs 46See also Remote Function Calls

Index


SSales Force Automation

development environment 1Field Sales Agent application 3project 6project contents 7run with emulator 21, 33Sales Manager application 3ZIP file 53

Sales Manager application 3, 38run with emulator 33viewing in emulator 33

sampleconfiguration errors 7importing files into Unwired WorkSpace 6opening in Unwired WorkSpace 7prerequisites 19setting up in Unwired WorkSpace 6starting 5

sample applicationoverview 1uses 3

sample filesextracting from ZIP file 5reference 45

samples 45downloading 50

SAPbusiness objects and sample data 53connecting to SAP DataSource 9data change notification 84system requirements 5

SAP systemconfigure business objects 53configure RFCs 53

SFA_FunctionModules 53SUP

See Sybase Unwired PlatformSUP213_SalesForceAutomation.zip 5Sybase Unwired Platform

documentation resources 50

getting help 51requirements for sample 5Technical Support, contacting 51tutorials 1

system requirementsSAP 5Sybase Unwired Platform 5

T

tutorials 45downloading 50

U

Unwired PlatformSee Sybase Unwired Platform

Unwired Serverconnecting 12deploying MBOs 13SAP connection 84starting 5, 12

Unwired WorkSpaceimporting project file 6starting 5

usage scenario 3

V

Visual Studioimporting solution file 21, 33setting up application 21, 33

W

Windows Mobile 6 Professional Emulator 26Windows Mobile 6 Professional SDK Refresh 1

requirements for sample 5Windows Mobile emulator 21, 33

Index


Sup Sample Sales Force Automation

Documents

Transcript of Sup Sample Sales Force Automation