Delta action="add"

[Former Member]

1)Delta action="add" means what ??

I Dumping file 'C:Program FilesSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'

I End of content of file 'C:Program FilesSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'

2)Conflict: R/3 = delete, device = modify

why device modify will trigger a delete in R/3 instead of modify

[Former Member]

> 1)Delta action="add" means what ??

add means that the incoming delta data will be inserted into your local MI repository.

these are the records that were not in your client but were in the backend table.

> 2)Conflict: R/3 = delete, device = modify

> why device <u>modify</u> will trigger a <u>delete</u>

> in R/3 instead of <u>modify</u>

i would suggest you to implement all getlist, getdetail, modify, create and delete

BAPIs. it seems that there is a problem in your modify bapi.

regards

jo

[Former Member]

1) comparing backend and client, if the record in client is not exists in backend, backend will trigger a delta action="add" to the client.

totalinstance + 1

2) i scratch my head to find a solution.

someone tell me i shouldn't call transaction, how come ?

this is the printscreen and function

i want to clarify here is

GetList: ZBAPI_AM_LIST_V1

GetDetail: ZBAPI_AM_DETAILS_V1

Modify : ZEMI_AM_P2P

ZEMI_AM_P2P will call ZBAPI_AM_P2P

In ZBAPI_AM_P2P ,it will call transaction as02

if you see the function ZEMI_AM_P2P

it will call insert zztable to insert system date and time

to test if the function get called.

but i found out the function is not invoke.

anyone pls checkout this printscreen in doc format

http://www.savefile.com/files/1005882