IBM Support

Release notes for IBM Transformation Extender, Pack for Financial Payments, V10.0.5.0

Release Notes


Abstract

These release notes contain the information required to install and configure the IBM Transformation Extender, Pack for Financial Payments, version V10.0.5.0

Content

Pack for Financial Payments V10.0.5.0 release notes.

© Copyright IBM Corporation, 2020. All Rights Reserved.
© Copyright HCL Technologies Ltd, 2020. All Rights Reserved.

=====================================================================
CONTENTS
=====================================================================

=====================================================================
ABOUT THIS RELEASE
====================================================================


Where to find the software to download

The software for this pack can be obtained from Passport Advantage.

What's new in this release

NACHA component:

  • New ACH 2020 type trees with updated description on Return reason codes ‘R10, ‘R11’ .
  • Updates to related examples maps to use latest ACH 2020 type trees.

SWIFT component:

  • Support is now provided for 2020 SRG Standards.
  • Corresponding updates as follows:

    • SWIFT type trees.
    • LMF maps and trees.
    • Java Validation Component.
    • MT - MX mapping examples.
    • MX schemas, type trees, and validation framework.
  • Mapping examples how to generate MT199 Universal Confirmation from different channels:    
    • SWIFT FIN MT103.
    • The CSV file structure for payment confirmation.
    • SWIFT Tracker PaymentStatusRequest API (camt.a01.001.04).      

=====================================================================
DOCUMENTATION NOTES
====================================================================


View the latest product documentation
See the online documentation for the latest documentation for this product.

ACH_ISO Mapping Assumptions spreadsheets:

The ACH_ISO Mapping Assumptions spreadsheets are used with the examples in the NACHA component of the pack. You can download these tables from this location:

ACH_ISO Mapping Assumptions spreadsheets

LMF mapping tables

The LMF mapping tables used with the SWIFT component of the pack can be downloaded from this location:

LMF Mapping Tables

Pack for Financial Payments Project List spreadsheet
This document contains a spreadsheet used with the example's documentation contained in the Pack for Financial Payments online documentation. The project list can be downloaded from this location:
 

Translated documentation

The online documentation is provided in these languages:

  • English (United States)
  • French


For the latest product information, see the English version in the online documentation.

Viewing translated documentation

To display translated content in the online documentation:

  1. Open the online documentation. A typical URL to the documentation is shown below:
    https://www.ibm.com/support/knowledgecenter/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  2. Edit the URL to include the desired language code immediately after "/knowledgecenter":
    https://www.ibm.com/support/knowledgecenter/<language code>/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  3. As an example, enter language code "/fr" to display French content.
  4. Remove the "/<language code>" to return to the English display. 

=====================================================================
INSTALLATION
====================================================================

Installation prerequisites

One of the following versions of the base product must be installed:
  • 10.0.3.0
  • 10.0.0.0
  • 9.0.0.4
For IBM Transformation Extender Advanced: See the Release Notes for IBM Transformation Extender Advanced.

Note: This product is supported on the same platforms as the prerequisite products.

Deploying the pack to other operating systems
See the individual component documentation for information on deploying to other operating system platforms.

Installation directories

The pack components are installed to the following directory, depending on the selected standard(s):

  • <install_dir>\packs\financial_payments_vn.n.n.n\nacha
  • <install_dir>\packs\financial_payments_vn.n.n.n\sepa
  • <install_dir>\packs\financial_payments_vn.n.n.n\swift

Where <install_dir> is the installation location of the IBM Transformation Extender base product, and n.n.n.n is the version of the pack.

Installing the pack on Windows systems

Follow these steps to install the pack on Windows systems:

  1. Obtain the image from Passport Advantage.
  2. Run the executable file:
    finpay_1005_1003.exe for base version 10.0.3.0
    finpay_1005_1000.exe for base version 10.0.0.0
    finpay_1005_900.exe for base version 9.0.0.4
    Accept the license agreement.
  3. Follow the prompts to complete the installation.

=====================================================================
PROJECT FILES
=====================================================================

The following projects are extracted from the IBM_financialpayments_10.0.5.0.zip when the file is unzipped.

Each of the projects is described briefly in the following section.

Project summaries

The following projects are contained in the UIProjectImports directory.


nachaContestedDishonoredReturn.zip - ACH Contested Dishonored Return example
Contains the files, schemas, and maps required to run the NACHA “ACH Contested Dishonored Return example”.

nachaDishonoredReturn.zip ACH Dishonored Return example
Contains the files, schemas, and maps required to run the NACHA “ACH Dishonored Return example”.

nachaEDI.zip - ACH EDI example
Contains the files, schemas, and maps required to run the NACHA “ACH EDI example”.

nachaISO20022CreditTransfer.zip - ACH ISO20022 Credit Transfer example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Credit Transfer example”.

nachaISO20022DirectDebit.zip - ACH ISO20022 Direct Debit example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Direct Debit example”.

nachaISO20022Rejects.zip - ACH ISO20022 Rejects example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Rejects example”.

nachaISO20022 Returns.zip - ACH ISO20022 Returns example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Returns example”.

nachaPaymentRelatedInfo.zip - ACH Payment Related Information example
Contains the files, schemas, and maps required to run the “ACH Payment Related Information example”.

nachaRefusedNotificationOfChange.zip - ACH Refused Notification Of Change example
Contains the files, schemas, and maps required to run the “ACH Refused Notification Of Change example”.

nachaReturnedEntriesReport.zip - ACH Returned Entries Report example
Contains the files, schemas, and maps required to run the “ACH Returned Entries Report example”.

nachaReturnNotificationOfChange.zip - ACH Return Notification Of Change example
Contains the files, schemas, and maps required to run the “ACH Return Notification Of Change example”.

nachaSchemas.zip - NACHA schemas
Contains common NACHA example schemas.

nachaSWIFT.zip - ACH mapping from/to SWIFT example
Contains the files, schemas, and maps required to run the “ACH mapping from/to SWIFT example”.

nachaValidation.zip - ACH Validation example
Contains the files, schemas, and maps required to run the “ACH Validation example”.

nachaXML.zip - XML to ACH PPD example
Contains the files, schemas, and maps required to run the “XML to ACH PPD example”.

sepaCompliance.zip - SEPA compliance validation
This validation framework will take in any UNIFI 20022 formatted XML message and validate UNIFI rules and the set of rules published by the EPC.
See topic Building multiple maps via Deploy.

sepaDE.zip - DTAUS SEPA Example
Contains the files, schemas, and maps required to run the “DTAUS SEPA Example”. (German example.)

sepaEPC.zip - SEPA EPC Validation Example
Contains the files, schemas, and maps required to run the “SEPA EPC Validation Example”.
See topic Building multiple maps via Deploy.

sepaFR.zip - MINOS/CFONB SEPA Example
Contains the files, schemas, and maps required to run the “MINOS/CFONB SEPA Example”. (French example.)

sepaIT.zip - RNI SEPA Example
Contains the files, schemas, and maps required to run the “RNI SEPA Example”. (Italian example.)

sepaPainPacs.zip - PAIN/PACS Example
Contains the files, schemas, and maps required to run the “PAIN/PACS Example”.

sepaSchemas.zip - SEPA schemas
Contains common SEPA example schemas.

sepaSwiftFin.zip - SWIFTNet FIN/ SEPA Example
Contains the files, schemas, and maps required to run the “SWIFTNet FIN/ SEPA Example”.

sepaUK.zip - BACS / SEPA Example
Contains the files, schemas, and maps required to run the “BACS / SEPA Example”. (U.K. example.)

swiftBankFileXML.zip - SWIFT BIC/CCY files to XML
Contains common SWIFT bictoxml and currencytoxml executable maps.

swiftFromLMF.zip - SWIFT from LMF
Contains maps that facilitate mapping data to SWIFT from Logical Message Format.
See topic Building multiple maps via Deploy.

swiftJVCReport.zip - SWIFT MT JVC Report example
Contains the files, schemas, and maps required to run the “SWIFT MT JVC Report example”.

swiftMT950Split.zip - SWIFT MT950 example
Contains the files, schemas, and maps needed to run the SWIFT MT950 Splitter map example.

swiftMTCompliance.zip - SWIFT MT Java Validation Component (JVC)
Contains the files, schemas, and maps required to run SWIFT MT compliance.

swiftMTmxTranslation.zip - SWIFT MT / MX Translation maps example for Design Server 10.0.0
Contains the files, schemas, and maps required to run the “SWIFT MT / MX Translation maps example”.

swiftMTmxTranslation_10.0.x.zip - SWIFT MT / MX Translation maps example for Design Server 10.0.3 and above
Contains the files, schemas, and maps required to run the “SWIFT MT / MX Translation maps example”.

swiftMTSchemas.zip - SWIFT MT schemas
Contains schemas that provide a full syntactic definition of the SWIFT MT user-to-user messages.

swiftMXCompliance.zip - SWIFT MX compliance schemas
Contains schemas that are needed to run the SWIFT Compliance example.

swiftMXmsgPackage.zip - SWIFT MX Message Bundle and Unbundle map example
Contains the files, schemas, and maps required to run the “SWIFT MX Message Bundle and Unbundle map example”.

swiftMXschemas.zip - SWIFT MX schemas
Contains schemas that provide a full syntactic definition of the SWIFT MX user-to-user messages,

swiftToLMF.zip - SWIFT to LMF
Contains maps that facilitate mapping data to SWIFT to Logical Message Format.
See topic Building multiple maps via Deploy.

swiftUCapi.zip - SWIFT Universal Confirmation API example 
Contains maps that generate Universal Confirmation MT199 from SWIFT Tracker PaymentStatusRequest API. 

swiftUCcsv.zip - SWIFT Universal Confirmation CSV example 
Contains maps that generate Universal Confirmation MT199 from CSV File Structure payment confirmation. 

swiftUCfin.zip - SWIFT Universal Confirmation SWIFT FIN example 
Contains maps that generate Universal Confirmation MT199 from SWIFT FIN MT103. 

Installation directory

The Pack for Financial Payments installs project import files into the following directory:

install_dir\packs\financial_payments_v10.0.5.0\UIProjectImports

The project import files are provided as a convenience and should not be used with Windows based Design Studio implementations.

The UIProjectImports directory contains multiple .zip files, each of which contains a project that can be imported into the Design Server.

You must have administrative privileges to import projects.

=====================================================================
USING THE PACK WITH THE IBM DESIGN SERVER
=====================================================================

  1. Login to the Design Server.
  2. Click the Import Project icon.
  3. In the Import Project dialog, drag the .zip file into the Project Zip File box.
  4. Click the Import button to import the project.

=====================================================================
CONFIGURATION FILES
=====================================================================
The swiftMTjvcConfig.tar.gz file is contained within UIProjectImports directory. The UIProjectImports directory is located in the following location:
install_dir\packs\financial_payments_vn.n.n.n\UIProjectImports
Where install_dir is the installed location of the base product, and 10.0.5.0 is the current version of the pack.
Use these steps to run this file:

Extract the swiftMTjvcConfig.tar.gz file:
Before you import the swiftMTCompliance.zip file, follow these steps.
Perform the steps in the same directory location as the Design Server is installed:
  1. Create a temp directory called packs.
    Example: /home/user/packs
  2. FTP (in binary mode) the swiftMTjvcConfig.tar.gz to the pack's directory defined in step 1.
  3. Untar the swiftMTjvcConfig.tar.gz file.
    Example:
    $ tar -zxf swiftMTjvcConfig.tar.gz
     
  4. Run the jvcsetup.sh script.
    Example:
    $ ./jvcsetup.sh

    The script copies the following to the ITX server:
    jvcwrap.jar
    jval2020.jar
    packs/swift folder and sub-folders, includes the jval2020.prop and XML metadata.
  5. OPTIONAL: Run the cleanjvc.sh script.
    Example:
    $ ./cleanjvc.sh
    The script removes the following to the ITX server:
    jvcwrap.jar
    jval2020.jar
    packs/swift folder and sub-folders, includes the jval2020.prop and XML metadata.
  6. After importing the swiftMTCompliance.zip project, the jval2020.prop file must be uploaded (added) to the project using the Files tab. Set the Folder to:
    data/../maps
  7. Restart Design Server: docker restart tx-server.
    NOTE: To reflect any jval2020.prop updates onto the swiftMTCompliance.zip project, delete the previously uploaded (added) jval2020.prop file, then repeat steps 6 and 7.

=====================================================================
USING THE SEPA VALIDATION EXAMPLE
=====================================================================
Follow these procedures to use the SEPA EPC Validation example.

Before using this example, the EPC Technical Validation Set schemas must be downloaded.

These schemas come with an EPC disclaimer:
Disclaimer: SEPA XSDs are not developed for ‘production’ purposes, they are to instantiate the business rules and restrictions contained in the implementation guidelines in a formal interchange format, sometimes referred to as Technical Validation Subsets (TVSs). Production instantiations should refer to the default ISO 20022 namespaces.

For Direct Debit implementation:
Download the Direct Debit schemas and unzip them into a directory of your choice.

Following the links below (all the schema files will need to be renamed to match the name of the ISO20022 schema name):

Download Direct Debit schemas as follows:

Direct Debit Core Scheme Customer-to-Bank Schemas:
Download EPC130-08 SDD Core C2B IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC130-08_2019_V1.0_ from each of the file names.
Direct Debit Core Scheme Interbank Schemas:
Download EPC114-06 SDD Core Interbank IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC114-06_2019_V1.0_  from each of the file names.
Direct Debit Core Scheme E-Mandate Service Schemas:
Download EPC002-09 SDD Core E-Mandate IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC002-09_2019_V1.0_ from each of the file names.
NOTE: The maps are designed to use the CORE schemas. Additional map changes will be necessary to use the B2B schemas.
Direct Debit Business to Business Scheme Customer-to-Bank Schemas:
Download EPC131-08 SDD B2B C2B IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC131-08_2019_V1.0_ from each of the file names.
Direct Debit Business to Business Scheme Interbank Schemas:
Download EPC301-07 SDD B2B Interbank IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC301-07_2019_V1.0_ from each of the file names.
Direct Debit Business to Business Scheme E-Mandate Service Schemas:
Download EPC129-09 SDD B2B E-Mandate IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC129-09_2019_V1.0_ from each of the file names.

For Credit Transfer implementation:
Download the Credit Transfer schemas and unzip them into a directory of your choice following the links below:

Download Credit Transfer schemas as follows:
Credit Transfer Scheme Interbank Schemas:
Download EPC115-06 SCT Interbank IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC115-06_2019_V1.0_ from each of the file names.

Credit Transfer Scheme Customer-to-Bank Schemas:
Download EPC132-08 SCT C2B IG 2019 V1.0 XSD.zip from
Rename the schemas included in this .zip file to remove the prefix -
EPC132-08_2019_V1.0_ from each of the file names.


Run the SEPA EPC Validation example
Before you can run the SEPA EPC Validation example, you must add the schemas that you download from SEPA with the schemas that are contained in the sepaEPC.zip file. Before you import the sepaEPC.zip into the Design Server:

  1. Download the schemas from SEPA from the location(s) described in the previous section.
  2. Unzip the contents of the sepaEPC.zip.
  3. Add the schemas that you downloaded from SEPA to
    filedata/schemas/ct
    filedata/schemas/dd
    schemadata/schemas/ct
    schemadata/schemas/dd
  4.  Compress the following folders into a compressed file called: sepaEPC_updt.zip.
    filedata
    files
    maps
    schemadata
    schemas
     __description__
  5. Import into the Design Server as described in Importing projects.

=====================================================================
KNOWN ISSUES AND WORKAROUNDS
=====================================================================

Building some of the source maps might trigger M202 warnings like the warning shown below. These messages can be ignored:

---------------------------------------------------------------------

M202 WARNING:

    Map: sepvalid   Output: FileType [4]:outputcard

    Parm 1 of EITHER doesn't match required type.

---------------------------------------------------------------------

=====================================================================
RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARS)
=====================================================================
The APAR PH28953 is fixed in this version of the product.  

=====================================================================
CONTACTING CUSTOMER SUPPORT
=====================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.
 

=====================================================================
NOTICES AND TRADEMARKS
=====================================================================

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Privacy Policy Considerations
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy , the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement .

Trademarks and service marks
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml .

  • Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
  • Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
  • Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
  • UNIX is a registered trademark of The Open Group in the United States and other countries.


This product includes software developed by the Eclipse Project ( http://www.eclipse.org/ ).

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSE82XJ","label":"IBM Sterling Transformation Extender Pack for Financial Payments"},"ARM Category":[{"code":"a8m0z000000bmLpAAI","label":"Pack for Financial Payments"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.0.5"}]

Document Information

Modified date:
05 October 2022

UID

ibm16249903