Skip to Content
author's profile photo Former Member
Former Member

BD87 hide "idoc entries in tRFC queue" by assigning to status or other meth

Hi,

I am working on the inbound side of an idoc interface for message type MATMAS. My problem is that when I enter in BD87 there are more than 400 hundred entries in "idoc entries in tRFC queue". Now, whatever filter I put on the first screen this line appears. Even, if I enter with a specific idoc number. These entries are obviously outbound errors and are completely irrelevant to the interface I am working on but will make the reprocessing screen unnecessarily complicated for the users. So, basically I want to allow the end user to filter out these messages.

I noticed that the errors "idoc entries in tRFC queue" aren't associated to a status and I was wondering if it is possible to give them a status value and so make them sensitive to a status filter. But if this isn't possible any solution to hide these error messages from the end user would be equally valid.

I know someone will probably suggest that the best solution would be to remove all old entries from tRFC queue in SM58 and that there shouldn't be so many idoc in entries in the tRFC queue. The problem is that it is not my role to monitor tRFC in production and if it has not been regularly monitored up to now then it probably won't be in the future.

Many thanks in advance,

Jamie.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Oct 06, 2009 at 06:18 AM

    Hi Jamie,

    To the best of my knowledge the shown outbound RFC entries in BD87 are a feature that cannot be suppressed. I.e. in the coding of BD87 one can see logic where it automatically checks for outbound RFC errors and adds those to the output.

    In general IDoc status 03 should be associated with the outbound RFC errors. Yet, when one sees those in BD87, the IDoc status field is empty. Along your train of thought I had also previously tried to suppress those displayed IDocs by adding a filter for suppressing status 03 or blank status, but nothing helps. And as you correctly point out, even when using BD87 on a single IDoc (e.g. specified via IDoc number), the transaction will still display the outbound RFC errors.

    So unless somebody else has some good idea or insight, I'm afraid you're stuck with that behavior.

    Cheers, harald

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hey Gordon,

      It´s not a bug ... it´s a feature 😉

      That's also what I thought. 😊

      I'm curious to know though, which tools you'd use for IDoc monitoring in SAP 4.6c (or ECC, only sure up to 5.0 though) as I don't think there's that many out there - especially when it comes to having an overview list including status messages (even without reprocessing). The only other tool I know is workflow, but that is also not ideal (especially when you start having lots of failed IDocs).

      Best wishes, harald

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.