Fix Readme
Abstract
This document contains V3.2.4 release information for Financial Transaction Manager for Corporate Payment Services (CPS), Digital Payments (DP), and High Value Payments (HPV) for Multiplatforms.
Content
Financial Transaction Manager for Corporate Payment Services (CPS), Digital Payments (DP), and High Value Payments (HVP) V3.2.4 Release Information
Contents
Common Across Releases
3.2.4.0 Release
... 3.2.4.0 interim fix 1 for CPS, DP and HVP
... 3.2.4.0 interim fix 2 for CPS
... 3.2.4.0 interim fix 2.1 for CPS
... 3.2.4.0 interim fix 2.2 for CPS
... 3.2.4.0 interim fix 2 for DP and HVP (Not released)
... 3.2.4.0 interim fix 3 for CPS
... 3.2.4.0 interim fix 3 for DP and HVP (Not released)
... 3.2.4.0 interim fix 4 for DP
... 3.2.4.0 interim fix 5 for DP and HVP (Not released)
... 3.2.4.0 interim fix 5 for CPS
... 3.2.4.0 interim fix 6 for HVP (Not released)
... 3.2.4.0 interim fix 6 for CPS
... 3.2.4.0 interim fix 6 for DP
... 3.2.4.0 interim fix 6.1 for CPS and DP
... 3.2.4.0 interim fix 6.2 for CPS and DP
... 3.2.4.0 interim fix 7 for DP and HVP (Not released)
... 3.2.4.0 interim fix 7 for CPS
... 3.2.4.0 interim fix 8 for HVP (Not released)
... 3.2.4.0 interim fix 8 for CPS
... 3.2.4.0 interim fix 8 for DP
... 3.2.4.0 interim fix 9 for HVP (Not released)
... 3.2.4.0 interim fix 9 for CPS
... 3.2.4.0 interim fix 9 for DP
... 3.2.4.0 interim fix 9.1 for CPS
... 3.2.4.0 interim fix 9.2 for CPS
... 3.2.4.0 interim fix 10 for CPS
... 3.2.4.0 interim fix 11 for CPS
... 3.2.4.0 interim fix 12 for CPS
... 3.2.4.0 interim fix 13 for CPS
... 3.2.4.0 interim fix 14 for CPS
... 3.2.4.0 interim fix 15 for CPS
... 3.2.4.0 interim fix 16 for CPS
... 3.2.4.0 interim fix 17 for CPS
When upgrading a fix pack or interim fix (iFix), in addition to the changes in the level that is being upgraded to, be sure to review the changes in the intermediate fix packs or iFixes.
Examples:
- Currently at level fix pack 1 and upgrading to level fix pack 3, review the changes in fix pack 2 and fix pack 3.
- Currently at fix pack 1 / interim fix 1 and upgrading to fix pack 1 / interim fix 3, review the changes in fix pack 1 / interim fix 2 and fix pack 1 / interim fix 3.
| Back to top |
Common Across Releases
|
Known Issues
Known Internet Explorer (IE) Issue
FTM will not set the "Cache-Control" & "Pragma" headers on certain responses even if they are defined in the "HTTP Response Headers" section in System Properties screen. This only happens on IE browser because of a known IE defect which has no immediate fix date available from Microsoft.
Work around:
Use Firefox or Chrome supported versions to have all headers properly set on all responses.
Use Firefox or Chrome supported versions to have all headers properly set on all responses.
WebSphere Application Server 9.0.x update issue
In WebSphere Application Server v9.0.x, there is a known problem updating components for an interim fix.
Automated Deployment Utility workaround:
The interim fix components to update need to be first uninstalled. The tokens file, for example pfs_deploy.xml, contains those interim fix components to update. These will appear in the <install> </install> section. You will also need to add these same components in the <uninstall> </uninstall> section.
Automated Deployment Utility workaround:
The interim fix components to update need to be first uninstalled. The tokens file, for example pfs_deploy.xml, contains those interim fix components to update. These will appear in the <install> </install> section. You will also need to add these same components in the <uninstall> </uninstall> section.
Manual update workaround:
Before updating the Console WAR modules stop the FrameworkUI_EAR application, then proceed as normal. The Engine modules can be updated as normal.
Before updating the Console WAR modules stop the FrameworkUI_EAR application, then proceed as normal. The Engine modules can be updated as normal.
Feature changes
Fix list and new feature summary
For a list of fixes, see V3.2.4 Fix List for Financial Transaction Manager for Corporate Payment Services (CPS), Digital Payments (DP), and High Value Payments (HVP).
Data Setup Utility
The following documentation describes the changes for the data setup utility (DSU) and the import and export workbooks:
DSUmigration_v3.2.4.pdf
DSUMigrationBR_v3.2.4.pdf
Refer to Entitled Documentation for the document.
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.4.pdf
Refer to Entitled Documentation for the document.
Entitled Documentation
Entitled documentation can be downloaded from Fix Central at:
3.2.4-FTM-CPS-MP-Documents for Corporate Payment Services (CPS).
3.2.4-FTM-DP-MP-Documents for Digital Payments(DP).
3.2.4-FTM-HVP-MP-Documents for High Value Payments (HVP).
General Instructions
Installation
- Start IBM Installation Manager.
- Add the location of the repository that contains the installation package:
- Select File > Preferences.
- Click Add Repository.
- Browse to the directory that contains the repository .zip file and select the file. Click Open and then OK.
- Click Test Connections and then OK.
- Click OK.
- Install the FTM product installation files to your installation directory:
- On the main pane, click Update.
- Select IBM Financial Transaction Manager for Digital Payments, IBM Financial Transaction Manager for Check Services, or IBM Financial Transaction Manager for Corporate Payment Services and then click Next.
- Select the fix pack or interim fix and then click Next.
- Follow the rest of the prompts.
- Confirm that the "Update packages" page shows success.
Deployment
- Do the database migration. Refer to the Database migration section in this document.
- Note: The runtime components can’t be running during the database migration.
- Note: Files can continue to be delivered to the Gateway inbound source folder.
- J2SE components: The installation overlays the J2SE applications, so no special migration instructions are needed. Restarting those applications updates them with the fixes.
- WebSphere Application Server components: You can use the Automated Deployment Utility (ADU), manually upgrade (refer to the update instructions in each WebSphere Application Server component doc folder), or, in a WAS Network Deployment configuration, use the Deployment Manager.
Note: Refer to "WebSphere Application Server 9.0.x update issue" in "Common Across Releases" > "Known Issues".- All WebSphere servers must be restarted after all the components were updated.
- For an interim fix, refer to the fix list for the modules to deploy. Note: Interim fixes are meant to be deployed on an existing WebSphere Application Server profile deployment. If you are using a new WebSphere Application Server profile and already installed the interim fix onto the prior installation, you must do two deployment passes. The first pass is to do the initial, full product deployment. The second pass is to do those components that are affected by the interim fix.
- Update your Transaction Server Scheduler.xml. Refer to the Transaction Server Scheduler XML section in this document. Note: Updating the scheduler file might not be required for your installation.
- Refer to the release-specific section for any changes that might affect your installation.
- Start your runtime components.
- If you are using the Data Setup Utility (DSU) worksheets capability for managing your data, update your worksheets. For more information, see the Data Setup Utility section in this document.
| Back to top |
3.2.4.0 interim fix 17 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 16 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 15 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 14 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 13 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 12 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 9.2 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 9.1 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 9 for DP
|
Known Issues
None.
None.
Feature changes
121399
Inbound Transaction screen adds received time to its default filter.
The FTM User Interface Inbound Transactions screen now includes two criteria in its default filter:
121399
Inbound Transaction screen adds received time to its default filter.
The FTM User Interface Inbound Transactions screen now includes two criteria in its default filter:
- 'Business Date' equal to current business day
- 'Transmission Received' in the 'past five minutes'
This will return transactions received within the past five minutes of loading the screen.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 9 for CPS
|
Known Issues
128548 (CPS - fixed at 3.2.4.0 interim fix 9 with the information provided below)
Permission changes for the Fraud Detection and Fraud Reviewed state.
Use the following file to merge the permission changes.
3.2.4.0_ifix9_128548.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
128548 (CPS - fixed at 3.2.4.0 interim fix 9 with the information provided below)
Permission changes for the Fraud Detection and Fraud Reviewed state.
Use the following file to merge the permission changes.
3.2.4.0_ifix9_128548.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
Feature changes
127586
Integrating custom account validation sheets.
Custom Account Validation sheets were integrated into product's CPA Adjust configuration spreadsheet.
127586
Integrating custom account validation sheets.
Custom Account Validation sheets were integrated into product's CPA Adjust configuration spreadsheet.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 6.2 for CPS and DP
|
Known Issues
None.
None.
| Back to top |
3.2.4.0 interim fix 6.1 for CPS and DP
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 6 for CPS
|
Known Issues
118670 (CPS - fixed at 3.2.4.0 interim fix 6 with the information provided below)
PAYMENT_DATA view having duplicate entries for PAYMENT versions
Use the following file to create the view.
3.2.4.0_ifix6_118670.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
118670 (CPS - fixed at 3.2.4.0 interim fix 6 with the information provided below)
PAYMENT_DATA view having duplicate entries for PAYMENT versions
Use the following file to create the view.
3.2.4.0_ifix6_118670.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 5 for CPS
|
Known Issues
118788 (CPS - fixed at 3.2.4.0 interim fix 5 with the information provided below)
On day of transmission reception check limit breach on value date
Use the following file to create the view.
3.2.4.0_ifix5_118788.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
118788 (CPS - fixed at 3.2.4.0 interim fix 5 with the information provided below)
On day of transmission reception check limit breach on value date
Use the following file to create the view.
3.2.4.0_ifix5_118788.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 2.2 for CPS
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 2.1 for CPS
|
Known Issues
None
None
Feature changes
None.
None.
| Back to top |
3.2.4.0 interim fix 2 for CPS
|
Known Issues
114245 (CPS - fixed at 3.2.4.0 interim fix 2 with the information provided below))
SSL Connection between Business Rule Server and WebSphere Application Server not working
Use the following file to add a new configuration property to CORE_PROPERTIES table.
3.2.4.0_ifix2_114245.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
114245 (CPS - fixed at 3.2.4.0 interim fix 2 with the information provided below))
SSL Connection between Business Rule Server and WebSphere Application Server not working
Use the following file to add a new configuration property to CORE_PROPERTIES table.
3.2.4.0_ifix2_114245.ddl
Which can be downloaded from Fix Central at 3.2.4-FTM-CPS-MP-Documents
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 interim fix 1 for CPS,DP and HVP
|
Known Issues
None.
None.
Feature changes
None.
None.
Migration
None.
None.
| Back to top |
3.2.4.0 Release
|
This is first release of Financial Transaction Manager for High Value Payments (HVP).
Compatibility Matrix
Because the development of releases and interim fixes (iFixes) for maintenance are done in parallel, a later release might not contain every interim fix that was created for an earlier release. The following table shows you which releases and interim fix levels can be successfully upgraded to V3.2.4.
In the following table, the "If you're on version" column shows you the releases that can be upgraded successfully. The highest release or interim fix level that can be upgraded for each release is shown in the "To successfully upgrade to V3.2.4, you must be no higher than version" column. If the release that you are upgrading from is at an interim fix level that is higher than the release or fix level that is shown in the right column, you can't upgrade the release without losing some changes. The upgrade needs to occur at the next release.
For more information about the individual changes in a release or interim fix, see the fix list for this version.
Compatibility Matrix
Because the development of releases and interim fixes (iFixes) for maintenance are done in parallel, a later release might not contain every interim fix that was created for an earlier release. The following table shows you which releases and interim fix levels can be successfully upgraded to V3.2.4.
In the following table, the "If you're on version" column shows you the releases that can be upgraded successfully. The highest release or interim fix level that can be upgraded for each release is shown in the "To successfully upgrade to V3.2.4, you must be no higher than version" column. If the release that you are upgrading from is at an interim fix level that is higher than the release or fix level that is shown in the right column, you can't upgrade the release without losing some changes. The upgrade needs to occur at the next release.
For more information about the individual changes in a release or interim fix, see the fix list for this version.
| If you’re on version | To successfully upgrade to V3.2.4, you must be no higher than version |
| 3.0.2.0 | 3.0.2.0 interim fix 2 |
| 3.0.2.1 | 3.0.2.1 interim fix 21 |
| 3.0.4.0 | 3.0.4.0 interim fix 3 |
| 3.0.4.1 | 3.0.4.1 interim fix 1 |
| 3.2.0.0 | 3.2.0.0 interim fix 1 |
| 3.2.0.1 | 3.2.0.1 interim fix 2 |
| 3.2.1.0 | 3.2.1.0 interim fix 3 |
| 3.2.2.0 | 3.2.2.0 interim fix 5 |
| 3.2.2.1 | 3.2.2.1 interim fix 2 |
| 3.2.3.0 | 3.2.3.0 interim fix 1 |
Known Issues
111624
Attempt to Cancel Zelle or ACH transactions from the UI results in a Database Accessor Exception
It is fixed with 3.2.4.0 interim fix 1.
Feature changes
111041
Installation Manager packages signing information
The products Installation Manager packages are now signed allowing you to confirm the package did come from IBM and that the package was not altered from the signed package. You can verify the package using the Java jarsigner tool. This tool is part of the Java Development Kit (JDK) and so is not part of the Java Runtime Environment (JRE) that comes with the product. You can use for example the JDK that comes with WebSphere Application Server. Multiple messages will be outputted. Insure the "Signer" certificate is from IBM and signed by a trusted authority. Towards the end should be a "jar verified" message. Refer to the Java documenation for specific information on the jarsigner tool.
Installation Manager packages signing information
The products Installation Manager packages are now signed allowing you to confirm the package did come from IBM and that the package was not altered from the signed package. You can verify the package using the Java jarsigner tool. This tool is part of the Java Development Kit (JDK) and so is not part of the Java Runtime Environment (JRE) that comes with the product. You can use for example the JDK that comes with WebSphere Application Server. Multiple messages will be outputted. Insure the "Signer" certificate is from IBM and signed by a trusted authority. Towards the end should be a "jar verified" message. Refer to the Java documenation for specific information on the jarsigner tool.
110372
FTM Products do not require default passwords to be reset - HVP
FTM Products do not require default passwords to be reset - HVP
- The ADU Token File Wizard (PFSTools.jar) no longer supplies a default password for the "FTM Database user ID" and "WAS Admin user ID".
- The Automated Deployment Utility (ADU) will now only create the "WAS Admin user ID" as defined in the tokens file. The other user ids that were being created by default in WebSphere Application Server are no longer configured.
- Only fxhadmin will be prepopulated in the Control Center. The other admin ids are no longer prepopulated.
99394
UI: Include "System Overview and Day in the Life" Information
To provide a centralized location locating exception items, a new screen has been introduced to FTM. This screen, System Overview, includes links to various existing screens for viewing and correcting exception items. Graphs have also been included to provide a general overview of the health of the system. A link to this screen is located at System Management -> System Overview.
System Overview screen:
Three symbols will be displayed next to every link. A green check mark indicates that no exception items were found. A red exclamation mark indicates errors are found, while non-errors are indicated by a yellow exclamation mark.
Refreshing
The screen can be refreshed by clicking the refresh symbol on the title bar. This will reapply the currently selected filter and update the exception counts.
Auto-refresh functionality can be enabled at Administration -> Components -> Payment Feature Services -> Properties -> System overview refresh rate. Note that the value is specified in seconds, and defaults to disabled (empty).
Filtering
Both sections of the screen have separate filtering capability, configurable by clicking the pencil/edit icon on the title bar. Selecting this icon will display a dialog box that allows the configuration of the start and end dates for filtering. The default filter is 1 day.
Range filter with custom selected:
If Custom is selected, date ranges may be specified. The filter range will not be updated on refresh.
Range filter with 1 day selected:
If any value except custom is selected, a moving date range will be used. For example, if the above screenshot were the current date and time, pressing okay would filter from 12:55 PM yesterday to 12:55 PM today. If you were to refresh the screen in 5 minutes, the filter would update to be 1:00 PM yesterday to 1:00 PM today. This applies to 1 hr, 1 day, 7 days, and 30 days.
System Overview graphs
The bar graphs display the monetary value and item count for both inbound and outbound batches. The pie charts display the complete and incomplete counts for the inbound transmissions and batches.
Permissions
New permissions have been added for viewing the system overview screen, and for overriding the hiding of counts when the user does not have view permission to an exception item’s screen.
Permission screen:
Links
Selecting a link will open the screen for viewing or correcting the exception items.
With the addition of the system overview screen, the graphs that previously existed on the home page were no longer needed. It has been simplified and modelled after the login screen.
Outbound Transmissions screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Expected Events screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Inbound Physical Transmission screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Suspended Work screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Outbound Segments screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Inbound Transaction screen
A new column has been added to the inbound transaction screen. This was required to filter the transactions by the Transmission’s received time. This field is filterable and sortable. The forward / return field is also now filterable.
UI: Include "System Overview and Day in the Life" Information
To provide a centralized location locating exception items, a new screen has been introduced to FTM. This screen, System Overview, includes links to various existing screens for viewing and correcting exception items. Graphs have also been included to provide a general overview of the health of the system. A link to this screen is located at System Management -> System Overview.
System Overview screen:
Three symbols will be displayed next to every link. A green check mark indicates that no exception items were found. A red exclamation mark indicates errors are found, while non-errors are indicated by a yellow exclamation mark.
Refreshing
The screen can be refreshed by clicking the refresh symbol on the title bar. This will reapply the currently selected filter and update the exception counts.
Auto-refresh functionality can be enabled at Administration -> Components -> Payment Feature Services -> Properties -> System overview refresh rate. Note that the value is specified in seconds, and defaults to disabled (empty).
Filtering
Both sections of the screen have separate filtering capability, configurable by clicking the pencil/edit icon on the title bar. Selecting this icon will display a dialog box that allows the configuration of the start and end dates for filtering. The default filter is 1 day.
Range filter with custom selected:
If Custom is selected, date ranges may be specified. The filter range will not be updated on refresh.
Range filter with 1 day selected:
If any value except custom is selected, a moving date range will be used. For example, if the above screenshot were the current date and time, pressing okay would filter from 12:55 PM yesterday to 12:55 PM today. If you were to refresh the screen in 5 minutes, the filter would update to be 1:00 PM yesterday to 1:00 PM today. This applies to 1 hr, 1 day, 7 days, and 30 days.
System Overview graphs
The bar graphs display the monetary value and item count for both inbound and outbound batches. The pie charts display the complete and incomplete counts for the inbound transmissions and batches.
Permissions
New permissions have been added for viewing the system overview screen, and for overriding the hiding of counts when the user does not have view permission to an exception item’s screen.
Permission screen:
Links
Selecting a link will open the screen for viewing or correcting the exception items.
- System Alerts -> System Alerts
- Approvals -> Approvals
- Expected Event Issues -> Expected Events
- Transmissions in Error -> Inbound Transmissions
- Pending Transmissions -> Inbound Transmissions
- Suspended Transmissions -> Risk Review UI
- Batches in Error -> Inbound Batches
- Pending Batches -> Inbound Batches
- Suspended Batches -> Risk Review UI
- Transactions in Error -> Inbound Transactions
- Suspended Transactions -> Risk Review UI
- Unmatched Returns -> Inbound Transactions
- Network Timeouts -> Inbound Transactions
- Fraudulent Transactions -> Inbound Transactions
- Unmatched Control Totals -> Control Totals
- Contested Dishonored Returns -> Inbound Transactions
- Transmissions in Error -> Outbound Transmissions
- Batches in Error -> Outbound Batches
- Segments in Error -> Outbound Segments
With the addition of the system overview screen, the graphs that previously existed on the home page were no longer needed. It has been simplified and modelled after the login screen.
Outbound Transmissions screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Expected Events screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Inbound Physical Transmission screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Suspended Work screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Outbound Segments screen
A new business day range has been added to support filtering screens after clicking the link on the System Overview screen. If no end business date is specified, only a single business day will be displayed. If an end business date is specified, all business days between the start date and the end date will be displayed.
Inbound Transaction screen
A new column has been added to the inbound transaction screen. This was required to filter the transactions by the Transmission’s received time. This field is filterable and sortable. The forward / return field is also now filterable.
103552
Payment Scheme
To clearly identify, sort, filter, etc. transactions based upon the payment scheme that the transaction is participating in, payment scheme has been introduced to FTM. The payment scheme will affect multiple components through configuration updates. Payment schemes will define if Saturdays and Sundays are considered workdays as well as allowing holidays to be defined by payment scheme. Holidays can be configured globally for the system or holidays can now be associated to specific payment schemes. Inbound payment schemes will be defined by the payment scheme associated with the inbound Transmission Type. Outbound payment schemes will be defined by the payment scheme associated with the outbound Transmission Definition.
Any module that performs business day “math” to determine next or previous business days will be affected and will use the assigned payment scheme when performing these calculations. Before the use of payment schemes were introduced, business day calculations were always done using the defined holidays as well as treating Saturday and Sunday as non-workdays. These calculations will now use the supplied payment scheme to determine what holidays to use and if Saturdays and Sundays are workdays.
Product configuration
The Payment Scheme values that are defined for the system are defined in the ProductConfiguration DSU spreadsheet and are defined as
Payment Scheme:
Calendar Group:
Schedule Entry:
Configuration screens
There are multiple configuration screens that have changed to allow for payment scheme integration into Calendars, Payment Message Types, Transmission Types and Transmission Definitions.
Calendar
The payment scheme value for the holidays will be displayed in on the calendar grid by default.
Calendar grid:
The payment scheme value for the holidays will be configurable for the Participant, Location data, and Payment scheme scopes. The drop down will list all available payment schemes.
Calendar Details:
Message Types
Payment message types has been expanded to include details by payment scheme. In order to provide these optional detail fields, a payment scheme must be supplied.
The payment scheme value for the message types will be displayed on all the message type screens. The grid screen will display the Payment Scheme by default. A new Add Details action has been added. This action will be used when new payment scheme details need to be added to a payment message type.
Message types grid:
Message Type Details:
The add message type screen now contains a payment scheme drop down which will contain all available payment schemes. Payment scheme is required when filling in any non-required/detail fields.
Add Message Type:
The add details screen is nearly identical to the Add Message Type screen, with the exception that you can add a new payment scheme to an already existing message type. The Message types dropdown will contain all available message types.
Add Details by Payment Scheme:
Transmission Types
The payment scheme value for the transmission types will be displayed on the transmission types screen accessible through Configuration -> Inbound -> Transmission Types menu. The grid screen will display the Payment Scheme by default.
Transmission Types grid:
Related details screen in view and edit modes (note the dropdown payment scheme selection list in edit mode).
Details:
Edit Mode:
Transmission Definitions
The payment scheme value for the transmission definitions will be displayed on the transmission definition screen. The grid screen will display the Payment Scheme by default.
Transmission definitions grid:
Associated details screen in view and edit mode (note the drop-down selection list for the payment scheme in edit mode):
Edit Mode:
Inbound processing screens
The payment scheme value for each transmission, batch, segment (when applicable), and transaction will be displayed in the various grid and transmission hierarchy UI screens. Each of the grid screens will display the Payment Scheme by default.
Inbound Transmission Grid:
Inbound Batch Grid:
Inbound Segments Grid:
Transaction Grid:
The Payment Scheme will be sortable and filterable on each of these screens. The payment scheme filter will provide the user with a dropdown of available payment schemes to choose.
Payment Scheme Filter:
Each level of the Transmission Hierarchy details UI will also display the Payment Scheme assigned to that transmission, batch, segment (when applicable), and transaction.
Transmission details:
Batch details:
Transaction details:
Outbound processing screens
The payment scheme value for each outbound transmission, batch, segment (when applicable) will be displayed in the various outbound grid and detail screens. Each of the grid screens will display the Payment Scheme by default.
Outbound transmission grid:
Outbound transmission details:
Outbound batch grid:
Outbound batch details:
Services Framework task updates
There are a few Services Framework tasks that have been updated to allow for an optional payment scheme value. Here are the tasks that were updated:
Business Day Open and Activate Task
Parameter: Payment Scheme
Description: Payment scheme to use during open and/or activation process. If the payment scheme parameter is left blank, default payment scheme will be used for business days to open and/or activate. Valid value for payment scheme should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
Business Day Close And End Task
Parameter: Payment Scheme
Description: An optional payment scheme used to filter the possible business days the action is executed against. If the payment scheme parameter is left blank, all business days that match the time interval will be acted upon.
Example: Check, NACHA, TCH RTP, etc.
Performance Monitor Purge Task
Parameter: Payment Scheme
Description: An optional payment scheme used during the process. If the payment scheme parameter is left blank during the process, the default payment scheme, defined in the Payment Feature Services component property called System Payment Scheme will be used. If payment scheme parameter is specified, it should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
File Tracking Purge Task
Parameter: Payment Scheme
Description: An optional payment scheme used during the process. If the payment scheme parameter is left blank during the process, the default payment scheme, defined in the Payment Feature Services component property called System Payment Scheme will be used. If payment scheme parameter is specified, it should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
Payment Scheme
To clearly identify, sort, filter, etc. transactions based upon the payment scheme that the transaction is participating in, payment scheme has been introduced to FTM. The payment scheme will affect multiple components through configuration updates. Payment schemes will define if Saturdays and Sundays are considered workdays as well as allowing holidays to be defined by payment scheme. Holidays can be configured globally for the system or holidays can now be associated to specific payment schemes. Inbound payment schemes will be defined by the payment scheme associated with the inbound Transmission Type. Outbound payment schemes will be defined by the payment scheme associated with the outbound Transmission Definition.
Any module that performs business day “math” to determine next or previous business days will be affected and will use the assigned payment scheme when performing these calculations. Before the use of payment schemes were introduced, business day calculations were always done using the defined holidays as well as treating Saturday and Sunday as non-workdays. These calculations will now use the supplied payment scheme to determine what holidays to use and if Saturdays and Sundays are workdays.
Product configuration
The Payment Scheme values that are defined for the system are defined in the ProductConfiguration DSU spreadsheet and are defined as
Payment Scheme:
Calendar Group:
Schedule Entry:
Configuration screens
There are multiple configuration screens that have changed to allow for payment scheme integration into Calendars, Payment Message Types, Transmission Types and Transmission Definitions.
Calendar
The payment scheme value for the holidays will be displayed in on the calendar grid by default.
Calendar grid:
The payment scheme value for the holidays will be configurable for the Participant, Location data, and Payment scheme scopes. The drop down will list all available payment schemes.
Calendar Details:
Message Types
Payment message types has been expanded to include details by payment scheme. In order to provide these optional detail fields, a payment scheme must be supplied.
The payment scheme value for the message types will be displayed on all the message type screens. The grid screen will display the Payment Scheme by default. A new Add Details action has been added. This action will be used when new payment scheme details need to be added to a payment message type.
Message types grid:
Message Type Details:
The add message type screen now contains a payment scheme drop down which will contain all available payment schemes. Payment scheme is required when filling in any non-required/detail fields.
Add Message Type:
The add details screen is nearly identical to the Add Message Type screen, with the exception that you can add a new payment scheme to an already existing message type. The Message types dropdown will contain all available message types.
Add Details by Payment Scheme:
Transmission Types
The payment scheme value for the transmission types will be displayed on the transmission types screen accessible through Configuration -> Inbound -> Transmission Types menu. The grid screen will display the Payment Scheme by default.
Transmission Types grid:
Related details screen in view and edit modes (note the dropdown payment scheme selection list in edit mode).
Details:
Edit Mode:
Transmission Definitions
The payment scheme value for the transmission definitions will be displayed on the transmission definition screen. The grid screen will display the Payment Scheme by default.
Transmission definitions grid:
Associated details screen in view and edit mode (note the drop-down selection list for the payment scheme in edit mode):
Edit Mode:
Inbound processing screens
The payment scheme value for each transmission, batch, segment (when applicable), and transaction will be displayed in the various grid and transmission hierarchy UI screens. Each of the grid screens will display the Payment Scheme by default.
Inbound Transmission Grid:
Inbound Batch Grid:
Inbound Segments Grid:
Transaction Grid:
The Payment Scheme will be sortable and filterable on each of these screens. The payment scheme filter will provide the user with a dropdown of available payment schemes to choose.
Payment Scheme Filter:
Each level of the Transmission Hierarchy details UI will also display the Payment Scheme assigned to that transmission, batch, segment (when applicable), and transaction.
Transmission details:
Batch details:
Transaction details:
Outbound processing screens
The payment scheme value for each outbound transmission, batch, segment (when applicable) will be displayed in the various outbound grid and detail screens. Each of the grid screens will display the Payment Scheme by default.
Outbound transmission grid:
Outbound transmission details:
Outbound batch grid:
Outbound batch details:
Services Framework task updates
There are a few Services Framework tasks that have been updated to allow for an optional payment scheme value. Here are the tasks that were updated:
Business Day Open and Activate Task
Parameter: Payment Scheme
Description: Payment scheme to use during open and/or activation process. If the payment scheme parameter is left blank, default payment scheme will be used for business days to open and/or activate. Valid value for payment scheme should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
Business Day Close And End Task
Parameter: Payment Scheme
Description: An optional payment scheme used to filter the possible business days the action is executed against. If the payment scheme parameter is left blank, all business days that match the time interval will be acted upon.
Example: Check, NACHA, TCH RTP, etc.
Performance Monitor Purge Task
Parameter: Payment Scheme
Description: An optional payment scheme used during the process. If the payment scheme parameter is left blank during the process, the default payment scheme, defined in the Payment Feature Services component property called System Payment Scheme will be used. If payment scheme parameter is specified, it should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
File Tracking Purge Task
Parameter: Payment Scheme
Description: An optional payment scheme used during the process. If the payment scheme parameter is left blank during the process, the default payment scheme, defined in the Payment Feature Services component property called System Payment Scheme will be used. If payment scheme parameter is specified, it should already be defined in the system.
Example: Check, NACHA, TCH RTP, etc.
107778
Zelle - Log system alerts and track "Out of sync with EWS" payments
When communication errors (SoapFault Exceptions) occur while communicating with EWS, FTM will now attempt to clearly alert when these instances occur and clearly define that a Zelle payment has encountered the error. When both originated and received Zelle payments encounter SoapFault conditions when communicating with EWS, the payment will be updated to have an “Out of Sync” Zelle status, payment tracking/history logs will be added to the payment, and a system warning will be written.
Originated Zelle payment
Out of Sync Zelle status:
Payment history:
System alert:
Received Zelle payment
Out of Sync Zelle status:
Payment history:
System alert:
Out of Sync Zelle status
The new Out of Sync Zelle status will be included in the transaction filter so that any problematic payments can be easily found.
Zelle Status filter:
When the Out of Sync condition occurs, FTM is not aware of the real status of the payment with EWS. In order to resync the payment with EWS, the user can use the Cancel action on the Transactions grid. If the payment cannot be cancelled (Ex. Originated payment already delivered), the FTM will update the payment accordingly (no SoapFault) and the payment will be back in sync with EWS. If the payment can be cancelled (no SoapFault), then the Cancel action will cancel the payment (like a normal cancellation) and the end user will need to create a new payment. If a SoapFault occurs while processing the Cancel action, the Out of Sync Zelle status will remain. There will also be new payment tracking entries and system warnings to denote that the payment is still out of sync with EWS.
Cancel dialog with Out of Sync Zelle status :
Zelle - Log system alerts and track "Out of sync with EWS" payments
When communication errors (SoapFault Exceptions) occur while communicating with EWS, FTM will now attempt to clearly alert when these instances occur and clearly define that a Zelle payment has encountered the error. When both originated and received Zelle payments encounter SoapFault conditions when communicating with EWS, the payment will be updated to have an “Out of Sync” Zelle status, payment tracking/history logs will be added to the payment, and a system warning will be written.
Originated Zelle payment
Out of Sync Zelle status:
Payment history:
System alert:
Received Zelle payment
Out of Sync Zelle status:
Payment history:
System alert:
Out of Sync Zelle status
The new Out of Sync Zelle status will be included in the transaction filter so that any problematic payments can be easily found.
Zelle Status filter:
When the Out of Sync condition occurs, FTM is not aware of the real status of the payment with EWS. In order to resync the payment with EWS, the user can use the Cancel action on the Transactions grid. If the payment cannot be cancelled (Ex. Originated payment already delivered), the FTM will update the payment accordingly (no SoapFault) and the payment will be back in sync with EWS. If the payment can be cancelled (no SoapFault), then the Cancel action will cancel the payment (like a normal cancellation) and the end user will need to create a new payment. If a SoapFault occurs while processing the Cancel action, the Out of Sync Zelle status will remain. There will also be new payment tracking entries and system warnings to denote that the payment is still out of sync with EWS.
Cancel dialog with Out of Sync Zelle status :
105851
Canadianization - Out of Balance issue caused by currency conversions and round-offs
Currency filter added on settlement screens to filter transactions based on original payment's currency code, in a multi-currency setup.
Canadianization - Out of Balance issue caused by currency conversions and round-offs
Currency filter added on settlement screens to filter transactions based on original payment's currency code, in a multi-currency setup.
107035
Dynamically generate Action Menu for the Inbound Transaction UI Grid
The inbound transactions screens will now have a dynamic action menus based on the inbound and outbound schemes. If the inbound and outbound schemes are different, then the action menus are union of both.
Dynamically generate Action Menu for the Inbound Transaction UI Grid
The inbound transactions screens will now have a dynamic action menus based on the inbound and outbound schemes. If the inbound and outbound schemes are different, then the action menus are union of both.
Migration
Refer to the following documents for migration details:
DSUmigration_v3.2.4.pdf
DSUMigrationBR_v3.2.4.pdf
Which can be downloaded from Fix Central at:
3.2.4-FTM-CPS-MP-Documents for Corporate Payment Services (CPS).
3.2.4-FTM-DP-MP-Documents for Digital Payments(DP).
3.2.4-FTM-HVP-MP-Documents for High Value Payments (HVP).
DSUmigration_v3.2.4.pdf
DSUMigrationBR_v3.2.4.pdf
Which can be downloaded from Fix Central at:
3.2.4-FTM-CPS-MP-Documents for Corporate Payment Services (CPS).
3.2.4-FTM-DP-MP-Documents for Digital Payments(DP).
3.2.4-FTM-HVP-MP-Documents for High Value Payments (HVP).
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.2.4","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
15 March 2024
UID
ibm16221096