Which RFC destination is missing?

On MEREP_SBUILDER, I try to do a "BAPI Wrapper interface checks" for a SyncBO.
I get the error: RFC communication failure: Error when opening an RFC connection".
I look into SM59 and see a lot of RFC (type=3) defined.
So which is missing?
Thanks!

Hi Jennifer,
go to MEREP_PD and open the last tab (SYNCHRONIZER). The table shows you all SyncBOs in the systen and its stae. Well, the RFC is written down there for each SyncBO in column RFC DESTINATION. And this is the one that you need to check. So open SM59 -> ABAP Connectors and you should find the one that was mentioned in MEREP_PD. Open it and do a Connection Test as well as a remote logon.
But: you can ask the BASIS people in your company to suppor tyou there as well - if you tell them the name of the RFC, they are able to find out if it is really a problem there and how to fix it.
Hope that helps!
Regards,
Oliver

Similar Messages

How to find out, which RFC-Destinations are in use?

Hi community
We have a huge list of RFC-Destinations in our productive system and I want to delete unneeded entries.
Is there a report or a log, which shows, which RFC-Destinations were used, and when?
Thanks in advance.
Regards, Michael

HI
can you see the default trace in tcode SMGW, Be careful about deleting any system rfc.
Read the documentation about default RFC, internal RFC, LDAP_RFC, transport RFC.
I don't know other way to do that you need
Regards
William Neira

Which rfc destination i has to use

hi
i m trying to connect internal network ftp server by using
<b>ftp_connect</b> functional module for that which RFC destination i has to use
thanks in advanced.

your basis person is the right guy to give you the RFC destination

Logs of used rfc destinations

Hi Guys,
i'm looking for some tables including log-information of used rfc destinations. For now i have table EDIDC for IDoc-Logs. Do you know more tables, e.g. regarding BAPI usage? RFC logs in general (here i found ARFCSSTATE/ARFCRSTATE and some others, but they don't look as they would log all records, do they?
i just want to find out which rfc destinations are used and which not!
Best Regards
Stefan

Hi Stefan,
Generally we will RFC logs from SM58.
(Or) Check tcode SLG1 for application Log.
Thanks,
Krishna.

Error CL_TAO_GUI_SESSION_SM- Create: Mandatory Attribute missing for Technical RFC destination

hai
We have installed solution manager and CBTA for test automation. For SUT , We have created Technical RFC for development client and quality client
as TST_BID_CLNT220 and TST_BID_CLNT_909 respectively. Similarly SMBID_CLNT_220 and SMBIQ_CLNT_909 are the business RFC destination to connect SUT.
Now I have created test System data container which have both target system (Quality and development) . I have also created Test profile
for both . In the Test Profile I have mentioned Techinical RFC name , Test profile name, business user and password.
I have record va01 tcode in development client. The same script is used for quality also .
I am able to execute the script in development . But when I execute for quality it is giving following error
Error CL_TAO_GUI_SESSION_SM->Create: Mandatory Attribute missing for Technical RFC destination TST_BIQ_CLNT909
Can any one help me . Pls tell me whether I followed the steps correctly
Regards
Jaya

Hi,
It will be very difficult to solve without being on the customer site and having all information.
Right now, the error code is network error...
Kind regards,
Yann

PI System Copy (JCO RFC destinations missing)

Hi,
We are doing a Homogeneous System Copy of a PI 7.0 system:
- Source system --> PI 7.0 Production system ("PIP")
- Destination system --> PI 7.0 Development system ("PID")
We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
Production system ("AI_RUNTIME_PIP"), is it OK?
Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
Thanks in advance.
Jon Larrucea

Hi Jon
Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
Creating RFC Destinations in the ABAP and Java Environments
http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards
Mark

RFC destination for Sender System in R/3 4.6c

Hi All,
I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?

Hi Arul,
One more important point u have missed.
Program ID,
When ur configuring sender service from RFC,The most important point is Program ID.
Use some name and create it.Use the same name in SM59.
s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
Reghards
chandra shekar

Transaction IDX1: Port SAPPRD, client , RFC destination contain errors

Hi all,
when I send an IDOC from Xi to R/3 I get the following message in XI monitoring:
Transaction IDX1: Port SAPPRD, client , RFC destination contain errors
ERROR= 2:IDOC_ADAPTER(151)
However everything is maintained correctly (i think) in IDX1. I can upload the IDOC metadata with IDX2 from the R/3 system.
I seems that Xi doesn't have the clientnumber available. (should be 600) but is not mentioned in the error.
Did I miss something?
Thanx Ron
Message was edited by: Ron van der Sterren

Hi Ron,
Settings in XI side.
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is R/3 server name and logon tab enter the R/3 logon details.
Test the connection is success and check the Remote login button it's connecting the R/3 system or not.
2. Create the Port IDX1 and pass the client number is (R/3 client) and pass the RFC destination which you created above.
R/3 side
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is XI server name and logon tab enter the XI logon details.
Test the connection is success and check the Remote login button it's connecting the XI system or not.
2. Create the TRFC port to transfer the IDOC'S and pass the RFC destination which you created above.
3. create the logical system in BD54 this name should be same as XI logical system name.
4. Create the partner profile (WE20) and partner type is 'LS' with inbound parameters and pas the appropriate values.
Let me know if you have any issues.
Regards,
venu.

Error in SWF_XI_CUSTOMIZING - Configure RFC Destination

Dear Experts,
Basis team is performing PI 7.1(EHP1 - SP04) readiness check. We are not able to activate Configure RFC Destination. Please refer the following attachment.
We have checked if WF-BATCH user got locked. It is fine and in unlocked status. Is there any setting which are missing? Thanks in Advance.
[http://www.flickr.com/photos/49754947@N07/4657473257/]
Thanks,
Phani Akella.

Hi Phani,
Create a RFC connection of type R/3 in the transaction SM59.
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/frameset.htm
Or you may go to:
Tcode SM59 -> R/3 connections -> Create
1) Give RFC destination name.
2) Connection type - 3.
3) Technical settings tab -> Target Host -> give the Application Server name -> press enter.
The IP address automatically gets filled up.
4) Logon security tab -> Assign the Logon details.
Also, on the button of the image you posted there is a:
"No Language Can Be Defined for the RFC Destination"
Check for that too.
Regards,
Caio Cagnani

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

No RFC destination is defined for SAP Global Trade Services

Hi Team,
I am getting error No RFC destination is defined for SAP Global Trade Services while transferring master data from one ECC Client to GTS.
Both clients has built in GTS. The situation is like this.... Client A which has ECC & GTS and Client B also has ECC and GTS. Client B we are intended
to use only for GTS. This is basically for proto type purpose we need to establish connectivity between A and B. B we intended to use as a feeder system
1) All the three BADI'sin SD0A,SD0B and SD0C level activated
SLL_PI_SD0A_TRANSFER
SLL_PI_SD0B_TRANSFER
SLL_PI_SD0C_TRANSFER
2) /SAPSLL/RFC_DEST Badi also active
I asked BASIS people to check in SM59 Client A is connected with Client B (here Client B as RFC destination) even connection test / remote logon also
tested and it is working between A an B
Where i am missing
Regards,
Ramji

Hi Dave,
Thanks for your reply.Sorry i forgot to include in my points already done.
BD97
BD64
Just to clarify one more point
sender should be EH6CLNT800 (ECC)
Receipient should be EICCLNT800 (GTS). Is it correct
Regards,
Ramji

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

Error in Creating RFC Destination

Hi,
I am Going for RFC to File Scenario.
For Sender RFC it < I am trying to create RFC Destination in SAP r/3
I have Given
RFC Dest : XI_CONNID
Conn type : Tcp/IP
Activation Type : Register Server Program
Program ID :sap
gateway host : sap-server( Sap server)
gateway service : sapgw00.
I saved and I tested but it is showing errors.
Error : Error in Opening RFC Connection
Whe i Click on this error message it i showing
Error Program sap not registered.
Points will be awarded.
regards,
Jayasimha

Dear Jaya,
create a RFC SENDER communication channel first and then activate the channel.
now go to sm59 there use the same program-id as u did at RFC SENDER COMMUNICATION CHANNEL.
note:program-id is registered by XI at R/3 level with details related to it's profile(XI profile).
step 1) create RFC COMMUNICATION CHANNEL with program-id as "any name" at XI first .
2)create TCP/IP connection with registered program-id created by XI at first step
so when you execute steps 2 then 1 you will get error ,coz by that time program-id is not yet registere by XI in R/3 domain.
after executing step 1 i.e creating porgram id at R/3 through XI.
got to ST22 at R/3 and check whether any dump is found against "XI creating porgram-id at R/3 level".
we failed at creating PROGRAM-ID itself at R/3 level because of missing authorizations against my R/3 user id,which we will be using at XI RFC channel.
generally problem will be at PROGRAM-ID creation itself,so just go to ST22 and check any authorizations missing for your userid which is being used at RFC channel configuring at XI.
Thanks & Regards,
Rama Krishna

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Which RFC destination is missing?

Similar Messages

Maybe you are looking for