none
Importing SAP BAPI as Generated Item - String Object RRS feed

  • Question

  • Am new to BizTalk, working on BT 2013 using Visual Studio 2012. Am adding a "generated item" for Z_BAPI_SALESORDER_CHANGE (using the "Consume Adapter Service" dialog) and am receiving the message below. Our ABAP programmer tells me it's type STRING which is causing the issue, but STRING is supposed to be an acceptable type (here: http://msdn.microsoft.com/en-us/library/dd787893%28v=bts.80%29.aspx). What am I missing?

    Appreciate the help!

    Microsoft.ServiceModel.Channels.Common.MetadataException: Retrieval of Type Metadata has failed while building WSDL at 'SAPTABLE/ZSSM_SO_HEADER_IN_CHANGE'

    ---> Microsoft.ServiceModel.Channels.Common.MetadataException: The SAP system returned error: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=UNSUPPORTED_TYPE.  AdapterErrorMessage=The RfcGetStructureInfoAsTable API returned the error code 2 when obtaining metadata for the type ZSSM_SO_HEADER_IN_CHANGE. Check the RFC SDK trace files for details.. when trying to retrieve metadata for table: ZSSM_SO_HEADER_IN_CHANGE.

    Monday, August 11, 2014 6:06 PM

Answers

  • Here's the answer: while working with the SAP programmer, it was NOT an ITAB II table that was the issue, but a STRING item "inside a structure" that was at fault. What is the difference? I don't know. Let's just suffice it to say that, in XML terms, the STRING elements must be under the root, not under any other element.
    • Marked as answer by MRDopita Tuesday, September 9, 2014 4:37 PM
    Tuesday, September 9, 2014 4:37 PM

All replies

  • Is it possible that your table is an ITAB II type table?
    Because that is not supported by the SAP Adapter in BizTalk, see the limitations list http://msdn.microsoft.com/library/dd787849(BTS.10).aspx

    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

    Monday, August 11, 2014 6:25 PM
  • Checked that. IT is not an ITAB II table.
    Monday, August 11, 2014 7:19 PM
  • Anybody else have any ideas?
    Monday, August 18, 2014 9:39 PM
  • I am just guessing. RFC destination in SAP has the option to use unicode or non-unicode. Maybe you can try different options.
    Tuesday, August 19, 2014 2:32 AM
  • Here's the answer: while working with the SAP programmer, it was NOT an ITAB II table that was the issue, but a STRING item "inside a structure" that was at fault. What is the difference? I don't know. Let's just suffice it to say that, in XML terms, the STRING elements must be under the root, not under any other element.
    • Marked as answer by MRDopita Tuesday, September 9, 2014 4:37 PM
    Tuesday, September 9, 2014 4:37 PM