ABAP Dump Error while creating Invoices

[Former Member]

Hi All,

Our End User is facing problem in creating Invoices.

The system is throwing Runtime Error while creating Invoices.

The following description has been sent by our SD consultant....

"While we are creating a Billing Request against to a Milestone

Order, we are getting the ABAP Runtime Error. So we are not able to Create any Billing request against to Milestone Orders."

How to resolve this issue?

Regards

Pavan

[Former Member]

hai,

go to t-st22 and see the reason . also post what error system shows in st22

regards

[Former Member]

Go to the dump analysis.

and you can findout the error.

other wise forward the same here we will see.

What you have posted by which i cann't able to give the solution.

Regards,

madan.

[Former Member]

Dump may occur for two reason:

1. For some customizing

2. For abap code (User exits/ BADI).

Ask the test data from the user for which he is getting dump and then debugg the code whether it is for some abap code (User exits/ BADI), If so then find out the reason and solve it.

[Former Member]

Excerpts from ST22....

Runtime Errors PERFORM_NOT_FOUND

Exception CX_SY_DYN_CALL_ILLEGAL_FORM

Date and Time 06.05.2008 10:35:02

Short text

Call (PERFORM) to a non-existent routine.

What happened?

There exist various options:

Error in the ABAP Application Program

The current ABAP program "SAPFV45C" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

or

Error in the SAP kernel.

The current ABAP "SAPFV45C" program had to be terminated because the

ABAP processor detected an internal system error.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was

not caught in

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

The program "SAPFV45C" is meant to execute an external PERFORM,

namely the routine "DATEN_KOPIEREN_905" of the program "SAPFV45C", but

this routine does not exist.

This may be due to any of the following reasons:

1. One of the programs "SAPFV45C" or "SAPFV45C" is currently being developed.

The name "DATEN_KOPIEREN_905" of the called routine may be incorrect, or

the routine "DATEN_KOPIEREN_905" is not yet implemented in the program

"SAPFV45C".

-

2. If the program SAPMSSY1 is involved in the runtime error, one of

the function modules called via RFC is not flagged as remote-capable.

(see Transaction SE37 Goto -> Administration -> RFC flag)

3. There is an inconsistency in the system. The versions of the

programs "SAPFV45C" and "SAPFV45C" do not match.

Source Code Extract

Line SourceCde

31 SVBAP-TABIX = 0.

32 ENHANCEMENT-SECTION VBAP_KOPIEREN_VORBEREITEN_02 SPOTS ES_SAPFV45C.

33 * Position und kaufmänn. Daten vorbereiten

34 PERFORM VBAP_BEARBEITEN_VORBEREITEN(SAPFV45P).

35 * Keine Textfindung im Kopieren_Pruefen

36 IF US_CHECK_ONLY NE SPACE.

37 NO_TEXT_COPY-CHECK = CHARX.

38 ENDIF.

39

40 PERFORM VBAP_FUSSZEILE_FUELLEN_VORLAGE.

41 END-ENHANCEMENT-SECTION.

42

43 IF US_CHECK_ONLY NE SPACE.

44 VBAP_MATNR_LOE = VBAP-MATNR. " Keine Hinweise auf

45 VBAP_WERKS_LOE = VBAP-WERKS. " Löschvormerkung

46 ENDIF.

47

48 * Referenznummer übernehmen, vor FUELLEN wegen Textübernahme

49 * Die VG-Felder wurden vor dem Umschlüsseln der Positionsnummern

50 * gesetzt

51 VBAP-VGTYP = US_VGTYP.

52 VBAP-VGBEL = US_VGBEL.

53 VBAP-VGPOS = US_VGPOS.

54 VBAP-VGREF = US_VGREF.

55 PERFORM VBAP_FUELLEN(SAPFV45P).

56 * Positionsdaten kopieren

57 PERFORM VBAP_COPY_DATA_STANDARD.

58 PERFORM (MODUL) IN PROGRAM SAPFV45C.

59

60 * Call SD Sales BAdI

>>>>> CALL FUNCTION 'GET_HANDLE_SD_SALES_ITEM'

62 IMPORTING

63 HANDLE = L_SD_SALES_ITEM_EXIT

64 ACTIVE = ACTIVE.

65 IF ACTIVE = CHARX.

[Former Member]

Hi,

Check BADI "BADI_SD_SALES_ITEM". Check for any active implementations of this BADI and check for the errors.

Regards

Kannaiah

[Former Member]

Hi,

The missing routine needs to be implemented with the transaction VOFM.

It seems that in the calculation schema the routine 905 has been set but the form routine is missing.

This Routine can be maintained with transaction VOFM -> Probably as condition value -> check with your SD consultant

Kind Regards