Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

POSTING_ILLEGAL_STATEMENT Dump in VL10B tcode

Former Member

‎03-01-2011 1:11 PM

0 Kudos

Dear Experts,

When we tried to execute VL10B tocde for PO, the system is terminating from session by Dump showing as POSTING_ILLEGAL_STATEMENT.. Please find the full details below in Dump Foprmat..

Statement "COMMIT" is not allowed in this form.

What happened?

Error in ABAP application program.

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

statements could not be executed.

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

Error analysis

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

following ABAP/4 statements are not allowed:

- CALL SCREEN

- CALL DIALOG

- CALL TRANSACTION

- SUBMIT

But SAPLLPRF program is SAP Standard program and no enhancements done in this tcode from last 3 years..

PLease suggest

Thanks in Advance,

Siva.

4 REPLIES 4

former_member195402
Active Contributor

‎03-01-2011 1:22 PM

0 Kudos

Hi,

please have a look at the code where the COMMIT is. Maybe its a user exit or something similar (Enhancement, ...).

There mustn't be a commit while booking is in process.

Regards,

Klaus

Former Member

‎03-01-2011 1:33 PM

0 Kudos

But the COMMIT WORK statemt wrote by SAP in SAP Standard function module.. for your info there is no enhancements in this tcode..

And tcode worked properly upto last 24 hrs. From last 24 hrs only we are facing this issue... and no new changes occured during this time in this tcode..

Please guide mee..

Clemenss
Active Contributor
In response to Former Member

‎03-01-2011 1:43 PM

0 Kudos

Hi Siva,

in the dump, there is a CODE section. Let me place a bet that this is inside a customer object. Identify who created the COMMIT WORK in the code. If it was someone at SAP he will get into serious trouble. If someone at your company did, your company may decide how to handle it.

Did you already check last 24 hours transport imports?

Golden Rule: Commit WORK is strictly forbidden in all customer extensions/modifications/enhancements/exits/BaDIs.

Regards,

Clemens

Former Member

‎03-01-2011 1:42 PM

0 Kudos

Hi,

Please check once again that in VL10B any user-exit/enhancement/implicit or explicit enhancements has done and whether any commit work has been defined.

You can also go through the note : 1548662.

Thanks

Arbind