none
Receiving SAP IDOC via WCF SAP Adapter as string results in unexpected elements RRS feed

  • Question

  • We are using SAP IDoc schemas which were generated with BTS 2006 R2 and have configured the WCF binding property receiveIdocFormat to String. However, the data contains more elements than is expected.

    The image below illustrates the issue. In this case the SAP IDOC has 4 E1EDL37 segments with child elements, e.g., E1EDL37 and E1EDL44. However, corresponding BizTalk XML has 14 E2EDL37005GRP.

    

    What is causing each of the child elements from SAP to be created within individual E2EDL37005GRP elements?

    Is this a bug or am I missing something obvious?

    Note: BizTalk Adapter Pack 2010 CU2 is applied, along with BizTalk Server 2010 CU4.

    Friday, October 11, 2013 9:35 PM

Answers

  • Hi,

    Please refer the information which might be helpfull:

    http://blogs.msdn.com/b/adapters/archive/2007/10/05/receiving-idocs-getting-the-raw-idoc-data.aspx

    http://go4answers.webhost4life.com/Example/wcf-custom-sap-adapter-picking-latest-32633.aspx

    • Marked as answer by Pengzhen Song Friday, October 18, 2013 11:39 AM
    Tuesday, October 15, 2013 2:03 AM

All replies

  • Hi,

    Please refer the information which might be helpfull:

    http://blogs.msdn.com/b/adapters/archive/2007/10/05/receiving-idocs-getting-the-raw-idoc-data.aspx

    http://go4answers.webhost4life.com/Example/wcf-custom-sap-adapter-picking-latest-32633.aspx

    • Marked as answer by Pengzhen Song Friday, October 18, 2013 11:39 AM
    Tuesday, October 15, 2013 2:03 AM
  • Hi, yes this is unusual - perhaps it is the tool used to display the Xml.

    Can you try this with Typed instead of string? - that should give you a different Xml but it may require a re-map.

    You may have to pull that Schema again.

    Can you post a screenshot of the receive location configuration and bindings (from the gui) 


    mark

    Thursday, October 17, 2013 6:48 AM
  • Thanks for the feedback. It seems the issue was with outdated DELVRY03 IDOC schema, pulling the latest version from SAP has fixed the issue.
    Monday, October 21, 2013 9:01 PM