cancel
Showing results for 
Search instead for 
Did you mean: 

Vf01 is dumping at the time of invoice creattion.

Former Member
0 Kudos

After doing PGI if if iam going to do invoice I am getting the dump.

Runtime Errors PERFORM_NOT_FOUND

Exceptn CX_SY_DYN_CALL_ILLEGAL_FORM

Date and Time 15.05.2007 12:22:44

ShrtText

Call (PERFORM) to a non-existent routine.

What happened?

The current program attempted to call an externally defined routine

that does not exist.

Error in ABAP application program.

The current ABAP program "SAPLV60A" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

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

processor discovered an invalid system state.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FORM',

was neither

caught nor passed along using a RAISING clause, in the procedure

"VBRK_VBRP_DATENTRANSPORT" "(FORM)"

.

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:

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

namely the routine "DATEN_KOPIEREN_350" of the program "SAPFV60C", but

this routine does not exist.

This may be due to any of the following reasons:

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

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

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

"SAPFV60C".

-

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 "SAPLV60A" and "SAPFV60C" do not match.

sing RAISING Clause in Interface

Program SAPLV60A

Include LV60AA95

Row 16

Module type (FORM)

Module Name VBRK_VBRP_DATENTRANSPORT

gger Location of Exception

Program SAPLV60A

Include LV60AA95

Row 407

Module type (FORM)

Module Name VBRK_VBRP_DATENTRANSPORT

rce Code Extract

e SourceCde

377 currency_new = ch_waerk

378 EXCEPTIONS

379 warning_occurred = 1

380 error_occurred = 2

381 OTHERS = 3.

382

383 IF sy-subrc = 2 AND NOT ch_waerk IS INITIAL.

384 * no invoice is created

385 * because gn_invoice_create is used with expiring currency (conditions)

386 IF vbrp-vgtyp = '2' AND

387 ( NOT xkomfkko[] IS INITIAL ).

388 PERFORM vbfs_hinzufuegen USING

389 space '215' vbrk-waerk space space.

390 ts_subrc = 4.

391 ELSE.

392 * new currency replaces expired currency without warning

393 CLEAR vbrp-kursk.

394 vbrk-waerk = ch_waerk.

395 CLEAR vbrk-kurrf.

396 ENDIF.

397 ENDIF.

398

399 * Datentransportmodul ausführen

400 IF tvcpf-grurp NE 0.

401 cpymodul-nr = tvcpf-grurp.

402 PERFORM (cpymodul) IN PROGRAM sapfv60c.

403 ENDIF.

404

405 * Userexit number_range in order to determine invoice date

406 DATA: da_numki LIKE tvfk-numki.

>>>> da_numki = tvfk-numki.

408 PERFORM userexit_number_range_inv_date USING da_numki.

409 PERFORM tvfkd_lesen USING da_numki.

410

411 * Vorgabedaten auf jeden Fall übernehmen

412 IF kom-fkdat NE 0.

At the time of debugging iam getting as follows

Fields

Main Program SAPLV60A

Source code of LV60AA95

cpymodul-nr = tvcpf-grurp.

PERFORM (cpymodul) IN PROGRAM sapfv60c.

ENDIF.

  • Userexit number_range in order to determine invoice date

DATA: da_numki LIKE tvfk-numki.

da_numki = tvfk-numki.

PERFORM userexit_number_range_inv_date USING da_numki.

PERFORM tvfkd_lesen USING da_numki.

  • Vorgabedaten auf jeden Fall übernehmen

IF kom-fkdat NE 0.

vbrk-fkdat = kom-fkdat.

ENDIF.

IF NOT tvfkd-fkdat IS INITIAL.

vbrk-fkdat = tvfkd-fkdat.

Field names 1 - 4 Field conten

Pls do the needful.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

This dump is due to error in the routine which should be present in delivery to billing copy control either at header or item level.

The statement >>>> da_numki = tvfk-numki.

is causing the problem.

Ask your ABAPer to analyse and rectify the issue.

Reward points if useful

Regards,

Amrish Purohit

Answers (1)

Answers (1)

Former Member
0 Kudos

execute vofm in menu data transfer -> billing documents

1. Selection Number routine

2. Active