DUMP in JOB SAP_REORG_SPOOL_DB

[Former Member]

Hello.

I have problems with the standard JOB SAP_REORG_SPOOL_DB. It is released in devolopment system and it works properly, but the same JOB in production system doesn't work.

The error is the next.

ABAP runtime errors CONVT_NO_NUMBER

Occurred on 11.08.2008 at 04:10:09

Unable to interpret "000007ST01" as a number.

What happened?

The current ABAP/4 program "RSPO1043 " had to be terminated because

one of the statements could not be executed.

This is probably due to an error in the ABAP/4 program.

[Former Member]

I had the same dump (ECC 6.0):

CONVT_NO_NUMBER

Unable to interpret "000000ST01" as a number.

I resolved my problem by debugging RSPO1043 and deleting all records from structure DATATAB which contain not numerical value in field COUNTER (function RSTS_READ, function module RSTS_READ).

You should do this after C_RSTS_READ function call (that function fill the structure DATATAB). To do this you can set breakpoint on statement:

RSTS_G_SUBRC = SY-SUBRC

function module RSTS_READ

when debug stop on that breakpoint you should delete records with not numerical value in field COUNTER

hope it helps,

Marcin

[Former Member]

I have the same problem (on 46C)

remark: in another client report RSPO1043 ran ok on same system

remark: report RSPO0043 runs ok

shortdump CONVT_NO_NUMBER

is there at least a workaround ?

do i really need report RSPO1043 or can i just use RSPO0043 ? I ask this, because if you just do

SPAD > administration > check consistency

then it is using RSPO0043 !! (saw this with sm66)

[Former Member]

I got it

the solution is described in note 741680:

IMPORTANT NOTE:After you implement this note in Releases 4.6C and 4.6D, dump CONVT_NO_NUMBER may occur in certain cases, resulting in a termination of RSPO1043. In this case, delete all existing Temse objects with the name KONS with transaction SP11.*

[Former Member]

Oss Note 1034532 and 16083

It shall work in PRD too.

Hope it helps

Amit