Hi @roman.gerteis,
Welcome to the community! 
The parse error issue that SonarQube creates is at the file level, so the parse error is somewhere in the file, not necessarily on the CREATE TRIGGER statement itself (I suspect the red underline is slightly misleading here). If you dig into the scanner logs, you should see a more precise indication of where the parser is tripping up. Feel free to post the log snippet when you find it.
Cheers,
Cameron.