topic Re: SE16 display problem in Application Development and Automation Discussions

SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:29:19 GMT

All,

I have a custom table that a primary key MANDT and VBELN (10 character length) and its have records from 0000000001 to 0000120000.

Here is my issue.

When i go to SE16 and display with parameters "Maximum No of Hits" with 200 and press F8 its starts display VBELN from 0000080126, Why it is not displaying from 0000000001.

Be default it should take from 0000000001 due to primary key VBELN

Any Info ?

PS : Please don't suggest to increase "Maximum No of Hits"

a®

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:36:30 GMT

Does it work with a range of 1 to 200?

Rob

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:39:08 GMT

Rob,

If i given range 1 to 200 in VBELN that is displaying fine.

But if given blank in VBELN and "Maximum No of Hits" as 200. then it starts displaying records with VBELN from 80126

a®

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:40:36 GMT

And if you write a Q&D program that selects up to 200 rows without any criteria in the WHERE, what happens?

rob

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:42:13 GMT

check the created date field in custom table, if the VBELN -0000080126 is inserted into custom

table first than VBELN - 0000000001, because of this it is displaying from 0000080126..

may i think this might be the reason...

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:45:27 GMT

I tried to write a select statement with UP To 200 rows , its giving me the same results as shows in SE16, its giving me results from VBELN 80126

Is it look strange ?

a®

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:46:58 GMT

There is no created date field in the table

a®

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:49:24 GMT

Hi,

Do you have any fields with INITIAL is checked and not Primary key checked? if yes then remove that checkbox and try

Thanks

Sudheer

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:49:56 GMT

check the order of the vbeln stored in the table by removing the maxiamum entries, you will know the data is stored...

if the data is stored in table with out sorting order, because of this the first entries in the table it is

picking with out sort order...

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:51:03 GMT

I have only one primary key as VBELN and for that key & Initial Checkbox are checked

a®

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 16:52:59 GMT

I don't want to change the maximum no of hits. I know that will display records properly. My question is i defined primary key as VBELN then it should pick from 1 and not from 80126

a®

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 16:53:05 GMT


> I tried to write a select statement with UP To 200 rows , its giving me the same results as shows in SE16, its giving me results from VBELN 80126
> 
> Is it look strange ?
> 
> a®s

I think this is "normal" although not "usual" behavior. If you don't specify a range, you cannot be sure of what you will get. But if in your SELECT statement, you put in an ORDER BY clause, you will probably get what you expect.

Rob

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 17:36:12 GMT

Rob,

I have written open sql statement (Oracle sql ) and get data checked , it found data not get sorted . so if we are not specify ROWs system will pick data from unsorted table , and display as per primary key sort order

a®

Re: SE16 display problem

former_member194669 — Tue, 02 Jun 2009 17:50:32 GMT

Any other opinion on this ?

a®

Re: SE16 display problem

naimesh_patel — Tue, 02 Jun 2009 18:39:03 GMT

SE16 uses the UP TO RSEUMOD-TBMAXSEL ROWS to get the records from the table.

This what the UP TO n ROWS documentation says:


If the addition ORDER BY is also specified, the rows of the hit list are sorted on the database server and only the number of sorted rows specified in n are passed to the result set. If the addition ORDER BY is not specified, n is filled with any number of rows in the result set that meet the WHERE condition.

Regards,

Naimesh Patel

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 19:34:39 GMT


> Any other opinion on this ?
> 
>  a®s

I still believe this to be expected behavior. Otherwise, why the option BY PRIMARY KEY for ORDER BY?

Rob

Re: SE16 display problem

Former Member — Tue, 02 Jun 2009 21:52:43 GMT

Just out of curiosity: go to VA03 or VF03 and display a document. Hit enter a few times...:-)

Then run SE16 for your table again?

Cheers,

Julius

Re: SE16 display problem

former_member194669 — Thu, 04 Jun 2009 16:51:01 GMT

Now i confused.

If i do SE16N it giving records different start records it showing with 45182 ?

a®

Re: SE16 display problem

Former Member — Thu, 04 Jun 2009 16:58:21 GMT

Darn, that means the golden solution of "Use a different transaction" won't even help...

Does SE16 now also give the same?

Cheers,

Julius

Re: SE16 display problem

former_member194669 — Thu, 04 Jun 2009 17:26:21 GMT

No , SE16 is giving results from starting record with VBELN 80126 , but SE16N giving starting records with VBELN 45182

a®