standard job failing -- SAP_CCMS_MONI_BATCH_DP

[Former Member]

Hi All,

I am running the standard job SAP_CCMS_MONI_BATCH_DP from last couple of years on my production system. I monitored from last 4 - 5 days the job is getting cancelled and providing a dump like ABAP/4 processor: CONVT_NO_NUMBER.

Sometime the job log says :

1. Logical system MSG_SSS is not configured in table /ISDFPS/ALE_SYS

Job cancelled after system exception ERROR_MESSAGE

2. Logical system Startuptoo is not configured in table /ISDFPS/ALE_SYS

Job cancelled after system exception ERROR_MESSAGE

Dump says :--

Runtime Errors CONVT_NO_NUMBER

Exception CX_SY_CONVERSION_NO_NUMBER

Date and Time 17.02.2009 13:16:59

Short text

Unable to interpret "More than 100 " as a number.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was n

caught in

procedure "RETRY_MECHANISM_SETUP" "(FORM)", nor was it propagated by a RAISIN

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The program attempted to interpret the value "More than 100 " as a number, bu

since the value contravenes the rules for correct number formats,

this was not possible.

There is probably an error in the program

"SAPLSALSLD_MODEL".

Please advice ..

[Former Member · Accepted solution]

Hai,

Seems to be the problem with the ABAP program, system is expecting a number in the place of 'More than 100'. So please have a look into the program in concern "SAPLSALSLD_MODEL".

Also check SAP Market place to get some appropriate notes.

Regards,

Yoganand.V

[former_member198270 · Accepted solution]

Hello Shashi, If standard job is failing in your production system which is inturn trigerring SAP standard program. I think you can have SAP to look into that and raise an OSS message.

Regards, Amber S

[Former Member]

Hi Shashi

Yes!!!!!! definitely an ABAP Program error..

The source code may have been modified and has something as "more than 100" wrongly written in it. This could also be a case of variable settings as text is input in place of numbers or something like this.

An ABAPer could help you better in this one or the best possible solution definitely would be an OSS message to SAP.

Regards

Chen

[Former Member]

Yes All !!

The issue has been resolved, I got the correction on note number 907975. I did the support pack upgrade and its working fine.

Thanks for all of your valuable inputs. I really Appreciate to all.

Added value points to all ..