on 04-05-2007 7:01 AM
Hi,
Our scenario is FIle-RFC-File.
We are calling the RFC from XI system in Development environment. This is working fine in Development environment, but not in Quality environment.
This changes are moved/transported to Quality environment in both XI and SAP side. But we are getting the following error in Quality system:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><b>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></b></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please provide the inputs, what we can check at SAP side and XI side.
We have tried to test from XI Development to SAP quality environment, but we are getting the same error message.
Waiting for the precious inputs.
Thanks,
Ramesh.
Hi Ramesh,
Is the RFC properly transported to R/3 Quality? Please check in Function Module Browser.
Regards,
Amitabha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramesh,
Refer SAP Note - 730870 Question no 16.
The problem could be related to the communication channel
If there was any change in the RFC structure, then please delete and then reimport the RFC
Regards,
Prateek
Message was edited by:
Prateek Srivastava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramesh,
Also check this..
Refer SAP Note - 730870 Question no 16.
cheers,
Prashanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramesh,
This might be because your RFC adapter would not have been configured properly. Just do a check on it,in RWB(adapter monitoring) and activate it once more in ID.
Also check RFC comm. parameters such as host name/user id/password etc..
Also check whether your XML document is having a mismatch with your RFC XML.
Check with your payload ( from SXMB_MONI) and test it in your message mapping.
All the best!
cheers,
prashanth
P.S Please mark helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.