topic Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND in Application Development and Automation Discussions

A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:08:10 GMT

Hi. i'm a new abap programmer and i'm working with screens (dialog programming). i have a DYNPRO_NOT_FOUND dump but i didn't find what does it means.

please help me.

thanks.

Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:11:30 GMT

Hi,

In the dump check the line where it is pointing....analyse what is wrong in that line OR post it here

thanks

chandra

Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:11:48 GMT

Please paste here what the short dump says from ST22.

Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:17:00 GMT

Runtime Errors DYNPRO_NOT_FOUND

Date and Time 18.07.2008 00:13:45

Short text

Dynpro does not exist

What happened?

Error in the ABAP Application Program

The current ABAP program "ZS0007_NURUS_EGITIM_SCR_PERS" had to be terminated

because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The system attempted to use dynpro 0008 in program

"ZS0007_NURUS_EGITIM_SCR_01".

This dynpro does not exist.

Trigger Location of Runtime Error

Program ZS0007_NURUS_EGITIM_SCR_PERS

Include ZS0007_NURUS_EGITIM_SCR_01_I01

Row 37

Module type (MODULE PBO)

Module Name PERSONELLER_ACTIVE_TAB_SET

21 *&SPWIZARD: OUTPUT MODULE FOR TS 'PERSONELLER'. DO NOT CHANGE THIS LINE!

22 *&SPWIZARD: SETS ACTIVE TAB

23 MODULE PERSONELLER_ACTIVE_TAB_SET OUTPUT.

24 PERSONELLER-ACTIVETAB = G_PERSONELLER-PRESSED_TAB.

25 CASE G_PERSONELLER-PRESSED_TAB.

26 WHEN C_PERSONELLER-TAB1.

27 G_PERSONELLER-SUBSCREEN = '0008'.

28 WHEN C_PERSONELLER-TAB2.

29 G_PERSONELLER-SUBSCREEN = '0009'.

30 WHEN C_PERSONELLER-TAB3.

31 G_PERSONELLER-SUBSCREEN = '0010'.

32 WHEN C_PERSONELLER-TAB4.

33 G_PERSONELLER-SUBSCREEN = '0011'.

34 WHEN OTHERS.

35 *&SPWIZARD: DO NOTHING

36 ENDCASE.

>>>>> ENDMODULE.

39 *&SPWIZARD: INPUT MODULE FOR TS 'PERSONELLER'. DO NOT CHANGE THIS LINE!

40 *&SPWIZARD: GETS ACTIVE TAB

41 MODULE PERSONELLER_ACTIVE_TAB_GET INPUT.

42 OK_CODE = SY-UCOMM.

43 CASE OK_CODE.

44 WHEN C_PERSONELLER-TAB1.

45 G_PERSONELLER-PRESSED_TAB = C_PERSONELLER-TAB1.

46 WHEN C_PERSONELLER-TAB2.

47 G_PERSONELLER-PRESSED_TAB = C_PERSONELLER-TAB2.

48 WHEN C_PERSONELLER-TAB3.

49 G_PERSONELLER-PRESSED_TAB = C_PERSONELLER-TAB3.

50 WHEN C_PERSONELLER-TAB4.

51 G_PERSONELLER-PRESSED_TAB = C_PERSONELLER-TAB4.

Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:23:12 GMT

dump is on 37th line that ENDMODULE.

Re: A Problem in Dialog Programming DYNPRO_NOT_FOUND

Former Member — Thu, 17 Jul 2008 21:36:52 GMT

ooo i found what was the reason of problem. i had changed my report name and the function of tabsctrip control was using the old name of my report so a dump is born. i changed old names in the functions and my problem is end.

thanks to everybody.