WCF-SAP Nco Connector creates additional white spaces in BizTalk Server
When you use the WCF-SAP Nco connector type (the .NET Framework connector) in BizTalk Server 2013 R2, additional padding (white spaces) is added and sent to SAP.
When an IDOC Receive operation occurs, text fields are padded with white spaces of a length that is equal to that field length. For example, the OBJECT_KEY element is defined by SAP as a 50-character string.
When you use classic RFC as in the following example, no trailing white spaces are added:
However, when you use the Nco connector type, trailing white spaces are added, as in the following example:
This issue occurs because the new Nco adapter is missing end-trimming functionality to exclude additional white spaces.
Cumulative update informationThe fix that resolves this issue is included in Cumulative update package 4 for BizTalk Adapter Pack 2013 and Cumulative update package 5 for BizTalk Server 2013 R2.
Note After you apply this update, the IDOC will be trimmed the same as when you use classic RFC.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about service pack and cumulative update list for BizTalk Server.
Learn about BizTalk Server hotfixes and cumulative update support.
Article ID: 3197184 - Last Review: 11/14/2016 04:54:00 - Revision: 2.0
Microsoft BizTalk Server 2013 Branch, Microsoft BizTalk Server 2013 Developer, Microsoft BizTalk Server 2013 Enterprise, Microsoft BizTalk Server 2013 R2 Branch, Microsoft BizTalk Server 2013 R2 Developer, Microsoft BizTalk Server 2013 R2 Enterprise, Microsoft BizTalk Server 2013 R2 Standard, Microsoft BizTalk Server 2013 Standard, Microsoft BizTalk Adapter Pack 2013
- kbqfe kbsurveynew kbfix kbexpertiseinter KB3197184