cancel
Showing results for 
Search instead for 
Did you mean: 

Error while executing the SOAP-XI-JDBC(syn) scenario

Former Member
0 Kudos

Dear Forum,

We have done SOAP-XI-JDBC(synch) scenario with out BPM.

When we sent the request data from EP to Oracle database through XI, we got an error,Runtime in Message-Mapping transformation~.

com.sap.aii.utilxi.misc.api.BaseRuntimeException: Runtime in Message-Mapping transformation: Cannot produce target element /ns:Customer/customers. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:291)

Exception message says that it is a mapping issue. But we got the responce data from database along with this message.In message monitoring we got the message processed successfully.

Now i am not able to understanding why it throughs an error Runtime in Message-Mapping transformatio~ first time ?

Pls revert me to fulfill this task successfully.

Points will be rewarded.

Regards,

Naresh

Accepted Solutions (1)

Accepted Solutions (1)

VijayKonam
Active Contributor
0 Kudos

hi,

I dont think for a message resulting in Mapping error would have had response from Database. It must be response for some other message. Check in SXMB_MONI, you should find a red flag. Check the Trace node there to know the exact problem.

VJ

Former Member
0 Kudos

Dear Friends,

Sorry for the delay,and Thank you for your quick responce.

Yes I got that message under trace option in SXMB_MONI,

Pls find the following msg structures and if any error please let me know status...

Soap request structure:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">

<xsd:element name="soap_reqmt" type="soap_reqdt" />

<xsd:complexType name="soap_reqdt">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

5b474a34c8a511dc8d8e001a4bf038d4

</xsd:appinfo>

</xsd:annotation>

<xsd:sequence>

<xsd:element name="Request" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

49b1ae20c81211dcce03001b78afb958

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="ORDERID" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

49b1ae21c81211dcc20d001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="Operation" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

49b1ae22c81211dc858a001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

Data base request structure:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">

<xsd:element name="db_reqmt" type="db_reqdt" />

<xsd:complexType name="db_reqdt">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

5b4e7620c8a511dcc4fe001a4bf038d4

</xsd:appinfo>

</xsd:annotation>

<xsd:sequence>

<xsd:element name="STATEMENTNAME" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb0bceb11dcbb54001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="FETCHDATA">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb1bceb11dc9750001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="TABLE" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb3bceb11dccc94001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="access">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb4bceb11dc9b35001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="ORDERID" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb5bceb11dca20a001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="ITEM" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

d0279840c81011dc8e4e001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="QUANTITY" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

d0279841c81011dcb8f4001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="PRICE" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

d0279842c81011dc832f001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="key">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

89f43170c81611dcc8fa001b78afb958

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="ORDERID">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

89f43171c81611dcb6e3001b78afb958

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:simpleContent>

<xsd:extension base="xsd:string">

<xsd:attribute name="compareOperation" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

89f43172c81611dccba5001b78afb958

</xsd:appinfo>

</xsd:annotation>

</xsd:attribute>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

<xsd:attribute name="action" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

fa204eb2bceb11dca298001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:attribute>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

Soap Responce Structure:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">

<xsd:element name="soap_resmt" type="soap_resdt" />

<xsd:complexType name="soap_resdt">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

8d49d494c8a411dc81f5001a4bf038d4

</xsd:appinfo>

</xsd:annotation>

<xsd:sequence>

<xsd:element name="response" minOccurs="0" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd30bd0611dcb29d001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd31bd0611dca3d7001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="ORDERID" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd32bd0611dcc7d1001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="ITEM" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd33bd0611dca6ad001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="QUANTITY" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd34bd0611dc95a8001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="PRICE" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

491ccd35bd0611dcc034001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

Database responce Structure:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">

<xsd:element name="db_resmt" type="db_resdt" />

<xsd:complexType name="db_resdt">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

8d3b7cb1c8a411dcb1d6001a4bf038d4

</xsd:appinfo>

</xsd:annotation>

<xsd:sequence>

<xsd:element name="STATEMENTNAME_response" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3410bcfd11dcaf4c001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3411bcfd11dc92d6001b78b0798a

</xsd:appinfo>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element name="ORDERID" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3412bcfd11dc92e8001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="ITEM" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3413bcfd11dc9f7a001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="QUANTITY" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3414bcfd11dcc6c4001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="PRICE" type="xsd:string">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/TextID">

adca3415bcfd11dca54c001b78b0798a

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

Regards,

Naresh

justin_santhanam
Active Contributor
0 Kudos

Naresh,

You got the response from DB. The issue is the mapping from DB Response to EP Response isn't it?

Rather than giving it as xsd, can u please reply the DB Response structure?

raj.

Former Member
0 Kudos

Dear Raj,

<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>

<m:soap_reqmt xmlns:m="http://soap2dbns">

<Request>

<ORDERID>12</ORDERID>

<Operation>EQ</Operation>

</Request>

</m:soap_reqmt>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

XML DB Response in Payload

(This is the exact data for Oderid 12 in DB table)

<?xml version="1.0" encoding="utf-8" ?>

- <ns0:db_reqmt_response xmlns:ns0="http://soap2dbns">

- <STATEMENTNAME_response>

- <row>

<ORDERID>12</ORDERID>

<ITEM>pens</ITEM>

<QUANTITY>12</QUANTITY>

<PRICE>468</PRICE>

</row>

</STATEMENTNAME_response>

</ns0:db_reqmt_response>

This message is not being processed in soap responce.

Pls find the error message "RuntimeException during appliction Java mapping com/sap/xi/tf/_soap2db_res_mm_</Trace>

<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:soap_resmt.

Thanks in advance.

Regards,

Naresh

justin_santhanam
Active Contributor
0 Kudos

Dear Naresh,

Can u confirm whether u created the Message type name as db_reqmt_response

raj.

Former Member
0 Kudos

Edited

Edited by: NARESH K on Jan 22, 2008 8:28 AM

Former Member
0 Kudos

Thanks a lot Raj...

Full points to you...that was the problem

Our message type was db_resmt..changed it to db_reqmt_response and it is working fine now...

But have small problem,there are no succes flags shown in SXMB_MONI though I got the response succesfully.

And the success flags are not shown only in the scenarios in which SOAP is a sender and for other scenarios success flags are shown promptly.

Any help on this is really appreciated

Rgds,

Naresh

Former Member
0 Kudos

Hi Naresh,

For synchronous messages you You have to turn on sync logging.

Transaction SXMB_ADM,

Change Specific Configuration. Then RUNTIME, LOGGING_SYNC set to 1.

Regards,

Santhosh

Answers (3)

Answers (3)

Former Member
0 Kudos

check this Blog and discussion at this

/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

have a look at this thread also

Regds

Abhishek

Edited by: Abhishek Agrahari on Jan 22, 2008 6:57 AM

Former Member
0 Kudos

Dear Abhishek,

Thanks for your reply.

Yes we have tested in IR & ID.It shows msgs processed successfully.

Regards,

Naresh

Edited by: NARESH K on Jan 22, 2008 8:41 AM

Former Member
0 Kudos

Hi Naresh

have you tested the message mapping take that payload and compare it with the payload from SXMB_MONI. sould be that the payload is not as expected

in integration directory tools-->test configuration

1. test with the payload u used while successfully testing in messag mapping

2. test with the payload u have in sxmb_moni

Regds

Abhishek

Former Member
0 Kudos

Hi Naresh,

if the mapping would fail in the inbound direction, the data would be never retrieved. So the mapping, which fails, is probablye the mapping of the response.

In intarface mapping, check, if you have correctly set-up response mapping.

Peter