Skip to Content
avatar image
Former Member

Server Driven SyncBO (T51)

Hi All

I have to create a Server driven SyncBo (T51). I have read all its theory

and I think I now understand its working well. I just have some technical queries for you all, which may be related to coding and stuff.

It seems to me that for Server Driven SnycBo, the back end needs to 'Catch a event' and then make a RFC call to the middleware to a particular FM. My question is how will the back end 'Catch the event' and automatically execute the programme makin the RFC call.

How will the back end know if some back end data is changed or created and how will it react on its own. Is it some user exit or something else...

The data which is in use might lie in Custom tables.

And how will the GetList BapiWrapper will only get the delta data. How will it send only the keys of the objects which have been changed.

Do we have to use some time or date fields and compare them to see which data has been changed or not.

Or we can use CDPOS tables to record changes.

Sample code and ideas are welcome.

If Any clarification is needed.. please free feel to ask me 😊

Points will be awarded for sure.

Thanks, Ankur

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 17, 2007 at 03:43 AM

    Hi Ankur,

    The easiest way to catch changes in the backend is to use BTEs. Or you can find some exits and write the code in that.

    Depends on the business scenario its not difficult to identify the changes for the object. The object lies in the backend system. Find out which program UI make changes to your business object. Once you identify that, you can easily track the changes by writing some code in the exits. Or incase the changes to the business object can be done via multiple UIs and even from remote systems, you can use BTE (if available).

    Worst case, write a program to identify the changes (via timestamp or similar fields) and then run this periodically to push the data..

    From MI perspective, the backend will inform the changes via calling the method MEREP_DELTABO. Once the call is made, MI will schedule a job to do the replication. The delay for the job is default 5mins, which can be configured in merep_pd (SP19 onwards). All the changes informed by the backend in this delay time is consolidated and then passed to Getlist. The only job of getlist is to verify this and return.

    Hope its clear..

    Regards

    Ajith

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I think people are really ignoring my questions. Or may be they(my questions) deserve to be ignored.

      Well, thanks to all who have offered all this help to me. It really helped me a lot.

      Thanks Again,

      Ankur

  • avatar image
    Former Member
    Aug 17, 2007 at 12:31 AM

    Hi Ankur,

    you might want to take a look at the document

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/818ac119-0b01-0010-ba8b-b6e3f3490a63

    which is published on mobile SDN.

    Document describes SDs for Mobile Asset management application but it gives a general picture as well.

    Regards,

    Larissa Limarova

    Add comment
    10|10000 characters needed characters exceeded