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: 

MIGO - short dump with POSTING_ILLEGAL_STATEMENT

Former Member

‎07-07-2009 6:30 AM

0 Kudos

Hi All,

Before posting this question I had gone through the posts related to similar error. I think none of them is related to MIGO.

When we are trying to do Goods issue against work order using MIGO, we are getting 'Update Termianted' message after we saved the transaction. Short dump has following info.

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

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

come across a statement that unfortunately cannot be executed.

Key words

"POSTING_ILLEGAL_STATEMENT"

"SAPLTAX1" or "LTAX1U07"

"CALCULATE_TAX_DOCUMENT"

Actually short dump is pointing to code in the FM CALCULATE_TAX_DOCUMEN where there is Call screen statement.

I am not able to relate this to any of the outputs because, we have two output types associated with material document but none of them uses print function.

Any pointers to this would be really helpful.

Regards,

Shahu

3 REPLIES 3

Former Member

‎09-05-2009 12:23 AM

0 Kudos

Actually we could not figure out why this happened in the system. But we disconnected the link between MIGO and output processing and its working fine.

Learning - Keep transactions like MIGO away processing outputs immidiately when saving the application optio :-)...

Former Member
In response to Former Member

‎12-05-2009 1:28 PM

0 Kudos

Hello,

Could you please describe the process of disconnecting the transaction step-by-step? I'm facing the same problem with SAPLTAX1 program but with different transaction - "KO88 - Actual settlement of orders".

The customer says, that everything works fine, but he gets an e-mail with a short dump description even if the settlement is OK. I think, this could be the same situation - but instead of output to the printer, there is output type mail.

Thanks for any hint.

Petr

MSA_91
Newcomer
In response to Former Member

‎08-24-2010 10:40 AM

0 Kudos

Hello,

Could you please describe the process of disconnecting the transaction step-by-step? I'm facing the same problem.

I use a output type using a program in a processing routine .

this program launches a call transaction MB11 .

Thank you very much for you help