cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicate Notification Items posted in backend in WM6.2 application

padma_mundru
Participant
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

mark_pe
Active Contributor
0 Kudos

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

padma_mundru
Participant
0 Kudos

Hi Mark,

Thanks You.I have verified the Notes, both are applicable to WM6.1 application.But we are facing issue in WM6.2 app.Hope these notes are applicable to WM6.2 as well.Correct me if I am wrong.

And the Note 2151097, suggest to import the definitions from an application( BCP191919.agxz) attached to it.But our app has customization.Kindly confirm if we import the definitions from  BCP191919.agxz into our custom app, does not have any dependencies.

And we are in the below versions:

SMP SDK: SP10 PL07

SMP Server: SP09 PL04

Thanks in advance.

Thanks & Regards,

Padma.

sravanthi_polu
Contributor
0 Kudos

Hi Mark,

Thanks for the valuable inputs and suggestions.

Thanks & Regards,

Sravanthi

mark_pe
Active Contributor
0 Kudos

Padma,

Hi. If you have compared the two Editor definition (Your WM 6.2 and the attached notes agxz file) and verified that the WM 6.2 did not have the same definition (or fix) then this note will be a fix to the issue. With respect to the merging on why WM 6.2 did not have the fix, there may be a chance that the note was not merged in or that the product development group expects the user to implement the fix by using the note.

Also, if you have customization tied in the same area then you need to merge your customization with the fix BCP191919.agxz with your WM 6.2.

This should be done by your best Agentry editor person so you can do the merging correctly.  Remember one hint, if it didn't work the first time during merging, you have to do bottom up merging and save as needed.

Example:  If the screen does not merge (on import) it may be because it is pointing to a global that should exist first.  So you have to merge the global in the editor first before doing the screen.  Or another example could be that the screen references a complex table, so do the complex table first before the screen.  This is just rule of thumb.

Best Regards,

Mark Pe

SAP Platinum Support Engineer

padma_mundru
Participant
0 Kudos

Hi Mark,

Thanks for the response.

As suggested, we have imported the definitions in the build BCP191919.agxz into our application project and published to SMP server.We could able to see that these new definitions are not downloaded to the device in intermediate sync.Hence we have reset the app and replicated the scenario.But still duplicate Notification Items are posted to back end.

Kindly suggest.Thanks in advance.

Thanks & Regards,

Padma.

sudhiranjan_lenka
Contributor
0 Kudos

Hi Sravanthi & Padma,

We also encountered the same issue for Notification and Workorder update post.

We could able to manage the issue by implementing the logic explained above by me. It's working fine for us, I can assure you  it's a full proof solution.

I also went through the code in the above SAP notes shared by Mark, they have also done the same.

We are working on Work Manager-6.2

Just wanted to let you know....

Thanks,

Sudhir.

sravanthi_polu
Contributor
0 Kudos

Hi Sudhir,

Thanks for the information.We have restricted the duplicates in middle ware.

Thanks & Regards,

Sravanthi

Answers (1)

Answers (1)

sudhiranjan_lenka
Contributor
0 Kudos

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.

sravanthi_polu
Contributor
0 Kudos

Hi,

We did face the issue, when we have set the response as "Update Client key property", when performing sync, after posting the notification to back end(after execution of Notification post current transaction),  the client got disconnected from server.Now at this point in time, the LOCAL_1 is not replaced with the back end Notification Number on the device.Now when again a sync is performed  two "Notification Post current" transactions are sent, which is posting two notifications in back end.Hence two notifications with the same data are posted.


Requesting you to please elaborate point 2.We have verified the Notification post current action/transaction  and could able to see that there is no execution rule.

Thanks in advance.

Thanks & Regards,

Sravanthi Polu

sudhiranjan_lenka
Contributor
0 Kudos

Hi Sravanthi,

I understand your point, in that case we have to write our own code to handle this kind of scenario.

On click of the Transmit button, standard WM creates transactions for all the newly created notifications. which is decided on a certain condition(need Transmit/Local).

we can write our own condition(will set one flag while creating notification) to decide the newly created  notifications. While looping the notification collection, as soon as we create the Transaction for the newly created notification we will revert back the particular flag in the notification object. So that in the next Transmit it will not create one more new Transaction.

I hope it might help you.

Thanks,

Sudhir.

padma_mundru
Participant
0 Kudos

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