COMPUTE_BCD_OVERFLOW

In ECM, the compensation planning iView, we get a runtime error when trying to apply a percentage adjustment to salary. Here is the error message. We're on ECC 6 EHP4, NW 7 EHP1.
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          06/23/2010 16:01:07
Short text
Overflow during the arithmetical operation (type P) in program "SAPLPARA".

try to identify the record causing the overflow....my guess is that it's a large number maybe in a currency which does not use decimal points, eg JPY
Also what was the % increase? Perhaps that was unusually large too.

Similar Messages

ABAP runtime errors    COMPUTE_BCD_OVERFLOW

ABAP runtime errors    COMPUTE_BCD_OVERFLOW
       Occurred on     12/08/2010 at 06:44:17
>> Short dump has not been completely stored. It is too big.
Error analysis
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1. The results field of type P is to small and the result does not fit
    into it.
    places.
2. The result or partial result has more than 31 decimal places.
How to correct the error
You may need to define the result field to be larger, if it is still
possible to do so.
It may be possible to split the current process so that only smaller
values occur.
Eine Vorablösung zu dem aufgetretenen Fehler findet sich vielleicht
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
If you require an interim solution to this error, you can look in the
SAP note system. If you have access to
the SAP notes system yourself, enter the following search strings:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
point)

Hi Ganapati,
Check this thread COMPUTE_BCD_OVERFLOW in Database Performance collector.
Note 543749 - ABAP runtime error COMPUTE_BCD_OVERFLOW
It may helps you.

COMPUTE_BCD_OVERFLOW Runtime Error in 'Z' Program

Hi Gurus,
In one of my report, i am getting this error:
Run Time Error: Compute_BCD_Overflow
Exception              CX_SY_ARITHMETIC_OVERFLOW
Short text
    Overflow during the arithmetical operation (type P) in program
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
     caught in
    procedure "OUTPUT_DATA" "(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:
    An overflow was discovered in an ongoing arithmetical operation with
    operands of type P. Possible causes are:
    1. The result field of type P is too small for the result.
    2. The result or a intermediate result has more than 31 decimal places.
I searched a lot on SCN but most of the solutions are for standard SAP programs and SAP has provided notes for that.
I am pasting a part of subroutine. Below is subroutine in which error is coming:
FORM output_data .
   gt_data1_copy = gt_data1.
   SORT gt_data2 BY article site sloc.
   SORT gt_data1_copy BY article site sloc.
   LOOP AT gt_data1 INTO gwa_data1.
     READ TABLE gt_data2 INTO gwa_data2 WITH KEY article = gwa_data1-article
                                                 site = gwa_data1-site
                                                 sloc = gwa_data1-sloc BINARY SEARCH.
     IF sy-subrc = 0.
       gwa_output-soh_qty = gwa_data2-soh_qty.
       gwa_output-count_qty = gwa_data2-count_qty.
       gwa_output-var_qty = gwa_data2-var_qty.
       gwa_output-var_value = gwa_data2-var_qty * gwa_data2-map. "Error is coming at this point.
             "Here I am multiplying variance quantity to Moving average price(MAP) to get variance value.
     ENDIF.
endloop.
endform.
Request your help.
Appreciate Your Help in Advance.
Regards,
Pankaj

Hi Nabheet,
Thanks for your reply.
ok..I ll try by keeping this as of type quantity.
data : var_value type mseg-menge.
Hope this will work fine.Actually this reports takes too much time. I ll run this in background and get back to you with result.
Regards,
Pankaj

Run time error COMPUTE_BCD_OVERFLOW coming at MFBF

Hi Guru's
User is getting runtime error at MFBF as below:
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
This coming at production but not coming at test server.
when user is trying to enter quantity 66059 there is error coming but when he enter quantiy as 6095 there is no dump.
Please suggest any solution to avoid and also suggest sap Notes if there is any available.
Thanks in advance,
regards,
Nilesh I

Hi,
I can see that there are several SAP notes regarding this issue, you just need to check their symptons and if they are valid for your SAP_APPL release and support package.
Here are the SAP notes:
- 1295055: Product cost collector: Field AFPO-WEMNG set incorrectly
- 964308: COMPUTE_BCD_OVERFLOW in CKMO_GET_ORD_HIST_NETWR_MMIM
I hope they help you.
Regards,
Marcelo

ABAP DUMP in ST03N : COMPUTE_BCD_OVERFLOW

HI Guys,
     When I go to ST03N, Expert Mode, Select the Daily workload, I double clicked on 15.03.2010, the system will hit the abap dump : COMPUTE_BCD_OVERFLOW. However, when I try for other dates, it is fine. Which meant it is only the 15.03.2010 causing the dump.
    following is the system's details:
     SAP R/3 Kernel :              640_REL
     Kernel Patch :                304
     SAP BASIS : SAPKB62041
    I have raised a OSS message to SAP, and the consultant had replied me with two sapnotes:
     881968
     840763.
    I've implemented the 881968 but there is some error after implement, the ST03N cannot be executed. ( ABAP DUMP syntax error). Hence, I revoked the sapnote 881968. For the 840763, I did not implement since it advised to upgrade the support package for SAP BASIS and I am not sure what is affected after I upgrade the support package.
    The system I mentioned above is not a BW system and I doubt this is why I get the SYNTAX ERROR dump after implement the sapnote.
    Did you guys encountered similar problem? Any solution for this?
    The following is ABAP DUMP: COMPUTE_BCD_OVERFLOW:
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
       Occurred on     29.03.2010 at 09:37:45
Overflow for arithmetical operation (type P) in program "SAPWL_ST03N"
What happened?
Error in ABAP application program.
The current ABAP program "SAPWL_ST03N" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
A value does not fit in a calculation field.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure
"CALCULATE_PROFILE" "(METHOD)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1. The results field of type P is to small and the result does not fit
    into it.
    places.
2. The result or partial result has more than 31 decimal places.
Edited by: Wei Jian Kwan on Mar 30, 2010 3:57 AM

Hi Amber,
    The following sapnote is not implementable in my system:
     0001384846 ST03N: BCD_OVERFLOW in SAPWL_LCL_03N_HITLNRESPTI
     This is due to the current Support Pack : SAP BASIS in my system is : SAPKB62041 and the corrections in the sapnote are only available for 700 until 720.
Best Regards,
Ken

Compute_bcd_overflow Error...

Hi everybody:
Anyone can helpme, about this error code:
compute_bcd_overflow and/or
CX_SY_arithmetic_overflow.
I get this when i'm trying into the Tcode CK40n
The DUMP says:
The result field of type P is too small for the result.
The result or a intermediate result has more than 31 decimal places.
Thanks in advance.
OP

Hello,
Refer SAP
Note 620532 - Runtime error COMPUTE_BCD_OVERFLOW in program SAPLCOSD
Note 1323002 - Material cost estimate: Runtime error COMPUTE_BCD_OVERFLOW
Note 1239612 - Short dump COMPUTE_BCD_OVERFLOW in profit center costing
Regards,
Ravi

COMPUTE_BCD_OVERFLOW MIRO Incoming Invoice

Hi, Gurus,
I have extended most of my domains successfully and everything seems fine until in MM when the MM consultant tries to simulate or save in trans MIRO, a short dump appears saying the above. I have look at the position specified in the dump and BETRAG and PX_DRSEG-WRBTR reference the same domain which has the same number of characters so, it seems here things are OK. But there is that dump as follows:
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          05.06.2008 09:49:32
Short text
     Overflow during the arithmetical operation (type P) in program "SAPLMRMP".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMRMP" 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_ARITHMETIC_OVERFLOW', was not
      caught in
     procedure "SPERRGRUND_T" "(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:
   An overflow was discovered in an ongoing arithmetical operation with
   operands of type P. Possible causes are:
   1. The result field of type P is too small for the result.
   2. The result or a intermediate result has more than 31 decimal places.
ow to correct the error
   The result field must be enlarged, if this is still possible. It may
   also be possible to break up the current process into subprocesses so
   that only smaller values occur.
   There may already be a solution to the error in the SAP notes system.
   If you have access to the SAP notes system first try searching with the
   following keywords:
    "COMPUTE_BCD_OVERFLOW"
    "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
    position)
    "SAPLMRMP" or "LMRMPF1K"
    "SPERRGRUND_T"
   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
"SPERRGRUND_T" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
tem environment
SAP-Release 700
Application server... "dev"
Network address...... "10.0.0.81"
Operating system..... "SunOS"
Release.............. "5.9"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "tetradev"
Database type..... "ORACLE"
Database name..... "DEV"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 31 2006 20:59:23"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 16759392
Heap.... 0
Page.... 188416
MM Used. 9422712
MM Free. 3143832
er and Transaction
Client.............. 300
User................ "USER01"
Language key........ "E"
Transaction......... "MIRO "
Program............. "SAPLMRMP"
Screen.............. "SAPLMR1M 6000"
Screen line......... 34
Information on where terminated
    Termination occurred in the ABAP program "SAPLMRMP" - in "SPERRGRUND_T".
    The main program was "SAPLMR1M ".
    In the source code you have the termination point in line 39
    of the (Include) program "LMRMPF1K".
    The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"
     occurred in
    procedure "SPERRGRUND_T" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMRMP "; its source code begins in line
    12 of the (Include program "LMRMPF1K ".
Source Code Extract
Line SourceCde
    9 * --> PI_XNULLPOS: Liegt eine Nullpos. vor? (wenn ja: keine Verarb.) *
   10 * <-> PX_DRSEG: Struktur mit den aktuell zu bearbeitenden Pos.daten    *
   11 ----
   12 FORM SPERRGRUND_T USING    PI_RBKPV TYPE MRM_RBKPV
   13                            PI_XNULLPOS LIKE BOOLE-BOOLE
   14                   CHANGING PX_DRSEG TYPE MMCR_DRSEG.
   15
   16   CHECK PI_XNULLPOS = SPACE.           "keine Nullpos.
   17
   18   DATA s_t169g TYPE t169g.
   19   SELECT SINGLE * FROM t169g INTO s_t169g
20                   WHERE   bukrs = px_drseg-bukrs
21                     AND    tolsl = 'ST'.
22   check sy-subrc = 0.
23   IF NOT s_t169g-xw2ne IS INITIAL.
24     EXIT.
25   ENDIF.
26   DATA: datum1 LIKE sy-datum,
27         DATUM2 LIKE SY-DATUM.
28   DATA: DT_DIFF(8) TYPE C.
29
30   CHECK: PI_RBKPV-XRECH NE SPACE,
31          PX_DRSEG-RETPO = SPACE, "keine Sperre durch eine Retoure-Pos.
32          PX_DRSEG-EINDT NE '00000000',
33          PX_DRSEG-PSTYP NE C_PSTYP_1, " keine Blanket PO
34          PX_DRSEG-FPLNR IS INITIAL.    " kein Rechnungsplan
35
36   DATUM1 = SY-DATLO.
37   DATUM2 = PX_DRSEG-EINDT.
38   CHECK DATUM2 > DATUM1.
>>>>   BETRAG = PX_DRSEG-WRBTR * ( DATUM2 - DATUM1 ).
40   DT_DIFF = ( DATUM2 - DATUM1 ).
41
42   SY-SUBRC = 0.
43   CALL CUSTOMER-FUNCTION '001'
44        EXPORTING I_RBKPV = PI_RBKPV
45                  I_YDRSEG = PX_DRSEG
46        EXCEPTIONS CALL_FAILURE = 001.
47   CASE SY-SUBRC.
48     WHEN 001.
49       MESSAGE E271 RAISING PARAMETER_ERROR.
50   ENDCASE.
51
52   RC = 0.
53   CALL FUNCTION 'MRM_TOLERANCE_CHECK'
54        EXPORTING
55             I_AKT_WERT       = BETRAG
56             I_BUKRS          = PX_DRSEG-BUKRS
57             I_TOLSL          = 'ST'
58             I_VERGLEICHSWERT = '0.00'
Please assist as urgently as possible. Assistance will be rewarded.
Thanx in advance.
Edited by: Darlington Chiyamha on Jun 5, 2008 11:06 AM

Hi Darlington,
You usually get that, if a number you calculate i getting bigger than the field it is stored in allows.
Check the data declaration of the variable which holds this value. If the resultant value is too large then the ABAP throws this exception.
You may handle this using CATCH ENDCATCH statement.
Check this e.g.:
PARAMETERS fact TYPE i.
DATA: fact_save TYPE i,
res(16) TYPE p.
ARITHMETIC_ERRORS contains COMPUTE_BCD_OVERFLOW ***
CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 5.
res = fact_save = fact.
SUBTRACT 1 FROM fact.
DO fact TIMES.
MULTIPLY res BY fact. "<- COMPUTE_BCD_OVERFLOW
SUBTRACT 1 FROM fact.
ENDDO.
ENDCATCH.
IF sy-subrc = 5.
WRITE: / 'Overflow! Factorial of', fact_save,
'can not be calculated.'.
ELSE.
WRITE: / 'Factorial of', fact_save, 'gives', res.
ENDIF.
Edited by: Raj on Jun 5, 2008 2:43 PM

COMPUTE_BCD_OVERFLOW (New GL Migration)

Hi Experts,
I'm doing the migration from Classic GL to New GL when I encountered this dump during migration of current fiscal year documents.
Runtime Errors: COMPUTE_BCD_OVERFLOW
Exception: CX_SY_ARITHMETIC_OVERFLOW
ABAP program "CL_FAGL_OI_READ===============CP" was terminated.
Error analysis:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "P_SPLINFO_COMPRESS" "(METHOD)", 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:
An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:
1. The result field of type P is too small for the result.
2. The result or a intermediate result has more than 31 decimal places.
How to Correct Error:
How to correct the error
    The result field must be enlarged, if this is still possible. It may
    also be possible to break up the current process into subprocesses so
    that only smaller values occur.
    There may already be a solution to the error in the SAP notes system.
    If you have access to the SAP notes system first try searching with the
    following keywords:
     "COMPUTE_BCD_OVERFLOW"
     "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
     position)
     "CL_FAGL_OI_READ===============CP" or "CL_FAGL_OI_READ===============CM00L"
     "P_SPLINFO_COMPRESS"
    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
"P_SPLINFO_COMPRESS" "(METHOD)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
SAP-Release 700
Application server... "cixusr"
Network address...... "10.216.15.219"
Operating system..... "HP-UX"
Release.............. "B.11.31"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 12
Shortdump setting.... "full"
Database server... "fh007204"
Database type..... "ORACLE"
Database name..... "CIX"
Database user ID.. "SAPERP"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700

Hi Dear,
In the running system if you add any additional depreciation area we have to run the program for data consistence. Please check with SAP. I hope there will be a Note.
Regards
Radha

COMPUTE_BCD_OVERFLOW on MIRO. Any SAP NOTE?

Hi,
I'm getting a COMPUTE_BCD_OVERFLOW dump with the the CX_SY_ARITHMETIC_OVERFLOW exception when doing a MIRO process.
The user is using huge values in the PO and the error is related to a multiplication between this values. (EKTE table is hoding the huge value that is greater than 1 billion).
I see no ABAP solution at this moment. A friend said that we should have some SAP note to make the field greater.
Does someone knows about this note?
below we have more details related to the DUMP:
Termination occurred in the ABAP program "SAPLFDMM" - in "DETERMINE_AMOUNTS".
The main program was "SAPLMR1M ".
The procedure is in program "SAPLFDMM "; its source code begins in line
197 of the (Include program "LFDMMF00 ".]
Source code:
300 *     Quantity of goods received greater than purchase order qua
301 *     or "Delivery completed" indicator is set
302       if ekbp-wemng > ekbp-bemng     "Überlieferung
303       or ekbp-elikz <> space.         "Endlieferungskennzeichen
304 *       offene Bestellmenge = Wareneingangsmenge minus Rechnungs
305 *       open PO quantity = quantity of goods received - quantity
306         offen_bestmenge = ekbp-wemng - ekbp-remng.
307       else.
308 *       offene Bestellmenge = Bestellmenge minus Rechnungsmenge
309 *       open PO quantity = PO quantity minus quantity invoiced
310         offen_bestmenge = ekbp-bemng - ekbp-remng.
311       endif.
312
313 *------- Obligo = offene Bestellmenge * Bestellwert / Bestellmen
314       if ekbp-bemng > 0.               "Division durch 0 verhind
315         if offen_bestmenge = ekbp-bemng.
316           wabetrag = ekbp-bewtw.   "erspart unnötige Multiplikat
317         else.
>>>>>           wabetrag = offen_bestmenge * ekbp-bewtw / ekbp-bemng.
319         endif.
320       endif.
321     endif.   "if ekbp-vrtkz = const_po_valuebased
Thanks in advanced!

Hi Rob, Thanks for answer.
Unfortunately, I do not have access to do that. The MM functional asked for the ABAP leader of the project for look for it...
I asked here because maybe someone had a common problem and want to share the solution. I'm not lazy If I could look at the note sure I would did!
Does someone knows this error or something related on this?
Thanks in advanced!

COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

Hello all,
I'm getting the ABAP Dump in CJ13 tcode please find below dump error & my system release info:
Component version    SAP ECC 6.0
SAP_ABA      700     0010     SAPKA70010
SAP_BASIS     700     0010     SAPKB70010
SAP_APPL     600     0006     SAPKH60006
Kernel release    700 (Sup.Pkg lvl.      52)
Begin of Dump -
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          07.04.2008 11:53:18
Short text
     Overflow during the arithmetical operation (type P) in program "SAPLKBPR".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLKBPR" 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_ARITHMETIC_OVERFLOW', was not
     caught in procedure "READ_COSA" "(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:
     An overflow was discovered in an ongoing arithmetical operation with
    operands of type P. Possible causes are:
    1. The result field of type P is too small for the result.
    2. The result or a intermediate result has more than 31 decimal places.
Regards,

HI,
My patch level is below but even i got a dump of "COMPUTE_BCD_OVERFLOW".
Component       Lvl
SAP_ABA     0019
SAP_BASIS     0019
Pls. suggest.
Thanks in advance.

COMPUTE_BCD_OVERFLOW ST22 dump

Dear All,
When I run the ECC_PRD_BITX_D_FDM_INVOICE, which is a standard SAP(program FDM_INVOICE_MEMORY).
I get COMPUTE_BCD_OVERFLOW ST22 dump.
This short dump occured due to CX_SY_ARITHMETIC_OVERFLOW i.e. Target field size was not able to store the value of source field at the folowing code location while assigning value to l_days_of_delay.
   90       ENDIF.
   91
   92 *     set actual discount and delay in payment
>>>>>       l_days_of_delay = sy-datlo
   94                       - <open_item>-zfbdt
   95                       - <open_item>-zbd1t.
Are there SAP Notes that can solve this problem?
My system details
S/w Component : SAP_APPL
Release : 604
Highest Support : SAPKH60405
sapnote_0000620532, sapnote_0001239612 , sapnote_0001323002 do not work in my system
Regards,
Jack Silverz

hi jack,
just check these avalilabe notes for your dump.
620532
1323002
1239612
hope this will help u.
thanks

DUMP (COMPUTE_BCD_OVERFLOW), when we are attenting to make an invoice MR1M

We are presenting a DUMP (COMPUTE_BCD_OVERFLOW), when we are attenting to make an invoice in trans: MR1M
The termination occurred in the ABAP/4 program "SAPLMRMP " in   "SPERRGRUND_T".
The main program was "SAPLMR1M ".
The termination occurred in line 346 of the source code of program "LMRMPFS0 " (when calling the editor 3460).
003430     DATUM1 = SY-DATLO.               (06.01.2011)
003440     DATUM2 = PX_DRSEG-EINDT.    (31.07.2011)
003450     CHECK DATUM2 > DATUM1.
Ø         BETRAG = PX_DRSEG-WRBTR * ( DATUM2 - DATUM1 ). ,
                                  87535759,78      * (20110731 u2013 20110106)Ø
We want to know, how can we skip the error and make the invoice without changing the delivery date in the PO (approbation are already made by president etc.) or changing the amount of the invoice.
This is a standard program.
Can i skip the error wih customizing??
Edited by: Auristela Marin on Jan 6, 2011 11:03 PM

If this is an unmodified SAP program, the forum really cannot help you. Look for notes and if you don't find any, raise an OSS message.
Rob

COMPUTE_BCD_OVERFLOW in Database Performance collector.

Hi experts,
I have problem with refreshing data in DB02.
I'm having COMPUTE_BCD_OVERFLOW short dump after attempting to refresh db02 view.
Please help

Hi All,
This only happens last monday. There were no system modification happend and the only ground that i'm looking at is the continuous growth of tablespaces.
It was stated in SAP note 1066044 that;
Reason and Prerequisites
Systems with more than 99999 database objects experience an overflow during refresh. Data-elements DB02N_SE_TAB_NUM, DB02N_SE_IND_NUM, DB02N_SE_OTH_NUM and DB02N_SE_TOT_NUM are too short to handle such figures.
"Solution"
The problem only occurs on release 700 and it is corrected with basis support package 13. Unfortunately the corrections cannot be applied via snote but you can perform it manually:
Go to transaction SE11 and change the following 4 data-elements as described below:
DB02N_SE_TAB_NUM from domain "DB02N_NUMBER_5" to "DB02N_NUMBER_15"
DB02N_SE_IND_NUM from domain "DB02N_NUMBER_5" to "DB02N_NUMBER_15"
DB02N_SE_OTH_NUM from domain "DB02N_NUMBER_5" to "DB02N_NUMBER_15"
DB02N_SE_TOT_NUM from domain "DB02N_NUMBER_5" to "DB02N_NUMBER_15"
==================================================================
I checked the data elements and its already 15 so I moved forward to SAPnote 1080761
- I'm now planning to do what is stated in this sap note.
Any suggestion on this experts?
here is the current level of sap basis: release 700 level 13

COMPUTE_BCD_OVERFLOW in st22

Hi guys, my 4.6C system in st22 show u201CCOMPUTE_BCD_OVERFLOWu201D
The dump detail show:
ABAP runtime errors COMPUTE_BCD_OVERFLOW
Occurred on 12.05.2010 at 17:15:07
Overflow for arithmetical operation (type P) in program "SAPLSTUW "
What happened?
The current ABAP/4 program "SAPLSTUW " 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.
A value does not fit in a calculation field.
If you require an interim solution to this error, you can look in the SAP note system. If you have access to
the SAP notes system yourself, enter the following search strings:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
point)
"SAPLSTUW " or "LSTUWF01 "
"CONVERT_PFDIAREC"
Appreciate anyone have any ideal what is going on?
Thanks

Hi,
Please search for SAP Notes for your system and patch level.
This sort of error usually occurs when the amounts involved are too big for the program to handle. The ABAP will be trying to write to a table or structure which does not have enough space.
Get an ABAPer to work with you and analyse the short dump (ST22 will take you there). Then run the proposal in debug mode and see where it drops out. Once you have identified the table or structure get your basis people to allocate more space to it, re-index it or generally kick it into shape.
Regards,
Shitij

ABAP Short Dump - COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

Runtime errors      COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
I want to move Currency variable with 4 decimals to another currency variable with 2 decimals. Please advice me with a suitable solution without causing short dump.
Appreciate Your Help in Advance.
Thanks.
Kannan.

SAP catch the exception like this :
CATCH SYSTEM-EXCEPTIONS conversion_errors = 1
                                    arithmetic_errors = 5.
              xkwert = xkomv-kwert * 1000 * xkomv-kpein / komp-mgame.
              xkomv-kbetr = xkwert.
            ENDCATCH.
            IF sy-subrc = 1 OR sy-subrc = 5.
              xkomv-kbetr = 0.
              xkomv-fxmsg = '802'.
              komp-fxmsg = '802'.
            ENDIF.

COMPUTE_BCD_OVERFLOW

Similar Messages

Maybe you are looking for