When you upgrade SAS Solution for IFRS 9 v01.2020 to v10.2020 and have two similar base dates (for example, previous and current) in both federated areas, in the current period, the Initialize Cycle task fails with the following message:

The error occurs because the system searches for default instances that are based on the federated area ID and do not take into account the base date and configuration set.

As a workaround, remove the prior SAS Solution for IFRS 9 federated area properties (for example, ifrs9.2020.01) from the IRM Mid-Tier Server Properties in SAS^® Management Console. The side effect is that the SAS^® Infrastructure for Risk Management instances from the prior federated area are not viewable anymore; however, the old SAS Solution for IFRS 9 objects (for example, cycles) are still viewable.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Infrastructure for Risk Management	Microsoft® Windows® for x64	3.6		9.4 TS1M6
		Linux for x64	3.6		9.4 TS1M6
SAS System	SAS Solution for IFRS 9	Linux for x64	10.2020		9.4 TS1M7
		Microsoft® Windows® for x64	10.2020		9.4 TS1M7

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for this issue for SAS Infrastructure for Risk Management 3.6 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/G2T.html#67254

---

After you upgrade SAS Solution for IFRS 9 v01.2020 to v10.2020 and have two similar base dates (previous and current) in both federated areas, in the current period, the Initialize Cycle task fails with "ERROR: There are no FX Analysis Data objects linked to the cycle: cycle_key."

Type:	Problem Note
Priority:	high

Date Modified:	2021-01-29 10:35:41
Date Created:	2021-01-18 03:50:24