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.

Similar Messages

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

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 for RFC to File scenario

Hi,
I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
Step 1:
For this a Registered server program is created in Jco RFc Destinations with,
Program Id : pgm1
Gateway host : PI's host
Gateway service : PI's service
application server host: ECC's host
system numer     : ECC's number
client : ECC's client
logon user : ECC user
password : pwd
Step 2:
In SM59, TCP/IP connection the following parameters are given:
Program ID : pgm1
Gateway host : PI's host       -
> is this correct
Gateway service : PI's service      -
> is this correct
Step 3:
So i am calling the RFC in ABAP program (R/3 system) like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
Step 4:
In PI side,
for RFC sender I am passing :
Application server : PI server
Application server service: PI host
program ID: pgm1 which was created in the previos step
For RFC Metadata Repository Parameter, i am passing all the values related to R/3
Please let me know whether the steps and values i given is correct.
B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
so i am confused as which is the correct method. pls clarify

Ok I will try to explain....
Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
    comp_detail = company_detail.
COMMIT WORK.
Regards,
Sarvesh

RFC Destination for RFC adapters?

What RFC destination is used by RFC receiver adapter?

Hi SSG,
You create remote function call (RFC) destinations on the J2EE engine so that SAP BW can make function calls on remote systems.
Look at these threads.. Shud help u out..
http://help.sap.com/saphelp_nw2004s/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/7c95731a9c5918e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
cheers,
Prashanth
P.S Please mark helpful answers

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.

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

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
     RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*"      PED_ORDEN STRUCTURE ZSD_RFC_T04
*"      RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
               tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
          FROM zsd_ped_orden
          WHERE estatus EQ space.
LOOP AT tb_ped_orden.
    MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
    APPEND ped_orden.
    tb_ped_orden-estatus = 'X'.
    tb_ped_orden-fecha_actualiz = sy-datum.
    tb_ped_orden-hora_actualiz = sy-uzeit.
    MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
          FROM zsd_rfc_r01
          WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
    MOVE-CORRESPONDING tb_rfc_orden_error TO return.
    APPEND return.
    tb_rfc_orden_error-estatus = 'X'.
    tb_rfc_orden_error-fecha_actualiz = sy-datum.
    tb_rfc_orden_error-hora_actualiz = sy-uzeit.
    MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
      return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
     TABLES
          ped_orden             = ped_orden
          return                = return
EXCEPTIONS
    communication_failure = 1
    system_failure        = 2
    OTHERS                = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

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

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

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

HTTP Receiver Adapter

Hi,
I am working on a scenario, where I am posting xml message on https url, for which I am using HTTP receiver adapter.
I have created RFC destination of type 'G' in sm59 to make an https call, where I have provided following details:
In Technical Settings:
Target Host - <Hostname>
Service No. - 443
Path Prefix - <url path>
Logon Security:
SSL - Active
SSL Client Certificate - Default SSL Client (Standard)
UserName - <Username>
Password - <Password>
I have used this RFC destination in 'HTTP Destination' of HTTP receiver adapter.
When I test this interface, I am getting this error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 110 reason</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Can you please help me resolve this issue. Please let me know, if I am following the right steps.
Thanks in advance
Regards,
Amit

Hi -
Since you're using the http destination option in the channel, you just specify the user/pwd in the destination.
Regarding the issue, first, for the Logon/Security option in the destination, unless you'll be using a client certificate to authenticate, you should choose option ANONYM SSL Client (Anonymous) - you still provide the user/pwd in the Logon section. Make sure you have imported the root cert of the CA verifying the server's identity into the client certificate list within STRUST (node SSL Client (Anonymous)).
Also, for some hints on the issue, look at the ICM trace - tcode SMICM->Goto->Trace File... you may need to increase the trace level - SMICM->Goto->Trace Level... After resolving the issue, make sure to set the trace level back to default.
Regards,
Jin

IDOC as a receiver adapter in XI to 3rd party scenario

Hi All,
I have an requirement to connect sap xi and 3rd party. the scenario as given below:
sap ecc 6.0 --> sap xi --> 3rd party
Here ecc is sending an idoc to the 3rd party. The 3rd party is SAP certified and intelligent enough to receive and send idocs. Here I'm using a idoc adapter as a receiver adapter. In the receiver adapter I have to give a rfc destination and a port name.
My question is how to create a rfc destination for the 3rd party. and which port name we'll use in this case. Is the port name will be the 3rd party port name is yes then how I can create a port in the 3rd party system.
Please help.
Regards,
Santosh

A communication channel with a receiver IDoc adapter can be created automatically for business systems that are defined in the System Landscape Directory. refer this link
[http://help.sap.com/saphelp_nw04/helpdata/en/42/d1a4d665c5574fa6e19784358ec948/frameset.htm]
You need to configure the receiver IDoc adapter to convert Integration Server contents from IDoc-XML to native IDoc format and to forward the IDocs to an SAP system .
you create a port and the rfc destination pointing to receiver in PI system
use tcode sm59 for creating rfc destination and IDX1 to create port and map it to rfc destination.

RFC Destination type RFC Receiver Adapter?

Similar Messages

Maybe you are looking for