Release notes for IBM Financial Transaction Manager for Corporate Payment Services 3.2.12 Multiplatforms

Content

• Before installation
• Product documentation
• Support

• 3.2.12 Release

  • Feature changes
  • Customizations
  • Known issues
  • .... 3.2.12.0 interim fix 1
  • .... 3.2.12.0 interim fix 2

  ---

  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 Corporate Payment Services for Multiplatforms, see the download document for IBM Financial Transaction Manager for Corporate Payment Services for Multiplatforms 3.2.12.

   

   

  Back to contents

   

  ---

  Product documentation

   

  • Release information (this document)
  • Financial Transaction Manager online product documentation in IBM Documentation
  • Fix list (key defects fixes in this release)
  • Entitled documentation fix pack (download from Fix Central)
  • Resources (for previous releases of this offering)

   

    

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

  • DSUmigration_v3.2.12.pdf
  • DSUMigrationBR_v3.2.12.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.12.pdf

  These documents are provided in the entitled documentation fix pack.

   

   

  Back to contents

   

  ---

  Support

  Defects:

  These release notes might contain references to defect numbers. These numbers refer to internal IBM problem numbers that you might find helpful when you are discussing problems with your IBM Support representative.
   

  Technotes:

  For more information about available fixes, see the IBM Support web page.
  To find the information, go to Download - Fixes, updates, and drivers, and then enter the product's name. This web page links the latest maintenance for the in-service IBM Financial Transaction Manager family of products.
   

  Back to contents

    

  ---

   

  Back to contents

  3.2.12

  New features and updates

   

   

  Back to contents

   

  Known issues

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

  • EDI X12 Processing is not supported in this 3.2.12 release.

   

   

  Back to contents

  3.2.12.0 interim fix 1

   

  Feature Changes

   

   

  CPA AFT: Validation for Returns and Reversals in FTM CPS

  Added validation checks between Returns/Reversals and their original payments based on the Payments Canada Standard 005 document. For returns, we are validating: Amount (pre-existing check), Due Date/Date Funds to be Available, Institution Id, Payor/Payee Account Number, Stored Transaction Type, Originating Direct Clearer's User Id, Originator's Cross Reference Number, Stored Institution Id, Original Account Number, Stored Item Trace Number (should never trigger since we won't find the original payment if it's wrong)
   
  For Reversals, we are validating: Transaction Type, Transaction Type (pre-existing check), Due Date/Date Funds to be Available, Institution Id, Payor/Payee Account Number, Stored Transaction Type, Originator's Short Name, Payor/Payee Name, Originator's Long Name, Originating Direct Clearer's User Id, Originator's Cross Reference Number, Stored Institution Id, Account Number for Returns, Originator's Sundry Information, Stored Item Trace Number (should never trigger since we won't find the original payment if it's wrong), Originator Direct Clearer Settlement Code, Invalid Data Elements.
   
  To support this, new Gateway Error codes were added to SampleCpaConfiguration.xlsx that correspond to the different fields Returns/Reversals: CPA0001_04Rev, CPA0001_06, CPA0001_07Ret, CPA0001_07Rev, CPA0001_08Ret, CPA0001_08Rev, CPA0001_10Ret, CPA0001_10Rev, CPA0001_11Rev, CPA0001_12Rev, CPA0001_13Rev, CPA0001_14, CPA0001_15, CPA0001_16Ret, CPA0001_16Rev, CPA0001_17Ret, CPA0001_17Rev, CPA0001_18Rev, CPA0001_19, CPA0001_20Rev, CPA0001_21Rev