mobile offline application development.pdf

7/28/2019 Mobile offline application development.pdf

1/32

Mobile offline application development: a complete guide using Mobile Infrastructure tools

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2007 SAP AG 1

Mobile offline application development: a complete guideusing Mobile Infrastructure tools

Appl ies to:

SAP NetWeaver Mobile Infrastructure (MI).

Summary

This article is mainly for the newbies in MI which provides with step by step development procedure for mobileapplications from the backend/middleware using Mobile Infrastructure.(Up to generation of MeRep XML).

Here a simple mobile application has been developed and explained with coding.

This article provides link to other published article, which explains step by step procedure to develop mobileapplication using MeRep XML with NWDS.

Thus this article can be taken as a guide to develop applications in MI.

Author(s): Karthick Lakkaraju

Company: Cognizant Technology Solutions

Created on: 3 J une 2007

Author Bio

Karthick Lakkaraju is presently working for Cognizant. For the past 1.6 years he has been workinfor SAP-NetWeaver MI. He has developed a few applications in Smart sync and presented in TecEd 2006. He is one of the top contributors in the area of NetWeaver Mobile (Forums).

Expertise: MI Backend/Middleware development, ABAP, Mobile infrastructure development tools.


2/32



2007 SAP AG 2

Table of Contents

Introduction:..................................................................................................................................... 3BAPI Wrappers and its types:...................................................................................................... 3How to develop BAPI Wrappers: ................................................................................................. 4GETLIST BAPIWRAPPER SAMPLE CODING:......................................................................... 12GETDETAIL BAPIWRAPPER SAMPLE CODING: ...................................................................13CREATE BAPIWRAPPER SAMPLE CODING:.........................................................................13MODIFY BAPIWRAPPER SAMPLE CODING:..........................................................................15DELETE BAPIWRAPPER SAMPLE CODING:..........................................................................17SYNCBO DESIGN: .................................................................................................................... 18CREATION OF MCD: ................................................................................................................25Download of MeRep XML: ......................................................................................................... 27Furthur development with MeRep XML using NWDS:.............................................................. 29

Related Content:............................................................................................................................ 30Disclaimer and Liability Notice....................................................................................................... 31


3/32



2007 SAP AG 3

Introduction:

SAP Netweaver MI (Mobile Infrastructure) is a technology platform for offline access to SAP systems or otherERP systems via portable devices like PDA or Laptop.

Here step by step development process for mobile applications from backend/middleware is clearly explained.

A sample application with one syncbo has been developed here.

How to develop BAPI wrappers.(In Backend).

How to develop BAPI wrappers.(In Backend)(For single syncbo).

How to design Syncbos (Mapping, Generating, replicating the syncbo) (In Middleware).

Creating MCD for the syncbo.(In Middleware).

Generating MeRep XML.(In Middleware).

Link provided to article on how to proceed with generated MeRep XML and further develop theapplication.

BAPI Wrappers and its types:

BAPI Wrappers are normal function modules which are RFC enabled , wrapped and follow certain rules to complya standard interface.

All the business logic of the application resides inside the BAPI Wrappers (coding)

There are 5 BAPI wrappers:

GETLIST : Returns a list of business object header data based on the selection criteria specified in the Importparameters.

GETDETAIL: Returns one header data as Export parameter out of the header data list based on the object key(s)specified in the Import parameters. It also returns one or more list of item entries associated with the header data.

CREATE: Creates a single business object, and returns object key(s)

MODIFY: Modifies the business object header and also its item data.

DELETE: Deletes the specified business object (including the items).

All the wrappers are not mandatory, only Getlist and Getdetail are mandatory.

Generated code make assumptions about the interface of the BAPI wrappers, so it needs to follow certain rules:

RFC enabled.

Parameter named RETURN of type BAPIRET2 structure, needs to be defined as Export or Tableparameters.

Parameters can only refer to a structure or field of a structure.

No changing parameters.

No Exceptions.

Consistency between all the 5 Bapi Wrappers must be kept, while defining Export, Import, Tableparameters.

All BAPIs must be stored in the same Function Group.


4/32



2007 SAP AG 4

How to develop BAPI Wrappers:

BAPI Wrapper Wizard ensures that all the assumptions are met.

Before creating BAPI Wrappers, backend tables have to be created.

EXAMPLE:

Z1CUSTOMER (Header table)

Z1CUSTOMERADD (Item table 1)

Z1EMAIL (Item table 2)

These item tables are related to the header table with foreign key relationship.

Logon to the backend system and Go To transaction MEREP_SBUILDERGOTO-->BAPI Wrapper Wizard


5/32



2007 SAP AG 5

Press Continue to proceed further.


6/32



2007 SAP AG 6

Fill the names of the BAP I Wrappers (only which are required).

Here sample application will be developed including the code.

Press Continue


7/32



2007 SAP AG 7

Here Z1CUSTOMER is the header table which is existing in the backend.

Press Continue.


8/32



2007 SAP AG 8

These are the fileds of the header table with the header key field checked.

Press continue.


9/32



2007 SAP AG 9

Add the entries and provide with the item tables (child tables of header table) with SID:010,020,030 etc.


10/32



2007 SAP AG 10

Either Export or Table parameters should be checked.

This will ensure that parameter RETURN of type BAPIRET2 will be filled in Export or Table parameters.

Press continue.


11/32



2007 SAP AG 11

Here Function Group name should be provided where all the BAPIs are stored in this function group.

Here Function group will be automatically generated.

Press Continue and then press complete in the next screen.

Save the functiongroup.

Now all the 5 BAPIWRAPPERS are generated and activated.

Goto se37 and provide the name of the bapiwrappers which were created using BAPI Wrapper Wizard.


12/32



2007 SAP AG 12

GETLIST BAPIWRAPPER SAMPLE CODING:


13/32



2007 SAP AG 13

GETDETAIL BAPIWRAPPER SAMPLE CODING:

CREATE BAPIWRAPPER SAMPLE CODING:FUNCTION ZSAMPLE_CREATE.*"--------------------------------------------------------------------*"*"Global Interface:*" IMPORTING*" VALUE(I_TOP) TYPE Z1CUSTOMER*" EXPORTING*" VALUE(E_ZCUSTOMERID) TYPE Z1CUSTOMER-ZCUSTOMERID

*" TABLES*" T_010 STRUCTURE Z1CUSTOMERADD*" T_020 STRUCTURE Z1EMAIL*" RETURN STRUCTURE BAPIRET2*"--------------------------------------------------------------------

DATA: z11customerid LIKE z1customer-zcustomerid.TABLES : z1customer.

DATA: z11addressid LIKE z1customeradd-zaddressid.TABLES : z1customeradd.


14/32



2007 SAP AG 14

DATA: z11sequencenumber LIKE z1email-zsequencenumber..TABLES : z1email.

DATA: lds_return LIKE bapireturn1.DATA: gdf_message_dummy TYPE string.

SELECT MAX( zcustomerid ) FROM z1customer INTO z11customerid.

z11customerid = z11customerid + 1.i_top-zcustomerid = z11customerid.INSERT z1customer FROM i_top.

DATA: zcustomerid LIKE z1customer-zcustomerid,wa_i_t_010 LIKE LINE OF t_010,wa_i_t_020 LIKE LINE OF t_020.

zcustomerid = z11customerid.e_zcustomerid = zcustomerid.

LOOP AT t_010 INTO wa_i_t_010.wa_i_t_010-zcustomerid = zcustomerid.SELECT MAX( zaddressid ) FROM z1customeradd INTO z11addressid.z11addressid = z11addressid + 1.

wa_i_t_010-zaddressid = z11addressid.INSERT z1customeradd FROM wa_i_t_010.ENDLOOP.

LOOP AT t_020 INTO wa_i_t_020.

wa_i_t_020-zcustomerid = zcustomerid.SELECT MAX( zsequencenumber ) FROM z1email INTO z11sequencenumber.

z11sequencenumber = z11sequencenumber + 1.wa_i_t_020-zsequencenumber = z11sequencenumber.INSERT z1email FROM wa_i_t_020.

ENDLOOP.

ENDFUNCTION.


15/32



2007 SAP AG 15

MODIFY BAPIWRAPPER SAMPLE CODING:

FUNCTION zsample_modify.*"--------------------------------------------------------------------*"*"Global Interface:

*" IMPORTING*" VALUE(I_TOP) TYPE Z1CUSTOMER*" TABLES*" T_010 STRUCTURE Z1CUSTOMERADD*" T_020 STRUCTURE Z1EMAIL*" RETURN STRUCTURE BAPIRET2*"--------------------------------------------------------------------

DATA: it_z1customer TYPE TABLE OF z1customer,wa_it_z1customer LIKE LINE OF it_z1customer.

DATA: lds_return LIKE bapireturn1,gdf_message_dummy TYPE string .

SELECT * FROM z1customer INTO CORRESPONDING FIELDS OF TABLE it_z1customer WHEREzcustomerid = i_top-zcustomerid.

LOOP AT it_z1customer INTO wa_it_z1customer.ENDLOOP.

IF sy-subrc = 0.DELETE z1customer FROM wa_it_z1customer.

ENDIF.

INSERT z1customer FROM i_top.

DATA: zcustomerid LIKE z1customer-zcustomerid,wa_i_t_010 LIKE LINE OF t_010,wa_i_t_020 LIKE LINE OF t_020.

DATA: wa2_t_010 TYPE z1customeradd,dt_zaddressid TYPE z1customeradd-zaddressid.

DATA: it3_t_010 TYPE TABLE OF z1customeradd,wa3_t_010 TYPE z1customeradd.

zcustomerid = i_top-zcustomerid.

SELECT * FROM z1customeradd INTO TABLE it3_t_010 WHERE zcustomerid =

i_top-zcustomerid.

LOOP AT t_010 INTO wa3_t_010.

DELETE it3_t_010 WHERE zaddressid =wa3_t_010-zaddressid AND zcustomerid = wa3_t_010-zcustomerid.

ENDLOOP.

DELETE z1customeradd FROM TABLE it3_t_010.


16/32



2007 SAP AG 16

LOOP AT t_010 INTO wa2_t_010.IF wa2_t_010-zaddressid = '00000000'.SELECT MAX( zaddressid ) FROM z1customeradd INTO dt_zaddressid.dt_zaddressid = dt_zaddressid + 1.wa2_t_010-zaddressid = dt_zaddressid.wa2_t_010-zcustomerid = i_top-zcustomerid.

ENDIF.MODIFY z1customeradd FROM wa2_t_010.

ENDLOOP.

DATA: wa2_t_020 TYPE z1email,dt_zsequencenumber TYPE z1email-zsequencenumber.

DATA: it3_t_020 TYPE TABLE OF z1email,wa3_t_020 TYPE z1email.

SELECT * FROM z1email INTO TABLE it3_t_020 WHERE zcustomerid =i_top-zcustomerid.


DELETE it3_t_020 WHERE zsequencenumber =wa3_t_020-zsequencenumber AND zcustomerid = wa3_t_020-zcustomerid.

ENDLOOP.

DELETE z1email FROM TABLE it3_t_020.


IF wa2_t_020-zsequencenumber = '00000000'.

SELECT MAX( zsequencenumber ) FROM z1email INTO dt_zsequencenumber.dt_zsequencenumber = dt_zsequencenumber + 1.wa2_t_020-zsequencenumber = dt_zsequencenumber.wa2_t_020-zcustomerid = i_top-zcustomerid.

ENDIF.

MODIFY z1email FROM wa2_t_020.

ENDLOOP.

ENDFUNCTION.


17/32



2007 SAP AG 17

DELETE BAPIWRAPPER SAMPLE CODING:

FUNCTION ZSAMPLE_DELETE.*"--------------------------------------------------------------------*"*"Global Interface:*" IMPORTING*" VALUE(I_ZCUSTOMERID) TYPE Z1CUSTOMER-ZCUSTOMERID*" TABLES

*" RETURN STRUCTURE BAPIRET2*"--------------------------------------------------------------------

DATA: it_z1customer TYPE TABLE OF z1customer,wa_it_z1customer LIKE LINE OF it_z1customer.

DATA: it_z1customeradd TYPE TABLE OF z1customeradd,wa_it_z1customeradd LIKE LINE OF it_z1customeradd.

DATA: it_z1email TYPE TABLE OF z1email,wa_it_z1email LIKE LINE OF it_z1email.

DATA: lds_return LIKE bapireturn1,gdf_message_dummy type string .

SELECT * FROM z1customer INTO CORRESPONDING FIELDS OF TABLE it_z1customer WHEREzcustomerid = i_zcustomerid.

LOOP AT it_z1customer INTO wa_it_z1customer.ENDLOOP.IF sy-subrc = 0.DELETE z1customer FROM wa_it_z1customer.

ENDIF.

SELECT * FROM z1customeradd INTO CORRESPONDING FIELDS OF TABLE it_z1customeradd WHEREzcustomerid = i_zcustomerid.

LOOP AT it_z1customeradd INTO wa_it_z1customeradd.

DELETE z1customeradd FROM wa_it_z1customeradd.ENDLOOP.

SELECT * FROM z1email INTO CORRESPONDING FIELDS OF TABLE it_z1email WHERE zcustomerid =i_zcustomerid.

LOOP AT it_z1email INTO wa_it_z1email.DELETE z1email FROM wa_it_z1email.

ENDLOOP.

ENDFUNCTION.


18/32



2007 SAP AG 18

SYNCBO DESIGN:

Now BAPI Wrappers are created in backend. Now we have to design the syncbos in middleware.

Syncbos are used to define the data exchange between client and server.

Logon to Middleware system and goto MEREP_SBUILDER and provide with the Syncbo ID which has to becreated

And press create incon.


19/32



2007 SAP AG 19

And select the syncbo type (Here T01-Timed two way has been selected).


20/32



2007 SAP AG 20

If BAPI Wrappers reside in the same system where syncbos are been created then select Default RFCdestination.

Otherwise select Syncbo specific and provide with RFC destination of the backend system.

(In this example application BAPIs reside in the same system)

Press enter.


21/32



2007 SAP AG 21

Fill in all the details. (Getlist and Getdetail are mandatory).

Press on the mapping screen on the top left corner.

This will take you to the mapping screen as below.


22/32



2007 SAP AG 22

Double clieck on the tables tab of ZSAMPLE_GETLIST BAPI Wrapper.


23/32



2007 SAP AG 23

Map the fields which should be visible to the client and save.

Come back to the mapping screen and double click on tables tab of ZSAMPLE_GETDETAIL BAPI Wrapper


24/32



2007 SAP AG 24

Check the key field and also mapping fields. Similarly check the key field and map the fields for the z1email table

also.

Double click the tables tab of Create bapi wrapper and check the mapping fields and similarly for modify bapiwrapper also.

Now save the syncbo and Generate the syncbo.(Ctrl +F3).

Now autogenerated Synchronizer code will be generated which consists ofREPLICATOR,UPLOAD,DOWNLOAD.


25/32



2007 SAP AG 25

CREATION OF MCD:

Goto transaction MI_MSD / MI_MCD and fill the details.

Press create MCD.

Fill in all the details and select the created syncbo as shown below:

Can select multiple syncbos also.

Save the MCD.


26/32



2007 SAP AG 26


27/32



2007 SAP AG 27

Download of MeRep XML:

Goto transaction MEREP_SBUILDER Gotodownload Metadata XML.


28/32



2007 SAP AG 28

Select the MCD which was created and press enter.

MeRep XML is generated and downloaded on the desktop.


29/32



2007 SAP AG 29

Furthur development with MeRep XML using NWDS:

Now this MeRep XML is used for futhur development from the client side using NWDS.

Furthur steps on how to use MeRepXML has been explained step by step in the below published article.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdfhttps://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdfhttps://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdfhttps://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdfhttps://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/mobile/Mobile%20Application%20Development%20using%20NWDS%20and%20Mobile%20Infrastructure.pdf


30/32



2007 SAP AG 30

Related Content:

BAPIWRAPPERS:

http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.html

Syncbo Design and mapping

http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.html
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/defining_syncbo.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.htmlhttp://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.html


31/32



2007 SAP AG 31

Disclaimer and Liabili ty Notice

This document may discuss sample coding or other information that does not include SAP official interfaces andtherefore is not supported by SAP. Changes made based on this information are not supported and can beoverwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methodssuggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of thistechnical article or code sample, including any liability resulting from incompatibility between the content withinthis document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold,SAP responsible or liable with respect to the content of this document.


32/32


mobile offline application development.pdf

Documents