Fix Readme
Abstract
Fix list for IBM Financial Transaction Manager for High Value Payments 3.2.11 Multiplatforms
Content
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
- To avoid a loss of functionality when you migrate from one release to another, check the Compatibility Matrix for the release being migrated to. The Compatibility Matrix is located in the release information for Financial Transaction Manager for High Value Payments 3.2.11 Multiplatforms.
| V.R.M.F | Download | Build date | Prerequisites |
| 3.2.11.0 interim fix 2 | 3.2.11.0-FTM-HVP-MP-iFix0002 | 20230609-0808 | 3.2.11.0 |
| 3.2.11.0 interim fix 1 | 3.2.11.0-FTM-HVP-MP-iFix0001 | 20230201-1727 | 3.2.11.0 |
| 3.2.11.0 |
Available from Passport Advantage
|
20230125-0852 | None |
| Back to top | 3.2.11.0 interim fix 2 |
| Fix number | Type | Component | Description |
| 140774 | Defect | Gateway | Problem:PACS.002 to Channel for Outgoing CAMT.056 Missing OrgnlEndToEndId. Solution: Generated PACS.002 sent to the Bank Channel application contains a the OrglEndToEndId field value. |
| 142172 | Defect | Gateway | Problem: MT103/MT202 Block 3 Field 111 Not Mapped Correctly in PACS.008/9. Solution: The value in Field 111 is mapped to CreditTransferTransactionInformation/PaymentTypeInformation/ServiceLevel/Code. |
| 142177 | Defect | Gateway | Problem: Outgoing MT202 COV Fails to be Sent to CSM due to Outbound Mapping Error. Solution: Fixed the code to avoid Outbound Mapping error. |
| 142250 | Defect | Gateway | Problem: Outbound PACS.009 with InstrForNxtAgt Tag Result in Invalid ISF. Solution: Fixed the code to complete the flow without an issue. |
| 14 2475 | Defect | Gateway | Problem: Outbound PACS.008 Purp Tag being dropped. Solution: Fixed the code to display Purp tag in the output file. |
| 144200 | Defect | Gateway | Problem: CBPR+ PACS.009 with Category Purpose Code of CORT Fail to Convert to MT202. Solution: MT202 is generated and tag 72 have six lines with max 35 characters including slashes. |
| 144421 | Defect | Gateway | Problem: CBPR+ PACS.009 Fails to Convert to MT202. Solution: File is successfully and converted to MT202. |
| 144572 | Defect | Gateway | Problem: Resend operator action fails and causes MapAbort event. Solution: Fixed the code to avoid MapAbort event. |
| 144641 | Defect | Gateway | Problem: Pacs004 is not getting completed in case the file has PrvsIntgAgt1 that is present. Solution: OG pacs004 is completed and No unexpected event is generated. |
| 145845 | Defect | Gateway | Problem: Inbound PACS.004 Hangs in Transaction Mapped State. Solution: FTM4HVP does not include Rejected Outgoing Payments in correlation criteria AND/OR FTM4HVP flags the payment as unable to correlate and processes the payment. |
| Back to top | 3.2.11.0 interim fix 1 |
| Fix number | Type | Component | Description |
| 143350 | Defect | Gateway |
Problem: The izxfix.jar was not empty in the 3.2.11.0 GA build.
Solution: The izxfix.jar was reset to empty to facilitate IBM Support. |
| Back to top | 3.2.11.0 release |
| Fix number | Type | Component | Description |
| 140477 | Defect | Incoming Payments FSM (FTM Model) |
Problem: A race condition was discovered. When the event processing flows are scaled up, the scheme is shown as CBPR+ in the Control Center for TRG2 payments. This problem occurs because the post inbound mapper gets called before the validation action where actual scheme is set.
Solution: A change was made to complete batch processing only after transaction validation is completed. This change calls the post inbound mapper after the validate action. |
| 142493 | Defect | MT196ToISFMapper/ MT296ToISFMapper (IBM App Connect Enterprise) |
Problem: Instructed Agent and Instructing Agent BIC values present in the status sent to channel (pacs002) for an outgoing response to recall (MT196/MT296) is truncated.
Solution: The mapping for MT 196 and MT 296 messages was modified to map the complete BICFI value.
|
| 142250 | Defect | Action creating the status ISF (IBM App Connect Enterprise) |
Problem: The status sent to the channel for an outgoing payment (pacs009) has the InstrForNxtAgt field populated with an invalid value. This problem causes the end-to-end flow to fail.
Solution: A change was made to populate the right value for the InstrForNxtAgt.
|
| 142177 | Defect | MT202ToISFMapper (IBM App Connect Enterprise) |
Problem: The outgoing payment (MT 202 COV) fails schema validation before it is being sent to CSM. The outbound PT throws an exception.
Solution: Mapping for MT 202 COV Tag 52A was corrected to populate the right values for the failing fields. |
| 142053 | Defect | Actions creating Ack and Nack messages (IBM App Connect Enterprise) |
Problem: The EndToEndIdentification field was populated as NOTPROVIDED in the status message sent to channel for all outgoing nonpayment MT messages.
Solution: Fix the mapper codes of all outgoing nonpayment MT messages to populate the right EndToEndIdentification. |
| 141318 | Defect | UI query |
Problem: The search by scheme is not working as expected in the Physical Transmission screen in OAC. It always displays 'No Record Found'.
Solution: The query to fetch the results based on scheme was corrected. |
| 140654 | Defect | MT103ToISFMapper (IBM App Connect Enterprise) |
Problem: The Field 72 of MT 103 sent from channel is not mapped properly to the pacs008 sent to the CSM. Some data in the field was not mapped.
Solution: The mapper code was modified to map the Field 72 as expected. |
| 140448 | Defect | The validate action of response to recall (IBM App Connect Enterprise) |
Problem: The scheme details are not set properly in the database for an uncorrelated outgoing response to recall message.
Solution: The logic to set the scheme for uncorrelated response to recall messages was corrected. |
| 139304 | Defect | Multiple mappers and validate actions (IBM App Connect Enterprise) |
Problem: An incoming pacs.004, camt.056, or camt.029 does not correlate to the original payment message. Only MessageID was used to correlate to original message.
Solution: A configurable option was added to choose one or more of the following fields as the correlation ID - Instruction ID, End to End ID, UETR, and Clearing System Reference Number. |
[{"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"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"3.2.11"}]
Was this topic helpful?
Document Information
Modified date:
13 June 2023
UID
ibm16839193