Skip to Content

Duplicate Notification Items posted in backend in WM6.2 application

Hi Experts,

When Notification Items are created from device iPad, duplicate entries are posted to back end system in WM6.2 application.When adding Items to the existing Notifications or Notification attached to work orders, "Notification Post Current" transaction is being called in device.The response to client attribute is set to "Replace Client Object" for this transaction in Notification object.Below is the sequence in which transaction are executed in iPad

Notification post current

Updating Notification

Refreshing Notification

Updating Notification

When we click on stop-cancel-start or encounters communication error, after the execution of Notification post current transaction,even though an entry is posted in back end for the item, another item is created with the same data since the transactions is again executing from the device

We think that the most appropriate value to "Response to Client" attribute in Notification post current transactions is "Replace Client Object".If we set "Update Client key property" then also the duplicate entries are posted when the client is interrupted while updating the data.

Kindly suggest on the issue and the other areas that need to be checked from Agentry front end perspective/JAVA/ABAP.

Thanks in advance.

Thanks & Regards,

Padma

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Feb 12, 2016 at 03:31 PM

    Padma,

    Hi. There was a reported issue before that we have a workaround or fix in an SAP note tied to modifying the Agentry editor with new items to detect the problem during transmit.

    Please review the SAP note attached and compare the Agentry Eclipse editor export with your version to see if you can either implement or study the solution.

    Please reference: SAP Note # http://service.sap.com/sap/support/notes/2151097

    Another issue is if you are using an older SMP 3.0 SDK SP version. You need to be at a certain version to prevent blank transmit.

    Please reference: SAP # http://service.sap.com/sap/support/notes/2141228

    Hope these suggestions help out.

    Best Regards,

    SAP Mobile Support Team

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 05, 2016 at 06:51 PM

    Hi Padma,

    Please try the following.

    1. Set transaction response as "Update Client key property".

    2. In the execution rule of Notification post current check if the primary key of the notification starts with "Local".

    I believe while creating the notification, notification id(PK) is set as "Local_.........." .

    Thanks,

    Sudhir.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      There is only one local notification item saved in the device.And we are creating only one item.But still duplicate entries are posted in back end.One of the scenario where we are facing an issue is when we are editing any data in work order header like adding an operation/performing status change etc, then adding item to the notification attached to work order.These items are posted as duplicates.

      Kindly suggest.

      Thanks & Regards,

      Padma

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.