RFC Analyzer

Consistency analysis and cleanup of existing SAP RFC destinations over the entire system landscape

Big Picture

With the evolution of SAP systems, more and more connections between systems have been created. The general overview of connections from a centralized platform makes it possible to verify and validate all these configurations in a simplified way.

If a client of a SAP system  is deleted, an administrator could easily see which RFC destination should be deleted on which system(s).

In the event of a network change, it would be easy to know beforehand how many and where the directors should act.

It is easy to maintain all these RFC destinations without needing to log on to each of the systems.

The SUIM’s RFC Analyzer provides a simple way to meet your needs. It also allows to verify and automatically validate the naming convention/description of the RFCs, creators, modifiers, so see the use of the latter, and much more..

Features

Inventory of all RFCs

Direct inventory of all RFC per target system, server, used user, …

Comparison of DN or IP addresses of a system

Comparison of each configured DN or IP addresses in the RFC destination for the same SAP system. It allows you rapidly to update the RFCs in case of a DN change

User existance (automatic)

Checks the existence of the user stored in the RFC destination on the target system

Password check (automatic)

Checks the validity of the password for the user stored in the RFC destination without blocking the user in case of a wrong password

Verify the autorisations (manually)

Verify and/or modify the autorisations of the user stored in the RFC destination on the target system

Validation of several RFC attributes

The Administrator is able to validate some attributes of the RFC destination in case of naming conventions or modifiers outside of a pre-defined pool of users. In case of forbidden sets, the corresponding attribute will be marked in red.

Validation of the creator of the RFC destination

If the creator is not part of the pre-defined set of allowed users for the creation of the RFC destination, the Validator must validate this entry, or react on the entry.

Validation of the last modifier of the RFC destination

If the last modificator of the RFC destination is not part of the pre-defined set of allowed users for the creation of the RFC destination, the Validator must validate this entry, or react on the entry.

Validation of the name of the RFC destination

A user exit can be implemented for checking if the RFC destination name corresponds to the defined naming convention. If it is not the case, an administrator must validate the entry, or react on the RFC destination.

Validation of the short text of the RFC destination

A user exit can be implemented for checking if the short text of the RFC destination corresponds to the defined naming convention. If it is not the case, an administrator  must validate the entry, or react on the RFC destination.

Action log for the validations

Each validation is saved. A reporting exist to display and analyze these logs for audit purposes

Last date of usage of the RFC (*)

The last date of usage as well as the detailed usage of the RFC destination is made available. This feature is only present with at least a valid license of one module of the AIM solution.

Executed functions and transactions using the RFC destination

A report displays the executer, the executed transaction and each used RFC function during the RFC connection.