topic Re: dump error in Application Development and Automation Discussions

dump error

Former Member — Fri, 17 Oct 2008 05:27:46 GMT

hi frinds

i got a dump error.the list os the detailed description f the error.kindly guide for me

What happened?

The current application program detected a situation whic

should not occur. Therefore, a termination with a short d

triggered on purpose by the key word MESSAGE (type X).

Error analysis

Short text of error message:

200016 already exists

Long text of error message:

Diagnosis

You have specified a record that already exists in the database.

System Response

Procedure

Choose a new key value.

Technical information about the message:

Message class....... "E9"

Number.............. 012

Variable 1.......... 200016

Variable 2.......... " "

Variable 3.......... " "Information on where terminated

Termination occurred in the ABAP program "SAPLERCU" - in "ISU_DB_ERCH_UPDATE".

The main program was "REAABR00SIBI ".

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

of the (Include) program "LERCUU07".

Source Code Extract

Line SourceCde

21 * Falls BelNr leer ==> Abbruch!

22 * Es sind bei Kunden Abrechnungsbeleg mit leerer BELNR

23 * aufgetreten.

24 IF X_ERCH-BELNR IS INITIAL.

25 IF 1 = 2.

26 MESSAGE A674(AJ) WITH X_ERCH-VERTRAG.

27 ENDIF.

28 MAC_MSG_PUTX CO_MSG_PROGRAMMING_ERROR '674' 'AJ'

29 X_ERCH-VERTRAG SPACE SPACE SPACE SPACE .

30 ENDIF.

31 * Eröffnungs-/Änderungsdaten schreiben

32 CALL FUNCTION 'ISU_OPENING_DATA_UPDATE'

33 EXPORTING

34 X_ERNAM = X_ERCH-ERNAM

35 X_ERDAT = X_ERCH-ERDAT

36 X_UPD_MODE = X_UPD_MODE

37 IMPORTING

38 Y_ERDAT = X_ERCH-ERDAT

39 Y_ERNAM = X_ERCH-ERNAM

40 Y_AEDAT = X_ERCH-AEDAT

41 Y_AENAM = X_ERCH-AENAM

42 EXCEPTIONS

43 NOT_CHANGED = 1.

44 IF X_UPD_MODE = CO_UPD_INSERT.

45 INSERT ERCH FROM X_ERCH.

46 IF SY-SUBRC <> 0.

47 * Eintrag schon vorhanden

48 IF 1 = 2.

49 MESSAGE A012(E9) WITH X_ERCH-BELNR."Hier Schlüsselfelder angeben

50 ENDIF.

>>> MAC_MSG_PUTX CO_MSG_UPDATE_ERROR '012' 'E9'

52 X_ERCH-BELNR SPACE SPACE SPACE SPACE .

53 ENDIF.

54 ELSE.

55 IF X_UPD_MODE = CO_UPD_DELETE.

56 X_ERCH-MANDT = SY-MANDT.

57 DELETE ERCH FROM X_ERCH.

58 ELSEIF X_UPD_MODE = CO_UPD_UPDATE.

59 UPDATE ERCH FROM X_ERCH.

60 ELSEIF X_UPD_MODE = CO_UPD_MODIFY.

61 MODIFY ERCH FROM X_ERCH.

62 ENDIF.

63 IF SY-SUBRC <> 0.

64 * Eintrag nicht vorhanden

65 IF 1 = 2.

66 MESSAGE A011(E9) WITH X_ERCH-BELNR."Hier Schlüsselfelder angeben

67 ENDIF.

68 MAC_MSG_PUTX CO_MSG_UPDATE_ERROR '011' 'E9'

69 X_ERCH-BELNR SPACE SPACE SPACE SPACE .

70 ENDIF.

raj

Re: dump error

Former Member — Fri, 17 Oct 2008 06:01:58 GMT

I think while you are inserting the data , this problem is coming

So check the Primary Key field data if same data is repeating

then u will get this error

Re: dump error

Former Member — Fri, 17 Oct 2008 06:30:39 GMT

what are you doing. are you calling any standard function module..? is error from a standard program when you are running.

Re: dump error

Former Member — Fri, 17 Oct 2008 06:38:15 GMT

Hi,

I think the error is in the following line:-

45 INSERT ERCH FROM X_ERCH.

i think you are trying to insert a duplicate entry.

-Goodluck,

Bhumika

Re: dump error

Former Member — Fri, 31 Aug 2012 19:56:42 GMT

Hi,Guy.

I got a dump error, when we´re processing the transaction EA29 (ISU-CCS) :

what happened ?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

error analysis

Short text of error message:

252001296243 not exist

Technical information about the message:

Message classe...... "E9"

Number.............. 011

Variable 1.......... 252001296243

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

please use the following search criteria:

"SAPLEITERDK" "MESSAGE_TYPE_X"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Termination occurred in the ABAP program "SAPLEITERDK" - in

"ISU_DB_EITERDK_UPDATE".

The main program was "REAPRIN0 ".

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

of the (Include) program "LEITERDKU02".

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

Job Name....... "BIPR20120827PRODT2_045"

Job Initiator.. "JOBUSER"

Job Number..... 20301501

| 41| IF X_UPD_MODE = CO_UPD_DELETE. |

| 42| DELETE EITERDK FROM X_EITERDK. |

| 43| ELSEIF X_UPD_MODE = CO_UPD_UPDATE. |

| 44| UPDATE EITERDK FROM X_EITERDK. |

| 45| ELSEIF X_UPD_MODE = CO_UPD_MODIFY. |

| 46| MODIFY EITERDK FROM X_EITERDK. |

| 47| ENDIF. |

| 48| IF SY-SUBRC <> 0. |

| 49|* Eintrag nicht vorhanden |

|>>>>>| mac_msg_putx co_msg_update_error '011' 'E9' |

| 51| x_eiterdk-opbel space space space space . |

| 52| if 1 = 2. |

| 53| MESSAGE a011(E9) WITH EITERDK-OPBEL. "Schlüsselfleder angeben |

| 54| ENDIF. |

| 55| ENDIF. |

| 56| ENDIF. |

| 57| |

| 58|ENDFUNCTION. |

Please, could you help us ?

Thank you,very much.

Best regards.

Montesi