RFC adapter Call BAPI error

Hi XIer,
I am using RFC receiver to make a BAPI call, I used a BAPI wrapper due to this BAPI don't have a RETURN structure in the Export Tab which is XI expected.
but after I made a wrapper, the same error occurs, just like I directly call the BAPI without wrapper function. the error as following:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:456)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
the BAPI name is :QIRF_GET_USAGE_DECISION2
the wrapper name is :ZZQIRF_GET_USAGE_DECISION2
and I added a RETURN structure, type is BAPIRET2.
Please give me some ideas, thank you for your time~~

I still am not sure why you need a Wrapper RFC? If SP 14 or above on XI, RFC adapter have the option of BAPI commit and this will make things easy for you.
You can call the BAPI directly.
regards
Bhavesh

Similar Messages

Error when RFC adapter calling the BAPI

Hi freinds
Today when I was executing my scenario ( File -- XI -- RFC ), I got following error ::
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_BAPI_POS_AUTOMATION in remote system (RfcClient[RFC_Connection_SAPR3_DEV]):com.sap.mw.jco.JCO$Exception:(104) RFC_ERROR_SYST
Before this error I executed my scenario 2-3 times without any errors.
I found that in RWB the message status was "Waiting". SO I checked the Component monitoring & found this error in Self Test Status ( the symbol was RED )-->
java.lang.ArrayIndexOutOfBoundException: -1 ( Not copied from the original error message )
I clicked the "Repeat Self Test" button & the status become green so I checked my message again. Now it was successfull but in 2 retries it was giving the JCO error & after the Self test ( 3rd retry) it went fine.
I didn't change anything else other than Self test.
This happened two times with me today. Can anyone tell me the reason behind this & what will be the permanent solution of
this. Is this related to some memory dumping ? Is their anything like clearing memory for adpaters in XI.
Best Regards
Lalit

Could you pls check whether a short dump occured in the target system.
Go to ST22 in the target system and check.
Thanks,
Renjith

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 and BAPI Commit

Hi everybody!
In my scenario I post an RFC call to a BAPI (BAPI_GOODSMVT_CREATE). The call succeeds (empty RETURN parameter, material document numer is returned). However, the resulting material document is not available in MB03 - I assume this is due to a missing COMMIT after the RFC call.
However, our system has SP 18 - and I have read that the RFC adapter is able to add a COMMIT after a successful call automatically starting from SP 14. What confuses me is the fact that the descriptions in the online sources state that I should check the "Extended Mode" checkbox in the RFC adapter config screen and then I should check the "Commit..." option. However, when I set the checkbox for extended parameters, I only get a simple table where I can enter property/value pairs.
Has something gone wrong with the upgrade and my RFC adapter doesn't have SP 18 yet? Or am I doing something wrong?
Regards, Joerg

Hi Joerg,
Check in your Repository if you imported the newest adapter metadata.
Check Software Component SAP BASIS - > SAP BASIS 6.40 -> http://sap.com/xi/XI/System
There Adapterobjects -> Adaptermetadata -> RFC
search after the attribute ..singelBapiCommit
Because you dont see a SP version there.
Maybe its better to search afer the label:
Commit handling for singel BAPI-calls
When you dont find the attribute .. try to reimport your BASIS 6.40 Software Componenent.
Regards,
Robin

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.

Doubt Regarding Sender Rfc adapter calls

Hi Experts,
When we call RFC in R3 system by giving destination as XI system,
1) where exaxtly RFC cal executes either in R3 or XI?
In case of sender RFC syncronouse call? where exaxtly RFC cal executes either in R3 or XI?
In case of sender RFC asyncronse call? where exaxtly RFC cal executes either in R3 or XI?
2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?
Please help me out.
thanks
siva

1) where exaxtly RFC cal executes either in R3 or XI? 
It is at R3 for bothe sync and asyn sender scenario.
2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?
RFC is called from XI. The call is actually executed at R3 receiver
Regards,
Prateek

Looking for alternate method for RFC adapter with BAPI

Hello Friends
Right now I have a scenario as follows
An External ==> SOAP ==> XI ==> RFC ==> SAP TABLE
Application
I have an external application that is sending some DATA to XI via SOAP adapter and in turn XI using a ZBAPI via RFC updates the table.
However, the problem is that BAPI's doesn't support STRINGS anymore.
SO MY QUESTION IS: Is there any other way (any other adapter) without using BAPI that I can update the table with this data.
Your feedback will be greatly appreciated.
Thanks
Ram
Edited by: Ram Prasad on Mar 20, 2008 2:16 PM

Hi Prateek
Thanks for your response.
To be honest with you, I have not used Proxy in my job here so far, even though I studied during the courses I took to get certified in XI. I have to go back and look at my notes :).
The data that I am having problems with is of 'STRING' Type, which is a blob data or a CUD string (XML string) of variable length.
If you have any hints or steps for creating ABAP proxy, please let me know. I would appreciate it.
Thanks
Ram

Receiver RFC Adapter Error

Hi All,
I have a file to RFC scenario. I keep getting the below error: Any Ideas?
Danny,
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found..

is this BAPI an SYNC one
check this link
RFC adapter Call BAPI error
Re: Invoice Not getting posted

SOAP - XI - RFC. XI not perform Adapter call after Technical Routing.

Hi, All!
I have a problem with XI.
My configuration (all calls are synchronous):
SOAP adapter -> XI mapping -> RFC adapter call to R/3
Most of the time it's works correctlly!
But some times XI does not call outbound RFC adapter after "Technical Routing". And there is no error in XI Monitor, but this XML message marked like "scheduled". So the SOAP adapter returns "Timeout error".
I have compared messages in XI monitor for a successful call and a unsuccessful one. There is no difference in "Routings" and "Mapings" they are the same, except for in the unsuccessful message no "Adapter call" at all!
Do you know how to solve such a problem?
Thank you!!

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

RFC adapter problem: ICM_HTTP_CONNECTION_FAILED

Hi All,
We have problems with a RFC adapter. The error is not consistent. Most of the time it works, sometimes we get the error below. It looks like the http communication with the XI adapter Engine fails. The problem is described in note 804124, but this note does not give us the correct answer.
We are on SP15, has anyone an idea?
Thanks,
Frank
Error:
Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
404 Resource not found
Partner not reached
Error:     -20
Version:     6040
Component:     ICM
Date/Time:     Tue Mar 7 09:35:20 2006
Module:     icxxconn_mt.c
Line:     2121
Server:     pxpci_PXP_10
Detail:     Connection request from (89/30444/0) to host: pxpci.fil-eu.sv.philips.com, service: 51000 failed (NIECONN_REFUSED) EX-T89, U30444, 660 XIAFUSER, 130.139.212.156, 09:35:20, M0, W0, , 1/0

Hi Michal,
I don't think the timeout is the problem here, as you can see in the error, it states the the resource can not be found (404) and further in the error you find that the connection is Refused. This error occurs within in second after the message comes into SAP XI.
Hi Holger,
The ICM log gives the same error as in the message monitoring. But I think it is not on level 3. I will try that.
Thanx,
Frank

Looking for a beginner guide - Adaptive RFC call BAPI in Web Dynpro Java

Hi,
im new in SAP Developeing. I developed some basic web Dynpro applications (after some tutorials) and they are all working.
Now i want to build an Web Dynpro application with an adaptive RFC Model.
I already imported the adaptive RFC Modell with a function Model (BAPI Z_...) from the R3 System successfully.
But if i deploy the application i will get following error:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:mypackages.com.types.BapiModel:mypackages.com.types.Zmbs_Bapi_Dispo_Orderdata could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
 at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:387)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:416)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
 at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
 at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:377)
 at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:322)
 at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:181)
 at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
 at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
 at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
 at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
 ... 49 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
 at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
 ... 59 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:754)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:747)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:511)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:439)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
 ... 62 more
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Failed to create CIM client. Check via 'Visual Administrator' tool if the secure store is operational.
 at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:117)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:751)
 ... 70 more
Caused by: com.sap.lcr.api.cimclient.CIMClientException: java.net.MalformedURLException: URL must have a host part
 at com.sap.lcr.api.cimclient.ClientFactory.createConnection(ClientFactory.java:466)
 at com.sap.lcr.api.cimclient.ClientFactory.createClientImpl(ClientFactory.java:413)
 at com.sap.lcr.api.cimclient.ClientFactory.createClient(ClientFactory.java:363)
 at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:113)
 ... 71 more
........Looks like a have a Problem with JCO.
Is there a good guide, which explains the Basic steps in developeing Web dynpro applications and BAPI ?!

thank you guys for all the answers.I have to read all the documentations.
to my szenario:
I installed on my notebook the Trial Versions of:
SAP NetWeaver Application Server 7.00/Java AS 7.00
SAP NetWeaver Developer Studio Version: 7.0.14
All my basic Web Dynpro Applications in Java are running (even with Adobe Interactive Forms) on the local NetWeaver Trail- Web AS Trail perfectly.
Now i want to connect per RFC to another SAPERP Server, which is in the intranet.
I did the whole RFC tutorial with the flights -
http://help.sap.com/saphelp_nw04/helpdata/en/c3/76b45d9688e04abe1a1070410ddc1e/content.htm (also with the JCO codeing etc)
so my web dynpro application should work.
I think I have to configure - like ramesh said something on the NetWeaver Trail.
So what do i need and configure excactly on my Netweaver Trial to work with RFC - to call the BAPIS in the other System?
- SLD ? JCO ?
If i over Web Dynpro - Content Administrator - >
it says "Connection to System Landscape Directory (SLD) could not be opended successfully." and all the buttons
create Jco destinations etc. are greyed out.
I didn´t configured the SLD and JCO in the Netweaver yet.

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

Multiple BAPI calls in RFC Adapter

Hi, Dear Friends!
I have asynchronous scenario File to RFC(BAPI).
File contains raws. For each raw I need to execute BAPI.
With the help of each raw I need to construct one document in R/3 database with the help of BAPI.
But now my scenario provide only one document (only one BAPI is executed).
I read file to xml structure. This structure contains elements. The elements represent raws of file. But BAPI is executed only for the first element.
How to explain to XI that I want it impement BAPI N times - as number of raws in file (or elements in xml structure).
So how to implement multiple BAPI calls. Have you any idea?
Thank you in advance.
Natalia Maslova.

Hi Natalia
have a look on these links
http://help.sap.com/saphelp_nw04/helpdata/en/43/b46c4253c111d395fa00a0c94260a5/frameset.htm
Best Design : for a SOAP -XI - BAPI ( Multiple )
Re: RFC adapter...How it handles multiple calls...
Re: Multiple BAPIs and COMMIT in BPM
Re: Is it possible to compose XML in BPM from responses of multiple BAPI calls?
Multiple BAPI calls in RFC Adapter
may be helpful
Thanks !!!

Http adapter call rfc: BAPI_PO_GETDETAIL1has an error,who can help me!

Hello, everyOne!
I have a question! When I call BAPI_PO_GETDETAIL1.request, I pass on parameters "PURCHASEORDER=5523" which exists in ECC6. However, the return message displays "<message>Document 5523 does not exist</message>". That is non-exist.
I used http_adapter to class BAPI_PO_GETDETAIL1. I am wondering who could tell me which parameters must be filled and how to be filled?
thank you so much!
Edited by: Gavin Tao on Dec 6, 2008 2:26 PM

HI Gavin
Need more information for solving this
My understanding is you are using RFC and calling BAPI_PO_GETDETAIL and its returning details not available.
If the PO exist there is it released. Check with the SD functional person for this
Thanks
Gaurav

Error while doing commint from RFC Adapter

Hi,
We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
This way program works fine and there is no error
So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any special way that PI calls this commit work.
PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
Appreciate help on this.
Regards,
Harish

Are there any error messages in the RFC Reciever channel in Runtime Workbench?
RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
Please try to give some more details on why the system says the messages are failing.

RFC adapter Call BAPI error

Similar Messages

Maybe you are looking for