Skip to Content

Delete Bapi Structure of a SyncBo

Hi, i need to delete a structure (040) of a SyncBo, i did this by the next code:

SyncBo syncBo = getSyncBoInstance("Y01_ORD_TR", topSyncKey);

SyncBoDescriptor sbd = syncBo.getSyncBoDescriptor();

RowDescriptor trd = sbd.getRowDescriptor("040");

Row row = syncBo.getRow(trd,syncKeyToDelete);

syncBo.deleteRow(row);

With this code appears in the merep_mon a "M" message for the TOP structure, and for the 040 structure a "D" message, but it doesn't call to the Bapi "Delete", what can i do to the Bapi Delete is executed ?

Thanks.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 10:02 AM

    Hi,

    if you send M and D , then form client side it is okay I think.

    Why do you say the delete is not called? Is the information still on the device? What is the state of the BO? And have you inserted a LOG writer into the Backend BADI for delete - so you see what happens there? DEBUG of that remote stuff is nbot really possible or very tricky in MI - i know. But I think the problem is not the code you mentioned, because the m and the D method are the thing we expect.

    Either the GETDETAIL handler still gives that information down. What is the type of the BO? Perhaps you have an Add for that item with one of the next syncs, because the information is still on the MW?

    - please check the sync state of the item

    - what information is send down to the client for that item?

    - can you implement a logging for the delete and confirm that it is really not called (I think it is called)

    Hope this helps to get any further.

    Regards,

    Oliver

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Julian Moreno Luna

      Hi,

      to delete the Top structure all items must be G or L as well. Is this the case?

      Furthermore you need to have the DELETE handler developed in the backend and assigned in the middleware. Beside that it should work.

      Well, if you still have the issue, we should talk via MSN, makes it much more easy and at least faster

      Regards,

      Oliver

  • author's profile photo Former Member
    Former Member
    Posted on Jan 17, 2008 at 01:13 AM

    Hi Juan,

    standard MAM does not allow user to delete any data received from the backend.

    Only locally created on the device data can be deleted by a mobile user UNTIL it is synchronised to the backend.

    As such no delete BAPIs are implemented for MAM to actually trigger delete global (backend) objects from the mobile device.

    "D" is only used when backend "recalls" object download from the device, ex. order is TECOed on the backend wich means it has to be removed from the device.

    Regards,

    Larissa

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.