Smart Sync Related Queries

[Former Member]

A. Any guidelines in defining parent chlid relation ships and association when making BAPI Wrappers???

Any documents/note/links.

C. How can we separate BAPI Wrappers Interface and filtering rules. Can I bring my Filtering /distribution rules defined at backend

to MI Middleware. If yes How??? Any documents.

D. Which type is suitable for Master Data and which Type is suitable for Transactional Data.

Is it OK to make every BAPI Wrapper of type T51(Server Driven).

Are there any drawbacks in this approach.

E. In the case of Server Driven, who has more load Server or the middleware??

regards

anubhav

[Former Member]

Hi Anubhav,

Adding to what Ajith has said above....

There are 3 ways in which the backend informs the middleware about the changes in the backend.

1) Using BTE's

2) Background program which calls the MEREP_DELTABO FM with keys

3) Idocs.

Check which of these are suitable for the you to make use of the benefits of the T51 SyncBOs.

Thanks...

Preetham S

[Former Member]

Hi Anubhav,

Answering on your last two questions:

>> D. Which type is suitable for Master Data and which Type is suitable for Transactional Data.

T01 and T51 are the best options when data is common among multiple clients, like master data. The question here is how critical for you to have the latest updates downloaded to Mobile client. Also, with T01 is more middleware-resource intensive.

When data is more user specific and it's still critical to have the latest updates downloaded, then you may consider S01. Disadvantage of that SyncBO is high load on the back end and problems with reprocessing after errors.

>> E. In the case of Server Driven, who has more load Server or the middleware ??

With T51 the logic is based on back-end side, so logically more load is on your backend side. And that load will be extremely high if a large number of changes are made.

T51 is optimal solution, when changes are done infrequently and you want your backend to control when to push the data.

Best regards,

Laziz

[AjithC]

Hi Anubhav,

T51 is the best type of syncBO not only for master data, but for transactional data also. This is the one with highest performance and the least load both on both backend and MI.

In T51 case, backend informs MI about the changes in the data (add/modify/delete). Backend is the best person to identify the change in data as the data resides there. The task to idendify the data changes is quite easy in backend (depends on the backend implementation), but if there are too many ways (too many applications) the data can be changed in the backend, the effort to catch all these cases will be higher in the backend.

In T01 case, MI identifies the changes in the data. Since the data is primarily residing in the backend and changes in data happens there, the only way MI can identify the changes is by comparing every record from the backend with the replicated data in the middleware RDB. This process will be very time consuming and can lead to performance problems if the data is huge. Also the replication time will be higher.

In the case of master data which seldom occurs changes, the T01 replicator will run periodically ( as scheduled ) comapring the whole data to find out there is no changes. In the case of T51, the replicator will be run automatically only when the backend informs there is a change in data.

Even for transactional data, T51 is better in terms of performance. The delay for the updation of data in the middleware after the change in backend is very small and is even configurable in middleware. So the latest data will be always there in middleware.

Regards

Ajith Chandran

[Former Member]

Hi Anubhav,

Coming to T51 type of syncbo..the only advantage is that we get the laterst data to middleware...the load will be inbackend..becaz only the delta changes are put into MEREP_DELTABO...from there middleware will pull the changes to MEREP_207....

There is no such harm to implement all T51 type of syncbos....as such.......but there are also few disadvantages for T51 type of syncbos.....if there is a huge delta changes in backend..when we replicate..there can be a performance issue to get all delta changed records to MEREP_DELTABO....

But T51 is best for types of syncbos.

Hope this is helpful.

Cheers,

Karthick