Skip to Content

Client Console Outbound Message queue

I am interested in using the Client Console to inspect messages that have been put in the outbound queue by a custom development enhancement in the sfa msa.

I have only found a summary total indication of outbound messages. This can be seen by starting the client console then going to Tools -> System Information or

by choosing the "Data Transfer" button on the left of the console application then selecting the Queue Manager.

My reason for wanting to look at the messages are because of a suspicion that the application from time to time is sending too much information to the server...which causes duplicate posting eventually in R/3...but that's a long sad story.

My Queue Manager tool with the binoculars does not seem to work...again I can see the total summary of outbound messages when I click the radio button...but no detail..even when I have more messages then zero.

I suspect this is suppose to work something like smq1 and smq2.

Any guidance or help is appreciated.

Also I understand that I could stop my inbound CRM queue for the site and inspect the data on the server...but for the moment I would really like to see the data on the client...I just don't trust the synchronization.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 22, 2005 at 02:33 AM

    Hi Brian,

    Client console will not show details for all the messages in the outbound queue due to technical design of the component. Also the Queue manager will not show the data in outbound queue.

    Hence please use the inbound queue on the server to debug.

    For more information you could mail me at

    kind regards

    Middleware developer.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 22, 2005 at 06:07 AM


    actually, the conntrans can´t do much wrong. It only picks up the data in the outbound queue, translates it to DCOMMs and sends these to the communication station which translates them to RFC´s. If you have communication errors they are either located on the site (which you can find out by stopping the inbound queue and checking the inbound sbdocs) or in the middleware (which you can find out by debugging the flow from the inbound queue on).



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 11, 2005 at 07:51 PM

    An idea a colleague provided to consider:

    to enable some traces files on the tablet to see how many outbound messages get generated after any scenario. You can also check it up on your tablet. Following are the instructions to do:

    1)Go to the following path in registry HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\MW\TL

    2)There should be a string entry TL_SOAP. If it doesn't already exist, please create it and give the value as 3

    3)In Mobile application, complete one scenario, for example, acknowledging a Shipment/Transfer In

    4)Next go to Start -> Run and type %Temp%. The temp directory is opened. In this directory, sort files by descending order of Date and you will see some xml files generated for the latest transaction done on Mobile. For a Shipment/Transfer In acknowledgement scenario, you will see one xml with the name SAP_DOCUMENTATION....xml (this corresponds to the update to the line item table SMOCONDOCU) and 2 xmls of type SAP_ACTIVITY_OBJECT....xml (This corresponds to the update to the activity table SMOVBKA). This proves the duplicate messages being sent from mobile.

    5)If you open the xml and scroll right to the bottom, you can see a Task field. This field indicates what kind of message has been created. The values are 2 for Insert, 3 for Delete and 1 for Update

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.