RFC Adapter not Call

Hello Friends,
I am working on XI 2.0
My Scenario is
IDOC --> XI --> RFC Adapter --> R/3 System
I am configuring the RFC adapter for the SAP system.
But when I am able to try to call using the Integration Engine its not call the RFC adapter.
I define the end point as
RFC Adapter
(X) Load Balancing Deactivated
Application Server -- <host name>
System Number -- 00
When I run the scenario it show me in the sm58 transaction as
Connection Close (no Data)
And in the SXMB_MONI Transaction it shows
A. Status as Green Flag means Message schedule on outbound side.
So can you please identify and suggest me the solution or what else configuration is required.
Thanks & Regards,
Gaurav Jain

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

Similar Messages

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 not started (Error starting AS Java Service XPI Adapter)

Dear Experts,
We have recently Upgraded our sustem from XI3.0 to PI 7.1, and have encountered a peculiar error in RFC adapter which could not be started
error says: Error starting AS Java Service XPI Adapter: RFC
corresponding instance when started says
Error starting AS Java Service XPI Adapter: RFC on DVEBMGS00
Hence our RFC channels are not functioning
Please help
Regards,
Rana De

can you try to restart XPI Adapter:RFC in NWA. if still it throws error then try to restart java stack.

Rfc adapter not recommended.

Which are the scenarios when RFC adapters are not recommended, and wat are the prerequisite for using RFC adapters.?

Hi Rahul,
>>Which are the scenarios when RFC adapters are not recommended,
RFC adapters are not suited for scenarios which involves large amnt of message processing. If you are sending big data from R/3 the its always advisable to go for Proxies..
>>wat are the prerequisite for using RFC adapters.?
RFC Adapter is used for conncting with SAP and for sending and reciving data frm SAP systems... Apart from that can u tell what pre-requisites you are looking for??
Regards
Suraj

RFC adapter not responding

Hi guys,
We are facing the following problem:
We have a receiver RFC adapter that executes some RFC functions on a SAP R/3 system connected to XI. When the R/3 system is down (e.g. for maintenance reasons) the RFC adapter (communication channel) has a red "error" status in Communication channel monitor (that could not connect to R/3), which is ok. However, when the R/3 system goes up, the RFC communication channel remains in the same error status, irrespective of the fact that the R/3 is now up. Morever, it needs some manual stop and start from CC monitor in order to be able to "see" that the R/3 is now up. This has an impact on our interfaces that it may be the case that sometimes the administrators, fail to notice this and the corresponding interfaces that make us of the RFC adapter, fail for no reason.
Is there a way to avoid this undesirable situation?
Best Regards
Evaggelos Gkatzios

Hi Gkatzios,
we also facing same problem as your,,when the R3 system is down for some maintenance reason at the same time XI expects something from R3 ,in this situation RFC adapter is going to error state,when R3 is up RFC adapter works fine but CC still shows error status.but some times we have to stop and start CC manually.
everytime when we open the CC monitoring particular CC always in error state eventhough it is working fine..
If you find any solution for this please let me know.
Thanks for your time.
Regards
Rao

RFC adapter not found in RWB

Hello,
I have a problem with RFC adapters (From ECC and from BW)
When I try to found the problem in RWB  communication channel monitoring (I choose RFC in adapter type section)
I'm not seeing these channels.
Any idea how I can found this channels?
Elad

Hi Elad,
I hope you were not able to see the communication channel in CC Monitoring.
First check whether the channel has been activated in the Integration Directory?
Thanks,
kumar.

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 adapter...How it handles multiple calls...

Hi folks
Basic doc'tation on RFC adapter states...qRFC is not supported..Agreed..
I have a scenario where I need to dump lot of transactions from a flat file to an RFC.
I have split the single structure by 1:n mapping(multi) and pushed each message using a Loop(For-each/Par-For-each) to RFC function..
Now question here..Is this a good approach to invoking RFC's(I find response times to be pretty slow on my server upto 20 secs for each RFC call). Cant I parallely execute all the messages by calling the RFC on SRM systems.(PAR for each loop has a limit of 999 loops)..Is there any other option you can suggest for this scene.?

chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
there is a recommendation on when to use parForEach. From what i understand , parForEach is helpful if u intend to send "One" Message to multiple receiver systems and intend to handle the responses in different context.I beleive it won't help if u send "different" messages to the same receiver system.
One more approach , i can think of is to make a Jco call from your "Message Mapping" itself using User defined functions instead of "configuring an RFC adapter" and "calling it in ccBPM". The below link should help on this.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/how to perform sap data lookups within xi mappings.
Good Luck
cheers
Saravana

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

Hi,
I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
I have configured a RFC Sender Adapter in XI. I get the
following Exception:
"lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
Is this scenario possible? Or do the connection from
a SAP Java Connector App to the XI RFC Adapter not work?
You can't set the Client and System ID of a Third-Party or
Standalone Java system in the SLD.
Thanks for any help!
Regards
Wolfgang

Hi,
We use a JCO for directly connecting to sap systems.
In that case we need not use any XI also.
But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
I donot think there is any architectural significance in using rfc adapter of XI while using JCO.
Let me know if I mis-understood the context.

Error while calling RFC adapter(FILE-XI-RFC scenario)

Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

HTTP Response code 404 - RFC Adapter des not connect to Integration engine

Hi,
I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
Begining of the erorr report -
2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
2006-01-23 13:35:55 Success Trying to put the message into the call queue.
2006-01-23 13:35:55 Success Message successfully put into the queue.
2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
2006-01-23 13:35:55 Success The message status set to DLNG.
2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
2006-01-23 13:35:55 Error The message status set to FAIL.
2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
end of error report -
and the runtime workbench does not connect to Integration engine and fails with the following error,
begin error report -
javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
 at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
 at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
 at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
end of report -
Have anyone experienced the same issue?. Are we missing some post installation configuration?.
Thanks in advance
Regards,
Arul

HI Anulraja,
Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
Check the Bussiness System in Sld , which you'll have defined for XI Server.
It should have ROLE : Integration Server And
pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
should be this if your http port is 55300.
Check if this url is right in SLD-Bussiness System.
You can check the exact http port in transaction sxmb_adm.
Go to Integration engine configuration and then click on check icon(F7).
It should match with that provided in the BS in SLD.
By default it should be 8000.
Check all these things and then try.
Regards,
Yomesh

Calling RFC Adapter fails - convert error

Hi,
I have a problem with calling RFC Adapter. I'm using JDBC->XI->RFC scenario. JDBC does just "select 'W' from dual". In the destination SAP system RFC function is created for test purposes. This function has one parameter - string type. After calling it, it should write a sysdate into the SAP Z_ table. The XI should call the function with the 'W' parameter. But this fails. Everything is ok, but calling the RFC returns following error (copied from the Runtime Workbench -> Message Monitoring :
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'W', in "u
(Yes, this is thw whole error message. I don't know what u should be...)
Did someone get this error?
Thanx 4 answers, Peter

Hello all,
Let me reopen the topic of my colleague. I'm facing the same error though with bit different symptoms. Here it is.
ERROR msg:
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'Z', in "T
The XML message (MainDocument):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_ACCESSIBILITY_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<BAPI1008 />
<PARAM>Z_XID_500_ACC</PARAM>
<ZTTOTH_BAPI1008 />
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500_ACC</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_ACCESSIBILITY_TEST_XI>
According to the error message the parser expects behind string ...<ZTTOTH_STRUCT><PARAM1> another tag, but the question is why.
To make all this more funny here I paste another XML message of BAPI calling which works fine (without the error described above):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_PARAMETERS_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<PARAM>Z_XID_500</PARAM>
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_PARAMETERS_TEST_XI>
The BAPI functions are absolutely the same except those other two import-pramater structures (BAPI1008 and ZTTOTH_BAPI1008). I'm gonna to try to add those import-parameter structures into Z_BAPI_PARAMETERS_TEST_XI, but anyway - this is weird.
Does anybody have an idea, what should be wrong ?
Thx. Tom
Message was edited by: Tomas Toth

RFC Adapter Receiver - change SAP User for each call

Hi guys,
I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
Can anybody help me, please?

hi,
>>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
sure we can help you but no in this way:)
it is possible to change the user for RFC adapter but using
principal propagation:
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
this is the way you need to go and not send password in XML payload
(this is certainly not the way and no client will approve it)
why use a password is anyone can see it ?
Regards,
Michal Krawczyk

Jco error RFC adapter field PT F not defined

Hi Experts,
I am in a strange situation as I have become clue less on this issue
It is a file to XI to RFC scenario.. runs fine in dev environment
When I change the parameters in teh rfc communication channel to point to QAS it throws
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
pls help me ou ton this
Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

Hi,
First of all, can you please elaborate what you want?
secondly, why don't you transport your developments to QAS?
Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
Please check communication channel if you getting any error?
Regards
Aashish Sinha

RFC Adapter not Call

Similar Messages

Maybe you are looking for