Skip to Content
author's profile photo
Former Member

Modify SyncBO on client - Always get a conflict

Hi all

I developed a SmartSync application using a S01 SyncBO Type. If I change data in the backend, the delta is succesfully synchronized to the client. But if I modify the SyncBO on the client and execute the syncronisation I always get a conflict "Conflict: R/3 = Change, Device = Change".

I get the conflict at every sync, even if I didn't change the data in the backend.

Does someone have an idea, what the problem is?

Thanks, Marcel

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Posted on Apr 20, 2006 at 02:20 PM

    Hi Marcel,

    just check ur GETDETAIL Bapi Wrapper .

    Here what u have to do is , in the in the EXPORT parameter , u will have to populate the HEADER Structure exactly corresponding to the import param of ur getdetail function module.

    GETDETAIL is using for Conflict detection also.

    what i mean is...

    we have one table parameter in our GETLIST Bapi WRAPPER.

    one of the field in this structure is the key field of the GETDETIL.

    here we have to include the same Structure , that we have given as TABLE in getLIST , in the EXPORT param of GETDETIL.

    at the same time, frame work call the GETDETAIL for each GETLIST instances.(at a time one GETDETAIL).

    this GETDETAIL execution is for one particular GETLIST instance at a time . So we have to populate the same data got from the GETLIST for this particular key every time and give this as EXPORT param.


    Kishor Gopinathan

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Aug 23, 2007 at 08:35 AM

    Hi Marcel,

    You may want to check this thread:


    It is about the same problem and I have written there one of the possible reasons.

    Plus, your getdetail and change BAPI should have the same tables. Even if you think that some tables will never be changed from the mobile device.


    Larissa Limarova

    Add comment
    10|10000 characters needed characters exceeded