Runtime error

[Former Member]

Hi,

i have problem while executing the transaction ML81n. It is giving runtime error as:

Runtime Errors BCD_FIELD_OVERFLOW

Except. CX_SY_CONVERSION_OVERFLOW

Date and Time 25.06.2010 17:55:10

Short text

A calculation field is defined too small.

Error analysis

An exception occurred that is explained in detail below.

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

caught in

procedure "ATREE_MODIFY_FOR_ORDER" "(FORM)", 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:

A value generated during processing is too large for the

field "ATREE_ESSR_WA-NETWR" of the program "SAPLMLSR".

The problem when i key in the transaction ML81n and press enter, it is directly giving the runtime error. In my view it may be the problem in recently opened PO which is there in ML81n by default. How to change that PO & why this error comes ?

-

---

thanks& regards,

Srinath

[Former Member]

A calculation field is defined too small.

How much more does SAP need to tell you?? In this case, I would be looking for an SAP note, or looking at the process in debug to find what the field contains and why it is now too small.

[Former Member]

Hi Break Point,

I can understand from the short dump that the calculated figure is large to accomodate into the field. But my doubt is how to by pass this short dump?

Becasue my user is not able to do any service entry sheets till this issue gets resolved as the system is not allowing the user to even enter into the transaction. And i can debug this but it takes time and moreover in production we dont have change authorization in debug to bypass the error. If u can suggest me in that case, it would be more helpful to me.

-

---

regards,

Srinath

[former_member206439]

Hi

This runtime errors that may occur during the conversion between data types. You can make an explicit conversion using MOVE, for example.

Implicit conversions are only caught in arithmetic expressions

Let me know one point.

Is it occured in custom development or standard program.

[former_member186444]

OSS is definitely the way to go. Maybe OSS Note 1051045 ?

[Former Member]

I can certainly understand the user's concerns... I would be trying to replicate somewhere where I could see the problem occur, or if this is happening in SAP standard code and not the result of a user enhancement that just went into production instance, begin an SAP Note search immediately.

If this suddenly starting occurring, I'd be looking a transport logs (STMS) to see what got put into Production that could affect this, if I didn't find an SAP Note in 10 minutes or so of searching with program name and fieldname and/or error text. If it's been introduced by user programming, the code needs to be fixed or the prior version obtained and retransported through the instances.