modify bapi wrapper is called even when data not modified in mobile device

[vivek_goenka]

hi

I have created 2 sync bos- ZOR_TRIP & ZOR_POINT.

ZOR_POINT is referencing ZOR_TRIP,

and both of them have modify bapi wrapper.

now the problem is, whenever on the mobile device

user is synchronizing, modify bapi wrapper for both

the sync bos are called even if user hasn't made

any changes.

moreover, out of many instances of ZOR_POINT

on the mobile device, if user is modifying one or more

instance and synchronize with the server,

then from the next synchronization onward

the modify bapi wrapper is not called for these instances

but for the remaining instances

modify bapi wrapper is called even if they are not modified

on the mobile device.

i was thinking that only the delta data is exchanged between

the mi server and mobile device but here, even unmodified data

are also transfered.

how to solve this unnecessary exchange of unmodified data?

also I want to know under what conditions modify bapi wrapper is called.

thanks & regards

vivek goenka

[AjithC · Accepted solution]

Hi Vivgo,

Check the monitor (merep_mon) whether the client is sending modify requests or not. Unless a request comes from the client, there is no chance that the modify bapi wrapper being called.

Check your application code. You might be calling some modify api's by mistake..

Regards

Ajith

[vivek_goenka · Accepted solution]

hi ajith

merep_mon is showing Action as M for the inbound data,

but there is actually no modification on the client.

i have checked the application code, there is no any modification on the client.

even if i assume that by mistake modify api is called in client

then why after once the user actually modifies the data

the modify bapi wrapper is not called from the next synchronization onward

for that instance but for other instances it is called.

had there been any such code then the modify bapi wrapper

for actually modified instances should also have also been called.

can we say that this problem is in MI7.0 SP09?

thanks & regards

Vivek

[AjithC · Accepted solution]

This is defenitly not a problem in MI 7.0. This is against the basic principles of MI. Lot of applications are working fine. Since SP09 is little old SP, it makes sence to upgrade to the latest SP14.

Since its appearing as M in the inbound, that means the client is sending the modify reques to server. So somehow the client framework is identifying this data as modified.

BTW are you using DB2E or file storage??

Regards

Ajith

[vivek_goenka · Accepted solution]

hi ajith

we are using DB2E.

thanks & regards

vivek

[vivek_goenka · Accepted solution]

hi ajith

after giving a closer look at the code, i found that it was the code which was actually modifying the syncbo instances.

thanks for your help.

thanks & regards

vivek