The adapter "WCF-SAP" raised an error message. Details "Microsoft.ServiceModel.Channels.Common.XmlReaderGenerationException: The segment or group definition E2IDB02003 was not found in the IDoc metadata. The UniqueId of the IDoc type is: IDOCTYP/3/PEXR2002//740. For Receive operations, the SAP adapter does not support unreleased segments.

This is the error I get when the 2 segments below are in the SAP IDOC sent to BizTalk

Here is the Generated schema that I receive from SAP when I use the wizard.

Whenever I remove the segment from the SAP export the file processes successfully. I have been toying with this adapter a little over a week. When I remove the segment the message comes in as Typed XML and resolves to the proper schema.  

When I change ReceiveIDocFormat to string and used xpath I get an error :

Reason: Object reference not set to an instance of an object. 

How can I modify the schema so that it matches what SAP is exporting? Every configuration I try has some type of error unless I remove the segments. Unfortunately the segments are important and cannot be removed from the final version. What are my options?

 

• Edited by JordanJ08 Monday, January 26, 2015 11:46 PM

The actual problem is that the IDOC you are receiving is containing unreleased segments and that's not supported, you should contact your SAP administrator to get this problem resolved.

Alternatively, you can refer to his link for the workaround http://geekswithblogs.net/PsudoKnowledgeBase/archive/2011/02/06/conversion-of-biztalk-projects-to-use-the-new-wcf-sap-adaptor.aspx

As mentioned in the link getting the raw xml data in string format is the only workaround within BizTalk. The error Object reference not set to an instance of an object could be because your XPath expression may not be correct.

Rachit

I presume you are listening to rfc server to get idocs from sap. I would check below things for "unreleased segment"
Few things you need to check with SAP person:
-> Whey they haven't release the segment? They obviously have to release the segment which is present in idoc. 
-> You then have to use consume wcf service wizard to generate your idoc definition because your local schema copy is missing definition for E2IDB02003. Perhaps they added this segment and your adapter is not able to recognize it.
-> Another thing to check is permission, whether necessary permission for your BizTalk account is assigned or not.

Rachit

 How does unreleased segments affect other RFC using the IDOC? Does it release the segment for those RFCs as well? I want to know what I am talking about when I speak with the SAP admin. 

Hi Jordon,

I found this hotfix, see if this is handy for you.

Hotfix to add the "ReceivedIdocRelease" binding property for the WCF-SAP adapter to BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010

Refer the articles below to have more understanding on the issue you are facing.

Unreleased Segment Problem in SAP

Receiving multipe IDoc Releases from SAP

Rachit