Get your SAP mobile architecture up and running

Get your SAP mobile architecture up and running in seven easy steps. Learn through a simple step-by-step approach that helps you build the SAP MI Architecture.

1.0 Scenario

The user selects to create a record in SAP R/3 using a portable device. The record can be a material, a vendor, or a volume.

2.0 Prerequisites

1. JDK must be installed.
2. The version-specific MI client must be installed and the device ID for the client is obtained.
For development, Backend/Middleware (Syncbos, Bapi Wrappers, etc.) must be completed and the metadata XML must be downloaded and prepared for the application under development.

3.0 Strategy and timing of mobile clients

Recommended implementation strategy that includes four important pillars.
o MI application runtime scenario,
o Strategy and synchronization development
or Administration
o Runtime perspective that contains the execution of a mobile application, contains the user interface, business logic, and data storage on each device.

4.0 Process Flow

4.1 Development of the back-end system

o In back-end, the development of the system is done from the MEREP_SBUILDER transaction and the BAPI Wrapper Wizard. After running this wizard, it creates BAPI containers.
o In MEREP_SBUILDER, syncBOs are built with details like RFC destinations and field mapping.
o This will allow you to download XML metadata.
o This file will be given to the MI application developer for further MI development.

4.2 Mobile application development

o SAP NetWeaver Developer Studio (NWDS) provides SAP’s own environment for developing Eclipse-based Java-based multi-tier business applications.
o An open source product, whose open plugin architecture provides a suitable platform for incorporating specific functions.
o NWDS provides easy-to-use tools for designing, developing, deploying, and continually changing business-critical applications in Java/J2EE.

5.0 Synchronization

o In order to send the data from the PDA to the middleware and R/3, we need to synchronize the device.
o This can be done manually, however the manual process is time consuming and cumbersome to carry out.
o To automate the synchronization process, we can run a background job that performs the synchronization and prevents the user from carrying out this process.
o We have programmed an automated synchronization process that will re-synchronize your device every 10 seconds.

6.0 Data flow between the host system involved

In the MI architecture, data flows between three systems for each material creation cycle.
Back-end system: A system in which the actual data, the Business Objects, and the BAPI wrapper are linked.
Middleware: Manages the data flow between the application and R/3.
Mobile device: SAP MI Client in association with Java Development Kit takes care of the rendering of the application (jsp files) or simply runs an application. This acts as a front-end to this entire process.

7.0 Portal Implementation Strategy

o SAP Netweaver Portal plays a fundamental role in the implementation of MI applications.
o The middleware ABAP stack is maintained on the same server.
o There is a default JCO connection between this ABAP stack and the Java stack. This allows communication between the ABAP stack and the Java stack without creating any connectors.

I must reiterate here that these are the 7 precise steps that can really help a naive user to understand what precise steps are needed to have rapid development of SAP Mobile. I must also say that these steps are the result of our hard work which involves a continuous struggle to learn these steps. I encourage readers to make full use of these steps, as I can promise you that you won’t get this approach documented even on SAP’s own developer network site. I wish you all the luck for the implementation.