Defining the Data Model and Business Logic 

Use

After starting a new project by creating a Mobile Service Component, the usual workflow in the Composite Development Scenario is to continue by defining the data model and business logic. You will use this logic later as the basis of your Mobile UI Component, when you model the user interface.

Prerequisites

You have started a new project by creating a development component (DC), in this tutorial the order_sv Mobile Service Component.

More information: Starting a New Project

Procedure

1. Create the Client Data Objects

The client data object will be defined by importing the ORDER data object from the Data Orchestration Engine (DOE) and selecting all node attributes (this is the default).

More information: Creating Client Data Objects

2. Define a Query

This query will be fired when an Order long text is entered as search string on the UI. This string will be compared with LIKE operator to the long text of orders available on the device.

More information: Defining a Query

3. Define a Custom Operation (Optional)

The custom operation generates dummy data and persists it in the database. This is required for meaningful searches in case the data model on the server-side has no back-end adapter, BAPI wrapper, or backend data. Then no data can be synchronized with the mobile device.

More information: Defining a Custom Operation

4. Build the Mobile Service Component

After completing the steps above:

       1.      In the Service Explorer, select your Mobile Service Component order_sv.

       2.      Open the context menu (by right-clicking) and choose Build.

Result

You have created a Mobile Service Component by creating client data objects, defining a query for your order application, and defining a custom operation. Now you can use this data for your Mobile UI Component.