on 07-02-2008 4:50 PM
Hi All,
I'm using MI 7.0 SP9. I have a syncBo Z_TEST type 2-Way.
I define GET_LIST, GET_DETAIL and CREATE BAPIs.
I create a Z_TEST syncBo on the client (status NEW).
After a synchronization, the Z_TEST object is created in the backend,
but the local syncBo status is INCONSISTENT and I have a second syncBo representing the new object with CONSISTENT status.
Log extraction :
02.07.2008 17:25:36 Adding header(mobile ID=0000002213, synchronization key=0000000006) data=TOP0001000
02.07.2008 17:25:36 Before BAPI wrapper call: Create
02.07.2008 17:25:36 Z_TEST_CREATE has started for run number 0000179341 and runtime counter 8
02.07.2008 17:25:37 Z_TEST_CREATE has finished for run number 0000179341 and runtime counter 8
02.07.2008 17:25:37 Before BAPI wrapper call: GetDetail
02.07.2008 17:25:37 Z_TEST_GETDETAIL has started for run number 0000179341 and runtime counter 9
02.07.2008 17:25:37 Z_TEST_GETDETAIL has finished for run number 0000179341 and runtime counter 9
02.07.2008 17:25:37 Updating replication DB for mobile ID 0000002213 (headers=0, items=0)
02.07.2008 17:25:37 All updates for one TOP block were successful (seq. no.=129, TOP cntr.=0000000001)
I should have :
Updating replication DB for mobile ID 0000002213 (headers=1, items=0)
Why the system doesn't make the link between the created object in the backend and the local object ?
Any idea ?
Hi,
it is your CREATE handler in the backend that has the issue. It sends the data down to the device - have a look into the standard codings for BOs how they handle this - this is in that case the easiest way, cause everything else is a guess from this side. But at least: it is most likely the BADI coding on the backend - could be the mapping on the Middleware as well, but that is not that oftenthe issue.
Regards,
Oliver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.