RFC Sender configuration

Trying to configure webservice(SOAP)-->XI->R/3(RFC) scenario.
Created a z_fun_mod and made it remotely enabled in R/3.
Trying to create a destination of type T in XI for R/3. As I need to specify 'ProgramID' for 'Registered Server Program', I specified a 'sdnweblogs' as per Michal's blog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step . When I test this connection, got the connection error saying 'program sdnweblogs not registered' in my R/3 host/gateway.
How do I register the programID?
Is this 'sdnweblogs' supposed to be a function module in R/3 client that calls my z_fun_mod ?
As per michal's blog, the programID is later needs to be specified while configuring the RFC Sender.
TIA,
Steve.

You want a R/3 -(RFC)-> XI -(SOAP)-> Webservice scenario, then? It's different from what you had previously informed (webservice -> XI -> R/3).
Anyway, for R/3 to send data to XI through a RFC, you need:
1. to configure a RFC Destination, inside R/3 (TX SM59), using type T (TCP/IP), activation type "registered server program", informing a Program ID, and informing the R/3 gateway host and gateway service (sapgwXX, where XX is your instance number). It's kinda confusing to use R/3 informations inside R/3 itself, but that's how it is.
2. to create a sender RFC Adapter, which will get the data from R/3 and send to XI. There, you'll need to inform the RFC Server (gateway) host and service again. The Program ID must be the same you used in RFC Destination above. And finally you need the info for the metadata repository. Generally, it's the same R/3 instance that runs the RFC server, so just input it again, but this time you'll need the client number, a language and a user authentication to the system (just like you'd configure a SAPGUI entry).
I spent quite a long time trying to understand this configuration scenario, but the best that I could come up with was this: A metadata repository is linked to a application that consumes the metadata through a RFC server. So, in your metadata repository, you'll need the information of this RFC Server (done in SM59) and in your application you'll need to reference both the RFC server and the metadata repository (both done on the adapter configuration). But in most of the cases the RFC server and the metadata repository are the same (R/3, for example), and so you'll need to reference R/3 in R/3 (in SM59) and reference it twice to XI (in adapter configuration).
hehehe, it was the only explanation that made any sense to me.

Similar Messages

RFC Sender configuration : RFC - XI - FILE

Hi All,
I read the post at RFC Sender Configuration in Asynchronous Mode and I have the same problem for the configuration.
I want to do a simple asynchronous RFC scenario ( RFC -> XI -> FILE) but I keep getting errors. Do I need to create a BPM to make it work? I'm using XI 3.0
Thanks

Hi,
For RFC to File Scenario, if you will be calling the RFC from any ABAP report then the import parameters will be passed to File.
Here you can use the Concept of Dummy RFC as below.
Lets say RFC1 --> Original RFC
RFC2 ---> Dummy RFC
1. Create one Function Module (RFC 2) in which take the import parameters similar to the RFC -1 Output parameters.
2. Now in ABAP report call the RFC-1 and get the Output in export parameters and pass it to RFC-2 as import parameters.
3. In XI import RFC-2 and map the import parameters to the Receiver File.
SO your purpose to pass the Output of RFC-1 to file in async way will be resolved .
Thanks
Swarup

XI RFC Sender Configuration

When configuring the communication channel for an RFC sender in XI, do I need to refer to the sending SAP system (e.g. R/3) or the XI system in the "RFC Server Parameter" and "RFC Metadata Repository Parameter"? I thought it would be the R/3 system, but I am having issues sending an RFC message (using RFC "STFC_CONNECTION") from R/3 to XI. The message never gets to XI (i.e. I can not see it in SXMB_MONI or RWB Message Monitor) and comes back with a "System Failure" message and no additional detail. My SM59 TCP/IP connection is working, I use this RFC destination in my RFC call to XI, and my programID matches between R/3 and XI. I am using the RFC - "STFC_CONNECTION" in this example.

Hi,
Pls find the following link about configuring Sender RFC Adapter.
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
Also find following blog.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Hope this helps..
Regards,
Moorthy

RFC Sender Adapter configuration - Program ID question

Hello All,
I am working on a Sync RFC(R/3) --> XI --> Webservice scenario. I have a question on Program ID's. We're going to be having different RFC's call the same webservice. In that case, we'll have one scenario for each RFC sender.
Do we need to create different TCP/IP ports and Program ID's in R/3 for each RFC sender or just one TCP/IP port and Program ID can be used by all RFC's from R/3?
Please respond with your suggestions.
Thanks in advance.
Karthik

Aamir,
Buddy please correct me if i'm wrong!! As u said u will design this as single scenario with conditional receiver determination, Wht happen if I create RFC channel under some other Business Service with same Program ID. In this case my receiver is different isn't it!!!
The key is Outbound Interface .. If the RFC sends BAPI_GET_DETAIL with say ProgramID TEST_1000 the corresponding interface in XI will be triggered, similarly if the RFC sends RFC_READ_TABLE with same program ID TEST_1000 the corresponding interface will be triggered?
Is the above example make sense, please correct me if my understanding is wrong.
raj.

R/3 to PI using RFC Sender Adaptor as Asynchronous scenario

Hello Folks,
RFC Adp. SOAP Adp.
ECC-->XI--
>ARIBA
I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
I have config the Sender comm. channel as below.
Appl. Server(Gateway): My Ecc Server host name
Appl. Server Service (Gateway) : My Ecc server
Program Id : XYZ.
Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
and put the same information as given above and test the connection which is working fine.
I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.

Appl. Server Service (Gateway) : My Ecc server
Confused with this statement.....
it should have the format sapgwXX ....
XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
http://<hostName>:5XX00:rep/start/index.jsp
How to configure sender RFC adapter...check this blog:
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
senderAgreement not found:
Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
Regards,
Abhishek.
Edited by: abhishek salvi on May 2, 2009 1:24 AM

Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv

Rfc sender problem: While executing the rfc in sap r/3 system
It is showing abap run time errors are
'alternativeServiceIdentifier: party/service from channel
configuration are not
(i have taken hint from this weblog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step)
These are the configuration at sap xi and sap r/3 system
1) SAP XI (ID)
I have created rfc sender commuication channel in I.D.
      Rfc server Parameters->
            A.S.(Gateway)-> server    {sap r/3 server name}
            A.S.S.(Gateway) -> sapgw00
            program id         -> PDPT
     AND RFC Metadata repository parameter
2)SAP R/3 (SM59)
    Rfc destination -> PPPP
    Connection type -> T
    Technical Settings->
         (*) Registered Server Program
      Program ID ->    PDPT
Gate way options
      Gateway host -> server
      gateway service -> sapgw00
Testconnection-> connected
3) testing rfc at sap r/3(se37)
But when i am executing a rfc in sap system
Rfc target system -> PPPP
and some import parameters
and it is showing the error message as
'alternativeServiceIdentifier: party/service from channel
configuration are not '
4)SAP R/3( SMGW)
CONNECTION TO CLIENT FOR PDPT(TP NAME) REGISTER STATUS IS WAITING
Please help me how to solve this problem

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>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".</i>
- 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

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

RFC Sender (XI 3.0, SP14) Load Balancing doesn't work

Hi all,
We're "desperately" trying to use the Load Balancing option of RFC Sender Adapter (XI 3.0, SP14). It doesn't work.
The Adapter can not register to the sender SAP server. But when we do not use the "Load Balancing" option, everything works well.
We did follow the XI guidelines step-by-step. All necessary configurations in XI and in SAP sender system (TA: SM59) are "properly" done and reviewed by different experts several times.
Do you have, by chance any running scenario using "Load Balancing" within a RFC Adapter? If yes, I would appreciate if you can share it with me.
Thanks a lot!
Regards,
Khaled

Hello Khaled,
the RFC sender adapter registers a program at the SAP Gateway. Load Balancing for the Sender Adapter means, that you have at least two J2EE server nodes within your XI installation. On all these server nodes the same RFC sender adapter is started and register the same program at the same gateway. The load balancing is then handled by the gateway. That means, that for the sender adapter the settings are the same, even if you use load balancing or not.
The settings are, e.g.
- SID=ABC
- hostname=abchost (central instance, message server)
- hostname=xyzhost (additional dialog instance of ABC)
- instance nr=00
application server (gateway): xi1host
application server service (gw-service): sapgw00
programm id: could be freely choosen
The Metadata Repository could be connected using load balancing. Here a user need to log on to the system.
The settings here must be:
Message-Server: abchost
Message-Server-Service: sapmsABC
System-ID: ABC
Logon-Group: e.g. PUBLIC; this logon group need to be created in system ABC using transaction SMLG
For the RFC-Receiver Adapter the same settings as for the Metadata could be used.
Keep in mind, that for the RFC Sender Adapter a RFC connection of type T must be created in transaction SM59 in system ABC.
Rgds.,
Andreas

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
<i>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".</i>
- 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

RFC Sender: Connection refused

Hi experts,
We are running a scenario with a RFC Sender communication channel.
When the RFC is executed this error occurs in the Runtime Workbench:
Transmitting the message using connection HOSTNAME failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused: connect
Our basis reported that the HOSTNAME value is incorrect, but could not tell where this information is configurated.
Can anybody tell where is this hostname configurated?
Is there any transaction to check the error?
Thanks anyway.

David,
http://SERVER:8002/sap/xi/engine?type=entry is your integration pipeline URL which belongs to your XI box.
In trasaction SXMB_ADM there are two ways through which you can enter the pipeline URL for the corresponding IE of XI system.
1) By creating and RFC destination and referring that in field "Corresponding Integ. Server" and
2) By directlyspecifying the pipeline URL in above mentioned field
in your case the URL is entered using 2nd option that can be edited by an option Edit-> Change Global parameters.
it will allow you to change the server name.
Thanks,
Sunil Singh

Regarding RFC Sender Communication Channel

Hi All,
I am working on RFC sender channel, need some important information.
1). Can i use single RFC Sender Channel in Multiple Sender Agreements.
2). Can i use Program ID in Multiple Sender RFC Channels. I am having one RFC to File interface and another RFC to JDBC interface.
Do i need to create 2 sender channels and 2 RFC destinations with 2 Program Ids????.
Please give me clarifications.
Regards,
Balu

If i will use single sender RFC channel and Single Program ID for my all sender agreements, how that Single RFC channel
will identify the information like
In our sender agreement we configure not only the channel but also the Sender Interface (in your case RFC)......this is the factor which defines what to accept......in broader term we use the same concept of channel re-use in other cases also and the same work fine because of this Sender Interface.
I found Q28 interesting: https://service.sap.com/sap/support/notes/730870
In first read it may sound confusing...but after some more rreads you will know what the answer means in the SAP note.
Regards,
Abhishek.

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

RFC Sender Adapter in XI..Possible??

Hi All,
I am trying to send data from XI using RFC Sender Adapter.
Have done all the configuration, ie created a tcp/ip destination in SM59 and then in the RFC adapter mentioned the program name.
In Adapter monitoring i can see the adapter working fine.
When i execute the Function Mouldule i get the following error in SM58.
parameter JCO.Request was <null> (server: RfcServer[CC_RFC_TX1_OUT]1)
Can anyone please lemme know if we can send data from XI box using RFC sender adapter.
Regards,
Sumit

Sumit,
Technically specking this should be possible.. I Havent tried it though..
So, you are using a Sender RFC to send data from XI to XI itself uh?
I have tried configuring a Receievr RFC adapter pointing to XI and it has worked fine.
Also, take a look at these blogs if your config is correct,
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards,
Bhavesh

RFC 2 File Error in RFC sender: java.lang.ArrayIndexOutOfBoundsException

Hello,
I'm sending data asynchronously from R3 to a file through XI, I've got the RFC destination (in R3) and sender RFC channel (in XI) configured and tested. Working fine.
Then in my report I've got the following code that sends 1 string and 4 internal tables 2 to XI:
CALL FUNCTION 'Z_RFC_ENVIAR_DATOS_PSP'
    IN BACKGROUND TASK DESTINATION 'SAP_2_XI'
    EXPORTING
      RUTA                       = p_ruta
    TABLES
      IT_DEMANDA           = p_gt_demanda
      IT_STOCKS              = lt_stocks
      IT_CUARENTENAS   = lt_cuarent
      IT_COMPRAS           = lt_repartos.
COMMIT WORK.
I've done that king of connection several times and allways worked but now I've got that error in the communication channel monitoring at RWB:
Error in processing caused by: java.lang.ArrayIndexOutOfBoundsException
And no message is created in XI. What can it be?
Thanks for your help

Hi Chen Lin,
The problem is with the adapter but no message is generated yet in XI, so I don't have XML yet.
The RFC sends the data to XI through the RFC destination and at this point something is wrong because that error is produced. The error is visible in both sides, In transaction SM58 at R3 I can see the error that tRFC hasn't been precessed because the ArrayIndexOutOfBoundsException.
But if I go to communication channel monitoring I can see the same error too, so that confirms that the communication between R3 and XI works fine but something is wrong and the error don't give me more details

How to send data to RFC Destination(RFC SENDER Adapter)

Hi ,
Scenario: R/3 Backendà RFC Sender Adapterà XIàsome other system.
I have configured the RFC destination (of the type TCP/IP) at R/3 System and have registered the Program ID (specified in the RFC destination) in the XI server and using it in the configuration parameters of the RFC Sender Adapter.
Problem: I do not know how I can send data to the RFC destination. (Should I use a report program/ ABAP Function Module?) Can anybody provide me with a sample code of Report Program/Function module (whichever is required), how to send data to the RFC Destination, so that it may be picked up by my RFC Sender Adapter.
Thanks and Regards,
Siva Maranani

I have one query for you that
I am trying to develop a scenario in SAP XI
SAP R/3 ( RFC function module) sends a synchronous request to the XI and SAP XI will send this request to a third party web application using HTTP receiver adapter.
I am able to send the data/message and it is successfully received at the third party web application.
But I am facing one issue that I am unable to receive any message/data in my RFC module back.i have seen in sxmb_moni that the two messages are displayed in successfuly processed but in SAP R/3 side nothing get happedned
Can you tell me how to use some waiting mechanism in function module to wait for the response from SAP XI.
Regards
Gopesh

RFC Sender configuration

Similar Messages

Maybe you are looking for