About RFC Adapter

hi
Expert's
when i am configure sender RFC ADAPTER i am facing problem so plz help me
in comm channel
Rfc:server parameters
application server gatway: it host name of sender system(sap abap)
application server service: it..........................?
wher can i get the host name of sap system
and server service?
RFC:MATAATA REPOSITROY PARAMETERS:
APPLICATION SEVER NAME:
SYSTEM NO:
Thanks&regards
upendra

Hi,
>>APPLICATION SEVER NAME:
login to your SAP system, you can find frm system - status or when you login to ur SAP system, you can find at the right corner(tool bar)
>>SYSTEM NO:
usually it is "00"
Regards

Similar Messages

Question about RFC adapter

Hi,
There is this little concept about RFC adapter
I would like a liitle clarifiaction about..
Here it goes..
Let's just say I have made an RFC in R/3.
The same I have imported In xi.
now when we say RFC ...By definition
it is a remote enabled function module.
We import the "interface" of the Same in Xi
So if I make changes in the BODY of the RFC in
R/3... do i need to reimport it in XI.
Besides when XI's reciver RFC adapter is using the
Rfc's interface to make changes in R/3
is it using a Copy of this RFC created in R/3
I would like to intercep at the point it's doing so...
tried putting a break point in the body of rfc.
Another question is regarding RFC sender adapter
Program ID..tcp Ip protocol.
Conceptually How does this connectivity takes place
I tried and it worked ...
I dunno How to explain this connectivity taking place
just on the basis of PROGRAM ID...
Kindly Help

Hi Deepak,
+
>>We import the "interface" of the Same in Xi.So if I make changes in the BODY of the RFC in R/3... do i need to reimport it in XI.+
Yes you have to.
>>Another question is regarding RFC sender adapter.Program ID..tcp Ip protocol.Conceptually How does this connectivity takes place I tried and it worked ...I dunno How to explain this connectivity taking place just on the basis of PROGRAM ID...
·An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).
·If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.
http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
Hope this will clarify your doubts.
Regards
Suraj

Hi.about RFC ADAPTER

can anybody tell me!
it is either xi calls sender system's function or xi's function is called by sender system for a sender RFC adapter?
thanks!

can anyone want to renew answer for the question?
i am ready to cancel this question!
i am gonna reward point.
thanks everyone to answer question!

RFC Adaptive Model Questions

Hi all,
I have some questions about RFC Adaptive Model in Web Dynpro:
1)Can I add a new RFC into a Model without recreating that?
2)Theres a way to WebDynpro dont lost de mapped attributes like an input field thats mapped to an import parameter of a RFC? Because all the times that I change the Model and recreate that, my application lost the link between Controller and View and its generate a lot of work to redo this manually.
Thanks,
Manoel

About RFC models, if I have this schema:
RFCModels
-- ZRFC_A
-- ZRFC_B
-- ZRFC_C
If I want to add a new RFC to this model (ZRFC_D), I can't do that. In this case I want to create a new Model with the ZRFC_D right?
When I import a Web Services Model and I have made some changes in Web Services, I don't have a Re-import option enabled like RCC models. What can I do in this case?
Thanks,
Manoel

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

File to JDBC Using RFC Adapter.

Hi All,
I've been trying to find out a scenario which is like a File-to-Database where RFC is the sender and JDBC is at Receiver end.
Kindly guide me in:
1) What are the steps I need to do when I use a RFC Adapter to pick a file from FTP?
2) Are the steps same for the JDBC Adapter as we do normally in a JDBC Receiver Adapter?
3) Is there any other configuration required for this type of scenario?
4) If I import the RFC only I wanted to know how would the file be picked from FTP Server? Is it likewhile create a RFC we import the File from FTP server.
My Plan of Action to do the scenario is:
1) Import the RFC from R/3.
2) Create the data types for target.
3) Map them both.
4) Use JDBC Adapter on the Receiver end.
These are the steps which I think should be done, if there are any other steps which I need to do, please do tell me.
Please do let me know the steps if all the are wrong as I'm doing this type of scenario for the 1st time.
Regards,
Sreedhar.

Hi,
Though i am not very sure about your interface requirement/design but would suggest you the following links :
Sender RFC :
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Reciever JDBC:
JDBC Stored Procedures:
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
JDBC Receiver Adapter -- Synchronous Select u2013 Step by Step
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to
on JDBC receiver response

RFC Adapter not getting data

Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
Gabriela

Hi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela

RFC ADAPTER destination hangs

To All
I am working on a XI 7.0 system SP5 for netweaver 2004s and am having problems with the RFC adapter.
Steps as follows:-
1.Configure SM59 tcp ip destination on r/3(4.6C) sender system using Xi system host and gateway service
2. step 2 - configure communication channel on my scenario in Integration directory. Activate channel
3. Send Asynchronous message via prgram from R/3 sender
this delivers successfully to BW target ssytem via asynchronous RFC
My problem is when I repeat steps 3 to send more my rfc destination fails with the following in the trace log:-
Trace file opened at 20060303 160158 WST, REL 46D,0,1984, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
DEST =ZSCEN2_XI
HOST =%%RFCSERVER%%
PROG =ZBWIP24_19
GWHOST =ux0800
GWSERV =sapgw53
If I repeat setps 1 to 3 above with a new transaction program it will again work but only once.
Any help would be greatly appreciated and I will award points.
Regards
Liz Porter
PS the adaptor monitor periodically gives the following message:-
Sender Channel 'RFC_INDE4' for Party '', Service 'ERP_WATERCORP_SAPR3_D' (Internal Name 'RfcServer[RFC_INDE4]')
Server data: {jco.server.gwhost=ux0800, jco.server.progid=ZBWIP24_19, jco.server.gwserv=sapgw53, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=100, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=portere0, jco.client.sysnr=81, jco.client.ashost=sapdev}
Current pool size: 1, max pool size : 50
RFC_HISTORY
- Error: 2006-03-03 16:49:27 WST:
RfcException:
message: CPIC-CALL: SAP_CMACCPTP3
no SAP ErrInfo available
Return code: RFC_SYS_EXCEPTION(3)
error group: 102
key: RFC_ERROR_COMMUNICATION

To All
The call from to the RFC destination is attempted as tRFC
see below:-
PARAMETERS:P_TPLNR LIKE IFLOT-TPLNR,
           P_DESTN LIKE TRFCQOUT-DEST DEFAULT 'ZSCEN2_XI'.
CALL FUNCTION 'ZBWIP_FUNCTIONAL_LOCN_OUT'
   IN BACKGROUND TASK
    DESTINATION P_DESTN
     TABLES
       FUNCT_LOC_MAIN       = T_TABLE.
IF SY-SUBRC = 0.
    COMMIT WORK.
    WRITE:/ 'So far so good check XI'.
ELSE.
    WRITE:/ 'Error ', SY-SUBRC.
ENDIF.
The SM59 parameters on R/3 4.6C as set as
Connection type T     TCP/IP connection
Activation Type: registration
Program ID   ZBWIP24_28
Gateway:-
Type                 T TCP/IP connection
Gateway host    ux0800
Gateway service sapgw53
and finally tRFC:-
Connection attempts up to task        2
Time betw. 2 tries [mins]             10
In the XI integration directory:-
Adapter type RFc sender
Application Server(gateway) ux0800
Application service(gateway) sapgw53
Program id                    ZBWIP24_28
Initial Connections           1
Maximum connections           50
Advanced Mode   Maximum reconnection delay 3
A bit more information from our XI system. In SMGW on XI our program shows as "connected" and on drill-down shows status receive data/send. If however we configure a SM59 TCP-IP connection on XI to our XI gateway(ie connect to myself) I get the same CPIC message about 677 timeout for registered program.
Regards
Liz

RFC Adapter - Where to Register Rfc2XmbService (Sender System or XI ?)

Experts,
I have the following scenario:
R3 --> RFC_ADAPTER --> XI --> SOAP --> THIRD_PARTY
My specific question is, In which system do I need to register the Rfc2XmbService program. Is this done in the R3 system or in the XI system.
If it is done in the R3 system then where is it done cause there is no J2EE administration tool in R3.
Could someone explain exactly what this registration concept is.
Thanks and appreciate any help in advance.
- Ravi
--- I have figured this one out already. The program needs to be registered in XI and Not the sender system.
Thanks
Message was edited by: ravi kumar

Hello,
the Rfc2XmbService registers itself when you activate the RFC adapter in the Configuration but you can preallocate it through the Visual Admin.
Further by default are logging for sync calls not enabled, e.g. you don't see anything in SXMB_MONI.
Therefore go to SXMB_ADM and the Integration Configuration option and under the RUNTIME specific option create an entry for
RUNTIME LOGGING_SYNC 1 (0 is default).
Also make sure that the rfc adapter is activate in the AdapterFramework overview. On the target system call transaction SMGW and go to logged on clients to see if you see the Rfc2Xmb Service. Then in SM59 of the R/3 system you should have an entry pointing to the Rfc2Xmb service and a test should give you an idea if it works.
I'm doing R/3 4.6c -> XI 3.0 -> R/3 Enterprise about 20 BAPIs, no issue.
I hope this helps.
Stefan

Sender RFC Adapter only processes first message

Hi there,
we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.
The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.
We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.
Can anyone help with this?
Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
Thanks in advance,
Henrique.

Hi,
>>>Or is it the abap calling that should be processed in another way?
the important thing is the commit work
which must be done after call function
and you can only have one call function
before the commit work
do you see any other errors in SM58?
>>>Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
one or the other - no doubt about that
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Program ID in RFC Adapter

Hi,
could you please explain me the about program id in configuring sender RFC communication channel.
Regards,
Nagarjuna.

hi,
when you configure rfc destination in your R/3 for the XI then you have to mention there the progrm id.
The exactly same program id has to be mentioned in the rfc sender communication channel.
You have to first cerate the sender communication channel and then register that program id in R/3 and use the program id in the RFC Destinationn.
This program id only establishes connection between R/3 and xi.
You can get more info here
http://help.sap.com/saphelp_nw04s/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards,
ujjwal kumar

Alerts not triggered for a RFC Adapter

Hi All,
I have done the alert configuration for triggering alerts whenever there is a problem in any communication channels of any adapter.i.e. I have given * for 'where did the error occur'.Alerts are being triggered for JDBC and File adapetrs.but when an error occurs in a RFC adapter no alerts are triggered.What can I do about it?
Thanks and Regards,
Jishi

Jishi Abraham,
Could u please try No Restrictions in the 'where did the error occur'
All of the File, JDBC and RFC adapters, reside on the Java Stack. Whenever there is a message being processed, by any of the adapters except for IDoc and HTTP, the config should be similar as far as the alerts are concerned.
Please try No Restrictions and let us know.
Reg,
-Naveen.

Problems in connecting the RFC adapter

Hi all,
we are using XI 3.0 which has been installed very recently. I am trying to configure the RFC adapter but i am getting an error "program <progname> not registered".
I have set up a TCPIP connection on the ECC system with the parameters :
gateway host: hostname of ECC system
gateway service : sapgwXX where XX is system number of ECC system
activation type : Registered server program ZXXXXX
On the XI system, I am creating a communication channel of type RFC sender with the Integration server as the adapter engine
RFC server parameters:
Application Server : hostname of ECC system
application Service: sapgwXX where XX is system number of ECC system
program ID : ZXXXXX (case-sensitive)
RFC metadata parameters:
application server : hostname of ECC system
system number : system number of ECC system
Logon Details of the ECC system
I am confused about which details to give where, but i have followed Michal's blog .
I am still getting an error . Could you please help in sorting out this matter?
Thanks,
Amit

Hi
RFC metadata parameter login should be U R ECC system login s and correct.
What is u r error.
Steps shown in the blog is all fine it works , no other configuration needed.
I guess u r testing the TCP RFC connection , u configure u r Sender RFC use the Register Program id same what u have used in the RFC (case sensitive) and run the scenario
it will work.
Regards
Srini

Difference In RFC Adapter and XI proxy

I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridhar

Hi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK 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 or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK 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.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
·        Interfaces designed for message exchange between application systems
·        Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
·        You define the interfaces to be used in an integration scenario.
·        Cross-component integration processes use interfaces to exchange messages.
·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
·        You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

About RFC Adapter

Similar Messages

Maybe you are looking for