Fix Readme
Abstract
This document contains the fix list information for Financial Transaction Manager for High Value Payments for Multiplatforms
Content
Fix List for Financial Transaction Manager for High Value Payments (HVP)
This document contains fix list information for Financial Transaction Manager for High Value Payments for Multiplatforms
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
| V.R.M.F fix list | Links to Fix Central download (by Fix ID) |
Product | Build Date | Prerequisites |
| 3.2.10.2 interim fix 5 | 3.2.10.2-FTM-HVP-MP-iFix0005 | High Value Payments | 20230327-1030 | 3.2.10.2 |
| 3.2.10.2 interim fix 4 | 3.2.10.2-FTM-HVP-MP-iFix0004 | High Value Payments | 20230302-0752 | 3.2.10.2 |
| 3.2.10.2 interim fix 3 | 3.2.10.2-FTM-HVP-MP-iFix0003 | High Value Payments | 20230203-0125 | 3.2.10.2 |
| 3.2.10.2 interim fix 2 | 3.2.10.2-FTM-HVP-MP-iFix0002 | High Value Payments | 20221019-1108 | 3.2.10.2 |
| 3.2.10.2 interim fix 1 | 3.2.10.2-FTM-HVP-MP-iFix0001 | High Value Payments | 20220930-0951 | 3.2.10.2 |
| 3.2.10.2 | Available from Passport Advantage | High Value Payments | 20220729-1856 | FTM 3.2.10.1 (Base) |
| 3.2.9.0 | Available from Passport Advantage | High Value Payments | 20211213-1035 | None |
For more information about issues and changes, see Release Information for Financial Transaction Manager for High Value Payments.
Note: The update instructions referred to by interim fixes are located in the installation location\component\doc folder, for example:
installation location\shared\v3210\pfs\Gateway\doc\updates.
| Back to top | 3.2.10.2 interim fix 5 |
| Fix number | Type | Description |
| 144421 | Defect | Problem: CBPR+ PACS.009 Fails to Convert to MT202. Resolution: Added code to truncate the Name field to 65 characters. |
| 144572 | Defect | Problem: Resend operator action fails and causes MapAbort event. Resolution: Fixed issue in routing mapper what this is invoked from MapAndPutPTToQueue. |
| 144641 | Defect | Problem: Pacs004 is not getting completed in case the file has PrvsIntgAgt1 is present. Resolution: Fixed the code to check for duplicates before inserting record into the ID_REFERENCE table. |
| Back to top | 3.2.10.2 interim fix 4 |
| Fix number | Type | Description |
| 144200 | Defect | Problem: CBPR+ PACS.009 with Category Purpose Code of CORT Fail to Convert to MT202. Resolution: MT202 should be generated and tag 72 should have six lines with max 35 characters including slashes (or less as per data), 6th line should end with +(as a 35th char) and rest of data should be truncated. |
| Back to top | 3.2.10.2 interim fix 3 |
| Fix number | Type | Description |
| DT178842 | Defect | MT103/MT202 block 3 field 111 not mapped correctly in pacs.008/9. |
| 140774 | Defect | Problem: pacs.002 to channel for outgoing camt.056 missing OrgnlEndToEndId. Resolution: Fix provided to avoid missing OrgnlEndToEndId. |
| 142177 | Defect | Problem: Outgoing MT202 COV fails to be sent to CSM due to outbound mapping error. Resolution: Fix provided to correct outbound mapping error. |
| 142250 | Defect | Problem: Outbound pacs.009 with InstrForNxtAgt tag results in invalid ISF. Resolution: Fix provided to avoid invalid ISF creation. |
| 142475 | Defect | Problem: Outbound pacs.008 Purp tag is being dropped. Resolution: Fix provided to display Purp tag is in the output file. |
| Back to top | 3.2.10.2 interim fix 2 |
| Fix number | Type | Description |
| DT169387 | Defect | Impact analysis on inclusion of STEP1 payments (ERP Ccode). |
| DT169414 | Defect | pacs.008 to MT103: does not fully map Field 72 |
| DT170056 | Defect | pacs.009 to MT202 is failing with illegal arguments for SUBSTRING functions |
| Back to top | 3.2.10.2 interim fix 1 |
| Fix number | Type | Description |
| 138772 | Defect | Problem: A Financial Transaction Manager for High Value Payments NACK ISF that was created in response to a duplicate outgoing MT payment does not have the full CreditTransfer ISF tree of the original payment. Resolution: Status to channel was updated. |
| 138826 | Defect | Problem: EndMapper v2 update as part of migration of EM v1 to EM v2. Resolution: EM v2 changes were applied to EndMappers. |
| 138865 | Defect | Problem: MT103 message created by Financial Transaction Manager contains several optional fields with the value of NOTPROVIDED. Resolution: For elements with choice D - NOTPROVIDED, they should be mapped only when the corresponding party role is present. |
| 138938 | Defect | Problem: The TARGET2 and EURO1 networks expect the MsgDefId field of the BAH to have a qualified pacs.009 message. Resolution: Set the right value for MsgDefId in the BAH for pacs.009 messages. |
| 138969 | Defect | Problem: System logs have excessive warning messages for the Financial Transaction Manager for High Value Payments application. Resolution: The code was changed to avoid unwanted context for the event. |
| 139304 | Defect | Problem: TARGET2 incoming messages are not correlating to earlier message correctly. Resolution: The code was changed to make correlation keys configurable for incoming transactions. |
| 139640 | Defect | Problem: The outgoing camt.056 physical transmission object stays in the "In Process" state when the original payment receives a "Canceled" pacs.002 response before the camt.056 gets its camt.029 response. Resolution: The camt056 physical transmission remains in process despite the completion of the flow. |
| 139877 | Defect | Problem: Completing the outgoing camt.056 message when the rejecting pacs.002 message for the outgoing payment arrives before the camt.056's response message. Resolution: The code was changed to correct the incoming ROI failing case. |
| 140151 | Defect | Problem: The Financial Transaction Manager-generated return for the camt.029 with CNCL status has an ISF validation failure. Resolution: The code fix for the invalid reference used to create the LocalInstrument field problem resulted in an incorrect ISF tree, which resulted in this schema validation error. |
| Back to table of fixes | 3.2.10.2 release |
|
| Back to table of fixes | 3.2.9.0 release |
|
Fix number
|
Type
|
Component
|
Description
|
|
126236
|
Defect
|
Simulator (IBM Integration Bus)
|
Problem
The Xsys.011 message that was returned by the provided High Value Payments simulator has an AcceptStatus field value of Accept and not Accepted as indicated in the SWIFT documentation.
Solution
Modified the CSM simulator, Xsys.011 messages to now use Accepted' instead of 'Accept'.
|
|
125729
|
Defect
|
Schema (IBM Integration Bus)
|
Problem
Reported that the "wrapped" messages are ingesting and writing Business Address Headers in the head.001.001.02 XML namespace. The TARGET2 network does not use the .02 namespace, but uses the head.001.001.01 XML namespace.
Solution
Wrapped messages are now sending head.001.001.01
|
|
125727
|
Defect
|
Actions (IBM Integration Bus)
|
Problem
High Value Payments populates the InstgdAgt BIC field (for example in a pacs.008 Document/FIToFICstmrCdtTrf/CdTrfTxInf/InstdAgt/FinInstnId/BICFI) with a value that the bank preconfigured in the FTM RSA Model. Instead, the InstgdAgt field needs to be a valid BIC for the bank that the payment is going to and the sending bank channel system provides the value.
Solution
Updated the code so AppHdr.To BIC is the value that is coming from the channel and the InstgdAgt value is the CSM BIC
|
|
125025
|
Defect
|
RSA
|
Problem
A "Good pacs.009" message somehow corrupts the use case processing. After this bad message was in the system, all future pacs.009 messages stalled in S_WaitOutPrecheck state and became bad messages.
Solution
Added a missing object filter for the E_OutPreChecksComplete transition for the pacs.009 message.
|
|
124942
|
Defect
|
Mappers
|
Problem
The High Value Payments ISO mappers require that the Message Tree is built by using XML's schema data types. If this setting is not set because a person incorrectly toggled the switch on the FTM Channel or if a person did not realize that the setting was not set when they were wrapping/calling the Product's Mapper, the inbound mapping fails on all data and decimal fields - no useful error message explains why.
Solution
Guard added to inbound wrapper mappers. An exception is thrown when a Format with domain XMLNSC and empty MessageSet is specified without including XMLNSC.BuildTreeUsingSchemaTypes parser options, and used by an inbound mapper
|
|
124940
|
Defect
|
Schema (IBM Integration Bus)
|
Problem
When FTM for HVP creates a pacs.002 message based on an xsys.011 message and calls the action that notifies the channel, the outgoing pacs.002 message is not compliant with the TARGET2 pacs.002 XSD (schema).
Solution
An update was provided to rename the wrapper schema
|
|
124890
|
Defect
|
RSA
|
Problem
The FTM HVP Common model includes the ONUS_BANK_CODES, which means a customer's production deployment has bad routing numbers that are used to identify the bank.
Solution
Moved the ONUS_BANK_CODES to the FTM HVP Application model so a customer can remove the codes as part of the tailoring and deployment of High Value Payments.
|
|
124243
|
Defect
|
Actions (IBM Integration Bus)
|
Problem
The A_DoNotifyChannel.esql creates the "outbound" notification transaction and properly propagates the RANK value, but it does not raise the correct event. Therefore, the outbound notification does not get routed to the correct FTM outbound channel.
Solution
The function was added to the action to raise the correct event.
|
|
123737
|
Defect
|
Actions (IBM Integration Bus)
|
Problem
During customer tailoring and deployment of High Value Payments, the A_DoNotifyChannel action did not behave as expected. The action has no trace statements and no useful details are provided in the FTM Level 2 trace.
Solution
Trace code was added to the action.
|
|
123578
|
Defect
|
Simulator (IBM Integration Bus)
|
Problem
A mapping failure occurs when an admi.007 message is sent back from the High Value Payments Network Simulator
Solution
The High Value Payments simulator was updated to create a schema-valid admi.007 message.
|
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSENX3","label":"IBM Financial Transaction Manager for High Value Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"3.2.10;3.2.9"}]
Was this topic helpful?
Document Information
Modified date:
29 March 2023
UID
ibm16526188