To All SAP Work Manager, Service Manager or ERP Mobile Add-ON users,

SAP Digital Business Service tries to be proactive in giving resolutions out to the customer to be readily available before the need arises.

Based on some internal and external installation of SAP Work Manager Products, the following SAP Next Generation Support guided answer – decision tree will help users deploy and troubleshoot performance issue successfully. This SAP guided answer can be used as a check point prior to deployment to production that key KBA articles and SAP notes were applied.

Please review each action path in the decision tree with their corresponding solutions or actions.

SAP KBA # 2453323 – Troubleshooting SAP Work Manager, Inventory Manager, Service Manager or ERP Mobile Add-On performance solutions and checklist – decision tree (guided answers)

We appreciate all the customers/developers/consultants who gave all the field report about our SAP products performance and where to improve. We value your feedback to help make our product best in class. In this blog, please see some of the troubleshooting or key KBA articles to improve performance issues for your production environment.

You may bookmark this article as we plan to update this guided answers with new SAP notes/resolution later.

Best Regards,

Mark Pe

SAP Platinum Support Engineer

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. vivek gaurav

    Hi Mark,

    we are facing issue while creating collective measuring document (IK34) , when measuring point is more than 63 in entry no.

    I had applied SAP note as given by you :

    1. SAP KBA # 2106336: Troubleshooting Performance Issue: SAP Work Manager – Measurement Point creation – update task is slow.

    But still it is giving Timeout dump in IK34.

    I had posted in SCN : SAP Work manager(Agentry) – IK34 collective measuring point performance issue

    Kindly suggest…

    (0) 
    1. Mark Pe Post author

      Vivek,

      Hi. This blog is used for creating a checklist of what consultants, users, SAP support and admin needs to check when a performance issue occurs. For your issue that is posted in SCN and in here, if nobody was able to assist with their examples then it may be a new issue that may require an SAP incident/ticket if our current fix that is available online or during the ticket creation didn’t help out. Make sure to do due diligence in specifying the ST12 or test documentation (show what time the issue occured, who the user is) and the corresponding SMPServer-smp-server.log and Agentry logs as a requirement in opening an issue in SAP to speed up processing.

      Best Regards,

      Mark Pe
      SAP Platinum Support Engineer

      (0) 

Leave a Reply