topic Select Query Failure in Application Development and Automation Discussions

Select Query Failure

Former Member — Fri, 09 Jan 2015 07:03:07 GMT

Hi All,

I have made a Z table and I am fetching data from it.

But the issue is some data is not being fetched, though the same data exists in the table.

I have 3 variables in where condition.

SELECT * FROM ZFIIST003 " Estimation Data
INTO CORRESPONDING FIELDS OF TABLE GT_ZFIIST003
WHERE PARTNER IN S_PART AND
ZDATE IN S_DATE and
VENDOR_NAME = PVENDOR .

if I remove VENDOR_NAME in this query then it is working fine.

But according to the requirement i have to keep this in the query.

Does any one having a solution.?

Re: Select Query Failure

Former Member — Fri, 09 Jan 2015 07:17:05 GMT

I think you have declare PVENDOR is PARAMETER filed. if you wont give in parameter field then you wont get anything.

make that field as select-option with no extension and no intervels and check it.

regards

laxman

Re: Select Query Failure

Former Member — Fri, 09 Jan 2015 07:18:39 GMT

Hi,

If you are missing conversion exit before your select, then add the below code before your select query and try again.

CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = PVENDOR
IMPORTING
OUTPUT = PVENDOR.

Re: Select Query Failure

former_member202818 — Fri, 09 Jan 2015 07:20:11 GMT

Hi Acharya,

Since PVENDOR is a parameter, if its value is initial the select query checks the records with VENDOR_NAME is initial.

So better make PVENDOR as obligatory field or change it to select option.

Note: If a select option is initial, 'where' will not consider this condition.\

Regards

Sreekanth

Re: Select Query Failure

RaymondGiuseppi — Fri, 09 Jan 2015 07:22:15 GMT

Did you check thru SE16[n] transaction, I could only suppose that either you don't pass the value or pass invalid values (e.g. conversio-exit or lowercase/uppercase characters mismatch)

NB: If SE16[n] is also unsuccesful there may be some incorrect data stored in database (nonn-consistent with field definition at Abap level, but correct at DB level, wrong conversion-exit or LC/UC) usually due to wrong coded upload of data.

Regards,

Raymond

Re: Select Query Failure

Former Member — Fri, 09 Jan 2015 07:29:02 GMT

Thanks a lot Raymond.

Yes I checked in SE16n.

I am getting the data in that.

I applied your solution to put the parameter as select options. And it worked.

Thank you:-)

Re: Select Query Failure

Mohamed_Mukhtar — Fri, 09 Jan 2015 07:29:50 GMT

Hi Yash,

Please check the value of PVENDOR in debugging mode and check the value in table.

May be it is lower and upper case issue.

Thanks

Re: Select Query Failure

RaymondGiuseppi — Fri, 09 Jan 2015 09:34:56 GMT

Usage of SELECT-OPTIONS was suggested by Laxman P, not by me…

Regards,

Raymond