Data Containers | Wrapper functions | Generic Sync Example
Generic synchronization allows mobile applications to call any SAP function module residing in any SAP backend (and even non-SAP backend, if the SAP Business Connector is used). MI offers a client-side API that allows to parameterize the module and then release this request for synchronization, where it is is processed in the corresponding application backend. The response data of the module will be returned to the device and can then be processed by the mobile application.
Generic Sync hence allows to easily connect a mobile application to a backend and reuse the business process logic prevalent in the backend. It is therefor ideal for simple data collection scenarios (for example, warehouse inventory). On the other hand, the central limitation of the approach is that only the response data of the called module are transported back to the device. This implies that a) the device needs to actively pull the data from the backend and b) the function module needs to bring back the right data for the current user and state of the device and also handle conflict situations correctly. The responsibility for this lies with the function module and hence with the backend application developer. For more complex business applications requiring powerful data replication, we recommend to use Smart Synchronization.
Generic Synchronization is entirely based on the data container concept, which itself is closely tied to the concept of wrapper function. You should read both chapters before proceeding the Generic Sync API.
For any easy start on Generic Synchronization, please read the Generic Sync Example.