Community
Application Development and Automation 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: 
Read only

Dump error: Dynpro does not exist while in transaction me31K

Go to solution
Former Member

‎2011 Oct 19 4:41 PM

0 Likes
5,659

HI,

I am getting dump while creating the Contract in ME31K.

hort text

Dynpro does not exist

hat happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

rror analysis

The system attempted to use dynpro 0201 in program "SAPLXM06".

This dynpro does not exist.

rigger Location of Runtime Error

Program SAPLXM06

Include MM06EO0C_CUSTSCR1_HEAD_SET_DAT

Row 10

Module type (FUNCTION)

Module Name EXIT_SAPLEINM_013

1 ACCEPTED SOLUTION
Read only

Go to solution
nomssi
Active Contributor

‎2011 Oct 19 5:52 PM

0 Likes
3,917

Hello,

use transaction SMOD to check SAP enhancement MM06E005 in your system. Screen SAPLXM06 0201 is the contract header subscreen. The system report it missing because the enhancement MM06E005 (Customer fields in purchasing document) was activated in your system, but not implemented. So either disable/delete the enhancement or create a subscreen.

regards,

J.N.N.

HI,

I am getting dump while creating the Contract in ME31K.

hort text

Dynpro does not exist

hat happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

rror analysis

The system attempted to use dynpro 0201 in program "SAPLXM06".

This dynpro does not exist.

rigger Location of Runtime Error

Program SAPLXM06

Include MM06EO0C_CUSTSCR1_HEAD_SET_DAT

Row 10

Module type (FUNCTION)

Module Name EXIT_SAPLEINM_013

Reply
5 REPLIES 5
Read only

Go to solution
Former Member

‎2011 Oct 19 4:52 PM

0 Likes
3,917

Check your exit. This is a subscreen, not a normal screen, so you need to CALL SUBSCREEN ...

Rob

Read only

Go to solution
Former Member
In response to Former Member

‎2011 Oct 19 5:10 PM

0 Likes
3,917

I checked in my Sandbox system.It is having the Normal screen and i am able to create the contract.

I am checking in development system.it is not working.I have checked the note 1517584.

Thanks

Srini

Read only

Go to solution
nomssi
Active Contributor

‎2011 Oct 19 5:52 PM

0 Likes
3,918

Hello,

use transaction SMOD to check SAP enhancement MM06E005 in your system. Screen SAPLXM06 0201 is the contract header subscreen. The system report it missing because the enhancement MM06E005 (Customer fields in purchasing document) was activated in your system, but not implemented. So either disable/delete the enhancement or create a subscreen.

regards,

J.N.N.

Read only

Go to solution
mshaheryarusmani14
Explorer
In response to nomssi

‎2022 Nov 10 5:35 AM

0 Likes
3,917

I have deleted MM06E005 on smod but it doesnt worked. How can i get back my enhancement?

.

Read only

Go to solution
former_member396030
Explorer

‎2020 Dec 17 7:47 AM

0 Likes
3,917

Implementation of 2693530 has resolved the problem. Buggy standard screens of SAPMM06E now contain CUSTSCR1 subscreen areas.

SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101
SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111
SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201
SAPMM06E 0211 CUSTSCR1 SAPLXM06 0211
SAPMM06E 0301 CUSTSCR1 SAPLXM06 0301
SAPMM06E 0311 CUSTSCR1 SAPLXM06 0311

5. Double click on the suitable screen line and create it if it was not created yet.
6. Correct the screen type by changing from 'Normal' to 'Subscreen' on attributes tab
7. Click save button and re-test the system behavior