Short dump while executing Ztransaction

[Former Member]

Hi,

I am doing module pool programming by desinging the screens, handling events and running it thru a Z-trnasaction.

My first query is how do I debug a module pool prg.. so as to understand that the error/short dump is because of my code or due to some other reason ...

My second query is that I am getting a short dump with "DIAG_RFC_EXCEPTION" ... I do have access to SM59 ... do I need to check for some other RFC propeties ??... Is this error related to Basis guys??? & the line where it is dumping is as follows :-

• Einzelbildverarbeitung Transaktionsvarianten/Batch-Input/CATT

call function 'SYSTEM_SCREEN_INPUT'

exporting

modul = p_repid.

endform. " %_CTL_INPUT

Thank You,

SB

[Former Member]

In your PBO, put a break-point on the first executable code and then run your transaction. It will stop at the break-point and then you can start debugging. This sounds like more of an error coming out of trying to start a screen(dialog mode) from an RFC scenario. What BAPI are you calling in there? Also, go to ST22 and see what the error says. Look at the call stack and you will see when the error occured. Do you have a RFC call in your code?

[Former Member]

No srini .. I am not using any RFC call or BAPI in my program ... I am trying to write a select statement ...

SELECT *

FROM ZTEST

INTO TABLE T_ZTEST.

On clicking the display button ... I want to display the contents of this table in screen 200 where I have setup the table control area ...

Thsnk you,

SB

[Former Member]

Hi,

Seems like there is a problem writing the selected data onto the screen.

Checkout the screen layout.

Regards,

Raj

[Former Member]

Hi,

Please check the type of transaction you created. If you have created transaction of type 'Program and screen (dialog transaction)', then delete it and create a transaction of type 'Program and selection screen (report transaction)'. You can create transactions using SE93.

I hope thia solves your problem.

Riyaz

[Former Member]

Hello SB what is the SAPGUI version level? What screen have u developed?

[vinod_gunaware2]

Hi

Suppose u want debug the screen which is popup.

Then do following step.

crete text file on desktop with following content.

<b>[FUNCTION]

COMMAND = /H

TITLE = DEBUGGER

TYPE = SYSTEMCOMMAND</b>

Save the file.

Then when pop is coming. Just drag and drop above file on the window in which pop is coming.(Minimize window then drag and drop on the window in which pop came)

Debuggin will start.

Hope this will be useful.

Regards

vinod

[Former Member]

Hi SB,

One way to debug module pool(Pop-up) is like this :

Many times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that.

*Instead, we have to start debugging all the way from main screen.

*Enclosed is a 3 line script would allow us to make our edits in a Pop-up.

*Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on.

FILE CONTENTSMany times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that. Instead, we have to start debugging all the way from main screen. Enclosed is a 3 line script would allow us to make our edits in a Pop-up. Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on!

<b>Code: (File Contents)</b>

[FUNCTION]

Command=/H

Title=Debugger

Type=SystemCommand

Hope this will help you to find out the error while debugging the pop up .

Cheers

Sunny

[Former Member]

thanx