cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Error - In PO creation

Former Member
0 Kudos

Hi friends,

Pls advise how to resolve this runtime error issue mentioned below...which Im getting in PO creation and at the time of releasing the same but getting the error as background express document.

Note(FYI):No enhancement has been developed and its a normal process only.

************Runtime error

Report outputRuntime Errors POSTING_ILLEGAL_STATEMENT

Statement "CALL SCREEN" is not allowed in this form.

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

Error analysis

There is probably an error in the program

"SAPLKKBL".

This program is triggered in the update task. There, the

following ABAP/4 statements are not allowed:

CALL SCREEN

CALL DIALOG

CALL TRANSACTION

SUBMIT

How to correct the error

Probably the only way to eliminate the error is to correct the program

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:

"POSTING_ILLEGAL_STATEMENT" " "

"SAPLKKBL" or "LKKBLU01"

"K_KKB_LIST_DISPLAY"

Information on where terminated

Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".

The main program was "RSM13000 ".

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

of the (Include) program "LKKBLU01".

The program "SAPLKKBL" was started in the update system.

438 if gt_stack-is_layout-detail_only is initial.

439 if gt_stack-is_layout-suppress_dynpro is initial.

440 if i_screen_start_line eq 0.

call screen 500.

442 sy-pagno = g_sypagno. "wegen Dynpro 200 Spoolinfo bei F8+Druck

443 else.

****************************************

Pls reply.

thanks & regards

sankar.

Edited by: sankar babu on May 23, 2008 12:05 PM

Edited by: sankar babu on May 23, 2008 12:05 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Problem in output type activation for Tcode:ME29N.

Got solved by BASIS Cons.

thanks

sankar.

Former Member
0 Kudos

Hi

Check with Abapers, it transaction is calling some screen 500, which is not compatible with the Form output.

Regards

Rahul