cancel
Showing results for 
Search instead for 
Did you mean: 

SMSY creates RFC user as "Communication" user type

Former Member
0 Kudos

Transaction SMSY was used to create RFC destinations to all satellite systems. In the SMSY wizard, it was requested that the RFC be created as well. After both RFC user and destination were created, it was perceived that the RFC user is of type "Communication".

According to SAP Note 622464, "Communication" user will require the user to modify the password after it has expired. Therefore, I ask:

1. Why does SMSY creates RFC user of type "Communication" instead of "System"?

2. Is there any harm if the RFC user is updated from "Communication" to "System"?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

'Communication' users are used to 'communicate' ! So they require dialog login (like here in these RFCs) and which they can do and for what they are defined i.e. to login or to make communcation possible via RFCs

'System' users are used to handle the background tasks which do not require dialog login across SAP systems or via RFCs. In other words, system user is not a dialog user and hence can't act as a user in RFCs to communicate acrosss SAP systems !

Hence,

1. SMSY creates 'communcation users'

2. if the RFC user is updated as the system user, then no 'dialog login' and hence 'no communication'