IBM Support

Release Information for Financial Transaction Manager for High Value Payments

Fix Readme


Abstract

This document contains release information for Financial Transaction Manager for High Value Payments for Multiplatforms.

Content

Financial Transaction Manager for High Value Payments (HVP) release information

   
   

Contents
3.2.10.2 Releases
... 3.2.10.2 interim fix 1
... 3.2.10.2 interim fix 2
... 3.2.10.2 interim fix 3
... 3.2.10.2 interim fix 4
... 3.2.10.2 interim fix 5

 

Back to top
3.2.10.2 release
 
   

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

  • DSUmigration_v3.2.10.pdf
  • DSUMigrationBR_v3.2.10.pdf

These documents are provided in the entitled documentation fix pack. For more information about getting this fix pack, see the Entitled Documentation section.

Database installation
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.10.pdf

These documents are provided in the entitled documentation fix pack. For more information about getting this fix pack, see the Entitled Documentation section.
 

Mapping Specs
These documents are provided in the entitled documentation fix pack. For more information about getting this fix pack, see the Entitled Documentation section.


Entitled Documentation
The entitled documentation fix pack for FTM High Value Payments can be downloaded from Fix Central by using the following link:

3.2.10-FTM-HVP-MP-Documents.

New Functions:
  • Message Flows (documentation link):
    • CBPR+ updates:
      • Incoming Payment Returned
      • Incoming Response to Recall (Good and bad)
      • Outgoing Response to Recall (Good and bad)
      • Incoming Recall (Bad)
      • Outgoing Recall (Bad)
      • Outgoing Payment Reject
      • Incoming Payment Returned
  • Mappers (documentation link)
    • CBPR+: 
      • pacs.010
      • camt.052
      • camt.053
      • camt.056
      • camt.057
      • camt.060 – All inbound and outbound
      • MT 103+, Return, Reject
      • MT 202 COV
      • MT 210
      • MT 192/292
      • MT 196/296
      • MT 900/910
      • MT 940/950
      • MT 941/942. All inbound and outbound
  • Validation:
    • CBPR+ 2.1 - Covers the previous CBPR+ messages
  • Business operations UI integration:
    • HVP Transactions appear in the Business Operations UI with relevant information.
    • Operator actions: Request for recall and process returns.
 
Back to top
                       3.2.10.2 interim fix 5
 
Known Issues

This interim fix has the same known issue as 3.2.10.2 interim fix 2.
 
 
Feature changes

None
 
Migration

None
 
 
Back to top
                       3.2.10.2 interim fix 4
 
Known Issues

This interim fix has the same known issue as 3.2.10.2 interim fix 2.
 
Feature changes

None
 
 
Migration

None
 
 
Back to top
                       3.2.10.2 interim fix 3
 
Known Issues

This interim fix has the same known issue as 3.2.10.2 interim fix 2.
 
 
Feature changes

None
 
 
Migration

None
 
 
Back to top
                       3.2.10.2 interim fix 2
 
Known Issues
 
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

 
 
Feature changes

None
 
 
Migration

None.

 
 
Back to top
                       3.2.10.2 interim fix 1
 
Known Issues

None.
 
 
Feature changes

None
 
 
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":"All Versions"}]

Document Information

Modified date:
29 March 2023

UID

ibm16517462

Page Feedback