CONVT_NO_NUMBER
mediumType Conversion Failed — Value Is Not a Valid Number
Module: ABAP
What this means
CONVT_NO_NUMBER is raised when ABAP tries to move or convert a character string into a numeric field (INT, NUMC, PACK, etc.) and the source value is not a valid number. This is extremely common when: user input from a screen field contains letters or special characters where a number is expected; a text file import contains formatting characters (commas, currency symbols, spaces) that were not stripped before conversion; Customising table entries contain non-numeric values in a field that the program expects to be numeric; or an RFC or BAPI receives a parameter that does not match the expected type.
ST22 will show the exact field and value that failed conversion. Trace back where this value originates — screen input, file, RFC parameter, or Customising. Add a numeric validation check (e.g., using a regular expression or CONDENSE + check) before the conversion. For file imports, strip formatting characters before moving to numeric fields. For Customising-sourced values, check the table entry in SM30.
Quick Info