Skip to Content
author's profile photo Former Member
Former Member

Error with Asynchronous RFC call to JDBC

Hi all,

We are working on a scenarion where in we have to make an asynchronous RFC call to JDBC.

We have configured RFC sender adapter following this weblog


We have created data types only for the database as RFC does not require any data types.

And also we have created message types,message interfaces accordingly.

In Message Mappping,we mapped the export parameters of RFC to the access fields of database message type.

Also we have created sender agreement,interface determinations etc.... accordingly

And for sending RFC request asynchronously we followed this weblog


Once done with all the above steps we could able to trigger the RFC call and caught with the following errors in SXMB_MONI and no errors are seen in communication monitoring

SOAP Error:

+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+

+- <!-- Request Message Mapping+


-" xmlns:SOAP="" SOAP:mustUnderstand="">





<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack> thrown during application mapping com/sap/xi/tf/_curr_exg_mm2_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>



Also trace shows the following error thogh the interface determinations are properly configured

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************


<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface BAPI_EXCHRATE_GETCURRENTRATES*</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--start receiver interface action determination</Trace>

<Trace level="1" type="T">Loop 0000000001</Trace>

<Trace level="1" type="T">select interface *</Trace>

<Trace level="1" type="T">select interface namespace</Trace>

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>

<Trace level="1" type="T">Hence set action to DEL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************


<Trace level="1" type="T">----


<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

the above errors are shown as part of request mapping..

Can any one please let me know what other configurations do we need to do?

I did not map the RFC import parameters,do we need to do that

Any help in this regard is really appreciated



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 26, 2008 at 05:30 PM

    Hi Santhosh,

    copy and paste the payload into the test-tab of message-mapping. Then test it!

    Regards Mario

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 26, 2008 at 05:20 PM


    It says there is error in Message Mapping. Did you tested your message mapping in test tab?


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.