Article ID: 923531 - View products that this article applies to.
When you use the Microsoft BizTalk Server 2004 Flat File Assembler (FF ASM) to serialize and then send a SWIFT FIN message to SWIFT, SWIFT receives the message as expected. However, some field contents may be truncated. Characters may be missing from certain fields in the message.
You experience this problem if the following conditions are true:
This problem occurs because the Flat File Serializer component currently forces the .xml file to comply with the SWIFT schema specifications.
For example, consider the following scenario:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesNo prerequisites are required to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThe Microsoft.BizTalk.Pipeline.dll file that is included in this hotfix replaces the Microsoft.BizTalk.Pipeline.dll file from the hotfix that is mentioned in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/908023/ )FIX: Per-instance pipeline configuration does not work as expected in BizTalk Server 2004
Hotfix implementation informationFor detailed information about how to use the functionality that this hotfix provides, see the "More Information" section.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix makes a change to the parser. This change adds a new Boolean positional field annotation that is named trim_field. The trim_field field annotation lets you suppress field coercion without modifying the padding behavior of the parser.
The value of the trim_field field annotation is true if the field is not present or if the field is not located. When the value of the trim_field field annotation is false, the parser does not perform the field trimming process before the parser serializes the particular field. You must manually add the trim_field="false" field annotation to the <FieldInfo> element of any field for which you want to prevent field coercion in the SWIFT Base Types.xsd schema.
When you add the trim_field="false" field annotation, this annotation does not affect field padding of fixed length fields that have less than the maximum number of characters.
Note This annotation does not have a corresponding design-time user-interface option in the schema editor. You must modify this annotation directly in the schema and in the field according to your requirements.
ExampleThe following example illustrates how to use the functionality that this hotfix provides.
Note To use the functionality that this hotfix provides, you must identify the exact XML location of the field that you want to modify. One method to identify this XML location is to use the XML pipeline to create a send port, and then use the send port to generate the XML representation of the message. Then, locate the field in the XML representation of the message.
In the XML representation of this message, locate the field for which you want to prevent field coercion. In this example, you want to prevent field coercion on the following field of all MT543 messages:
SequenceE1, Party_E1_95P, BankIdentifierCode, BranchCodeTo prevent field coercion of this field, follow these steps:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 923531 - Last Review: October 9, 2011 - Revision: 2.0