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

[Former Member]

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.

[Former Member]

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

[Former Member]

Thanks a lot it good to know when something can't be done. I'll leave the thread open in case anyone out there knows an intresting trick for this but I guess you're right and it can't be done.

[Former Member]

Jamie,

which version you are using, right now ?

We are at: SAP ECC 6.0

SAP BASIS 700.

TRFQ Entries "are not shown" in BD87.

[Former Member]

What about using AUTHORITY-CHECK OBJECT 'S_ADMI_FCD'.

Objekt: S_ADMI_FCD

This one is checking the TRFC Queue Authority.

Maybe you can setup a userrole for the BD87 User.

[Former Member]

I'm in R3 4.6C. I tried the authorisation object you suggested. The tRFC are still displayed on the intial screen of BD87 the diffrence is that without this authorisation object you can get into sm58 by pressing the button display tRFC.

[Former Member]

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

why do you using bd87 ? cause of processing idocs ?

in case of monitoring without processing, you have a lot of tools to do that instead of using BD87

[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