topic Re: Select .. EndSelect : inconsistency in selection sequence in Application Development and Automation Discussions

Select .. EndSelect : inconsistency in selection sequence

navdeep_thakur12 — Mon, 14 Sep 2015 14:43:45 GMT

Hi All,

I came across a strange behavior of select.. endselect query.

want to know the sequence in which this will select data from DB tables?

eg:

select * from vbfa where vbeln = 'XXXXX'

.................

..................

endselect.

there are 5 records that meets the where condition.

that are stored in DB table as 1

but its fetching first 5th record then 1-2-3-4.in sequence.

not able to get the sequence logic in selecting these records.

thanks and regards

Re: Select .. EndSelect : inconsistency in selection sequence

former_member183073 — Mon, 14 Sep 2015 14:55:16 GMT

The Data in Database table will not be stored in sequence, it is the output in which it will be sorted and presented, Basically your se11 or se16 output is also a program which fetches the data and presents it.

If you want to get in sequence you can use ORDER BY Clause with select statement.

Re: Select .. EndSelect : inconsistency in selection sequence

Former Member — Mon, 14 Sep 2015 20:25:42 GMT

Navdeep - SAP selects and then sorts in order to show the display. In you program as well, you need to explicitly sort or order (as Syed suggested).

We had a similar issue where the primary keys were not sorted and our Binary READ was failing. SAP suggests, explicit sort.

Regards,

Raju.

Re: Select .. EndSelect : inconsistency in selection sequence

navdeep_thakur12 — Tue, 15 Sep 2015 06:06:53 GMT

Hi Syed,

thanks for your response.

it means select.... endselect will fetch record randomly from vbfa table??

since for most of the time select...endselect fetches record in the same sequence as it is present in VBFA table.

Regards

Re: Select .. EndSelect : inconsistency in selection sequence

RaymondGiuseppi — Tue, 15 Sep 2015 06:50:33 GMT

As soon as you don't use a ORDER BY option, SQL optimizer will usually read data in an unpredictable order, can also be complexified for buffered tables. In most database the assertion "as it is present in XXX table" is false or non-sense. In your example you are not selecting using first primary keys, so optimize may use some other secondary index, or even temporary hash table or buffer created during previous SQL execution.

Hint: Also read 185530 - Performance: Customer developments in SD if you didn't already create an index on VBELN.

Regards,

Raymond