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
Showing results for 
Search instead for 
Did you mean: 
Read only

Memory ID in debbuger

Former Member
0 Likes
10,944

Hello,

How can i see the Memory ID variables in debugging mode ?

Thanks in advance

1 ACCEPTED SOLUTION
Read only

former_member776318
Participant
0 Likes
5,131

Hello,

Consider, for example, you set a SPA/GPA parameter using the statement SET PARAMETER 'ZSP' FIELD w_vbeln.

Then you can see the value of parameter-id ZSP in the ABAP debugger.

In the debugger, from the menu, select GOTO -> SYSTEM AREAS -> SAP MEMORY.

The SPA/GPA parameters are stored in SAP memory.

Hope that helps.

Thanks,

Saurabh

If that is the case, the parameter-id is would not be the right thing to look for.

At the handler method, you should pass the appropriate item number to the FM.

8 REPLIES 8
Read only

Former Member
0 Likes
5,130

In your debugging mode go to and switch on the classic debugger

and then go to> system areas>sap memory or abap memorys.

You will be able to see the values stored in memory ID if import/export is used then in ABAP memory

and for set/get parameter ID it will be in SAP memory.

Thanks

Read only

former_member776318
Participant
0 Likes
5,132

Hello,

Consider, for example, you set a SPA/GPA parameter using the statement SET PARAMETER 'ZSP' FIELD w_vbeln.

Then you can see the value of parameter-id ZSP in the ABAP debugger.

In the debugger, from the menu, select GOTO -> SYSTEM AREAS -> SAP MEMORY.

The SPA/GPA parameters are stored in SAP memory.

Hope that helps.

Thanks,

Saurabh

Read only

0 Likes
5,130

Thanks i got it!

I have another problem now.

I write a report program

REPORT DOUBLE_CLICK_PO.

DATA:
GV_PO_NUMBER TYPE EKKO-EBELN,
GV_PO_ITEM TYPE EKPO-EBELP.

GET PARAMETER ID 'BES' FIELD GV_PO_NUMBER.
GET PARAMETER ID 'BSP' FIELD GV_PO_ITEM.

BREAK-POINT.

CALL FUNCTION 'ME_DISPLAY_PURCHASE_DOCUMENT'
  EXPORTING
    I_EBELN = GV_PO_NUMBER
    I_EBELP = GV_PO_ITEM
    I_ENJOY = 'X'
  EXCEPTIONS
    OTHERS  = 1.

in order to get in the PO with double click at an ALV query output by assigning this code to query. As i sow in SAP memory the ID's taken are from the selection screen and not the from the ALV .

Why is this ?

Read only

0 Likes
5,130

What I could understand is that you are having an alv in which PO number/item is displayed & on double-clicking, you want to navigate to PO transaction.

For this, the following should be the steps:

When you double click on the ALV column, the event DOUBLE_CLICK get triggered.

In the handler method for the DOUBLE_CLICK event, you should set the parameter-id & the do a CALL TRANSACTION me23n AND SKIP FIRST SCREEN.

I could not understand the reason to use the function module.

Regards,

Saurabh

Read only

0 Likes
5,130

The reason is that the F.M goes you directly to the corresponding item instead of CALL TRANSACTION that goes you to the 1st item.

But my problem is that the parameter ID isn't the right one when i click to the line. How is this possible ?

Read only

0 Likes
5,130

If that is the case, the parameter-id is would not be the right thing to look for.

At the handler method, you should pass the appropriate item number to the FM.

Read only

0 Likes
5,130

If you want to get the values of the double click row then you can use below things.

If you are using Function module to display the ALV then you have to give the form name

to the import parameter user command of these function module and then implement this as

FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM

RS_SELFIELD TYPE SLIS_SELFIELD.

CASE R_UCOMM.

WHEN '&IC1' " double click event

here you can use the variable RS_SELFIELD where you will get the PO number and po item

where you have clicked and then you can call your function module

CALL FUNCTION 'ME_DISPLAY_PURCHASE_DOCUMENT'

EXPORTING

I_EBELN = clicked po number

I_EBELP = clicked po item

I_ENJOY = 'X'

EXCEPTIONS

OTHERS = 1.

or else you can use set parameter id and call trasaction and skip first screen.

endcase.

endform.

or

Else if you are using the ALV class then declare one local class with method dpoble clickas

class ...

method on_double_click for event double_click of cl_salv_events_table importing row cloumn.

endclass.

and also set event handler using

set handler event_handler->on_user_command for gr_events(object of cl_salv_events_table)

and then implement the event handling class and write the logicas written in case R_UCOMM as above.

Thanks

Read only

0 Likes
5,130

I want to assign this report to a query, will this code work ?

i think queries don't support OO ALV.

Thanks