SAP Knowledge Base Article - Preview

3149633 - How to avoid/optimize long running BW2HANA authorization replication or timeout


Authorization replication will take place during transport/activation automatically, if the 'Limit replication' option in RS2HANA_VIEW is disabled.
Enabling 'Limit replication' option is potential workaround to avoid long activation/transport times. This, of course, does not impact the authorization replication time which still may be longer than expected, or maybe even time out:

  • TSV_TNEW_OCCURS_NO_ROLL_MEMORY, TSV_TNEW_PAGE_ALLOC_FAILED, SYSTEM_NO_ROLL dumps happen during the replication of privileges.
  • During the transport TIME_OUT and CALL_FUNCTION_REMOTE_ERROR dump(s) are triggered at authorization replication step.

This KBA provides an overview of what contributes to long running authorization replication in general and how to avoid/optimize it.



  • SAP NetWeaver 7.5
  • SAP BW/4HANA 1.0, 2.0, 2021


"authorization replication" "performance" "long running" "long runtime" "SAPLRSEC_CHECKS" "LRSEC_CHECKSF03" "FILL_UP_AUTHS" "CL_RS2HANA_AUTH_MANAGER" "RS2HANA_AUTH_RUN_RFC" "RS2HANA_AUTH_RUN" "RS2HANA_GEN" "ADSO" "InfoCube" "Query" "elem" "hcpr" "compositeprovider" "IOBJ" "TIME_OUT" "CL_RS2HANA_AUTH_AMDP" "ASSIGN_OBJECTS" , KBA , BW-WHM-MTD-HMOD-AUT , BW2HANA authorization generation , BW4-ME-HMOD-AUT , BW2HANA authorization generation , How To

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.