RE:[sap-basis] ABAP DUMP in ST03N : COMPUTE_BCD_OVERFLOW
Posted by
Admin at
|
Share this post:
|
0 Comments
| | Posted by Ken_Kwan (SAP Basis) on Mar 30 at 11:58 PM | |
1384846 is not for SAP BASIS 620.
Best Regards,
Ken..
---------------Original Message---------------
From: Ken_Kwan
Sent: Tuesday, March 30, 2010 2:48 AM
Subject: 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.
__.____._ Best Regards,
Ken..
---------------Original Message---------------
From: Ken_Kwan
Sent: Tuesday, March 30, 2010 2:48 AM
Subject: 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.
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion