What's the schema for the table that was generated?

Consolidated (Oracle):

create table lfv_del_pos 
(
   avisnr    varchar2(10)  not null,
   aviscode  varchar2(1)   not null,
   itemnr    varchar2(18)  not null,
   amount    number(4)     null,
   ml_stat   varchar2(2)   not null,
   ml_lstmod varchar2(14)  not null, 
   constraint pk_lfv_del_pos primary key (avisnr, aviscode, itemnr)
);

Remote (Ultralite):

create table lfv_del_pos 
(
   avisnr    varchar(10)  not null,
   aviscode  varchar(1)   not null,
   itemnr    varchar(18)  not null,
   amount    numeric(4)   null,
   constraint pk_lfv_del_pos primary key (avisnr, aviscode, itemnr)
);

It is possible that Mobilink wants to compare old and new values before deleting the record. E.g. imagine if someone already modified the field "amount". If you want to delete it, because you have old values, you probably will not want to do this. And in theory, you have to fetch the changes again and delete the record.

E.g. the upload part is described here: http://dcx.sybase.com/index.html#1200/en/mlstart/foursteps-ml-basics.html

Thanks Vlad, you are right, the text explains the behaviour: "The upload consists of a set of new and old row values for rows modified in the remote database. (Updates have new and old row values; deletes have old values; and inserts have new values.)" and that makes sense too. Then the documentation for the upload-delete table event explains the parameters wrong: http://dcx.sybase.com/index.html#sa160/en/mlserver/upload-delete-ml-scriptsref.html*d5e19662

I will not be surprised if these parameters go through all synchronization scripts. Because the request from the device has already reached the server, and it is up to MobiLink to filter or not, parameters that came from the client :)