COMPUTE_BCD_OVERFLOW or CX_SY_ARITHMETIC_OVERFLOW
Hi!!
After BW 3.5 now We have working with BI 7.0 and I'm trusting to charge a infoobject with rutine in a transformation and when I trust to charge the infoobject with DTP, the system gives me a dump with this message:
Err.tmpo.ejec. COMPUTE_BCD_OVERFLOW
Excep. CX_SY_ARITHMETIC_OVERFLOW
What can I do?The level patch is 8.
Thanks and best regards,
Patricia
Hi
It occurs when any of your variable is not able to accomodate the result of the calculated expression.
Please find out the place where it is raising this exception.
Please change the type of the variable to accomodate the calculated value.
Kindly reward points.
Thanks
Sriram
Similar Messages
-
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. -
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 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,
PankajHi 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 IHi,
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 AMHi 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 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 AMHi 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....... 700Hi 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
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. -
Overflow dump ( COMPUTE_BCD_OVERFLOW) in Routine RV64A920
Hi,
Routine RV64A920 changes resulting in "Overflow during the arithmetical operation (type P) in program "SAPLV61A" dump".
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Form FRM_KONDI_WERT_920
Issue with the below line of code
xkomv-kbetr = ( xkwert * 1000 ) / komp-mgame .
kbetr is curr length 11 decimals 2
xkwert is curr length 13 decimals 2
mgame is quan length 13 deciamls 3
Please let me know how to fix or if any note available for rounding.
Thanks & Regards,
Jack.Hi,
Instead of directly assigning the value to xkomv-kbetr. Store the value in a temporary variable of type p length 13 decimals 2 . Multiply by 10^n to get the correct result.
Then assign the temp value to xkomv-kbetr.
Sample Code
DATA : lv_temp TYPE P length 13 decimals 2.
lv_temp = ( xkwert * 10^n ) / komp-mgame.
Then assign lv_temp to xkomv-kbetr.
To get proper value, you have to multiply or divide by 10^n .
Regards,
DPM -
Getting dump everyday COMPUTE_BCD_OVERFLOW
Hello Everybody,
Everyday at particular time we are getting COMPUTE_BCD_OVERFLOW runtime error.
At same there is no failed jobs..........
=========================
Runtime Error COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Occurred on 17.05.2010 at 09:15:41
Overflow for arithmetical operation (type P) in program "SAPLXM06"
What happened?
Error in ABAP application program.
The current ABAP program "SAPLXM06" 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.
User, transaction...
Client.............. 600
User................ "INTE"
Language key........ "E"
Transaction......... "ME22 "
Program............. "SAPLXM06"
Screen.............. "SAPMM06E 0120"
Screen line......... 88
Information on where terminated
The termination occurred in the ABAP program "SAPLXM06" in "WRITE_LIST".
The main program was "SAPMM06E ".
The termination occurred in line 124 of the source code of the (Include)
program "ZXM06F01"
of the source code of program "ZXM06F01" (when calling the editor 1240).
The program "SAPLXM06" was started as a background job.
Error occurred during batch input processing
Processing was terminated because the exception "CX_SY_ARITHMETIC_OVERFLOW"
occurred in the
procedure "WRITE_LIST" "(FORM)" but was not handled locally, not declared in
theRAISING clause of the procedure.
The procedure is in the program "SAPLXM06 ". Its source code starts in line 69
of the (Include) program "ZXM06F01 ".
=====================================
Please advice us on this.
Thanks in advance.
Regards,
PratyushaHi,
What is your SAP release ?
I am not sure if it applicable for your problem..
Have a look at the below note
[Note 869851 - Field overflow with large purchase order quantities|https://service.sap.com/sap/support/notes/869851]
Regards.
Rajesh Narkhede -
Error while doing MIRO-Overflow for arithmetical operation (type P) in prog
Hi ,
I am getting the error while doing the MIRO as below-
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Date and Time 20.05.2009 10:07:03
Short text
Overflow during the arithmetical operation (type P) in program "SAPLMRMC".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMRMC" 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 "MRM_AMOUNT_QUANTITY_PROPOSE" "(FUNCTION)", nor was it propagated by
a RAISING clause.
Since the caller of the procedure could not have anticipated that the
Please let me know how can this be removed.Hi,
There can be some problem with tolerances set in the customizing.
In my case, I was getting this error because of delivery date variance. The difference between delivery date maintained in PO and invoice date was huge and hence the multiplication of price of PO and difference of delivery date was huge and that was the reason for error.
Similarly in your case also, there will be some tolerance limit problem.
Please check your tolerance limits set in customizing.
Regards,
Mihir Popat -
Error while execting Tcodes ST04,ST03,DB12,DB02
Hi Experts,
I had installed QAS & DEV instances successfully on one windows host.Below are the syste details.
OS :- Windows 2003 64 bit Standard Edition
Database :- Oracle 10.2.0.2
SAP :- R/3 4.7 Enterprise Ext. 200 SR1
Support Pack :-
SAP_Basis 6.20 Level 41
SAP_APPL 470 Level 21
SAP_ABA 6.20 Level 41
I am facing problem while executing transactions related to database i.e st04,st03,db12,db02.
After executing this transactions I received followng dumps.
1) Runtime Errors DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Database error text........: "ORA-00904: "KEY": invalid identifier"
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "DBDS/NEW DSQL"
2) Runtime Errors RAISE_EXCEPTION
Exception condition "DB_RELEASE_UNKNOWN" raised
Error analysis
A RAISE statement in the program "SAPLSORA" raised the exception
condition "DB_RELEASE_UNKNOWN".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
3)Runtime Errors BCD_ZERODIVIDE
Exception CX_SY_ZERODIVIDE
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ZERODIVIDE', was neither
caught nor passed along using a RAISING clause, in the procedure
"SKOM_CT_PERF_BUF_REDO" "(FUNCTION)"
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:
In the current program "SAPLSKOM", an arithmetic operation ('DIVIDE',
'/', 'DIV', or 'MOD') with a type P operand attempted to divide
by 0.
4) Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
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
"SKOM_CT_PERF_BUF_LIB" "(FUNCTION)"
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.
Thanks,
SachinHi Markus,
I have seen the note#741119, it asks to apply pack SAPKB64004, but its says its valid for Release 640 only. My release is 640 currently:
Software Component Name SAP_BASIS
Software Component Release 620
Support Package Level 0041
Highest Imported Support Package SAPKB62041
Short Description of Software Component SAP Basis Component
Support Package type Basis Support Pkg.
My question is, can i apply the pack directly on release 620? The prequisite to this pack says, the release should be 640. This forum helped me a lot, hoping you guys will solve my this issue as well.
Regards. -
Revoked SES with account assignment distributed by quantity cannot be modified or deleted
Hi All
I have users who are posting service entry sheet with the account assignment distributed
on a quantity basis across multiple maintenance orders. The acceptance works perfectly but we are having problems if a correction or cancellation is required.
The service acceptance can be revoked successfully but afterwards it is not possible to change the service quantity or to delete the service entry sheet. When we try we receive an ABAP runtime error:
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Date and Time 08.07.2014 14:25:12
Short text
Overflow during the arithmetical operation (type P) in program
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_EX_MMSRV_ACC_DIST_SAP======CP" 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 "IF_EX_MMSRV_ACC_DIST_SAP~DISTRIBUTE_ACC_ASSIGNMENTS" "(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.
This problem does not occur if I run the same scenario any of the following variations so I'm confident the problem is related to the account assignment distribution by quantity:
Single account assignment
Distributed account assignment via percentage
No service acceptance/revoke has been posted
There are ways to get around the problem but I'm trying to find a SAP Note that may be relevant. I haven't had any luck yet. Does this problem ring a bell with anybody who might be able to point me towards an appropriate note?
Thanks
RobynHi,
Kindly refer the below OSS Note, which explains the reason and correction for the error which you are facing.
1715475 - MAA2: ML81N/MIRO: false postings for Service PO -
Hi,
We are getting the following error in the PRD system .
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Short text
Overflow during the arithmetical operation (type P) in program
What happened?
Error in the ABAP Application Program
The current ABAP program "AQFKSD01========SD_STOCKS-01==" had to be termi
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', wa
caught and
therefore caused a runtime error.
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 have tried searching in notes and etc but still not helpful.
Did anyone solve the problem.
Thanks in advanceThis seems to be a query, right (transaction SQ00/SQ01)
The computation fields are too small, the values don´t fit into the types you defined.
Markus
Maybe you are looking for
-
IPod is seen by Windows but not iTunes
Ever since upgrading to iTunes V7.x (currently the latest version 7.3) my iPod does not show up in iTunes. I can access the iPod from Windows and open folders etc. My iPod is connected via Firewire and has worked fine in all versions of iTunes until
-
Display Port to DVI, 22inch Neovo, no signal
So I bought a new Alu Macbook last week including the according Display Port to DVI adaptor, arrive home, plug in the adaptor, connect the screen (Neovo E-W22) > NO SIGNAL. I see my laptop screen "flash" for a sec like it always does when it detects
-
Ipad air 2 touch id not working when plugged in
A very strange problem tonight. After work, I grabbed my iPad Air 2 which was plugged in to the Apple Charger next to my chair. Touched the home button to open it - nothing happened. Tried again. Nothing happened. Entered the code and the IPad Ai
-
Authentication on OnDemand for WebServices
Hi, We are developing an interface from Siebel to CRM On Demand. We imported the Account WSDL into Siebel. I do not see any login method in the WSDL. So when sending XML from Siebel to On Demand, how do I send the authentication? Will it be as part o
-
Idoc state 56. jdbc to multiple idoc.
hi, i have made a jdbc to multiple idoc scenario. i disabled so many mandatory field. i defined a external defination for the idoc. i changed occurance for "IDOC" segment. i can send multiple idoc successfully to ECC. BUT: I found that state 56 of th