Skip to Content

B2B add-on inbound XML root node

Hi Guys,

I'm working on a "ANSI X12 810" to IDOC scenario.

Everything looks good, but I noticed that the payload from EDISeparator (which will go through my operational mapping), has this XML structure with root node <ns:ASC810_004010......>. root-node.jpg

This caused an error in the mapping since I have defined my source message type with a different name, which I fixed by parsing it through a XSL mapping first.

But I'm curious to know where it's pulling this "ASC810_004010" and if it's something we cane change.

Thanks,

~Jay

root-node.jpg (29.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Jan 18 at 12:55 PM

    Hi Jay,

    "ASC810_004010" is the name that would be generated for the data type if you use the B2B cockpit to create the .xsd schema. You can alter the generated content but IMO the name tells you everything you need to know about the message type including the version number so I'm not sure why you would prefer to alter it.

    Regards,

    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 18 at 04:33 AM

    Hello Jay,

    How you generated the source XSD ,using B2B cockpit?

    You might need to change the XSD before importing it.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Raghu,

      Thanks a lot for your feedback.

      I try doing this, and it didn't work.

      Please see my reply to Ryan.

      ~ Jay