SAP Knowledge Base Article - Preview

2897322 - Dump CONVT_NO_NUMBER occurs when printing form labels by SATO device types


  • You are trying to print a SmartForm or SAPScript label with SATO device type YS* e.g. YSTLTGL2 or YSTLTGT3, if the label contains any images or graphics, printing fails in Error status in SP01, Status text for output req. is  "Incorrect (Error in ABAP Processing)".

  • In transaction ST22, a short dump CONVT_NO_NUMBER is shown with following information:

Category                           ABAP Programming Error                                                                       
Runtime Errors                 CONVT_NO_NUMBER                                                                           
Except.                             CX_SY_CONVERSION_NO_NUMBER                                                  
ABAP Program                 YCL_PDL_IMP_ST_YST1===========CP                                          
Application Component    Not assigned                                                                                           

Short Text                                                                                                                                         
"BDS_L" cannot be interpreted as a number

What happened?                                                                                                                              
Error in the ABAP Application Program

The current ABAP program "YCL_PDL_IMP_ST_YST1===========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.


Information on where terminated                                                                                                      
The termination occurred in ABAP program "YCL_PDL_IMP_ST_YST1===========CP",
in "CONVERTLI". The main program

In the source code, the termination point is in line 32 of (Include)
program "YCL_PDL_IMP_ST_YST1===========CM006".
Termination was caused when the exception "CX_SY_CONVERSION_NO_NUMBER" was not
caught locally in
an internally called procedure (for example, a conversion exit). The
language command that calls the procedure internally is in the program
"RSPO_PDL_ADRV" - to be precise, in line " " of the (Include) program " ".


Source Code Extract (Source code has changed)                                                                            
Line SourceCde
28 xpos_tw = otf_data(5).
29 ypos_tw = otf_data+5(5).
30 l_direction = otf_data+10(1).
31 len_tw = otf_data+11(5).
>>>>> thickness_tw = otf_data+16(5).
33 num5 = thickness_tw / 2.




  • SAP_BASIS release 702 and above


SAP NetWeaver all versions


Dump, CONVT_NO_NUMBER, CX_SY_CONVERSION_NO_NUMBER, YCL_PDL_IMP_ST_YST1===========CP, CONVERTLI, RSPO_PDL_ADRV, thickness_tw = otf_data+16(5), print, label, SAPScript, Smart Form, SATO, Incorrect, Error in ABAP Processing , KBA , BC-CCM-PRN , Print and Output Management , BC-SRV-SCR , SAPscript , BC-SRV-SSF , Smart Forms , 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.