Skip to Content
avatar image
Former Member

Message Mapping issue in Multi-Mapping


Hi Folks,

    I am encountering a "Message Root-Tag" error in one of my scenarios. I have a proxy to Soap scenario. I am have implemented a multi mapping, but I am having the above said error. I followed the below blog but still the error occurs.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?overridelayout=t…

the below is the structure I see when I test the interface mapping in the ESR

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

<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">

   <ns0:Message1>

      <ns1:TransactionalData_ECC xmlns:ns1="http://Softel.com/xi/SOFTEL_SC_PLANNING/GPEO/TransactionalData">

         <Header_Data>

            <RecipientId/>

            <ControlNumber/>

            <MessageId/>

            <DocumentType/>

            <DateSent/>

         </Header_Data>

         <Body_Data>

            <DocumentType/>

            <Version/>

            <Date/>

            <Attachments>

               <Attachment>

                  <Href/>

                  <FileName/>

                  <FileType/>

                  <FileCreateDate/>

                  <FileSize/>

               </Attachment>

            </Attachments>

         </Body_Data>

      </ns1:TransactionalData_ECC>

   </ns0:Message1>

</ns0:Messages>

The Below is the payload I get in the runtime when I execute the proxy

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

  <nm:TransactionalData_ECC xmlns:nm="http://Softel.com/xi/SOFTEL_SC_PLANNING/GPEO/TransactionalData" xmlns:prx="urn:sap.com:proxy:FI0:/1SAI/TAS097D92A93F9E8143C96A:731">

  <Header_Data>

  <RecipientId>SOFTELINC</RecipientId>

  <ControlNumber>0000000000000001</ControlNumber>

  <MessageId />

  <DocumentType>SoftelOrder</DocumentType>

  <DateSent>20140119204641</DateSent>

  </Header_Data>

  <Body_Data>

  <DocumentType>SoftelOrders</DocumentType>

  <Version>1.0</Version>

  <Date>20140119204641</Date>

  <Attachments>

  <Attachment>

  <Href>Wi1234uKjYTmbx2{ReJ</Href>

  <FileName>E2Open_Attachment_20140119204641</FileName>

  <FileType>.txt</FileType>

  <FileCreateDate>20140119204641</FileCreateDate>

  <FileSize>200</FileSize>

  </Attachment>

  </Attachments>

  </Body_Data>

  </nm:TransactionalData_ECC>

Can somebody let me know where I am going wrong

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jan 20, 2014 at 05:21 AM

    Hello,

    Where exactly u are getting message-root-tag error?

    >>The Below is the payload I get in the runtime when I execute the proxy

    BTW, at runtime PI will add messages/message1 node and split messages. So don't worry abt that.

    Thanks

    Amit Srivastava

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Amit Srivastava

      Hi Amit,

          I have another issue in the attachment. Now the attachment & the payload are flowing nicely to the webservice but there they are having a parsing issue. The reason what causes parsing error at their end is the sequence of attachment & payload being sent by XI.

      The current sequence of payload & attachment is

      1. Attachment

      2. MainDocument(Payload)

      Rather the way it's expected is

      1. MainDocument

      2. Attachment

      I have already created a new thread for this requirement, if you can help me here then you can reply to the below thread

      http://scn.sap.com/thread/3486032

  • avatar image
    Former Member
    Jan 20, 2014 at 05:29 AM

    Hi,

    While doing testing at message mapping level you need to explicitly add the additional namespace tags ns0 & ns1 ..or in other way use the generated sample test message as is and place your payload as per the namespaces generated...where as runtime this will be taken care automatically you need to pass the xml message in normal way i.e. no need to add the additional namespace messages..

    Messages you pasted as is as per expected behavior only...

    where exactly you are getting the error provide more info on that..

    HTH

    Rajesh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Rajesh,

          I am not sure where exactly the error is happening in the Message mapping or in the XSLT mapping. But one thing I observed is when I remove the XSL mapping or change anything in the mapping then I get the error "Integration Engine: general Error" with the description "Use case DUPLICATE_CONTENT_IDS not recognized". If I use the XSL then the error changes to "Mapping: General Error" with the description "Messages Root-tag".

      Regards,

        Santosh

  • avatar image
    Former Member
    Jan 20, 2014 at 06:02 AM

    Just a quick question, how do I check wheather SAP has really added the Messages & Message1 Tag to the message


    Add comment
    10|10000 characters needed characters exceeded

    • Hi santosh,

      i think you can not see it in the message monitoring as it happens in the runtime.

      you can test the same in test configuration in ID if you are in dual stack.

      like without giving Message1 tags.

      but still no way to see those tags.

      Regards,

      Muniyappan.