How to connect SAP Mobile device with BADI?

Question

Dear experts,
We have some functionality written in the BADI program for handling Stock movement . We want to bring the same functionality for SAP Mobile device.
Can you please provide your suggestions?
Thank you!
Saravanan

Answer 1

continuing...
How NW Mobile can achieve this is:
1. By creating BAPI Wrappers (these should follow the CRUD principle)
2. Then you import these BAPI Wrappers as 'Data Objects' into NW Mobile.
(In your case, I guess you would have a Data Object relating to instances of Consignment Stock Movements)
3. Then you create distribution rules (this will define which data object instances will flow to which devices)
4. You create and deploy an application on your device (you can write whatever business logic you want in your application, including taking inputs from a user, or doing manipulations to the data object instances)
When the user uses your application, changes will be done to the data object instances, either due to synchronizing data with NW Mobile (to get latest set of changes to the instances) or by creating, modifying or deleting the instances in the device.
Later, when the user synchronizes with NW Mobile, the changes made to the data in the device will be forwarded to the backend via the BAPI Wrappers which you created earlier.
This, in essence is how NW Mobile works.
If however, you want to replicate the logic that is being performed in your BAdI in your mobile device, there are only two ways to it:
1. You rewrite your logic in your mobile application (in Java, or whatever language it is that you wish to develop your application in)
OR
2. Say your BAPI Wrapper internally causes your backend to call certain BAdI's. But this is of no concern to the NW Mobile system itself.
An example of #2 would be:
Every time your user modifies a 'Consignment Stock Movement' in the device and syncs with NW Mobile, NW Mobile will call the MODIFY BAPI Wrapper in the backend (SRS system). The MODIFY BAPI Wrapper will trigger a workflow, or run an SAP shipped report or whatever it is that will lead your BAdI to be called... Finally, all this will cause some change to be done to your 'Consignment Stock Movement' in the backend. Which will get pushed to the NW Mobile system and the next time the device syncs with it, this change will be reflected in the device as well.