SMSY creates RFC user as "Communication" user type

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"?

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'

Similar Messages

SAPJSF user System user or communications user ??

Hi Experts
I have a doubt regarding user type of SAPJSF user .
Link 1 says SAPJSF user should be of type "System".
http://help.sap.com/saphelp_nw70/helpdata/en/49/bf6e8101755d5de10000000a421937/frameset.htm
Link 2 says SAPJSF user should be of type "Communication"
http://help.sap.com/saphelp_nw04/helpdata/EN/d4/abdc3ed98f7650e10000000a114084/frameset.htm
Only difference i found between two from portal perspective is
System User : password does not expire.
Communication user : password can expire according to security policy.
Kindly let me know which link should i follow ??

I got the answer .
In nw2004 ,
SAPJSF as Communication user.
http://help.sap.com/saphelp_nw04/helpdata/EN/8f/67d27676ace84080964d4c4223bb3c/frameset.htm
In Netweaver 7.0
SAPJSF as System user.
http://help.sap.com/saphelp_nw70/helpdata/en/8f/67d27676ace84080964d4c4223bb3c/frameset.htm.
Thanks
Purav

How to trace communication users in system & build a role

Hi all
I have a requirement in my compnay to create a role for communication users currently assigned to SAP_ALL
we have 20 communication id's & turning on trace is not feasible option due to the impact on system performance.
Plz let me know what is the approach i need to have inorder to find neccessary tcodes & objects into my role.
thank you in advance.
Best Regards
NaveenMurthy_

What I meant is that good "housekeeping" and securing of these sensitive RFC connections is hard to do properly if you are "far away" from them.
Go figure why SAP delivers many of their connection wizards with SAP_ALL... they don't know either what the customer will be using and which data will be transfered and when you might need to temporarily debug the connection or when someone will try to use an existing connection for a new application without thinking about developing a new role to go with it, or which checks an SP might introduce which then pop up as a problem in a remote program or system, etc.
Really, it is not an easy thing to do properly (both technically and procedurally) and the further you are away from it, the more hassle it will be.
No inflamatory hype intended toward any specific type or location of "offshoring".
Cheers,
Julius

Creation of Communication users in CUP

Hi,
Is it possible somehow to manage the creation of a non dialog user (i-e: communication) using CUP after the relevant request has been ended and approved?
Thanks in advance. Best regards,
Imanol

Imanol,
here's what you need to do:
Create a custom field "User Type" with the following values:
A - Dialog User
B - System User
C - Communication User
L - Reference User
S - Service User
(or at least the ones you need...)
Make "Dialog User" the default.
Then create a mapping in Field Mapping - Provisioning where you map this to the R/3 field "User Type" for the systems that you want to create non-Dialog users in.
Hope that helps,
Frank.

Difference between service and communication user

Hi,
We ran into a big problem in our CRM system getting millions of Dynpro_Send_in_background dumps while processing inbound queues R3AD* from R/3 system to CRM. Lots of Updates getting failed with CRM_SCHEDLIN_UPDATE_DU function module while executing report LCRM_SCHEDLIN_DUU01.
Error Details - CRM_ORDER_MISC 002: Error in updating object SCHEDLIN
We posted to SAP as well but did not find root cause. SAP saying we need to change RFC user "S_ECC_PR0400" from Service user to Communication user, that would stop the dump problem.
I want to know what is the unique difference between these users(Service & Comm) which will resolve the dump problem though I know the common difference between these users.
Thanks
Anju

Hi Anju ,
Communication 'C' User :
Use the user type Communikation for dialog-free communication between systems (for RFC or CPIC service users of different applications, for example, ALE, Workflow, TMS ZBV).
Dialog logon is not possible.
Service 'S' User :
A user of type Service is a dialog user available to a large anonymous set of users. It usually has closely-restricted authorizations.
Service users are e.g. used for anonymous system access via an ITS service. You can change a session which began as an anonymous session with a service user into a personal session under a dialog user with an individual authentification.
There is no check for obsolete/initial passwords at logon. Only the user administrator can change the password.
Multiple logon is allowed.
Hope this may help you.
Thanks
Gyan

Create RFC destination

HI,
I want to build RFC destination between 2 ABAP system ,
i need step by step solution ?
Regards

Hi,
1)Log on to ABAP system.
2) Goto T-code SM59.(For Creating RFc destination)
3)Different connection types will appear select for ABAP CONNECTION
4)Click on Create button from top.
5)Give the name of RFC destination------ex:ZR/3TOBW
6)Connection type -
3
7)Short Description
8)Click on Technical Settings Tab and maintain the Host name and system number of another ABAP System.
9)Click on Logon&Security Tab Provide the log on Credentials of another ABAP system
10)click on save.
11)Click on Connection Test Button.
12)Click on Remote logon.
after that you will be connecting to the another ABAP system Remotely.(If and only if the Technical Settings which you provide are correct We can connect to other ABAP system)
If any error occur's please check your Technical settings and also Logon&Secirity which you provide.
Thanks.

Use of communication user in RFC of HCM process types

Dear All,
I have created an HCM-PA package, and when used a communication user in the RFC it gives me the error that no data exists for your user in the Transfer selection criteria activity (This is not an issue with defining target areas I have confirmed)
I then used my ID ( a dialog user) and it works well. However, now I want other users (about 10) to be able to run their respective packages. Does that mean I have to add each of these 10 users to the RFC? How can I resolve this without having to use their ID in the RFC maintenance?
Thanks
Harmeet

Hi Harmeet,
the easiest thing to do is to define a CPIC user in your receiver system destination and then to use the customising activity "Set technical switches". Here you can set a switch called SND_LOGON to the value 'X'. When you do this, the person who calls the transfer program with the activity "Transfer Selection Criteria" must explicitly log on using their own sender system user.
This method means that the user must have the correct HCM authorisations and prevents that a dialogue user is defined in the RFC definition (which, of course, anybody could use).
Hope this helps.
Gerard.

Communication User Is Enough In RFC Destination Userid-Parameter

Hi Guys,
   I Have The Rquirement Like,i have to call the remote function module which is in quality server from the development system,so for that i have created rfc destination in development system in the logon&security,i have given the userid,which was created by the basis team,this user is a communication user,not a dialog user,with this communication user, iam unable to connect to the system through program
         call function fm1 destination des.
i would like to know whther we can conncet to the system through the communication user,or dialog user is must.please give ur valuble suggestion on this query..
                         thanks in advance...
thanks&regards
   srinivasulu.j

Hi Ranganath,
    Thanks For u r valuble suggestion,with the communication user given in rfc destination ,the connection is not establishing,when i click on test connection button in sm59,it is not showing any error,but when iam trying to execute form the program by calling the remote function module by giving the rfc destination,i checked in debugging,it is not connecting to the other sytem,pls provide some solution for this..
thanks&regards
srinivasulu.j

BPC 7.5 NW- error 'Name or password of RFC Communication user is invalid '

Hi
Environmen: Win 2008 R2, CPMBPC 7.5 SP09, BW 7.2 Sp09, .NET BPC 7.5 SP09
I just completed installing .NET BPC 7.5 and when I try to open BPC Server manager, i get "cannot coonect to ABAP server' error.
When I try to open the website http://localhost/osoft I get the error "name or password of RFC communication user is invalid".
I see the same error in the BPC logs as well.
I have the tried the following so far:
1. Created single domain user for the three communication users BPC_sysadmin, BPC_admin & BPC_user.
2. I momentarily changed to dialog users and logged in to check their fucntioning.
3. I have generated their relevant profiles. Inlcuded SAP_ALL, SAP_NEW for the sysadmin ID
4. I have disabled firewall, allowed port 80 on Windows firewall.
5. I have disabled UAT
6. I have followed the rest of the installation as per inst guide.
When I run BPC server manager diagnostics, I see error "SAP ABAP server connection:database connection:status error".
Can someone tell is there anything else that I could try ?
many thanks
Sreekanth

Hi,
If when you launch BPC Server Manager, you do not get "Cannot connect to ABAP server", this means user BPC_SYSADMIN is connecting correctly. And assuming you had invalid RFC user in BPC Web, your issue is then only with user BPC_USER (or BPC_ADMIN if the issue is with BPC Admin client only)
If you do get that error, it means the error is for more than one user, so I would look for something big missing.
In point 1 you mention domain users, make sure in BPC Server Manager under "reset login credentials" that you do not have windows users specified there as it's a common mistake, those should be your 3 BW communication users
On BPC .Net server, if you installed SAP GUI, run an MDX_PARSER test in SM59 to check librfc32.dll is working correctly
Also quite common issue it is possible your background users have wrong authorizations; in PFCG check the roles SAP_BPC_SYSADMIN SAP_BPC_ADMIN and SAP_BPC_USER were copied to customer namespace and that the role are active (user tab should be displaying green light) and assigned to the background communication users
Also check the background users are not locked in SU01 (if they are locked the password saved on .Net server was or is not matching the real password defined on NW server)
Thanks,
Julien

RFC function module always creating BPs with the same user name (RFC user )

Hi All
I posted the below question in a different area before. But thought it would be more suitable here.
Moderators - Please let me know if am doing any mistake.
Question:
I have a RFC function module in CRM that creates Business Partners in ECC (XD01 tcode).
I am using a dialog RFC destination configured in SM59 in CRM.
But my RFC function module in CRM is always creating the Business Partners in ECC with the RFC user id (the user that we maintain for the RFC destination in SM59).
This is a problem for the users because they are not able to track the actual person responsible for creating these Business Partners.
Can somebody please let me know how to solve this problem?
Thanks
Raj

Hi.
You may use the trust relationship between CRM and R/3 and in SM59 instead of set a specific username, you set the flag "current user".
With this flag, the system will access R/3 system with the user logged in CRM system. The Trust relationship must be created between CRM and R/3 in order to the system doesn't ask for a password to login in R/3.
If you need more details please reply.
Kind regards,
Susana Messias

Creating Communication users in CUP (II)

Hi again,
Following the previous post Creation of Communication users in CUP I would like to post a further question:
When requesting provisioning for a user in a target SAP System and having LDAP set as user data source, user ID is search by using the "magnifying glass".
Question 1) What if we are creating a user ID for a communication user that does not exist in LDAP?
Thanks in advance. Best regards,
Imanol

Frank,
You never loose
Clear first option. What about the second one? What do you mean by sending the request through the web service? Could you provide me more details about that?
Many thanks in advance. Regards,
Imanol
By the way, sorry for beaten Germany in Semifinals Spain is crazy these days.after winning the first football world cup.

When I try to sign in to the support community using one of my email addresses it asks for my apple support community user name and when I type in what I think it might be I get one of several messeges Ie. An account using this e-mail address already exis

When I try to sign in to the support community using one of my e-mail addresses and I put in nothing or what I thought was my apple support community user name I can get one of several messages
Ie.1. Please specify a user name
2.An account using this e-mail address already exists; only one account per e-mail address is allowed on Apple Support Communities
How do I find out what my Apple Support Communities user name is

Good luck with this!!!
EVEN USING what WAS my Username, this is the exact problem I am having having entered my correct ID and Password.
Rgds
Rod

Difference between RFC, SYSTEM and AUDIT users?

Hi All,
Can you highlight the main differences between the following users:
RFC
SYSTEM
AUDIT
how do their functions differenciate them ?
Thanks in advance,
Diwakar

RFC User
RFC user is basicly used to receive status messages. An RFC user has to be created in all the system clients where messages needs to be recieved. An RFC user can also be used for receiving messages using SMTP plug-in.
The RFC User is an sap user of type System and that's why no person can logon with this user on SAP System.
Following is thr procedure to create RFC User, remember the purpose is to recieve messages including status messages as well.
Creation of RFC User
Go to Tools > Administration > User Maintenance > Users.
Enter a name, for example MAIL_ADMIN.
Select "New"
On the Logon data tab page, select the user type System.
Enter a password.
On the Profiles tab page, enter the authorization profile S_A.SCON. This profile minimizes the risk of misuse, even if the communication system does not store the password is encoded form.
Select "Save"
Both RFC user and a System user are of type System only. Now the difference, depends upon the profile and authorization of the user.
Audit users are of type dialog, and can be used by a person to logon to system. There might be many roles assigned to this user. My understanding is that an Audit User is not a standard sap type user but just a dialog user and can be created with a conventional method of creating any other dialog users with a specific profile and authorizations.
Still to confirm, Can you please tell us, how many types of users does it shown in 4.6c at the time of user creation?
Best Regards,
Amol Bharti

Is Communication user recommended to access Webdynpro ABAP?

Hi,
I don´t know if somebody knows if we can recomend the client to use a communication user type for accesing Webdynpros for ABAP, can this cause some licence problems? or communication users can be used by final users without a problem?
Hope somebody can help!
Thanx in advanced!
kind regards,
Gerardo J

Hi Gerardo,
main difference between dialog and communication user is the access via SAPgui. The license still depends on the role of the user not the user type.
Property \ User Type            Dialog Communication   System Service
Dialog logon (SAP GUI)          X       -               -       X
Multiple logons                 -       X               X       X
RFC logon                       X       X               X       X
Background job execution        X       -               X       X
Password change                 X       X               -       -
Logon ticket can be generated   X       X               -       -
Probably you mean "named user" and "anonymous user". For this Q you always have to ask your SAP sales person (because it depends...)
Hope this helps a little bit.
Best regards, Uwe

Communication User Locked..

Hi All,
Can you plz provide the information for this problem.
How does a communication user gets locked & what could be the root cause for that problem?
Thanks & Regards
Srinivas K

Hi Srinivas,
Reasons for this:
1) Somebody has changed the password of the communication id
2) An RFC defined to refer that client has an incorrect password in SM59 for that Comm. id.
>
Srinivas K wrote:
> a) If the password for the communication user has been expired, then do we need to reset it by using SU01?
>
Passwords for Communication users do not expire. Yes, SU01 is the way by which you change passwords, even for communication users. As mentioned earlier, its a bad idea changing the password of a Comm. user, as all other RFC's referencing to that client will have to be updated with the correct credentials.
> b)"Communication users details not changed in all RFC communication configuration"---> I couldnt understand this, so could u plz provide some more information regarding this.
>
> Can we get information in ST05, with related to this problem?
Debug the issue more. Look at the change documents of the Comm. user. See if anyone has changed the password. If not, then there might be a possiblity that some RFC referencing to that client has the incorrect details. ST05 is not what you are looking for. Look at SM20N (AIS) for the details.
Do not change Comm. users to Service type! Comm. users normally have broad authorization, making it a service id is a heavy risk as SAP GUI access will be opened up!
You might want to post/move this to the security forum
Thank you
Abhishek

SMSY creates RFC user as "Communication" user type

Similar Messages

Maybe you are looking for