- Report E2E_EMERGMON_CONFIGURE execution ends in dump:
Category ABAP Programming Error Runtime Errors ASSERTION_FAILED ABAP Program CL_SMSY_TRACER================CP Application Component SV-SMG-SYS Error analysis The following checkpoint group was used: No checkpoint group specified If the FIELDS addition was used in the ASSERT statement, you can find the content of the first 8 fields specified in the following overview: LV_NO_SMSY_USAGE = `Call of SAPLSMSY_SHLP-SMSY_SHLP_EXIT_RESTRICT_KONZS is forbidden! Caller is SAPLSDSD-CALL_SHLP_EXIT` IV_MSG = space IV_CHAR_PARAM_1 = SMSY_SHLP_EXIT_RESTRICT_KONZS IV_CHAR_PARAM_2 = space IV_CHAR_PARAM_3 = space Information on where terminated The termination occurred in ABAP program "CL_SMSY_TRACER================CP", in "TRIGGER_DUMP". The main program was "E2E_EMERGMON_CONFIGURE". In the source code, the termination point is in line 47 of (Include) program "CL_SMSY_TRACER================CM00D". Contents of system fields SY-TITLE Program E2E_EMERGMON_CONFIGURE SY-MSGTY E SY-MSGID SMSY_OBSOLETE SY-MSGNO 001 SY-MSGV1 SAPLSMSY_SHLP-SMSY_SHLP_EXIT_RESTRICT_KONZS SY-MSGV2 SAPLSDSD-CALL_SHLP_EXIT
- SAP Note 2422106 is not applicable on SolMan 7.2 systems
- KBA 2583923 is not valid for the system as there is no custom (Z) code
SAP Solution Manager 7.2 SP08
matchcode button f4 help , KBA , SV-SMG-SYS , Solution Manager System Landscape , SV-SMG-DIA , Diagnostics , Problem
About this pageThis 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.