RFC destination types

When do we use RFC destination Type T versus Type 3?
While creating RFC destination Type T, the program ID, blogs says we should use "Registered server program" and can give any free text. I tried that but says there is no registered server program called XXX on system. So, i'm really confused here.
my understanding is for IDOCs you need Type 3, and for RFC you need Type T. Is that true or we can use any type with these?
Thanks,
Anika

Hi Anika,
i think this links could be useful:
http://help.sap.com/saphelp_47x200/helpdata/en/22/04262b488911d189490000e829fbbd/frameset.htm
Differences in the RFC destination types
You're right, for Idoc you have to use type 3 and for RFC you have to select a type T destination entering a program ID.
Let's make an example.
Suppose you have defined an RFC destination RFC_X with program id PID_X on ECC.
On XI you have created an RFC sender adapter and you have specified ECC as the sender and PID_X as the program ID.
When from ECC an RFC is called using destination RFC_X then the sapgateway looks for a receiver registered with the program id PID_X, it finds your RFC adapter and sends the call to XI.
Hope it helps.
Kind Regards,
Sergio

Similar Messages

RFC Destination Type G too fast

Hi All,
I have an RFC Destination (Type G) that is pointing to another XI system. We use that to send messages directly from XI to XI. However, when there is heavy load,we get a lot of failures in the source XI System. Messages go eventually after many retry attempts.
Is there any way that i can slow this down, so that the messages queue up in the Source system and flow slowly towards the target. We can do this in a Type 3 RFC destination by reducing the number of connections in Transaction SMQS. Any such options for Type G?
Thanks,
Varun

Hi Liang,
Thanks for your response.
We are using the XI adapter. Also, to clarify, this is a connection between 2 separate XI Systems.
Thanks,
Varun

RFC Destination type for IDOC to FILE

Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeff

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

RFC Destination type RFC Receiver Adapter?

Hi,
What is the RFC destination type for Sender RFC Adapter?
and what is the need a Program ID for sender Adpter.
What is the RFC destination type for Receiver RFC Adapter?
Regards
Gopi

When we use the RFC Adapter?
SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter).
You require the sender adapter if you want to use the Integration Engine to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine to arrive in RFC format. In this case, the Integration Engine must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
The following three scenarios are possible when using the RFC adapter and the Integration Engine:
    1) SAP R/3 to SAP NetWeaver Application Server
    2) SAP NetWeaver Application Server to SAP R/3
    3) SAP R/3 to SAP R/3
When we use ABAP Proxy ?
SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.
To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.
Please Reward the points if it's helpful...
Regards,
Ramana.

Rfc Destination problem in RFC Sender Adapter

Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
   i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

HTTP with RFC destination problem

Hi,
We're doing an SAP R/3 --> XI --> External System scenario. We've had no problems making the SAP R/3 to XI work. For XI to External System, we're using the Plain HTTP adapter with an RFC destination. The Server, Intermediate and Root CA of the External System have been already installed on the ABAP layer of XI using the transaction STRUST/STRUSTSSO2 . The Server Certificate and Root CA of XI have also been installed on the External System Server. The problem is that everytime we test the RFC destination, we are still getting an ICM_HTTP_SSL_ERROR
Additional Parameters:
SSL has been enabled on the RFC destination
All three certificates can be found in STRUST
Regards

HI
is the certificate same for both of you have installed external system certificate and external system have PI certificate
Check SAP note 510007
Check similar threads
ICM_HTTP_SSL_ERROR
ICM_HTTP_SSL_ERROR for plain HTTPS with RFC Destination type G
Thanks
Gaurav

Prob with RFC destination - 4.5B 2 XI ABAP

Hi,
I created an RFC destination type 3(R/3 connection) in 4.5B, to address Integration Server.
It gives the following error.
<b>Connection error : Conversation 09163404 not found / CPI-C error CM_PARAMETER_ERROR</b>
Can any one guide me on this.
-Naveen.

Hi,
Please check on 'Authorisation to Read Metadata'at the end
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
Regards
Vijaya

Error: Illegal destination type 'H'

Hello All,
We've maintained an RFC destination type 'H' for the ALE connection from the HR system to FI. When running tcode PC00_M99_CIPE the following error is received:
System error during RFC call BAPI_FIXACCOUNT_GETLIST: Illegal destination type 'H'
Any ideas?

Hi,
The /sap/bc/soaprfc is the "old style" generic node for calling RFC as web services.
It is used up to WAS 6.20.
Beginning with WAS 6.40, it is still there and funcional but you are supposed to use the new web service implementation with one SICF node per RFC module function.
In that case, You can create an HTTP destination per function module to call.
If you just test the HTTP destination from SM59, you will, of course, get an error because you just send a GET to the URL which does not respect the SOAP protocol.
What you need to do is to create a web service proxy from the WSDL.
Regards,
Olivier

HTTP destination type G with scpecial characters in the path prefix

Hi guys,
I am having an issue with a RFC destination type G in a ECC 5, the HTTP service that I am trying to use is asking me for an authentication that needs to be embeded on the Path prefix, the user has an "@" and the pwd also contain a special character "!". So the complete uri that I want to access is in the form of https://server:443/path?user=MyUser@MyDomain.com&password=MyPwd! when I tried in my web browser I got authenticated but when I put the information in the RFC destination in the form described below I am not able to authenticate and I am getting an error of Unauthorized.
Target Host: server
Service: 443
Path prfix: /path?user=MyUser@MyDomain.com&password=MyPwd!
Logon procedure: No logon
SSL: Active
I also have tried with the basic authentication but I am still not able to authenticate.
I think the issue is the "@" in the user: MyUser@MyDomain.com , I also have tried replacing the "@" for "%40" and still not working.
Do you know how I can pass this special character?
Do you think it can be something else that it doesn't let me authenticate to the server?
My system is a non unicode ECC 5, SAP_Basis 640
Thanks
Omar Hernandez

Hi Mark,
Thanks for your response, the HTTP service that I am trying to access is not accepting a basic authentication but it is getting the authentication info from the parameters in the URL. Anyway I also have tried to use basic authentication but it is not working.
Regarding SMICM, I havent seem anything useful, maybe the just the "BINDUMP of content denied" string but I am not sure what does this mean.
[Thr 1076382016] IcmHandleNetRead(id=91/11638): pending SSL data: 0, rollout=0
[Thr 1076382016] <<- SapSSLReadPending(sssl_hdl=0x2aaaaf53f380)==SAP_O_K
[Thr 1076382016] out: pendlen = 0
[Thr 1076382016] NiIPeek: peek successful for hdl 79 / socket 46 (r)
[Thr 1076382016] <<- SapSSLRead(sssl_hdl=0x2aaaaf53f380)==SAP_O_K
[Thr 1076382016] result = "max=65312, received=88"
[Thr 1076382016] IcmReadFromConn(id=91/11638): read 259 bytes(timeout 250)
[Thr 1076382016] BINDUMP of content denied
[Thr 1076382016] PlugInHandleNetData: role: 2, status: 2, content-length: 0/88
##buf_len: 259, buf_offset: 171, buf_status: 0, conn reused
[Thr 1076382016] PlugInHandleNetData: read response body (len=88/88)
[Thr 1076382016] PlugInHandleNetData: response completely read(EOS=0)
[Thr 1076382016] IcmFlushBuf: Flushing 259 Bytes, buf_status: 6
[Thr 1076382016] flush buffer with mpi buffer id 10
[Thr 1076382016] MPI<1e8c9>1a#5 FlushOutbuf l10 1 1 1c14e8 311 6 -> 0x2b4bc7cd64e8 0
[Thr 1076382016] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 1076382016] PlugInHandleNetData: keep connection
[Thr 1076382016] IcmPlCheckRetVal: Next status: WRITE_REQUEST(3)
[Thr 1076382016] IcmHandleNetRead(id=91/11638): read_len: 88, HandleNetData returned: 3
[Thr 1076382016] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 1076382016] IcmWorkerThread: Thread 4: Waiting for event

Monitor RFC Destinations

Hi guys,
Couldn't find a way simply monitor RFC destinations with CCMS monitor. Specifically, I've RFC destination type T (http)
can't find a way to monitor it.
Please advice,
Dimitry

Hi
        Availability can be implemented using the RFC availability check for specific RFC destinations.
        Monitoring of specific and critical RFC destinations can be done by using the standard CCMS MTE
        class CCMS_RFCDest_Availability_Col
        Using the methods described above, alerts can be generated in the CCMS monitoring transactions
As specified above note 1069130 will help you in achieving it.
Thanks
Amit

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.

Program ID in RFC destination of type T

can one please explain what exactly is program id in rfc destination of type T

Hi,
from
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042652488911d189490000e829fbbd/content.htm
"Type T destinations are connections to external programs that use the RFC library to receive RFCs."
so program id is the name of such a program
Regards,
michal

Use of RFC destination "DEST" of type SNA/CPI-C connections

Hi ,
Please tell me the use of RFC destination "DEST" of type SNA/CPI-C connections in PI system .
Connection test for this RFC is failing with message "Error when opening RFC connection" . whether it is normal ?
Regards ,
Hanumant

Dear Hanumant Anarase,
Have you find any solution for your problem,
Because i am facing the same issue, as you mentioned above.
Regards,
Furqan

Why RFC destination of type H in ABAP proxy

Hi All,
We specify the XI integration server url in the Sxmb_adm transaction of the application SAP system..
Why do we still require a RFC destination of type H pointing from application sys to XI...
What is the exact function of that RFC of type H

in SXMB_ADM, as far as I know we can give in two ways,
one is explicit URL, i.e., http://HOST:PORT/sap/xi/engine?type=entry
second option is, dest://RFCDestinationTypeH
RFCDestinationTypeH actually uses the above http entry.

RFC destination types

Similar Messages

Maybe you are looking for