Note that this A* to Z* is a regular source of confusion.
Due to "piggy backing" of ranges (if you start using them...) it often does not show up.
Particularly if you see special characters at the beginning of the FROM value then it is suspect that the ASCII range might end with something after Z if it is another strange character.
But the main source of confusion lies in inadequate use of the function module SUSR_SYNC_USER_TABLES with table type = 'X' in programs. PFCG "orphans" data into UST12 and does not clear the fields nicely every time, which leaves BIS data which can create strange ranges for the COUNTER field.
Users typically end up with more access than they need or appear to have (they won't complain...) but sometimes also have less.
Old roles created / maintained / transported which contained these problems might still exhibit such behaviour.
Unfortunately the old notes (which relate to the time when such roles might have been created and transported) are mostly not available anymore, but there are some new ones about ranges and the table sync from PFCG data to the real data in the AUTHORITY-CHECK.
As Patrick mentioned, convert to A-Z* type patterns and you will be better off.
Julius