Tutorial: Developing an Order Application for
Handhelds
In this tutorial, you develop a single-screen application that shows a list of orders and provides the option of filtering them. The tutorial assumes that the corresponding data model has already been created on the Data Orchestration Engine (DOE) and therefore concentrates on client-side development only. All required steps are shown and discussed in detail.
The developed application will look like this on a desktop installation of the Mobile Client for Handhelds:
Task
This tutorial introduces you step-by-step to the tasks involved in creating an application for mobile handheld devices.
Using an Order Taker project as an example, this tutorial walks you through the development steps from creating the required development components to running the application.
Objectives
The purpose of this tutorial is to provide you with a quick and easy introduction to the development paradigm and the tools required to develop a Mobile Application for Handhelds.
The following features of the mobile capabilities in SAPNetWeaver Development Studio are used:
· Service Explorer
Mobile Service Components, data objects, services, queries, and custom operations
● Handhelds UI Explorer
Web Dynpro (WD) application wizard, WD template for component controller, view layout and context, context mapping, data binding, action button, and application deployment
The tutorial aims to introduce you to the tasks you will need to create your own Mobile Applications for Handhelds. Specifically, it will show you how to:
● Create Mobile Service Components, Mobile UI Components, and Mobile Applications
● Import data objects from the Data Orchestration Engine (DOE)
● Define queries and custom operations
● Model UI views, create contexts, and handle actions
● Build, deploy, and run the created Mobile Application
Prerequisites
Knowledge
You should be familiar with the concepts of:
· Java
· Eclipse
· NetWeaver
· Web Dynpro
Installations
1. Install the mobile plug ins for SAPNetWeaver Developer Studio on the development workstation.
More
information:
Installing Mobile
Plug-Ins in the IDE
2. Configure the SAP NetWeaver Developer Studio to connect to the DOE.
More information: Configuring the Development Workstation
For this tutorial, you also require a NetWeaver Application Server (AS) with the following system details:
Parameter |
Value |
System ID |
MBF |
Client number |
100 |
Host |
uscimbf.wdf.sap.corp |
Port |
50 |
Data Model
You also need a data model on Data Orchestration Engine (DOE). The tutorial assumes that the following data object is available on the DOE:
You can easily create such a data object for yourself.
More information: help.sap.com → SAP NetWeaver 7.1 → SAP NetWeaver Mobile Library → Developer’s Guide → Developing Mobile Applications → Defining Data Objects and Distribution for Mobile Applications.
For this tutorial, you only need to create a single data object node and generate it. Only if you wanted to synchronize data with the backend, would you also need a back-end adapter and BAPI wrappers.
Object Type |
Object ID |
Software Component Version |
ORDER_TAKER |
Data Object |
ORDER |
Data Object header node |
ORDERHEADER |
The header node contains the following fields:
Attribute Name |
Attribute Description |
Type |
Length |
ORDERID |
Order ID |
CHAR |
8 |
CUSTID |
Customer ID |
CHAR |
4 |
LONGTEXT |
Order description |
CHAR |
32 |
SERVICEUNIT |
Service Unit, which will process the order |
CHAR |
32 |
CREATED_ON |
Date, on which the order was created |
DATS |
8 |
CREATED_AT |
Time on which the order was created |
TIMS |
- |
Basic Procedure
Using the New Project wizard in the Mobile Applications for Handhelds perspective of the SAP NetWeaver Development Studio, you start the new Order Taker project. Then you carry out the basic steps to create and define the three types of development components required for a viable application in the Composite Development Scenario:
● Mobile Service Component
...
To provide the required business logic to the UI, you first create a Mobile Service Component, into which you import data object metadata from the Data Orchestration Engine (DOE). Now you can create a query for reading orders from the database.
...
· Mobile UI Component
To provide a user interface (UI) for your Mobile Application, you create a UI component, a Web Dynpro (WD) application, and WD component, apply a template to the component controller, and then layout the required views.
...
· Mobile Application
For subsequent testing and rollout, you compose the Mobile Service Component and the Mobile UI Component into a Mobile Application. You define the component dependencies, set the startup application, and then continue to build, deploy, and run the application on the Mobile Client for Handhelds.