Smart Sync Related Queries

Question

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

Answer 1

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