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

Similar Messages

Alert on locked users in RFC Destinations

Hi,
I have setup availability of RFC Destinations but also need to monitor the user in the destination. We need to know if the user is locked or not. Any idea how I need to do this ?
Thanks,
Ann

Hi Ann,
the same can view in RZ20 ccms monitor templates-> availablity and performance overview ->availablity-> Rfc destinations.
to assign the rfc destinatiion define the method in RZ21->method definition->choose CCMS_RFCDest_Availability_Col(availability of RFC destinations)->set RFC destination to parameter RFC_DEST, if you want to define more rfcs can define as new colloum.
[Note 1069130 - RFC Destination Monitoring: |https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1069130]
check the posiblities.
Jansi

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

RFC Destination contains errors

Hello,
I am doing a IDOC - File scenario.
for XI :
RFC : R3RFC
Port : R3PORT
LS : XICLNT010
for R3 :
LS : CLNT090
RFC : XICLNT100
Port : XI100
When the IDOC was sent, its showing up in green color but when I go to SM58, I see the error message, " Transaction IDX1: Port SAPB999, client 800, RFC desestination contains erorrs "
But when I click on remote logon, the RFC is taking me to XI start sap access screen (same is the case with XI RFC connection, working as expected)
No messages were shown in SXMB_MONI
The port specified in the error message and the actual port varies.
Checked in port... specified a proper RFC destination.
Where are the things going wrong?
Checked previous answered posts related to the same and tried few things from them
dint work out..
Help !!!
thanks
Nikhil.

Hi,
Check the User you are providing in RFC Destination is Exist & have the Proper Authorizations
In XI Side RFC Dest::
Give the User name & PWD in RFC Destination , Which you are using for R/3.
In R/3 Side RFC Dest:::
Similarly Give the User name & PWD in RFC Destination , Which you are using for XI
Regards
Bopanna

RFC destination error in SM58

Hi,
We are getting an error in SM58 "P85040 does not exist".
What could be the reason for this error in PI system?
When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
Kindlly help.
Thanks,
John

Hi John,
The reason can be the host name you are assigning is not existing.
In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
Sachin
Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

Interface RFC destination Error

Hi, while testing our interfaces we get this error, Stack>Error: Transaction IDX1: Port HED_020, client , RFC destination contain errors
We have checked IDX1 and SM58/59 and cant find any error.
Has anybody come across this before?
Thanks

Where do you get this error? In MONI or in SM58?
Make sure that the User Id in the RFC destination has the authoizations to post Idoc's.
Make sure that the receiver Idoc adapter has a valid Port name and RFC destination values as created in IDX1 and SM59
Regards
Bhavesh

Steps to create rfc destination

hi,
what are the steps to create rfc destination

Follow the following steps :
1. Create RFC destination for both the systems on CRM and R/3 in SM59.
2. Create the logical systems and assign clients to logical system in SALE transaction both on CRM and R/3.
3. Create a user in the R/3 table CRMCONSUM with the name CRM.
4. Maintain the Middlware Parameter tables on CRM : Table SMOFPARSFA:
Create an entry for following parameter entry:
Key - R3A_COMMON
Para name - CRM_DEFAULT_DESTINATION
Value - R/3 logical system
5. Maintain the parameter tables on R/3 system : CRMRFCPAR, CRMPAROLTP
CRMRFCPAR :
Create new entry with following data:
User - CRM
Object name - *
RFC Destination - RFC destination for CRM
Load types - All Load Types
In Queue flag - X
Send XML No XML
CRMPAROLTP :
Create the following parameter entry:
Para name - CRM_DEFAULT_DESTINATION
User - CRM
Value - Name of the CRM logical system
6. Create Sites and attach subscriptions in Admin Console : Tcode SMOEAC
Create a Site as CRM and another as R/3. Attach the required subscriptions to the R/3 site.
7. Register the queues in SMQR and SMQS transactions.
PS : For detailed steps refer the Middlware Base Customizings(CR500 and CR100)
Regards.

What are the authorization requirements for an EDI communication user?

I'm trying to find documentation describing the authorization objects required for an EDI communication user to have appropriate RFC access.

Take a look in the FAQ thread at the top of the (security) forum...
Is there something in addition to the standard documentation which you would like to know?
Cheers,
Julius

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.

RFC Destination User Authority

Hi fellow XI-ers,
I have an Integration Server (A01) and a Business System running ECC 5.0 (B01). Now I am sending IDocs from the Integration Server to the Business System.
To do this I set up an RFC Destination B01CLNT010 and a port SAPB01 which is referenced by the Idoc Communication Channel.
My question now is: In the RFC Destination I need to specify a user id. What authority must that user id have to succeed with my Idocs.
I tried a user (on B01) with the roles SAP_XI_IS_SERV_USER and SAP_XI_APPL_SERV_USER but the sending of an Idoc failed (in SXMB_MONI it shows a red flag in the 'Outbound Status' - actually where can I follow up on this error?).
When I assign SAP_ALL profile to the user, it works fine. But I'm sure there must be something inbetween that is also sufficient for the purpose.
Your help is appreciated,
regards,
Peter

Hi Peter,
If IDocs fail while being sent from XI to SAP, there should be an entry in tRFC queue (transaction SM58). This entry should typically give an error like "missing auth. to send IDoc XXX".
This means, that the user is missing the authorizations to send this IDoc to R/3. The necessary auth. object is B_ALE_RECV which allows the reception of IDocs via RFC with the according message types you are going to send.
Additionally if your Inbound IDocs are configured for immediate processing the user sending the IDocs needs the according application authorizations e.g. for an Orders IDoc the user needs authorizations to post an order.
Best regards
Christine

Java communication error - RFC destination NOT_CONFIGURED does not exist

Hello,
We are facing problem when sending reports(BEx Quert) through broadcasting to the users. We are getting the error "Java communication error RFC destination NOT_CONFIGURED does not exist" in the Log Display (Tcode: RSRD_ADMIN).
In the broadcasting setting, if we select variable values in the tab "General Precalculation" then we can able to send the report to user, instead of selecting variable values, if we use the option "User Specific" check box in the tab Receipient(s) (which will take selection from the role authorizations defined in the respective user roles), then we are getting the above error.
Recently we have upgraded suppor package, please find the system details below
P_BASIS - SAPKB70025
PI_BASIS - SAPKIPYM12
SAP_BW - SAPKW70027
Java - Support Package 25
We didn't change any roles and authorizations recently, just upgraded to latest SP. Can anyone suggest if any steps or checks need to be perfomed after applying these SP or missing anything?
Thanks in advance
Regards,
Venkatesh

Hi,
This is configuration issue. Please check the configuration between BW and EP below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a?QuickLink=index&overridelayout=true
Thanks,
Venkat

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'

Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist

Hi Experts,
I have one standard ALV report in ABAP Webdynpro.
When i try to print the ALV Report it gives Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
Can you give solution for this one.
Regards,
Sri

Hi Sri
Please go through this..
/people/bv.pillai/blog/2007/01/09/webdynpro-abap-alv-print-versionpdf
also Have a look this note SAP NOTE 918236; you will need help from basis.
Cheers,
Kris.

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

Why do we need to define RFC destination and user for material replication

Dear Experts,
why do we need to define RFC destination and user for material replication? Here we use crm middleware only for material replication. Could you please help me to understand it?
regards,
Ranjan

Hello,
As far as I know, you can use the same RFC destination already available in ECC to SRM to replicate materials.
You can refer to note 720819.
Regards,
Ricardo

Communication User Is Enough In RFC Destination Userid-Parameter

Similar Messages

Maybe you are looking for