diff --git a/src/sap.ui.core/src/sap/ui/model/FilterProcessor.js b/src/sap.ui.core/src/sap/ui/model/FilterProcessor.js
index <HASH>..<HASH> 100644
--- a/src/sap.ui.core/src/sap/ui/model/FilterProcessor.js
+++ b/src/sap.ui.core/src/sap/ui/model/FilterProcessor.js
@@ -101,7 +101,7 @@ sap.ui.define(['./Filter', 'jquery.sap.global', 'jquery.sap.unicode'],
 		if (typeof oValue == "string") {
 			// Internet Explorer and Edge cannot uppercase properly on composed characters
 			if (String.prototype.normalize && (sap.ui.Device.browser.msie || sap.ui.Device.browser.edge)) {
-				oValue = oValue.normalize("NFD");
+				oValue = oValue.normalize("NFKD");
 			}
 			oValue = oValue.toUpperCase();
 			// use canonical composition as recommended by W3C
[FIX] FilterProcessor: Adapt normalization for MS Edge <I>+

Since MS Edge <I> the behaviour of toUpperCase with composed Unicode
characters changed, which requires compatibility decomposition to still
work as expected.

BCP: <I>
Change-Id: Id<I>a<I>c<I>cd9aab<I>c4dd<I>bc<I>