topic Re: Selecting Data from CE1* tables in Application Development and Automation Discussions

Selecting Data from CE1* tables

Former Member — Sat, 21 Jul 2007 08:54:14 GMT

Hi guys!

Why is it that when I select data from our CE1* table, it is faster to select

PERIO = '2007.007'

than to select

GJAHR = '2007' and PERDE = '007'?

Thanks!

Re: Selecting Data from CE1* tables

seshatalpasai_madala — Sat, 21 Jul 2007 08:56:27 GMT

Hi,

There can be various reasons,

1) PERIO may be part of any INDEX.

2) Since you have only one field to check in the first case it may be fast.

Regards,

Sesh

Re: Selecting Data from CE1* tables

Former Member — Sat, 21 Jul 2007 09:05:51 GMT

I see..

Why is that when I execute the code below, I do not get any data:

SELECT *
FROM ce1c5b1
INTO CORRESPONDING FIELDS OF TABLE itab_fert
    WHERE paledger EQ '10'
    AND perio EQ '2007007'
    AND mtart EQ 'FERT'.

But when I tried selecting in SE16 using the same logic I get data.

Thanks!

Re: Selecting Data from CE1* tables

seshatalpasai_madala — Sat, 21 Jul 2007 09:13:17 GMT

Hi,

Are you executing the query and Se16 in same client? if you are then the reason can be that some of the fields are case sensitive and you are passing data in all Caps.

Also you can check by accepting the data through PARAMTERS rather than hard coding the stuff, the reason can be that there are some converison routines that convert the data into a format that is required to fetch the data which may be Se16 does and your hardcoding does not.

Regards,

Sesh

Re: Selecting Data from CE1* tables

Former Member — Sat, 21 Jul 2007 09:32:36 GMT

> Hi,

> Are you executing the query and Se16 in same client?

> if you are then the reason can be that some of the

> fields are case sensitive and you are passing data in

> all Caps.

> Also you can check by accepting the data through

> PARAMTERS rather than hard coding the stuff, the

> reason can be that there are some converison routines

> that convert the data into a format that is required

> to fetch the data which may be Se16 does and your

> hardcoding does not.

> Regards,

> Sesh

I found out now. It is because actual data for PALEDGER is '010' not '10'.

Thanks anyway!