Hi All,
This document is to discuss OBJECTS_OBJREF_NOT_ASSIGNED dump we have encountered on our GRC system(GRC 10).
We had a scenario where certain users are unable to display/process their GRC request from the browser with HTTP 500 - Internal Server error ( Screen-1) on the browser and OBJECTS_OBJREF_NOT_ASSIGNED dump in the GRC system(ABAP Stack).
Our security team investigated this for missing authorizations and they also deleted and recreated the user, but users still have this issue.
Screen 1 : Error user received
Screen 2 : ABAP dump on GRC system
Dump : OBJECTS_OBJREF_NOT_ASSIGNED
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
Excetion : CX_SY_REF_IS_INITIAL
ABAP Program CL_POWL_UI_HELPER=============CP
Application Component CA-GTF-SGF-POW
Reason for dump:
On further investigation of this issue we understood that this issue was caused due the old query/queries cached for that particular user id and got corrupted. Hence when user tries to open his/her GRC session, system was executing these corrupted query and hence dumps in the system. As these quires are stored at database level against the user name, the attempt to delete and recreate the user id will not work in this case.
Resolution :
We have run a report POWL_D01 to fix this issue. This report is used to clear the cache for the users to delete the all old queries .
This report allow you to input affected user id( multiple selection available) and you can run in display mode to view the current queries.
Screen 3 : POWL_D01 selection screen
Check box 'DISPLAY' will allow you to view the queries before deleting them, remember to un-tick this box to cleat the user cache
Screen 4 : Report output on deleting the user cache
Result :
User will be able to run new queries from browser without any dumps.
References :
- If you are interested to know more about report on POWL(Personal Object Worklist) please go though the below link
http://wiki.scn.sap.com/wiki/display/WDABAP/POWL+Reports
- FAQ on POWL
http://wiki.scn.sap.com/wiki/display/WDABAP/FAQ+ABOUT+POWL
Please comment and let me know if you have faced similar errors and resolution details.