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: 

Transaction me31k crashing with short dump

Former Member

‎11-20-2007 2:29 AM

0 Kudos

Hi Experts

Can anyone tell me why my transaction crashes when i run me31k to create contract type the vendor, agree type, agree date,agreement, pur org, purchasing group, item category , plant , storage location then it is crashing in test server but in production it is ok

I am getting the following error

Runtime Error

Occurred on

Screen does not exist

What happened?

Error in ABAP application program.

The current ABAP program "SAPMM06E" 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 program had to be terminated.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

Program "SAPLXM06" tried to use screen 0201.

The screen does not exist.

Is there any way to solve this error

2 REPLIES 2

Former Member

‎11-20-2007 6:29 AM

0 Kudos

Hi Monto,

Please can us send the code that is being shown in your debugger as of where is the dump is getting generated. I beleive that the screen number which is being called is not present or is not active. Please check the Screen Status if it is active or not.

Regards,

Sai

Former Member

‎11-20-2007 7:10 AM

0 Kudos

Hi Monto

I think you probably have not created/activated the screen 0201 for SAPLXM06.

follow the docmentation of the enhancement MM06E005:


Dynpro areas

  If you use the enhancement, you must create and generate the following
  dynpros (even if the dynpros are not going to be used):


  o   SAPLXM06    0101    Subscreen header purchase order

  o   SAPLXM06    0201    Subscreen header outline agreement

  o   SAPLXM06    0301    Subscreen header RFQ

  o   SAPLXM06    0111    Subscreen item purchase order

  o   SAPLXM06    0211    Subscreen item outline agreement

  o   SAPLXM06    0311    Subscreen item RFQ

  You must identify all dynpros as subscreens. It is not necessary that
  they contain fields, but it is essential that they exist in order that
  no program abend occurs.

I hope this solves the issue..

Rewards the point if it answers you.

Best Regards

Amit