Missing closing tag in message mapping

I have an RFC --> PI --> JDBC scenario with the following message mapping:

SOURCE --> TRIM --> mapWithDefault [] --> DESTINATION

If the source field doesn't come, the input XML is a follows:

<SOURCE/>

And after the mapping I obtain the following: <DESTINATION></DESTINATION> that is exactly what the reciever system is expecting. This was been working fine until the upgrade to ECC 6.0 of the Sender system. Actually I don't know if it has anything to do, because the RFC XML looks exactly the same, but the user claims it has stopped working since the upgrade.

Now the same mapping, with the same <SOURCE/> input creates this output: <DESTINATION/>. This is not accepted by the reciver system and throws an error.

What can be happening? The message mapping has not changed and the RFC XML looks exactly the same....any ideas?? Thanks! Pablo

Add comment

RFC XML looks exactly the same, but the user claims it has stopped working since the upgrade

Can you please try importing the RFC again and doing some dummy changes in the mapping .Might be meta data update issue.Also test the RFC from the SAP system once.similarly do some dummy changes in communication channel (like, edit channel and in the description field add some text or spaces and save and activate).Please test again and see if it works ..do the cache refresh also