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.
Will Variant 1 work with all data types like Variant 2. I don't want to use Variant 2 because the performance is important.
But im not sure if Variant 1 works with all data types or only with characters. Because for example Dates are saved with 0000000 and not '' in the Database.
Variant 1
SELECT * FROM table INTO ls_table WHERE field <> ''.
DO something.
ENDSELECT.
Variant 2
select * from table into ls_table.
if field is not INITIAL.
do something.
endif.
endselect.
SELECT * FROM t000 WHERE logsys <> @( VALUE #( ) ) INTO TABLE @DATA(gt_out).
If your release does not support it yet I suppose you can always create a dummy line and use that since all its values are initial.
DATA: ls_dummy TYPE t000,
lt_result TYPE STANDARD TABLE OF t000.
SELECT * FROM t000 INTO TABLE lt_result WHERE logsys <> ls_dummy-logsys.
I was looking for constants of initial values for each predefined type so you do not have to declare the dummy variable and make the code more readable but could not find them.
Will Variant 1 work with all data types like Variant 2. I don't want to use Variant 2 because the performance is important.
But im not sure if Variant 1 works with all data types or only with characters. Because for example Dates are saved with 0000000 and not '' in the Database.
Variant 1
SELECT * FROM table INTO ls_table WHERE field <> ''.
DO something.
ENDSELECT.
Variant 2
select * from table into ls_table.
if field is not INITIAL.
do something.
endif.
endselect.
SELECT * FROM t000 WHERE logsys <> @( VALUE #( ) ) INTO TABLE @DATA(gt_out).
If your release does not support it yet I suppose you can always create a dummy line and use that since all its values are initial.
DATA: ls_dummy TYPE t000,
lt_result TYPE STANDARD TABLE OF t000.
SELECT * FROM t000 INTO TABLE lt_result WHERE logsys <> ls_dummy-logsys.
I was looking for constants of initial values for each predefined type so you do not have to declare the dummy variable and make the code more readable but could not find them.
Sure, I was more looking for something like cl_abap_exceptional_values=>char_initial_value to avoid the helper variable all together. For just comparing one field your approach is the better option though!
Given that usually you know the type, I've not had a problem. I use WHERE field EQ SPACE or WHERE field NE SPACE in most cases. However, where I've needed to check for initial date, I've declared
DATA initial_date TYPE d.
And used initial_date in the where clause. I didn't use a constant, because that requires setting a value.
it still doesn't work 6 years later in release 7700.1.10.3395
You are indicating the SAP GUI for Windows release, but your question is about "IS INITIAL" ABAP SQL, so what is your ABAP version? (see the link given by Horst, it's the release news about ABAP 7.53)
Of course, the ABAP SQL syntax cannot be transferred to the DB Cockpit. You enter native SQL in the SAP GUI SQL Editor. If the underlying DB does not support IS INITIAL, you cannot use it.
ABAP SQL's IS INTIAL depends on ABAP data types (built-in DDIC type) and must be translated by the DBI to a native SQL condition.
Bluesky
