Runtime Error - POSTING_ILLEGAL_STATEMENT

[Former Member]

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:04 PM

[matt]

>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"

Has the program been modified? If not do the above.

[Former Member]

Solved.

thanks

sankar.

[Former Member]

Sorry Sankar,

could you post me the solution? I have the same problem!!

Thanks in advance!

Bye!

Ferdinando

[Former Member]

Hi,

Can you please post me the solution, << Oh, I don't know, maybe sometime next year >>....I have a similar problem in production system and is critical.

Deepti

Edited by: Rob Burbank on Feb 17, 2009 10:43 AM

[Former Member]

I had the same problem involving smartforms. The debugger had missed that I had changed the size of a template, making it bigger than the window it was contained within. This seems to usually be caught, but i guess it can be missed.

[Former Member]

I am also facing same problem in T.Code CLM1.

plz help.

Thanks

Peram Srinivas

Edited by: Peram Sriniwas on Apr 28, 2009 7:20 AM

Edited by: Peram Sriniwas on Apr 28, 2009 7:20 AM

[Former Member]

Hi sankar, i have the same problem with you. Could you please share with me, how did you fix the problem issue at the line code 442. İ need urgent help!

440       if i_screen_start_line eq 0.

441         call screen 500.

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

443       else.

Thanks in advance.

Cenk

[Former Member]

Hi Sankar,

could you post me the solution? I have the same problem!!

Thanks in advance!

Bye!

Erika.

[Former Member]

Hi All,

The error is related to the ABAP coding of the particular program. The program related to sales and billing.

The error you get must be the user own output screen.

Please refer to the SAP Note for further analysis and solution.

http://service.sap.com/sap/support/notes/1472777

[sharonvinod]

Similar issue was encountered in a case of PO creeation from BAPI, which went to V1 update error. User was not configured with default printer parameter. Check user parameters for the output settings.