cancel
Showing results for 
Search instead for 
Did you mean: 

Mapping errors

Former Member
0 Kudos

Hi,

I am mapping a data type (table) to an RFC table. I have mapped my data table with my RFC table name and the indiviual fields. I get the following error:

Cannot produce target element /p3:ZHRI_LEAVE/EMPLOYEES.

my XML mapping looks as follows:

/p3:ZHRI_LEAVE/EMPLOYEES=/p2:LeaveMessageType/Employees==/p2:LeaveMessageType/Employees= /p3:ZHRI_LEAVE/EMPLOYEES/item=/p2:LeaveMessageType/Employees==/p2:LeaveMessageType/Employees= /p3:ZHRI_LEAVE/EMPLOYEES/item/PERNR=/p2:LeaveMessageType/Employees/PERNR==/p2:LeaveMessageType/Employees/PERNR= /p3:ZHRI_LEAVE/EMPLOYEES/item/SUBTY=/p2:LeaveMessageType/Employees/SUBTY==/p2:LeaveMessageType/Employees/SUBTY=

My XML monitor trace is as follows:

<?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="">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>com/sap/xi/tf/_LeaveMessageMapping_</SAP:P1>

<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>

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

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>During the application mapping com/sap/xi/tf/_LeaveMessageMapping_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Any ideas would be appreciated. I am running on XI3.0 SP13.

Thanks,

Leanne

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Leanne,

This error is occured when there is a mismatch in the case of your xml elements like lower case and upper case.

In XI Mapping is case sensitive.

So try to check the case of your elements.

You can see this in the inbound message payload of your sender message and in the Message Mapping-> Test - "Source Document View".

check the case of each xml element and if they are different then correct the elements in the Data Type of Outbound message interface.

Try this and tell me if you are able to solve your problem or still some more issues.

Regards

Gopesh

Answers (2)

Answers (2)

former_member187339
Active Contributor
0 Kudos

Hi Leanne,

Try removing this mapping...

/p3:ZHRI_LEAVE/EMPLOYEES=/p2:LeaveMessageType/Employees==/p2:LeaveMessageType/Employees=

ie map the

<i>

LeaveTable (complex type)

which <b>includes a struture (element 0...unbounded)</b>

with several fields (all element type string 0..unbounded) </i>

field with the RFC and the fields on the table to the RFC table fields.

Regards

Suraj

Former Member
0 Kudos

Thanks

Former Member
0 Kudos

Can you give us a little more detail on the input and output message structures and a sample input and output message so that your problem could be understood clearly?

Former Member
0 Kudos

HI,

My mappings are as follows:

The mapping for the input from the database is:

LeaveTable (complex type)

which includes a struture (element 0...unbounded)

with several fields (all element type string 0..unbounded) I hope this makes sense.

The mapping for the RFC is:

Leave Table contains several fields (this is brought in the the RFC import).

The fields on the table maps to the RFC table fields. (no funny mappings).

I hope this sheds more light.