Analyis Authorization, sometimes : is fine sometimes * is needed

[former_member318517]

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

[former_member209032 · Accepted solution]

Hi,

  If 0comp_code is used in the query (ex if it is in rows) then : authorization won't work. If 0COMP_CODE is not used for authorization check then remove the authorization check for the infoobject or make it *.

Regards,

Raghavendra.

[oliver_luette]

Hi,

is 0COMP_CODE compounded to any other infoobject you're using in the query? That may cause the auth check to fail...

Regards

Oliver

[former_member182470]

Why don't you keep * for 0costcenter as well as for 0comp_code as all your reports are being controlled by 0plant?

Hope you got my idea..