Skip to Content

SUP 2.1.2 Native Android Application Development… Things to note

I hope all you developers are getting your hand dirty with building native mobile apps on various platforms with SUP..

I started building my first native app on Android.

I would like to share my first experience of building Android Native App with SUP2.1.2 here in this blog post…

1. Background Sync:

We all are familiar using the mail application in our mobiles.. When we compose a new mail and clicks the send button, Sync will happen in the secondary thread and still we will be able to compose further new mails, check out our inbox, etc..

I thought of doing the same in my app in which when a user creates a PO, immediately I started the Sync in the secondary thread using Service API of Android.

But the problem here I faced is, I had to read the data from MBOs when the Sync happens at background, so that I would still be able to allow the user to use the app, which didn’t happen.

the problem is that when the Sync happens, actual tables that would have got created for our MBOs will be locked.. We won’t be able to read anything out of the MBOs when the Sync happens.. Sometimes you will be able to read the data but after couple of times, your DB will get corrupted and further Sync requests will get failed with error…

So Finally I changed the design in such a way that when the Sync starts, the progress bar will appear in the app and the users are not allowed to do any operations on the app until the Sync finishes.

I thought of sharing this because this will save some time for you developers when got into the same issue..

Thanks.. Will see you in the next post.

4 Comments
You must be Logged on to comment or reply to a post.
  • Hi Raja,

    From this post I could know that you are android developer in SAP mobility.

    I am also in the same position. So I would like to communicate with you to share

    information and issues.

    If you don't mind can you share your email id.

    Regards

    Midhun

    midhunvp@gmail.com

  • Hi Raja,

    Did you try to make different syncGroups in the Workspace. Make a syncGroup like PostPO in which you will add only that MBO which is responsible for posting data into SAP. And after pressing some post button you synchronize only that particular group.

    So you will be able to read data from other MBO's while that group is in process..

    Hope this helps 🙂

    Thanks.

    • Hello...

      In my case, I used create operation in the MBO to create the transaction. So I hope there is no separate synchronization group we can maintain for operations...

      Only MBO's can be added to the sync group..

      In my case, if I create a transaction using Create operation and does sync, I am not able to read the data of the MBO with which the operation is kept..