Enhancement for Monitoring RFC

[Former Member]

Hi,

Due to limited system resources, our audit logs are regularly purged, and reading audit logs is slow. Considering this background, I would like to save all RFC called records to a custom table, regardless of whether the RFC is called directly by an external system or through SAP PI.

Is there an enhancement point available for this purpose without inserting monitoring code in each RFC function?

Best Regards

[jmodaal · Accepted solution]

Hello,

are you aware of the RFC statistics data in ST03? If the information available there is sufficient to your needs, you can have a look at transaction /SDF/ST03DL for downloading the data (see SAP note 2943445). Another approach would be using function module SAPWL_WORKLOAD_GET_STATISTIC in an own developed ABAP and store the received data in an own table.

Kind regards

Jan

[Former Member · Accepted solution]

Hello Jan,

Thank you for your suggestion, it is indeed a good approach. I have examined the RFC profile content for transaction code ST03, and it does contain records of RFC calls made directly by external systems.

However, there are some limitations, such as the absence of records for RFCs developed on the same day and for RFC calls made by SAP PI (Process Integration) services.

If overlook these limitations, calling this function module will be indeed a good method.

Reference:

https://blogs.sap.com/2007/04/08/statistical-records-part-4-how-to-read-st03n-datasets-from-db-in-nw...

[turkaj]

Hi Kai,

I was also looking for a similar solution and could not find a central place to trace all RFC calls.

The ARFCRSTATE (State of the ARFC calls on the receiver side) table helped me.

I found it in this article: Transactional RFC and Queued RFC Monitor

Regards
Jim

[Former Member]

Hello,

Thank you for your sharing. After checking and verifying, the volume of data in this table is very low, and the content is not what we need.

Regards