topic Re: Runtime error while executing transaction BDLS in Application Development and Automation Discussions

Runtime error while executing transaction BDLS

Former Member — Fri, 22 Aug 2008 12:32:04 GMT

Hello,

While executing BDLS transaction for converting logical system names I am getting following error

Runtime Errors CONVT_NO_NUMBER

Except. CX_SY_CONVERSION_NO_NUMBER

Short text

Unable to interpret "7,160 " as a number.

How to resolve the above problem?

Re: Runtime error while executing transaction BDLS

jurjen_heeck — Fri, 22 Aug 2008 12:35:04 GMT

> Runtime Errors CONVT_NO_NUMBER

> Except. CX_SY_CONVERSION_NO_NUMBER

> Short text

> Unable to interpret "7,160 " as a number.

Make sure this 7,160 is entered as 7.160 or 7160, depending on the desired figure.

This is -by the way- not a security issue so this isn't the proper forum.

Re: Runtime error while executing transaction BDLS

Bernhard_SAP — Fri, 22 Aug 2008 12:54:18 GMT

Hi Rachel,

BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly

lives in runtime only and is checked by syntax checker.

Now, sometimes tables have inconsistencies associated with them and you

will get this dump when a syntax check is performed on them.

So please check this and regenerate the culprit tables.

So please redo the steps for BDLS and check. There are

probably some tables which could be determined by you (syntax

check - in case program has already been saved only)

An easy way to check this is to run RBDLS2LS program (old BDLS) and

afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>

<<)>(>

<<(><<)>)>ClientName>) program.

Known tables which caused such dumps in the past are:

DFKKCOLFILE_P_W

DFKKKO

DFKKMKO

DFKKREP06

DFKKREP06_S

DFKKREP07

DFKKREV06

DFKKREV07

Simply reactivate the tables you find out in SE11.

Another thing which has lead to this dump in the past is

in your R/3-System the value ' x ' is

additionally added to the value of your current release in the basis

release table SVERS.

The table RSBASIDOC takes the release value from the table SVERS.

If you change value 'x' to your release in both tables (SVERS and

RSBASIDOC) and

and activate again your source system connection. This could solve the

dump too.

I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)

b.rgds, Bernhard

Re: Runtime error while executing transaction BDLS

Former Member — Mon, 25 Aug 2008 09:33:26 GMT

Thanks Bernhard for the quick response.

You have Immense knowledge.

Regards,

Rachel

Re: Runtime error while executing transaction BDLS

Bernhard_SAP — Mon, 25 Aug 2008 10:54:03 GMT

....no, I don't.

But I have the possibility to make use of shared knowledge inside the SAP support organisation....

By the way...could you solve the issue in the meantime?

b.rgds, Bernhard