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

Exception in Message mapping for JDBC -> XI-> file

Hi,

In the above scenario, Sender JDBC adapter has processed the message but when i checked the processed XML messages, its giving an error message with details

<i>During the application mapping

com/sap/xi/tf/_MM_XXXX_a

com.sap.aii.utilxi.misc.api.BaseRuntimeException

was thrown: RuntimeException in Message-Mapping

transformatio~</i>

how to make the source structure so that it gets correctly populated with the result set of sender JDBC adapter? Are there any constraints while making the Data type for the source structure?

Regards,

Nitin Aggarwal.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on May 19, 2005 at 08:22 AM

    Hi,

    did you try the one from the example:

    http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm

    Regards,

    michal

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2005 at 11:38 AM

    Hi,

    I have the same problem. I treid to create various Data Types, but i get always mapping error.

    I tried simple string -> string conversion and also complex type (resultset-row-string -> row-string(since i know, that outbound File Adapter must receive the complex type of ROW (and it must be called "row"!)) conversion, but it doesn't work.

    If someone knows the solutions of this issue, please let me know!

    Thanx, Peter

    Message was edited by: Peter Jarsunek

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      Message Mapping BaseRuntime exception occurs in the following cases,

      1. When the required Mandatory fields are not coming in the input file.

      2. When required mandatory fields are NULL.

      3. When executing message map with large data files.

      etc etc etc..

      I faced this problem with message mapping. With small data files it will work fine. But with large file it will throw baseruntime exception. Now we are using XSLT map now.

      Thanks,

      Sasi

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2005 at 11:44 AM

    Hi nitin,

    Which mode are you using for this adapter e.g. XMB2DB_XML or XMB2DB, etc...?

    And Can you please post a sample of the source structure?

    Thanks.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2005 at 12:06 PM

    Hi,

    The problem is solved...

    Actually, the runtime system was not able to map the result set generated by the Sender JDBC adapter to the source structure of message mapping. This was because the result set has a particular structure and its like

    <resultset>

    <row>

    <column1>value1</column1>

    <column2>value2<column2>

    </row>

    </resultset>

    To map this kind of structure to the source structure, a <b>row</b> element should always be there below the root node and the structure fields should be placed as sub elements to row. One more thing the root node of the source structure should be same as the document name specified in the sender JDBC adapter config.

    Anyways, Thanks to all for the valuable efforts.

    Regards,

    Nitin.

    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.