Skip to Content

Troubleshooting: SAP Work Manager 6.X Attach Document issue

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

Based on some internal installation of SAP Work Manager 6.0 (released on SMP 2.3) or Work Manager 6.X (released on SMP 3.0) or Service Manager or Sales Manager the following SAP finding answers or decision tree (with SAP notes/KBAs or Information) will help users deploy and troubleshoot attach document successfully.

We partnered with most customers to attain the best solution.  Some of the solutions we have documented and presented in the SAP decision tree or finding answer program. We thank the SAP user community for being part of an active network of users who wanted to be supported properly and to share their knowledge to help benefit the SAP community as a whole.

SAP Work Manager / Service Manager / Sales Manager Attach Document decision tree (get your answer here).



Mark Pe

SAP Platinum Support Engineer

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

    I have been an avid follower of your posts on SCN and the replies you post to queries on SDN. The guidance provided has been very helpful for the mobility consultants like us.

    We are implementing Work Manager 6.0 for one of our customers and rolling it out to Windows 8.1 Toughpads. In this we are facing a challenge that none of the DMS attachments are flowing to the device.

    As I understand, this is a multi step process:

    1.     Send the list of attachments along with the work order details

    2.     User makes a request for the attachment to be pushed

    3.     GET method of /SMERP/CL_CORE_DMS_PUSHDOC_DO is called and is able to get the content of the attachment

    4.     Corresponding BAPI Wrapper should get triggered

    5.     Data is passed back to the Java class as per the configuration in Client Global

    We are able to successfully track the flow till steps 3. However, we notice that the control passes to ‘/SMERP/CORE_DODMSDOCUMENT_GET’ instead. This disrupts the onward flow to the Java class.

    This issue has also been raised as an incident#661557/2014.

    Would request you to shed some light on the resolution of this problem as it is critical to the success of the implementation.

    Best regards,

    Harsh Mathur

    SAP Mobility Consultant

    London, UK

    • Harsh,

      Your issue seems tied to multiple custom/extra BAPI KPRO configuration or patches which will rely highly on debugging the user.*.log and Backend-java-1.logs from your transmit (Need to make sure it is set to most detail and you have enable it from the SCC). Those log files will dictate what the next action item would be. You have some details in incident # 661557/2014 and you have summarized the issue above. I suggest to continue the debugging in this support ticket and if additional help is needed the ticket (incident # 661557/2014) can be escalated to the product owners worst comes to worst.

      Work with the processor of this issue to get the next action item. Then detail out the issue as spelled out in the user.*..jpg and Backend-java.1.log in the ticket so that the processor will know the next action item. If your issue then gets resolved, we can add it to the items above (I see I have two colleagues supporting you in this incident). Make sure to show the log files at the point of item 3 above because the details in the log can specify if you are missing a step as listed in the mandatory patches above (1828657 – has lots of details).

      I quickly look at the incident and reviewed the history (+attachments. I didn’t see the user.*.log or the backend-java-1.log or the backend-httpxml.log) to see if I can find anything that pops out but I believe it may require more processing (Analysis) to determine the issue.

      What we normally do is take all the reported issues through the tickets like yours 661557 and compile all the common issue based on how much traffic it has (in SAP tickets or SCN) and post details in the SCN to help consultants/users avoid it. The list above and the solution is tied to multiple SAP incidents #. It is part of us trying to be proactive to share the solution.

      For this particular issue, I would suggest working closely with the incident to get the resolution as it is too detailed and custom to your environment or business requirement.


      Mark Pe

      SAP Senior Support Engineer (Mobility)

  • Hi Mark,

    Can you tell me if WM 6.1 supports upload of documents to SAP for KPRO enabled type to Content Server (ie. non SAP SYSTEM).



  • Small test to verify whether the push port is  blocked by firewall or internal network settings when SAP tries to push document to the SMP 3.0 Server- Courtesy Daniel.


    a) Install  Advanced REST client/REST client for Google chrome or Firefox

    b) Specify URL of your SMP server with push port. Like  http://<FQDN&gt;:8282  select type as  Post. paste URL as





    c) SMP should process http request and initiate document download to the client.

  • Hi Mark,

    Could you please let me know what are the authorizations a user should have inorder to download the documents in SAP WM mobile application .



    • Reshma,

      It is in the middle of the blog above.

      Pasting it below.

      ~~~~~~From the Requirements above~~~~~~~


      This is the doc we give the customers basis team.



  • Hi Mark,

    In the section “Attach Document Work Manager Requirement” Point No 4 you had mentioned to maintain

    a. File Size (required)

    b. Class Type

    c. Class

    But when try to enter the class CL0001 I get an error “Please enter existing class for class type 017.

    Could you let me know if the class CL0001 is a standard class or a customized class.



    • Reshma,

      That point 4 is to mention not to leave it blank and to put a file size in it. The example I gave is from the default selection I have from our system. I am assuming when you select yours you should have a value in it. When we state “maintain”, it should have a value that corresponds to your actual value of your own system. So that actual number may not correspond to your own setting. I just want to show a picture but not to copy the exact values but you need to maintain your own environment based on your installation.



        • Reshma,

          The requirements that it should be maintained came from our own product development team after debugging other issues tied to attach document that didn’t work. I just don’t know what is different between your environment versus our own sand box in SAP for you to get the missing type. You may need to check with the team responsible in setting up the SAP documents as the mobility team (Product team) assumes this is handled by that group and not by the mobility (Work Manager) group.



  • Hi Mark,

    In the Attach Work Manager Requirement section, you said “from Work Manager 6.2 release onwards, DMS document feature supports KPro external content server in addition to SAP internal storage (Storage Category SAP-SYSTEM)”.

    Does it support both uploading and downloading attachment to/from KPro External Content Server?  We are having problem uploading document into Content Server from Mobile device and our developer has looked at the Work Manager 6.2 and 6.3 source code and found the Storage-Category “SAP-SYSTEM” hard-coded in the setDocumentFiles method.

    Please advise,


  • Hi Mark,

    Kindly suggest does the WM6.2 application has the feature of updating metadata of the attachments like (Date taken..etc) to back end.We are attaching a photo from device iPad to the Notification in back end system.When we save the attached photo of Notification updated from WM6.2 application to local PC, the meta data of the attachment(photo) is not shown.

    Kindly suggest does the standard WM6.2 application captures the metadata of the attachments from device and update to back end

    Thanks in advance.

    Thanks & Regards,

    Sravanthi Polu

    • Sravanthi,

      Please create a new Discussion marked as a Question.  Comments to a Blog (or Document) is not the right vehicle for asking questions as the results are not easily searchable.  Once your issue is solved, a Discussion with make the results much more visible to others experiencing a similar problem.  If a blog or document is related, put in a link.


      NOTE: Getting the link is easy enough for both the author and Blog.  Simply MouseOver the item, Right Click, and select Copy Shortcut.  Paste it into your Discussion.  You can also click on the url after pasting.  Click on the A to expand the options and select T (on the right) to Auto-Title the url.