This file provides important information about enhancements and fixes in webMethods SWIFT FIN Module 6.1 Service Pack 1. For information about enhancements and fixes in previous webMethods SWIFT FIN Module releases, see the readme for those releases.
1.0 Fixes and Service Packs Included in This Release
2.0 Enhancements
3.0 Resolved Issues
5.0 Added and Removed Services and APIs
6.0 Enhancements and Fixes in Previous Release
webMethods SWIFT FIN Module 6.1 Service Pack 1 includes the following fixes that were shipped since the last release:
- FIN_6-1_Fix1 through FIN_6-1_Fix18
For detailed information on these fixes and service packs for webMethods SWIFT FIN Module, see the Knowledge Base on the webMethods Advantage Web site.
webMethods SWIFT FIN Module 6.1 Service Pack 1 includes no new enhancements.
The issues listed below have been addressed in this release.
1-YHG5T (FIN_6-1_Fix1)
The SWIFT FIN Module fails to parse raw
FIN messages on IS 6.5.
This is due to changes in the underling XERCES DOM parsing classes used in the Integration
Server 6.5 platform. The issue has been corrected so that webMethods SWIFT FIN
Module 6.1 now parses raw FIN message correctly on both IS 6.1 and IS 6.5.
1-Z7NKZ (FIN_6-1_Fix2)
webMethods SWIFT FIN Module fails to
parse an MT535 message.
When parsing an MT535 message through the wm.fin.format:convertFINToIData service, the following error is
thrown:
com.wm.app.b2b.server.ServiceException: Error in parsing the object.
Additionally, the data remains unprocessed after parsing. The remaining data is:
:93B::AVAI//UNIT/700,
:19A::HOLD//USD10
However, the message is correct. Message template file has been corrected to address this issue.
1-ZC0NB (FIN_6-1_Fix3)
After adding or updating the Bank
Identification Code (BIC) in the
This error occurs because the SWIFT
FIN Module does not update the HostBic variable after
changes have been made to the BIC code in the
Now, whenever the BIC in the
1-10WAJT (FIN_6-1_Fix4)
Loading the WnFINSamples package on Integration Server 6.5 causes a java.lang.VerifyError exception.
The webMethods SWIFT FIN Module 6.1 contains a class file (migration.class) that is not compatible with the JVM version used by Integration Server 6.5. This causes the WmFINSamples package to not load properly.
This issue is resolved and the WmFINSamples package loads correctly on Integration Server 6.5.
1-11DNGR (FIN_6-1_Fix5)
When invoking the SWIFT FIN Module wm.fin.validation:validateIDataUtil service for an MT210 message, the 52A field is marked as invalid.
This error occurs because the SWIFT FIN Module does not correctly parse the 52A field, and throws a T34 error when the field's value contains only the BIC code. The SWIFT documentation states that the 52A field should be 52A:BIC and not 52A://BIC. 52A:BIC is also what the gateway expects.
This issue is resolved and the SWIFT FIN Module validation engine correctly parses the 52A field.
1-129U09 (FIN_6-1_Fix6)
After importing message types MT520 (nov02), MT521 (nov02), and MT540 (may05), the resulting IS document types do not contain subfields for some fields.
These subfields are missing because the DFDs for these message types are not complete. Fields 33V, 77R, 34G, 34H, 71E, 13B::LINK, 92F::RSPR, 22F::NETT, 22F::CCPT are missing from the corresponding DFDs.
This issue is resolved and the imported document types now contain all the fields.
1-11XW4Z (FIN_6-1_Fix6)
When invoking the SWIFT FIN Module wm.fin.format.convertFINToIData service for a FIN message with trailer fields in random order, a parse error is thrown.
This error occurs because the SWIFT FIN Module expects trailer fields in a particular order. However, it should expect these fields in any order.
This issue is now resolved. By converting the trailer block into a list for all the message types, the SWIFT FIN Module can now accept trailer fields in any order.
1-135LEH (FIN_6-1_Fix7)
Error T27 received when SWIFT FIN Module parses nov02 57A field in an MT103 message.
When invoking the SWIFT FIN Module wm.fin.validation:validateIDataUtil service for an MT103 message containing field 57A or other fields containing an optional Party Identifier followed by BIC Code, these fields are marked as invalid.
This error occurs because the SWIFT FIN Module does not correctly parse these fields when an optional Party Identifier is present. The validation logic for Party Identifier is not correct and always returns false.
This issue is resolved.
1-146XKM (FIN_6-1_Fix8)
In webMethods SWIFT FIN Module 6.1, the wm.fin.dfd:convertTagFormat service hangs occasionally.
The wm.fin.dfd:convertTagFormat service in webMethods SWIFT FIN Module 6.1, hangs when invoked in another flow service. This problem occurs when the BIC table is not present in the Trading Networks database.
The wm.fin.dfd:convertTagFormat service internally invokes the BIC validation to obtain a data store connection. If the BIC table is not present, an exception is thrown and the connection is not freed up. Thus when invoking this service several times, the connection pool is exhausted and the service hangs.
This issue is resolved by handling the exception thrown.
1-145JPM (FIN_6-1_Fix8)
In webMethods SWIFT FIN Module 6.1, the wm.fin.dev:importFINItems service when executed with message type as 572, few sub-fields in the IS Doc type are missing.
In webMethods SWIFT FIN Module 6.1, when executing the wm.fin.dev:importFINItems service with message type as 572, the following fields in the IS Doc type do not have sub-fields:
- SB2/60A
- SB2/SB1/60B
- SB2/SB1/SB1/66A
- SB2/SB1/SB1/34C
- SB2/SB1/SB1/34D
- SB2/62A
These sub-fields are missing because the data field definitions for these fields are not present in the dfdmt000.xml file.
This issue is resolved. The required data field definitions have been added to the <IntegrationServer>/packages/WmFIN/config/dfdmt000.xml file.
1-14K48T (FIN_6-1_Fix9)
In webMethods SWIFT FIN Module 6.1, the wm.fin.dev:importFINItems service when executed with message type 535, some of the fields are not named as per SWIFT standards.
In webMethods SWIFT FIN Module 6.1, when executing the wm.fin.dev:importFINItems service with message type 535, the following fields in the IS Doc type are named incorrectly:
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/34B:MILT
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/34B:SIZE
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/34B:ORGV
As per SWIFT standards, the fields should be named as:
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/36B:MILT
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/36B:SIZE
- 16R:SUBSAFE[0]/16R:FIN[0]/16R:FIA[0]/SB8[0]/36B:ORGV
This issue is now resolved. The required data field definitions have been corrected in the <IntegrationServer>/packages/WmFINDev/import/may05/swiftmt535.xml file.
1-14QBSW (FIN_6-1_Fix9)
In webMethods SWIFT FIN Module 6.1, the wm.fin.dev:importFINItems service when executed with message type 535, few sub-fields in the IS Doc type are missing.
In webMethods SWIFT FIN Module 6.1, when executing the wm.fin.dev:importFINItems service with message type 535, the following fields in the IS Doc type do not have sub-fields:
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::CLEN
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::DIRT
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::DRAW
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::MARG
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::OTHR
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PDMT
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PDUM
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PRMT
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PRUM
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PECA
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::PLED
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::RSTR
- 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/:93B::UNRG
These sub-fields are missing because the data field definitions for these fields are not present in the dfdmt000.xml file.
This issue is now resolved. The required data field definitions have been added to the <IntegrationServer>/packages/WmFIN/config/may05/dfdmt000.xml file.
1-14NHI3 (FIN_6-1_Fix9)
In webMethods SWIFT FIN Module 6.1, on executing the service wm.fin.format:convertFINToIData, unwanted debug messages are logged into the server log.
In webMethods SWIFT FIN Module 6.1 that has the FIN_6-1_Fix6 installed, the service wm.fin.format:convertFINToIData when executed, unwanted messages are logged into the server log.
This issue is now resolved.
1-14OMVB (FIN_6-1_Fix9)
In webMethods SWIFT FIN Module 6.1, when executing the service wm.fin.dfd:convertBizNameFormat with FIN message type 543, the output message format for the field 94F::SAFE is incorrect.
When executing the service wm.fin.dfd:convertBizNameFormat with message type 543, the output message for the field 94F::SAFE contains an extra slash(/) which is incorrect.
This issue is now resolved by modifying the data field definition for the field 94F::SAFE.
1-14NPGI (FIN_6-1_Fix10)
In webMethods SWIFT FIN Module 6.1, the service wm.fin.format:convertFINToIData service when executed with message type 523 or 519, and with values YLD, PCT, or REN in the field 33T, throws a parse error.
In webMethods SWIFT FIN Module 6.1, the service wm.fin.format:convertFINToIData when executed with message type 523 or 519, and with values YLD, PCT or REN in the field 33T of the IS doc type, a parse error is thrown. Only the standard currency codes in the 33T field are accepted. This happens because the data field definition for the field 33T does not contain the values YLD, PCT, and REN.
This issue is now resolved. The values YLD, PCT, and REN for the field 33T have been added in the following dfd files:
<IntegrationServer>/packages/WmFINDev/import/nov02/dfdmt523.xml
<IntegrationServer>/packages/WmFINDev/import/nov03/dfdmt523.xml
<IntegrationServer>/packages/WmFIN/config/may05/dfdmt000.xml
<IntegrationServer>/packages/WmFIN/config/nov02/dfdmt000.xml
<IntegrationServer>/packages/WmFIN/config/nov03/dfdmt000.xml
1-14NPED (FIN_6-1_Fix10)
In webMethods SWIFT FIN Module 6.1, when executing the service wm.fin.format:conformIData with message type 571, the sub-fields for few output fields are duplicated.
When executing the service wm.fin.format:conformIData with message type 571, the sub-fields for few output fields are duplicated. This happens in cases where the IS doc type has a field that has two sub-fields with the same name, and the service's input record finIData has only one value for one of the sub-fields. For example, consider that the field SBA/67A in the IS doc type has two sub-fields with the same name Date2:
SBA/67A/DATE2
SBA/67A/DATE2
and the input record finIData for the service has a value for the first Date2 sub-field:
SBA/67A/DATE2
The wm.fin.format:conformIData service misinterprets this value to be the value for both the sub-fields of the IS doc type and thus updates both the fields with the same value, which is incorrect.
This issue is now resolved.
1-17IV6D (FIN_6-1_Fix11)
SWIFT FIN Module needs to add support to SWIFT 2006 messages.
Every year, SWIFT revises the rules for parsing and validating the FIN message syntax. Therefore, the webMethods SWIFT FIN Module needs to include the new message standard released by SWIFT for the year 2006.
This issue is now resolved. SWIFT FIN Module includes the updated 2006 message definitions as a new message version -'nov06'. These new messages will appear in the Integration Server namespace in wm.fin.doc.nov06.
1-152QS7 (FIN_6-1_Fix11)
In the webMethods SWIFT FIN Module 6.1, when the wm.fin.format:convertIDataToFIN service is executed, an ArrayIndexOutofBoundsException exception is thrown.
When the wm.fin.format:convertIDataToFIN service is executed with the 541 message type and with only one line in the 35B field, an ArrayIndexOutofBoundsException exception is thrown.
This exception is due to erroneous handling of the array records containing empty data by the convertIDatatoFIN service.
This issue is resolved. The convertIDatatoFIN service now correctly handles the array records with empty data.
1-16024V (FIN_6-1_Fix11)
In the webMethods SWIFT FIN Module 6.1, when the wm.fin.format:convertBizNameFormat service is executed, the resulting output is incorrect.
When the wm.fin.format:convertBizNameFormat service is executed with the 572 (nov02) message type, the resulting formatted output contains '//' prefixed to the 60A, 60B, 62A,and 62B fields. This is because the data field definitions of these fields in the WmFIN/config/dfd/nov02/dfdmt000.xml file are incorrect.
This issue is now resolved by correcting the data field definitions.
1-17QD6P (FIN_6-1_Fix11)
In the webMethods SWIFT FIN Module 6.1, when the wm.fin.format:convertBizNameFormat service is executed, the resulting output contains erroneous field 35B.
When the service wm.fin.format:convertBizNameFormat is executed with subFieldFlag set to 'true' with the 521 (nov02) message type, field 35B is incorrectly split in the resulting output. This is because the first line of the field is assumed to be an ISIN code which is incorrect.
This issue is now resolved.
1-18DORN (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module, a field is missing in the MT535 document.
A field in the MT535 document for May05 has an incorrect tag 95A instead of 92A in all the elements of the "16R:SUBSAFE_Block - Sub-safekeeping Account[0]/16R:FIN_Block – Financial Instrument[0]/16R:FIA_Block - Financial Instrument Attributes[0]/SB4/" field.
This issue is now resolved. The incorrect tag, 95A is corrected to 92A in the "16R:SUBSAFE_Block - Sub-safekeeping Account[0] /16R:FIN_Block - Financial Instrument[0]/16R:FIA_Block - Financial Instrument Attributes[0]/SB4/" field.
1-18DOX7 (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module, a field is missing in the MT548 document.
After generating the MT548 document for may05, the "16R:SETTRAN_Block - Settlement Transaction Details/SB4/" field is missing the 94C field. The SWIFT documentation mentions that the 94C field should be present.
This issue is now resolved. The 94C field is added to the "16R:SETTRAN_Block - Settlement Transaction Details/SB4/" field.
1-18DOV9 (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module, a field is missing in the MT586 document.
In the MT586 document for May05, the 13B field is missing in the "16R:ALLDET_Block - Allegement Details[0]/16R:LINK_Block - Linkages/" field. This is incorrect according to the SWIFT specification.
This issue is now resolved. The 13B field is added to the "16R:ALLDET_Block - Allegement Details[0]/16R:LINK_Block - Linkages/" field.
1-188KKT (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module 6.1, some fields and qualifiers are missing in the MT578 document.
In the webMethods SWIFT FIN Module 6.1, the MT578 document has a missing "(44) Field 92a: Rate Option F :4!c//3!a15d (Qualifier) (Currency Code) (Amount)" field. Also the "MT578: (50) Field 22F: Indicator" field has missing qualifiers like "REST, SETS, NETT, CCPT, LEOG".
The issue is resolved now. The missing qualifiers and fields are added.
1-18EO6D (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module 6.1, in the MT548 document the tags 25D & 24B and their qualifier's [SETT] reason codes are ignored by the wm.fin.dfd.convertTagFormat service.
In the webMethods SWIFT FIN Module 6.1, in the MT548 document, the tags 25D & 24B qualifier's [SETT] reason codes are ignored by the wm.fin.dfd.convertTagFormat service. When the data with the tag 25D qualifier SETT with reason codes is processed by the service, it results in the reason codes being ignored; i.e. 25D::SETT//PEND becomes 25D::SETT and 24B::PEND//DKNY becomes 24B::PEND.
The issue is resolved now. The incorrect field definition for the document MT548 is corrected.
1-188KLK (FIN_6-1_Fix12)
In the webMethods SWIFT FIN Module 6.1, after the Integration Server is restarted, the wm.fin.dfd.convertTagFormat service fails when it uses the MT541 message type of may05 specification.
In the webMethods SWIFT FIN Module 6.1, the wm.fin.dfd.convertTagFormat service fails when it uses the MT541 message type after the Integration Server is restarted. This is because the empty dfdmt541.xml throws an exception.
This issue is resolved. The dfdmt541.xml now contains the field specifications.
1-18EJU7 (FIN_6-1_Fix13)
In the webMethods SWIFT FIN Module 6.1, when the wm.fin.format:convertFINToIData service is executed with MT537 message type as input, an error is thrown.
In the webMethods SWIFT FIN Module 6.1, when the wm.fin.format:convertFINToIData service is executed with MT537 message type as input, an error "Mandatory field TRAN is missing from the message OR field null is invalid or in the wrong place" is thrown. The Parser is taking wrong definition of STAT block assuming it should contain TRAN block. This is because there are 2 definitions of STAT block, one at the top level, another within TRANS block. The Parser is taking the top level definition in every case.
This issue is now resolved by correcting the parser logic.
1-19QQVE (FIN_6-1_Fix14)
In the webMethods SWIFT FIN Module, the 20C::PROC field of the MT548 document for may05 and nov06 versions is incorrectly placed.
In the webMethods SWIFT FIN Module, the 20C::PROC field of the MT548 document for may05 and nov06 versions is incorrectly associated with the SETTRAN block (Sequence B Settlement Transaction Details) instead of SETPRTY block (Repetitive Optional Subsequence B1 Settlement Parties).
This issue is now resolved.
1-1A2S23 (FIN_6-1_Fix14)
In the webMethods SWIFT FIN Module, the 35B field does not parse correctly.
In the webMethods SWIFT FIN Module, the 35B field containing a '&' in the 4*35x description field does not get parsed. This is because the validation utility for this field is missing the '&' in the list of acceptable characters.
This issue is now resolved.
1-1A2S50 (FIN_6-1_Fix14)
In the webMethods SWIFT FIN Module, the fields containing an optional negative sign followed by the Currency codes do not parse correctly.
In the webMethods SWIFT FIN Module, the fields containing an optional negative sign followed by the Currency codes do not parse correctly if the code starts with a 'N'. This is because the parser misunderstands the first character 'N' as a negative sign.
This issue is now resolved.
1-1AH3PF (FIN_6-1_Fix15)
In the webMethods SWIFT FIN Module, the fields containing [/1!a] [/34x] party identifier pattern are not getting parsed correctly.
In the webMethods SWIFT FIN Module, the fields containing [/1!a] [/34x] party identifier pattern are not getting parsed correctly when the value of the field begins with the character 'C' or 'D'.
This is because the field definitions in the DFDs are not correct. Such fields need to be handled by a special function called 'BICPLUS' defined in the FIN Module. Therefore, the DFD's need to be updated to contain a reference to this function for all such fields in every message type.
This issue is now resolved. Any fields that contains the party Identifier pattern [/1!a][/34x] have been updated to validate correctly across all message types. After applying this fix the structure of such message documents will change. Now such fields will have following structure
Field->
BICPLUS->
CHOICE->
Party Identifier->
1!a
34x
1-1AKG3K (FIN_6-1_Fix15)
In the webMethods SWIFT FIN Module, the 35B field is not allowing arbitrary strings in the first line of the description field.
In the webMethods SWIFT FIN Module, the 35B field is not allowing arbitrary strings in the first line of the description field. It allows only strings starting with 'ISIN' or '/xx/', where xx represents two letter country code. The Parsing logic for 35B field needs to be corrected.
This issue is now resolved.
1-1AKG5T (FIN_6-1_Fix15)
In the webMethods SWIFT FIN Module, the field 95P::SELL is spelled incorrectly in the document type MT542.
In the webMethods SWIFT FIN Module, the field 95P::SELL is spelled incorrectly in the document type MT542 as :95P::SELL.
This issue is now resolved.
1-1AQKCH (FIN_6-1_Fix16)
In the webMethods SWIFT FIN Module, when the wm.fin.dfd.convertBIZNameFormat service is run on a FIN IData, the resulting output eliminates the 35B fields that contain only the description fields.
In the webMethods SWIFT FIN Module, when the wm.fin.dfd.convertBIZNameFormat service is run on a FIN IData that has a 35B field, which does not contain the ISIN/NON-ISIN fields, the resulting output eliminates these 35B fields. This is because the subfield format convertor assumes that it is mandatory for the 35B fields to begin with the ISIN or NON-ISIN fields, and the resulting output string returns a null. The ISIN/NON-ISIN fields should be made optional and not mandatory.
This issue is now resolved.
1-1AY3YR (FIN_6-1_Fix17)
In the webMethods SWIFT FIN Module, the 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/93B::BLOK field in the MT535 document type does not contain the subfields.
In the webMethods SWIFT FIN Module, the 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/93B::BLOK field in the MT535 document type does not contain the subfields. The field definition of the 16R:SUBSAFE/16R:FIN/16R:SUBBAL/SB2/93B::BLOK field is missing in the dfd list.
This issue is now resolved.
1-1AKKJL (FIN_6-1_Fix17)
In the webMethods SWIFT FIN Module, the message types ranging from 960 to 967 are not generated.
In webMethods SWIFT FIN Module, the message types ranging from 960 to 967 are not generated because the XML parsing templates for these message types are missing.
This issue is now resolved.
1-1DIL84 (FIN_6-1_Fix18)
In the webMethods SWIFT FIN Module, the fields containing [/1!a][/34x] party identifier pattern are not parsed correctly.
In the webMethods SWIFT FIN Module, the fields containing [/1!a][/34x] party identifier pattern are not parsed correctly when the value of the field begins with a '/' character. This is because the sub-field utility does not understand the '/' character.
This issue is now resolved by correcting the sub-field logic.
None.
To view information about the previous release of webMethods SWIFT FIN Module, see the previous readme on the webMethods Bookshelf.
SWIFTFIN-E&F-61-20061215