Short dump when creating SD billing with error message as Overflow during the arithmetical operation (type P) in program "SAPLV45P"

[Former Member]

Hi All,

Please suggest how to remove this Short dump that is coming when creating SD invoice thru t-code VF01. Error message: Overflow during the arithmetical operation (type P) in program "SAPLV45P". I have enclosed Short dump error message as an attachment for reference.

Thanks & Regards,

Saurabh

I am unable to attach screen shot so giving below Dump data as per SAP message;

What happened?
    Error in the ABAP Application Program

    The current ABAP program "SAPLV45P" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.

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 "RV_XVBAPF_MENGEN_ERMITTELN" "(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.

[Lakshmipathi]

Overflow during the arithmetical operation (type P) in program SAPLV45P

Check the following notes on similar issue but not related to above program

• Note 858223 - FSCM-BD: Overflow for arithmetical operation
• Note 1358895 - Contract billing: Dump due to too large totals flow
• Note 1614397 - FCC: Overflow during arithmetical operation -account

G. Lakshmipathi

[Shiva_Ram]

In order to guide further, you must provide additional information like what kind of billing document, what kind of sales process etc. You may check OSS Note 1132220 - COMPUTE_BCD_OVERFLOW: Field overflow during rebate settlemnt if it is related to rebate processing.

Also check whether any of the user exit used in VF01 is causing this.

Regards,