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 dooesn't show any data at DEBUGGING

Former Member
0 Likes
424

hi all,

i have make a coding for report in which PRIMARY KEY of table EBAN has not been used in SELECTION PARAMETERS,so i have used it with my internal table as shown in the code.i have used all my SELECT-OPTIONS parameters when i execute my coding, my internal table i-e gi_reqdate doesn't give any data.Following are the coding:

SELECT badat
        FROM eban
        INTO CORRESPONDING FIELDS OF TABLE gi_reqdate
        WHERE ekorg IN s_ekorg
        AND   ebeln IN s_ebeln
        AND   lifnr IN s_lifnr
        AND   matnr IN s_matnr
        AND   banfn eq gi_reqdate-banfn.

Thanks,

sapabappk

hi all,

i have make a coding for report in which PRIMARY KEY of table EBAN has not been used in SELECTION PARAMETERS,so i have used it with my internal table as shown in the code.i have used all my SELECT-OPTIONS parameters when i execute my coding, my internal table i-e gi_reqdate doesn't give any data.Following are the coding:

SELECT badat
        FROM eban
        INTO CORRESPONDING FIELDS OF TABLE gi_reqdate
        WHERE ekorg IN s_ekorg
        AND   ebeln IN s_ebeln
        AND   lifnr IN s_lifnr
        AND   matnr IN s_matnr
        AND   banfn eq gi_reqdate-banfn.

Thanks,

sapabappk

2 REPLIES 2
Read only

brad_bohn
Active Contributor
0 Likes
398

AND banfn eq gi_reqdate-banfn.

This does not make sense - why are you doing that?

Read only

Former Member
0 Likes
398

I am completely agree with Brad.

If not required then remove last where condition.

you will get the data.