online Scenarios and offline ?

[Former Member]

Hi ,

Can you confirm online and offline scenarios are possible in MI . we are having NW 2004s here .

online : I want a purchase order number to be checked with the backend instantly?

Is this scenario possible ?

Offline : should i replicate the data from the backend on to the MI client to do the check of a purchase order ?

Regards

Abhilash

[stefan_schwing]

Hi,

the main idea behind the generic sync and the smart sync/snycbo mechanism in MI is to query the backend for data, and store that data locall for offline usage.

Of course, you can build an MI application which uses generic sync conatiners which are processed immediately in the backend so that you have the results on your client in realtime. So yes, you can build a complete ONLINE application which will not work once you loose network connectivity. That's not what MI was built for, but that's also not a reason not to do it

So: "I want a purchase order number to be checked with the backend instantly?

Is this scenario possible ?"

--> YES, definitely possible

Cheers

stefan

[Former Member]

Hi Stefan,

Thanks a lot for for the clarification. This is very valuable information.

Cheers.

[Former Member]

Hi Abhilash, Saurabh

MI CANNOT be used for online applications. Only offline apps are supported on MI. Generic Sync is a one way of synchronizing with MI middleware but it does not mean that Generic Sync apps are online. Whatever records are created on MI will not be transferred to the backend untill and unless a sync is performed. This is not the definition of an online app.

-->online : I want a purchase order number to be checked with the backend instantly?

-->Is this scenario possible ?

No this is not possible using MI.

-->Offline : should i replicate the data from the backend on to the MI client to do the check of a purchase order ?

Yes you are right.

Hope this is clear.

Best Regards

Sivakumar

[Former Member]

Hi Siva,

What you have mentioned is something different from what i have understood about MI till now.

I would really appreciate if you could put some more light on this issue to make it more clear.

What according to you is the true meaning of an online application? and

How is it different from what a generic sync application enables you to do?

I have developed a few generic sync applications wherein on quering the backend i immediately get the desired output from the backend. This is what i consider as online because this gives me an immediate result from the backend. It is as if i am actually sitting at the backend and executing my query. And i do not need to do another sync to get this result i.e. i get it at the very moment when i am connected to the backend (online). Also this result does not come from my local database which i consider as working offline.

Cheers.

[Former Member]

Hi Abhilash,

You can do do both online as well as offline.

Online :-

You can do it by creating a generic sync application.

You need to create a remote enabled function module which will take as input a purchase order number and check it from those available on the system.

To know how to create a generic sync application refer the link : <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eba3a7-0601-0010-b982-92f1fca3258a">Generic Sync</a>

Offline :-

You can do it by creating a Smart sync Application.

Here you will have to create atleast two remote enabledfunction modules viz Getlist and Getdetail implementing the same functionality.

To know how to create a Smart sync application refer the link : <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eba3a7-0601-0010-b982-92f1fca3258a">Smart Sync</a>

The decision of choosing one among the two must be based on various aspects.

Smart sync/Offline is preferred for complex scenarios and those having a lot of data to be transferred between the client and the backend.

On the other hand Generic Sync/Online is preferred for relatively simple scenarios and those involving less amount of data.

I feel since you only need to see the availability of a particular purchase order in the backend, it is a very simple scenario and can be easily implemented via a generic sync/Online appln.

Not that it cannot be done through a Smart Sync/Offline appln, it can be done easily here also but its just that i think that it is not needed here.

Cheers.