The folowing dump occurs when executing Data Consistency check in Usage Logging Scenario in Solution Manager system:
Category ABAP Programming Error
Runtime Errors CONVT_NO_NUMBER
ABAP Program CL_AGS_CC_SCMON_CU_EXE========CP
Application Component SV-SMG-CCM
"22/2018" cannot be interpreted as a number
Error in the ABAP Application Program
The current ABAP program "CL_AGS_CC_SCMON_CU_EXE========CP"
had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
This exception cannot be caught in the context of the current statement.
The reason for the exception is:
An attempt was made to interpret value "22/2018" as a number.
As this value contravenes the rules for displaying numbers correctly,
this was not possible.
Information on where terminated
The termination occurred in ABAP program "CL_AGS_CC_SCMON_CU_EXE========CP",
in "TRANSLATE_WEEK_MONTH_FORMAT". The main program
In the source code, the termination point is in line 27 of (Include)
Program "CL_AGS_CC_SCMON_CU_EXE========CP" was started as a background job.
Job name....... SM:CCM_SCMON_WEEK_AUTO_CLEAN
Note: the value "22/2018" is subject to change.
Solution Manager SP05-SP07
SM:CCM_SCMON_WEEK_AUTO_CLEAN, CONVT_NO_NUMBER, CL_AGS_CC_SCMON_CU_EXE , KBA , SV-SMG-CCM , Custom Code Management , Bug Filed
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.