Like I said, it's a very custom query and there have been significant database changes from v8.2 to v12. There have even been significant code and business logic changes so while the field exists, the use of it is no longer valid in version 12 for whatever reason. I'd suggest debugging the query more to see what it is doing and why.