General Electronic Reporting and ISO20022 Configurations Operations 7.1 and 7.2

General Electronic Reporting and ISO20022 Configurations Operations 7.1 and 7.2

GER and ISO20022 Payments

General electronic reporting and ISO20022 configurations Operations 7.1 and 7.2

Reviewed 01122017

  1. Get updated platform for General Electronic Reporting (GER)
  1. Operations 7.1

Ensure all provided corrections for Organization Administration are installed

  1. On the Project, Full details | Monitoring, choose X++ updates
  2. Filter by Organization Administration, select all and add to the package:

2. Operations Spring release 7.2

KB’s for Electronic reporting (GER) are now cumulative updates:

KB 4052250 Electronic reporting (GER) framework aggregated update 2

KB 4054500 Electronic Reporting (GER) Cumulative Update 3

KB 4055564 Electronic reporting update 4

KB 4056107 Electronic reporting (GER) cumulative update 5

Generally, for any updates for GER framework in 7.2 version, search Electronic reporting (GER) Cumulative Update, choose the latest version and add it to the package.

Note only the latest update needs to be installed. The latest updated includes the all the previous updates.

Install the package.

  1. Run Full build on All models, mark Referenced packages and synchronize Database

  1. Install KB’s needed for the feature you are setting up in Operations

In addition to having the most updated GER framework (the step above), some additional updates are needed. Such prerequisites, if any, are listed while importing a configuration.

Make overview over features with corresponding configurations user plans to take in use. Import the latest versions of these configurations and make an overview over missing, if any, KB’s needed to be installed.

More information about importing electronic reporting configurations:

Example for vendor payments based on ISO20022 Credit transfer and the configurations used. Note the order – it is starting from the child level (ISO20022 Credit transfer (country extension) and ending to the root configuration (her Payment model).

Export

ISO20022 Credit transfer (country extension)

ISO20022 Credit transfer

Payment model mapping 1611

Payment model mapping to destination ISO20022

Payment model

Import

ISO20022 Pain.002

ISO20022 Camt.054

Example of such overview over needed KB’s for Operations 7.1 and Operations 7.2:

Operations 7.1 (as of 14th November 2017)

Selection of KB’s listed as prerequisites while importing configurations for ISO20022 Credit transfer, ISO20022 Pain.002 and Camt.054

Payment model mapping 1611:

4036459

Payment model mapping to destination 20022

3213292

3218206

4020082

4020448

4023992

4025797

4032903

4034278

4034005

4035918

4040236

4041922

4039640

Payment model

4012871

Operations 7.2 (as of 14th November 2017)

Payment model mapping to destination 20022

4036532

4039636

4039639

4041207

4043157

  1. Rebuild table references

Organization administration | Electronic reporting | Rebuild table references

  1. Update Electronic reporting parameters

Organization administration | Electronic reporting | Related links – Electronic reporting parameters

LCS

This parameter control number of threads/parallel downloads from LCS repository (mainly to speed up the LCS repository opening).

In the future, number of LCS configurations will increase, so downloading (open LCS) will take more time. If you do any heavy calculations (while opening LCS) in the background (rare scenario, but still), you should adjust this number in parameters to reduce system load.

  1. Setup (in not already done) Repository based on LCS – configuration provider Microsoft).

Note: configurations imported from Operations resources are no longer supported. If you already have imported resources from Operations resources, and adjusted these, you need to import the corresponding configuration from LCS repository, generate derived configuration and add any customizations on that. This requires that you have setup your company as configuration provider (in addition to Microsoft).

  1. Open the repository and import the needed configuration(s) – use always the latest version for the configuration provided. Start importing the configurations from the child level.
  1. Default for model mapping

Note: Starting from the Payment model version 8, mappings are existing in separate configurations (Payment model mapping 1611, Payment model mapping to destination ISO20022).

First, this is done for better solution maintenance – in case of changes in mapping, Payment model version will not be incremented, and this will not require to rebase all existing formats and other derived configurations, only download the latest mapping configuration.

Second, having different functionalities separated (like ISO20022, NETS or ESR payments) will allow user to skip installing X++ hotfixes for functionality they are not going to use.

In some cases when we have more than one mappings of the same type in the GER solution tree (i.e. when we have mappings in the model configurations with version lower than 8, or in case of additional customization mappings not provided by Microsoft), we should specify which mapping to use by selecting the Default for model mapping checkbox. Task recording is available: Manage model mapping configurations for electronic reporting (ER).

After configurations are imported, set both Payment model mapping 1611 and Payment model mapping to destination ISO20022 as default for model mapping:

Trouble shooting

  1. GER framework is updated
  2. Check that you use the latest configurations versions available on LCS
  3. Delete usage data
  4. Reset IIS
  5. Delete existing report configuration and import it again
  6. If you need but cannot delete a configuration, check Migration cleanup tool (Organization administration > Periodic > Migration cleanup) and delete the configuration. If not available deploy KB 4045747.
  7. Import configuration manually at Shared assets library

Note:

Importing configurations manually, you need to start on the root level (from Payment model to ISO20022 Credit transfer (Country context)).

Importing the configurations from MS LCS repository, you need to import the child level first (From e.g ISO20022 Credit transfer (Country extension) – configurations on the parent levels are automatically imported.

Some important links:

Page 1 of 9

Top View