Hello,
Ran across this issue a few times. Lets say a report is being secured by 0PLANT (where we will created AAuths with specific plant values), and that report is coming off a Cube where 0COSTCENTER and 0COMP_CODE is also auth relevant. We don't care about those and most times a : will suffice as a value. But this time the report runs fine with a : for 0COSTCENTER but we get an auth error on 0COMP_CODE because a : won't suffice, the logs say that the system is looking for a *. The message is: "AND 0COMP_CODE LIKE *"
Any reason for this?
Thanks,
Tom