BCD_OVERFLOW

[Former Member]

Hello Friends,

We are extracting data from CRM system into BW using data source 0CRM_SALES_ACT_1.

Data load failed with a short dump on the R/3 side. Short dump details are below..We are using BW 3.5 sp20.

Could you please help with this ? Any advice/comments greatly appreciated.

-

---

Runtime Errors BCD_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW Date and Time 13.03.2008 10:29:29

Short text

Overflow during an arithmetic operation (type P) in program

What happened?

Error in the ABAP Application Program

The current ABAP program "GP46IA8SII8PEAO4PK4UG075ZAE" had to be terminated

because it has

come across a statement that unfortunately cannot be executed.

A value is too long for a calculation field.

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_CONVERSION_OVERFLOW', was not

caught in

procedure "DECODE_BY_MOVE_CORRESPONDING" "(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:

In the current arithmetic operation with operands of type P an overflow

has been detected. Possible causes are:

1. The result field of type P is too small to store the result.

2. The result or an intermediate result has more than 31 decimal places.

How to correct the error

Maybe the result field - if still possible - must be defined larger.

Maybe the current process can be divided into separate units in a way

that only smaller values occur.

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"BCD_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"

"GP46IA8SII8PEAO4PK4UG075ZAE" or " "

"DECODE_BY_MOVE_CORRESPONDING"

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

"DECODE_BY_MOVE_CORRESPONDING" "(FORM)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "app41ccp"

Network address...... "10.24.40.239"

Operating system..... "SunOS"

Release.............. "5.9"

Hardware type........ "sun4us"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 79

Shortdump setting.... "full"

Database server... "ira72016"

Database type..... "ORACLE"

Database name..... "CCP"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Mar 19 2007 20:59:32"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 102

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.... 6264368

EM...... 0

Heap.... 33345696

Page.... 24576

MM Used. 37522816

MM Free. 1973120

User and Transaction

Client.............. 880

User................ "BWP_RFC"

Language key........ "E"

Transaction......... " "

Transactions ID..... " "

Program............. "GP46IA8SII8PEAO4PK4UG075ZAE"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

Termination occurred in the ABAP program "GP46IA8SII8PEAO4PK4UG075ZAE" - in

"DECODE_BY_MOVE_CORRESPONDING".

The main program was "SBIE0001 ".

In the source code you have the termination point in line 0

of the (Include) program " ".

The program "GP46IA8SII8PEAO4PK4UG075ZAE" was started as a background job.

Job Name....... "BIREQU_494DY81L1FND4FF8XRI9PVXWH"

Job Initiator.. "BWP_RFC"

Job Number..... 10292100

The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"

occurred in

procedure "DECODE_BY_MOVE_CORRESPONDING" "(FORM)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "GP46IA8SII8PEAO4PK4UG075ZAE "; its source code

begins in line

0 of the (Include program "???".

Contents of system fields

Name

Val.

SY-SUBRC

0

SY-INDEX

1

SY-TABIX

1

SY-DBCNT

1

SY-FDPOS

0

SY-LSIND

0

SY-PAGNO

0

SY-LINNO

1

SY-COLNO

1

SY-PFKEY

SY-UCOMM

SY-TITLE

Data extraction using SUBMIT_JOB as batch process

SY-MSGTY

SY-MSGID

-

---

[Former Member · Accepted solution]

Hello Kiran,

in the mapping of fields, infoobjects....you have mapped one or more field to different data type.

for example......you mapped field A ->> Infoobject ZZA

but the content of A cant fit in ZZA since its of different data type.

( this can also happen if you wrote a code to fill a field with another field....)

simply check the mappings if they are correct.

hope this helps...revisit the mappings.

regards,

Lax