Skip to Content
avatar image
Former Member

Missing closing tag in message mapping

Hi experts,

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
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    Jun 22, 2010 at 05:30 PM

    Hi Pablo,

    Try to stop and start again RFC communication channel in RWB (communication channel monitoring).

    transaction sxmb_ifr
    
    Integration Monitoring (Runtime workbench) -> Component Monitoring -> Display
    
    Expand the tree, and choose Adapter Engine in Integration Server
    
    Choose Communication Channel Monitoring, use filter as it is, and check RFC communication channels

    Best Regards,

    Pedro Pereira

    Edited by: Pedro Pereira on Jun 22, 2010 7:39 PM

    Edited by: Pedro Pereira on Jun 22, 2010 7:50 PM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 22, 2010 at 05:44 PM

    Hi Pablo,

    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

    Regards,

    Srinivas

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 22, 2010 at 07:17 PM

    Please reimport the RFC and then clear CPA Cache.

    That should solve your problem.

    Thanks,

    Hetal

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 22, 2010 at 08:06 PM

    >. This is not accepted by the reciver system and throws an error.

    What is the error?

    If you use JBDC adapter, it is no difference, whetehr you have <tag></tag> or <tag />, because this is the same.

    Add comment
    10|10000 characters needed characters exceeded

    • > Hi Venu, I have just checked. In the XML from the ECC6.0 RFC I'm getting the input as <SOURCE></SOURCE>.

      When the source tag is available, then mapwithdefault paases the empty node.

      So the change in your scenario was:

      First: source was missing, so mapwithdefault provided default value ' '

      second: source is availble, but empty, so the empty string is passed to target.

      in my proposol when I wrote "then" I meant to use the "if" function. do constant space to then branch. the source - mapwithdefault to else branch.

  • avatar image
    Former Member
    Jun 22, 2010 at 09:23 PM

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

    I faced the same problem after upgrade so I used MapWithDefault in my mapping to generate the empty tags. Go through this thread it may help you..

    After Upgrade to ECC, Proxy is not sending empty tags to XI

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 23, 2010 at 08:10 PM

    We couldn't fix it...we figured out a workaround 😔

    Add comment
    10|10000 characters needed characters exceeded