Skip to Content

Quick Start Guide: SAP Work Manager 6.X with SMP (Agentry)

As a proactive support to our SAP Work Manager/Inventory Manager customers, we have setup some quick start guides on how to install and get the SAP Work Manager to sync with the typical Agentry Test Environment (ATE) or SAP Agentry WPF clients.

Most of these Quick Start Guides reviewed multiple support tickets, QA tricks and request for help from the SAP Community Network (SCN discussions) to enhanced our documentation. This means by following the steps outline in the guide, the user will not see the same common error as reported in SCN or SAP ticketing (incidents). This will help each user tremendously in setting our products.

Thanks for making our SAP Work Manager and Inventory Manager successful. We wanted to share more hands on guide to help you in setting this product easily for your project and the customers.

  1. Quick Start Guide to install SAP Work Manager 6.0 with SMP 2.3 – Agentry – See SAP KBA # 2048221
  2. Quick Start Guide to install SAP Work Manager 6.1 with SMP 3.0 – Agentry – See SAP KBA # 2060561
  3. Quick Start Guide to install SAP Work Manager 6.2 with SMP 3.0 – Agentry – See SAP KBA # 2153990
  4. Quick Start Guide for SAP Work Manager 6.3 is similar to Work Manager 6.2 above – See Blog WM 6.3

# You may need to access your SAP account to properly view the KBA link above.

Special Note:

  • SAP Inventory Manager 4.0 (with SMP 3.0 – Agentry) also follows the same quick start guide as of SAP Work Manager 6.1 (Names of files or mobile product is different but it has the same flow)
    • Needs Mandatory SAP note: 2016236 – Mobile configuration panel changes for SAP Inventory Manager 4.0 to make the sync work

Additional References (Mandatory SAP back-end setup):

Users are expected to setup the SAP back-end add-on. Please set it up prior to running or following the Quick Start Guide above (please read any special mandatory patches as discussed below).

Others Information:

As this is a living document, you may bookmark this for future updates on Quick Start Guides.

If you have any feedback we could use it to further enhance our products or documentation. Rating each of the Quick Start Guide will help us understand if you need more of it.

Best Regards,

Mark Pe

SAP Platinum Support Engineer (Mobility)

You must be Logged on to comment or reply to a post.
  • hi Mark,

    i tried with steps you have given but, i am not getting the back end details pulled after uploading work manager package under app specific settings, when i go to back end TAB it is empty,

    i am referring your guide "Quick Start Install Guide Work Manager 6.1 SMP3.0"  slide number 15, i have installed SMP3.0 SP04, could you please help on the same.

    Thanks, Prem

    • Premnarayan,

      Can you close the Application Settings window then reopened it?

      Also, like on Side 12, the path will be different now in SP04, instead of, it would be<ApplicationName> 

      <ApplicationName>  would be the name you defined in the Cockpit.


    • Prem,

      Hi. The trick here is to figure out if your backend is actually not loaded. In the startup.log file, you can tell if the backends were fully loaded even though it is not shown on the tab. This startup.log file is key to make sure it is clean so you can verify that the startup is successful. The cockpit "displays" the data but your server (the startup.log) indicates if you are actually connected or not.

      As suggested above by Steve, sometimes it could be a refresh issue but verify that the connection to the backend in the startup.log is working. If it is then you can sync with your client. I have seen this before.



      • Hi Stephen, Hi Mark.

        Thanks for timely reply, i am now able to get the backend details in SMP and able to connect with app from device, basically i went through startup.log everything was OK there then i checked event.log, there is says "Data Object Assignment for BAPI /SYCLO/CORE_MDW_SESSION1_CRT Not Found!" .

        then i realize that my backend system was not up to the mark to connect with Agentry, i changed backend where all the objects were available and now it works.

        Thanks, Prem