Structural Authorization in HR Standard Reports

[Former Member]

Hi Experts,

Structural authorization applied works as intended in standard transactions (e.g. PA20, PA30, PP01 etc.) but it does not work in standard report (e.g. Date Monitoring). User able to extract information for employee that he/she does not authorised to.

Is this normal Structural Authorization behaviour ? Is there anything that need to be done to enable the restriction as intended ? Appreciate your help to look into this matter and advise the way forward.

Best Regards.

[Former Member]

Hi,

I believe you should have the standard report debugged to see if there any authority check for P_ORGINCON. Since you say the report output is not being restricted by structural authorizations, so I suspect the the report has not been coded to check of the aforesaid authorization object. You can also run backend trace in ST01 to see if P_ORGINCON is being checked at all.

To enforce check on the object, you might want to explore the feasibility of implementing a BADI like HRPAD00AUTH_CHECK with the help of your developer.

Thanks

Sandipan

[Former Member]

Hi,

Are the standard reports executed, are a part of logical databases like SAPDBPNP, SAPDBPAP etc? You can reach out to technical team to get an answer for that. If yes, then ensure you are not having P_ABAP auth object with COARS = 2, REPID = * or the Program being executed.

[Former Member]

Hi Debmalya,

Thank you for highlighting, I've review P_ABAP granted to this ID. Once SAPDBPNP and COARS = 2 removed from the role. Standard report extraction works as intended but the message appeared seems misleading 'No Data Was Selected' - you'll only knows it failed Structural Authorization from SU53 screen shot.

Thank you again and best regards.

[shailvora]

This message was moderated.