Originally Posted by
HariOm
This problem persists as of October 2021. We don't even have FFP entered, and it gives us that error when trying to manage the booking. Tried clearing caches in multiple browsers. Only workaround was to handle the task by phone.
[Correction: ticket purchased using AA miles, so that FFP must be in there.)
I conclude this is an issue with QR unable to distinguish between FQTS, FQTV, FQTR and FQTU on partner redemptions.
I had this issue with an Aadvantage redemption. The only solution is to have the ticketing carrier update the FF numbers after ticketing which should resolve with QR within 24 hours.
See
https://www.australianfrequentflyer....deus-fqtv/amp/ for the definitions of FQ fields