IBM Support

Release notes for IBM Financial Transaction Manager for High Value Payments 3.2.11 Multiplatforms

Release Notes


Abstract

Release notes for IBM Financial Transaction Manager for ISO 20022 High Value Payments 3.2.11 Multiplatforms

Financial Transaction Manager for ISO 20022 High Value Payments V3.2.11 offers the ability to process ISO 20022 high-value payment types. This addition to the modern, robust IBM Financial Transaction Manager suite brings together capabilities that were not available within the existing suite.

Financial institutions can now process the following payments through a single ISO 20022-compliant platform by using a common Internal Standard Format (ISF).
- TARGET2 and EURO1/STEP1 ISO 20022 payment messages that follow the High Value Payments Plus (HVPS+) specification.
- SWIFT cross border payments that follow the Cross-border Payments and Reporting Plus (CBPR+) specification.

Content

 

Before installation

System requirements

Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For more information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
 

Downloading the product

For information about how to download IBM Financial Transaction Manager for High Value Payments for Multiplatforms see the download document for IBM Financial Transaction Manager for ISO 20022 High Value Payments 3.2.11.
 

Product documentation

Data Setup Utility
The following documentation describes the data setup utility (DSU) and the import and export workbooks:

  • DSUmigration_v3.2.11.pdf
  • DSUMigrationBR_v3.2.11.pdf

These documents are provided in the entitled documentation fix pack.

Database migration
For database migration instructions, refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\db2\{os}\doc


Transaction Server Scheduler XML
The following documentation describes the changes to the scheduler XML for the Transaction Server component:

  • TransactionServerSchedulerChanges_v3.2.11.pdf

These documents are provided in the entitled documentation fix pack.
 

 
Back to top
                       3.2.11.0 interim fix 2
 
Known Issues

An eFix is required for FTM Base (refer the PMR case#: TS01293799).
 
This interim fix has the same known issues as per 3.2.11.0 Release.
 
 
Feature changes

None
 
 
Migration

None

 
 
Back to top
                       3.2.11.0 interim fix 1
 
Known Issues

This interim fix has the same known issues as per 3.2.11.0 Release.
 
 
Feature changes

None
 
 
Migration

None

 
Back to top
                       3.2.11.0 Release

New features and updates

Integration of MT messages and all nonpayment messages with Payment Feature Services (PFS)

The integration of all message types with PFS is implemented in this release. The following messages are part of this update.
  • MT Payment messages
  • MT nonpayment messages
  • ISO nonpayment messages
These messages can be viewed from the Control Center. Also, the loading of messages to the Gateway Server is made configurable. The user can choose to load or not load a specific message type by changing the configuration. For more information about the configuration details, see the FTM for High Value Payments documentation.
 

Payment initiation and payment status report messages

The following payment initiation message and payment status report message were implemented:
  • pain.001 (payment initiation)
  • pain.002 (payment status)

Known issues

This section outlines the known issues and their workarounds (if any).
 

Issue 1

142495 - Rejected Recall messages and Response to Recall messages are shown as Accepted in Control Center

The integration of MT messages and nonpayment messages with the Control Center was implemented as part of this release. The status of successfully processed transactions is shown as Accepted and the rejected transactions is shown as Rejected on the Transaction page of the Control Center.
However, for the following message types, the rejected transactions are also shown as Accepted.
  • camt.056
  • camt.029
  • MT 196 / MT 296
  • MT 192/ MT 292
The FTM Base status column shows the correct status, but the status column alone shows as Accepted on the Transaction page of the Control Center.

Issue 2

141730 - Trace Number and Recipient account number fields are empty in the Control Center

The inbound transaction page has empty values for the trace number and recipient account number fields for all the nonpayment messages. These fields should show the alternate ID in the trace number field and the destination account number in the recipient account number field.

Issue 3

Special character slash (/) handling in tag 72 for the following flows
  • PACS.009 to MT202
  • PACS.008 to MT103
This issue can occur during the payment processing for the MX to MT flow when the data contains the special character slash (/) in the Instruction Information field.
The problem occurs because codes in the Instruction Information field are prefixed and suffixed with slash and can contain up to eight characters. If the data contains a slash, no logic or rule is available to identify whether the slash is a code separator or a data separator.
The following example shows the case where the user is trying to send 3 codes (INT, SDP, and REP) and corresponding data. The same data, when it is translated to MT, has a different structure of codes and data. This issue is due to the presence of the slash special character as part of the data under the Instruction Information, which leads to a different code and data structure in the MT because of its position within the data.
Example:
 
Original Data from MX (For example, pacs008):
----------------------------------------------------
<InstrForNxtAgt>
   <InstrInf>/INT/SYORPUTN/PRT</InstrInf>
</InstrForNxtAgt>
<InstrForNxtAgt>
   <InstrInf>/SDP/GENTINC/REP/NEWONEDATA</InstrInf>
</InstrForNxtAgt>
 
The code and data from the user (based on pacs008):
---------------------------------------------------------------  
Code: /INT/    
Corresponding Data: SYORPUTN/PRT
Code: /SDP/    
Corresponding Data: GENTINC
Code: /REP/    
Corresponding Data: NEWONEDATA
 

Data from the 2 instances of the Instruction Information is concatenated as shown in the following example.

Data concatenation per the CBPR+ rule:
------------------------------------------------  
/INT/SYORPUTN/PRT/SDP/GENTINC/REP/NEWONEDATA

The concatenated string is translated to MT with the code and corresponding data format that is shown in the following example.

Data translated to tag 72 of MT (MT 103):
----------------------------------------------------  
:72:/INT/SYORPUTN
/PRT/SDP
/GENTINC/REP/NEWONEDATA
 

Originally, the MX had 3 codes (INT, SDP, and REP) and each code had its corresponding data associated with it. Because the data for INT has a slash after SYORPUTN and the next part of the instruction information begins with a slash to represent a code, the data part PRT is treated as a code, and the structure is changed.

The translated MT has a different way of representing the code and data, which might be misleading. The translated results are shown in the following example.

The code and data as translated in MT:
----------------------------------------------------  
Code: /INT/    
Corresponding Data: SYORPUTN
Code: /PRT/    
Corresponding Data: SDP
Code: /GENTINC/    
Corresponding Data: REP/NEWONEDATA

 

Migration

None.

[{"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.11"}]

Document Information

Modified date:
13 June 2023

UID

ibm16839173

Page Feedback