Short dump in Z transaction code

[Former Member]

Hi,

We have a Z transaction code 'ZPROFIT' for a report. After executing the report from output screen of report if i type 'se38' in command bar and if I press enter key it is going to short dump. But if I type '/nse38' it is working fine.The short dump description is as follows .

ShrtText

An exception that could not be caught occurred.

What happened?

The exception 'CX_SALV_OBJECT_NOT_FOUND' was raised but was not caught at any

stage in the

call hierarchy.

Since exceptions represent error situations, and since the system could

not react adequately to this error, the current program,

'CL_SALV_FUNCTIONS=============CP', had to

be terminated.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assinged to the class 'CX_SALV_OBJECT_NOT_FOUND', was

not caught,

which led to a runtime error.

The reason for this exception is:

No text available for this exception

Trigger Location of Exception

Program CL_SALV_FUNCTIONS=============CP

Include CL_SALV_FUNCTIONS=============CM00J

Row 28

Module type (METHOD)

Module Name IS_SALV_FUNCTION

Source Code Extract

Line SourceCde

1 method is_salv_function.

2 data: l_name type string.

3 data: l_msgtext type string.

4 data: ls_message type scx_t100key.

5

6 *get item

7 try.

8 call method get_item

9 exporting

10 function = name

11 importing

12 salv_function = value.

13 catch cx_salv_object_not_found.

14 try.

15 call method get_group

16 exporting

17 group = name

18 importing

19 salv_function = value.

20 catch cx_salv_object_not_found.

21 l_name = name.

22 message w026(salv_exception)

23 with 'CL_SALV_FUNCTIONS' 'IS_SALV_FUNCTION' 'Function: ' l_name

24 into l_msgtext. "#EC NOTEXT

25

26 ls_message-msgid = sy-msgid.

27 ls_message-msgno = sy-msgno.

>>>>> raise exception type cx_salv_object_not_found

29 exporting

30 textid = ls_message

31 object = 'Function'

32 key = l_name

33 class = 'CL_SALV_FUNCTIONS' "#EC NOTEXT

34 method = 'IS_SALV_FUNCTION'. "#EC NOTEXT

35 endtry.

36 endtry.

37

Please let me know how we can solve this?

Is there anything wrong in report source code?

Thanks in advance.

Regards,

Brahma Reddy

[Former Member]

If you are at any screen other than the main SAP menu screen and you want you go into another transaction (without backing out of what you are already in), you should always type <b>/n</b> in the command field before the new transaction code. Otherwise it will not work. You don't need to change anything with your report.

- April King

[Former Member]

Hi,

There is no problem in your code.You should always use either /n or /o to go to any other trsndsction.(only exception is when you are in main menu screen.

[Former Member]

hi Brahma,

when u said writing "SE38", r u in SAP Easy Access?

...

u can try reinstall ur SAP GUI...

Regards

Allan Cristian

[Former Member]

Hi brahma,

the sap will work in such a way that when you are already entered into any transaction say

mm01. if you type any transaction code 'se38 ' in that mm01 window . it wont go that specified transaction, but instead you can give either '/ose38' to create new session or '/nse38' to come out of current transaction ...

reward if usefull...

[Former Member]

Yes...I agree to all the comments. But my thing is it is not supposed to give sgort dump. i have another reports wher in if I type 'se38' , it will stay in that screen itself without going to dump.

Please advise.

Brahma Reddy

[Former Member]

hi brahma,

try to reinstall ur Front End...

it's not a error from ur Program, I think it's dumb because SAP GUI it's not all right working,

try to remove and install SAP GUI, maybe it's can solve ur problem...

Regards

Allan Cristian

[Former Member]

I think you're getting the dump because your report basically thinks that the user is trying to modify it in some way. You've got an ALV report, which is designed to be interactive. So when the user types something into the command field it is trying to figure out what changes that should cause in the report. To see where you should handle this, go to your report output. Then type /h in the command field to switch debugging on. Then you can type in SE38 to see what part of your report is trying to handle the command code. Whatever you enter into the command field will be stored in SY-UCOMM.

- April