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

internal table handling

Former Member
0 Likes
345

hi all,

I have a module program which is allow user to key in multiple PO and material, there is an internal table to store PO,material,open qty.

i use PgUp, PgDown button to let user navigate the entry in the internal table.

when user navigate the data,the record is identify through the following code:

READ TABLE t_open_summ INTO w_open_summ INDEX tap_index_openpo

now the user have a new request when they key in PO,material

in the first screen. They want to get only related PO & material

from the internal table above. Not all the data in the table.

i know i can use

READ TABLE t_open_summ INTO w_open_summ with key PO =xxxx matnr=xxx to retrieve the data.

however to make the PgUp, PgDown button works, i have to use READ TABLE t_open_summ INTO w_open_summ INDEX tap_index_openpo

please advise how to use in-coporate both in one statement?

thanks.

1 ACCEPTED SOLUTION
Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
325

You need to make sure that table t_open_summ contains only the data for PO =xxxx matnr=xxx to begin with. I.e. when that table is filled in, just don't put any other data there. Then all the corresponding scrolling code (Page Up/Down) will work as usual.

As an alternative, you could create a "clone" of t_open_summ and work with it instead.

1 REPLY 1
Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
326

You need to make sure that table t_open_summ contains only the data for PO =xxxx matnr=xxx to begin with. I.e. when that table is filled in, just don't put any other data there. Then all the corresponding scrolling code (Page Up/Down) will work as usual.

As an alternative, you could create a "clone" of t_open_summ and work with it instead.