Skip to Content

Work Manager 6.4: OOB Edit Notification not working

Dear All,

I am using Work Manager 6.4 , SMP 3.0 SP12 and Agentry client 7.0.14

I am trying to edit a notification say description, priority .. etc . so when ever I transmit the change does not gets updated in SAP backend.

This is irrespective of the fact that its an independent notification or notification associated with any workorder.

It invokes the Bapi wrapper /SMERP/PM_DONOTIFICATION_UPD, while debugging we found that the values do get pass from Syclo to this Bapi wrapper but then does not gets updated in SAP system.

This is the standard functionality and we have not yet done any enhancement in this yet.

If anyone has face this issue, Can you please suggest .

Many thanks in advance

Thanks and Regards

Neha Mahanty

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Aug 08, 2017 at 09:49 PM

    Dear Neha,

    Besides you're talking about an OOB implementation of Work Manager the issue can most probably come from a non-standard configuration of PM in the backend system. Enhancements in the backend, validations or mandatory fields will cause an error if you don't adjust your mobile app.

    For the understanding of this issue you need to provide more information. If you managed to set a breakpoint and debug the ABAP part you could see if the BAPI returns any errors when trying to update the notification. Moreover, the agentry logs can be switched on and look for any clue in there, but I would probably start with an ABAP debug in your place. Once you get to the BAPI Wrapper that would lead you to the CREATE method of the Notification Data Object. If my first guess is correct, this method is calling a BAPI to update the notification and it should be returning some error there.

    Best regards,

    Leonardo.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Leonardo,

      Thank you !! You were right , there was an enhancement in ECC, due to which this functionality was not working.

      We have corrected that and its working now.

      Thank you so much for the suggestion, it really helped.

      Best Regards

      Neha Mahanty