SAP Knowledge Base Article - Preview

3640223 - Risk analysis not working in GRC access control, throws error "0 cannot be interpreted as number"

Symptom

  • SuccessFactors risk analysis in GRC is not functioning as expected.
  • User-level risk analysis shows no results in both foreground and background modes, except when a single user is selected.
  • Role-level risk analysis works in the foreground but throws the error "0 cannot be interpreted as number" when running in the background.
  • HTTP 500 Internal Server Error encountered during background risk analysis.
  • Runtime error observed: CX_SY_CONVERSION_NO_NUMBER in ST22 logs.


Read more...

Environment

  • Access Risk Analysis

Product

SAP Access Control all versions

Keywords

risk analysis, grc access control, successfactors, background risk analysis, role-level analysis, user-level analysis, 500 internal server error, cx_sy_conversion_no_number, runtime error, extra spaces in role, gg_d_rbp security admin, sap note 3578935, sap note 3262940, sap note 3524696 , KBA , GRC-SAC-ARA , Access Risk Analysis , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.