topic Re: Runtime error in transaction ME31L in Application Development and Automation Discussions

Runtime error in transaction ME31L

Former Member — Sun, 07 Feb 2010 09:19:25 GMT

Hi Experts,

I am facing the problem with tranasaction code ME31L ,its showing the runtime error..

here i am writting the whole error discription which occurs at runtime.

Short text

Dynpro does not exist

What 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.

Error analysis

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

This dynpro does not exist.

Trigger Location of Runtime Error

Program SAPLXM06

Include MM06EO0C_CUSTSCR1_HEAD_SET_DAT

Row 10

Module type (FUNCTION)

Module Name EXIT_SAPLEINM_013

Source Code Extract

Line SourceCde

1 ----

2 * MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT *

3 ----

4 * ........ *

5 ----

6 MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT.

8 PERFORM CUSTSCR1_HEAD_SET_DATA_PBO using fc_call.

>>>>> ENDMODULE.

Re: Runtime error in transaction ME31L

vinod_vemuru2 — Sun, 07 Feb 2010 09:29:12 GMT

Hi,

Yesterday someone has posted the same question. Please find my reply in below thread.

Thanks,

Vinod.

Re: Runtime error in transaction ME31L

Former Member — Sun, 07 Feb 2010 09:53:54 GMT

hi vinod,

Actually for the include 'ZXM06U35' its giving the error as :-

Program names ZX... are reserved for includes of exit function groups

Re: Runtime error in transaction ME31L

Clemenss — Sun, 07 Feb 2010 11:13:11 GMT

Hi Yash,

your system has been enhanced with an exit function. Probably this exoit does not work correct at least not in the context where you get the dump.

You can find the error in one of the function kodules of function group XM06.

Regards,

Clemens

Re: Runtime error in transaction ME31L

vinod_vemuru2 — Sun, 07 Feb 2010 11:51:04 GMT

Hi,

This means that the exit is not implemented yet. Infact what you are seeing is a warning message(ZX...).

Is your system recently upgraded? Wrong OSS note implementation is also a possibility.

Just debug and see at what point you are getting the error. Also did you check the program whether it has the required screen or not? If not available then you can raise an OSS note to SAP if you are not able to find any.

Thanks,

Vinod.