getting abap dump "convt_no_number" only for some users

[Former Member]

gurus ,

There was a request from HR department to add new infotypes for P_ORGIN . we were to add 022 (education) , 41(date specification_ and 105(communication) ,

when i add those info types and generated the role ,

The user was able to login to that transaction but on executing ABAP dump CONVT_NO_NUMBER is generated saying "unable to interpret "A" as number .

But when i execute the same transaction from the Admin user , i am able to execute it successfully .

below is the ABAP dump ,

"

Runtime Errors CONVT_NO_NUMBER

Exception CX_SY_CONVERSION_NO_NUMBER

Date and Time 24.11.2008 14:59:56

-

---

-

---

Short text

Unable to interpret "A" as a number.

-

---

-

---

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSPO1" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

-

---

-

---

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

-

---

-

---

Error analysis

An exception occurred that is explained in detail below.

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

caught in

procedure "POPUP_TO_CONFIRM" "(FUNCTION)", nor was it propagated by a RAISING

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 "A" as a number, but

since the value contravenes the rules for correct number formats,

this was not possible.

-

---

-

---

How to correct the error

Whole numbers are represented in ABAP as a sequence of numbers, possibly

with an algebraic sign.

The following are the possibilities for the representation of floating

point numbers:

[algebraic sign][mantissa]E[algebraic sign][exponent]

[algebraic sign][whole number part].[fraction part]

For example, -12E+34, +12E-34, 12E34, 12.34

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"

"SAPLSPO1" or "LSPO1U06"

"POPUP_TO_CONFIRM"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"POPUP_TO_CONFIRM" "(FUNCTION)", or its possible occurrence must be declared in

the

RAISING clause of the procedure.

To prevent the exception, note the following:

-

---

Kindly help to solve this

Edited by: Julius Bussche on Nov 24, 2008 11:47 AM

[Former Member]

When confronted by a runtime error (dump), your first port of call should be https://service.sap.com to search for the runtime error message for that transaction, or possibly the message which it would have raised had it not dumped...

In this case it [SAP Note 1223807|https://service.sap.com/sap/support/notes/1223807] looks like a possible candidate.

I also removed the very long parts of the dump for you and some information about your server / company...

Cheers,

Julius

[Former Member]

i have already searched the market place but i didn't get any solution .

i have also saw the note you mentioned , but that doesn't help me in my case .

because i am not getting this abap dump when i run it from a user who has development /admin authority

but for other normal users they get this dump when they execute this ..

also these are new info types that we added to P_ORGIN

[WolfgangJanzen]

Please quote also the coding excerpt which shows where the error was detected.

In addition check on the caller of this function module (see ABAP dump: caller stack section).

One potential candidate is the very first coding line (# 35):

answer = 'A'.

If the caller has passed a numeric-typed actual parameter ANSWER, then this will result in the reported runtime errror. Unfortenately, the formal parameter ANSWER is not assigned to any data type (should be TYPE C).

Most likely you'll have to send a bug report to SAP (use the message component assigned to the component which calls function module POPUP_TO_CONFIRM, or BC-SRV-ASF-POP).

Edited by: Wolfgang Janzen on Nov 24, 2008 1:06 PM