Kick Start Your SAP Mobile Architecture

Kick start your SAP Mobile Architecture in seven simple steps. Learn through simple step by step approach that helps you to build SAP MI Architecure.

1.0 Scenario

User selects to create a record in SAP R/3 using handheld device. Record may be a material, vendor or volume.

2.0 Pre-requisites

1. JDK must be installed.
2. MI client specific to the release should be installed and device ID is obtained for the client.
For development, Backend/Middleware (Syncbos, Bapi Wrappers etc) should be completed and Metadata XML should downloaded and made ready for developing application.

3.0 Mobile Client Strategy & Synchronization

Recommended Implementation strategy comprises four important pillars.
o Runtime scenario of MI application,
o Synchronization strategy & development
o Administration
o Runtime perspective that contains running a Mobile Application, Contains user interface, business logic and data storage on each device.

4.0 Process Flow

4.1 Back-end System Development

o In back-end, system development is carried out from transaction MEREP_SBUILDER and BAPI Wrapper Wizard. After running this wizard, it creates BAPI wrappers.
o In MEREP_SBUILDER, syncBO are built with details like RFC destinations & field mapping.
o This will enable you to download XML metadata.
o This file will be given to MI application developer for further MI development.

4.2 Mobile Application Development

o The SAP NetWeaver Developer Studio (NWDS) provides SAP’s own environment for developing java-based, multi-layered business applications based on Eclipse.
o An open source product, who’s open plug-in Architecture, provides a suitable platform for incorporation specific functions.
o NWDS provides easy to use tools to design, develop, deploy and continuously change critical business applications in Java/J2EE.

5.0 Synchronization

o To push the data from PDA to the middleware and to the R/3, we need to synchronize the device.
o This can be done manually, however, manual process is time consuming and cumbersome to carry out.
o To make the process of synchronization automated, we can run a background job that performs synchronization and relives user from carrying out this process.
o We have scheduled automated synchronization process that will re-synchronize the device after every 10 seconds.

6.0 Data Flow between the major system involved

In the MI Architecture Data flows between three systems for every material creation cycle.
Back-end system: A system where actual data, Business Objects and BAPI wrapper lies.
Middleware: Handles the data flow between the application and R/3.
Mobile Device: SAP MI Client in association with the Java Development Kit takes care of the rendering of application (jsp files) or simply, running an application. This acts as a front-end for this entire process.

7.0 Implementation Strategy of Portal

o SAP Netweaver Portal plays pivotal role in implementation for MI applications.
o ABAP stack of middleware is maintained on the same server.
o There exists a default JCO connection between this ABAP stack and Java stack. This enables the communication between ABAP stack and the Java stack without creating any connector.

I must re-iterate here that these are the 7 precise steps that can really help a naive user to get hold of what precise steps are needed to have a rapid SAP Mobile developments. I must also state that these steps are outcome of our hard work involving continuous struggle to learn these steps. I encourage readers to make full use of these steps, as I can promised you folks that you will not get this approach documented even on SAP’s own developer network site. I wish you all the luck for implementation.