ERROR while accessing RFC function

[Former Member]

Hello,

I am facing strange error that my RFC function call from XI server sometimes work and sometimes don't. I try to figure out any sequence in error generation but there is none. I compared the both the version of the request files and both were identical. I am getting Interface mapping urn:ooms:dev/xi IM_SO_SIMULATION does not exist in runtime cache.

I have clear the runtime cache for Repository, configuration and sld. Also clear the AE cache using SXI_CACHE. but still facing this issue. I will be glad if someone shed some light on this issue.

Regards,

Jawed Ali

[Former Member · Accepted solution]

Hi,

Check the RFC destionation type H used for cache refresh..

INTEGRATION_DIRECTORY_HMI test this connection it should return 200 or 500

also check the user used for the same if it gets locked also you will face problem

HTH

Rajesh

[Former Member]

For the record, this issue was not directly related to XI, instead when you have any error at R/3 end while calling function module it gives you the same error that interface mappings not found in runtime cache. So check your R/3 end also.

[adnanmaqbool]

Dear Jawed

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Request Message Mapping 
  --> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code> 
  <SAP:P1>urn:ooms:dev/xi IM_ABL_TREQ</SAP:P1> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Interface mapping urn:ooms:dev/xi IM_ABL_TREQ does not exist in runtime cache</SAP:Stack> 
  <SAP:Retry>N</SAP:Retry> 
  </SAP:Error>

I am also getting this error while passing the SOAP request, payload is also now showing completely in MONI.

In Moni I am getting only this payload

  <?xml version="1.0" encoding="UTF-8" ?> 
  <ns0:MakePayment xmlns:ns0="http://tempuri.org/" /> 

SOAP request from Java Class

String str = "<SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:SOAP-ENC=\"http://schemas.xmlsoap.org/soap/encoding/\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\">"
				+ "<SOAP-ENV:Body>"
				+ "<ns0:MakePayment xmlns:ns0=\"http://tempuri.org/\">"	
	     		+ "<ns0:UserId/>"				
				+ "<ns0:Password/>"								
			    + "<ns0:FromAccountNumber>"+data.get("ACCOUNTNO")+"</ns0:FromAccountNumber>"
				+ "<ns0:ToAccountNumber/>"
			    + "<ns0:TxnAmount>"+data.get("AMOUNT")+"</ns0:TxnAmount>"
		     	+ "<ns0:RRN>"+data.get("PAYMENTID")+"</ns0:RRN>"
			    + "<ns0:TransactionReference>"+"ABL"+data.get("PAYMENTID")+"</ns0:TransactionReference>"
		        + "</ns0:MakePayment>"
	            + "</SOAP-ENV:Body>"
                + "</SOAP-ENV:Envelope>";

[Former Member]

Check weather all the data type and message type, message interface having software component and check interface mapping also having the software component of message interface.

Just enter some description in Interface Mapping and try to reactivate it.

refer this thread helps you resolve your error