BW uses more Native SQL than R/3 does?

hi all,
BW uses more Native SQL than R/3 does? can anyone explain me how does bw makes effective use of native sql. (i knew what is meant by native sql). can anyone explain me with an realtime scenario.
regds
hari

Hi,
I don't get your question exactly; Native SQL is the SQL coding used in ABAP in order to deal with the underlying database objects (but I read that you knew that already...).
BW and R/3 are using extensively native SQL, I couldn't tell if one the application uses more than the other, furthermore I don't think such a statement would make sense.
BW uses native SQL to post data in the PSA, read this data in the PSA and pass it the internal tables for further processing (Trules / URules for instance); insert records in a cube; read the data in a cube/ods/IObj... in order to display the result of a query; native SQL is used for administrating the BW objects, monitoring, to record statistic; native SQL is used to generate code dynamically and to store/retrieve it from the database...
In few words, there's a database table behind every single object/process in BW and R/3.
The database is the memory of your system, native SQL is the mean to use this memory.
hope this answers your question
Olivier.
Message was edited by:
Olivier Cora

Similar Messages

Use of native SQL-select statment

hi,
in my z-abap i use a native sql, saying the following:
EXEC SQL.
select agzdau into :gf_agzdau from APZD08/AG
                where AGMAID = '77732' and
                      AGJAHR = 2008 and
                      AGMON = 09 and
                      AGSPAL = 'ZASALD'
                      %_HINTS AS400 'HARD_CLOSE'
ENDEXEC.
before that i make a connection to the server where the table is stored.
APZD08 is the library and AG is the filename (on a AS/400-machine)
BUT: the file is not always in APZD08-lib, it depends on the employee.
how can i make the lib-name and file flexible:
i have tried it with
select...............from :gf_file
and i have put a value for gf_file before.
but with that i got an SQL-error -104 when executing.
i can't use a hostvariable there it seems.
any ideas ?
reg, Martin

Hi.
I would use ADBC instead of EXEC SQL. Then you can concatenate the SQL statement in the way you want it. But in that case you should use host variables in the where condition to get better performance.
So something like the following (untested, no syntax check yet, pseudo code...):
DATA: p_con_name   TYPE dbcon-con_name,
      p_con_ref    TYPE REF TO cl_sql_connection,
      p_stmnt      TYPE REF TO cl_sql_statement,
      p_result_set TYPE REF TO cl_sql_result_set,
      query        TYPE string.
p_con_ref = cl_sql_connection=>get_connection( 'YOURCON' ).
LOOP AT it_employees
* CASE your logic
CONCATENATE 'select agzdau from ' table_name
            'where AGMAID = ? and AGJAHR = ?'
       INTO statement SEPARATED BY SPACE.
* ENDCASE
TRY.
p_stmnt = p_con_ref->create_statement( ).
GET REFERENCE OF p_agamaid INTO p_paramref.
p_stmnt->set_param( p_paramref ).
GET REFERENCE OF p_agjahr INTO p_paramref.
p_stmnt->set_param( p_paramref ).
p_result_set = p_stmnt->execute_query( query ).
GET REFERENCE OF gf_agzdau INTO p_resultref.
p_result_set->set_param( p_resultref ).
p_result_set->next( ).
CATCH CX_SQL_EXCEPTION.
* error handling needed!
ENDTRY.
ENDLOOP.
p_con_ref->close( ).
Oh, I was assuming that there is only one result. If there can be more (and better style anyway) do a while-loop until next( ) is different from zero.
Best regards,
Jan

Use of Native SQL

Can i use all sql statementsa which are used in oracle ? Basically I am more interested in oracle data conversion functions like to_date(),To_Char() with appropriate formats.
I know that to use oracle's native commands i have to use Native SQL and for that i have to write my query between EXEC SQL and ENDEXEC. But i am not able to use query that uses date conversion fuctions like to_date() and to_char().
Also i want to know the list of SQL statements which can be used with Native SQL in Oracle.

HI.
please refer this one.
To avoid the standard F4 help to be show, insert the event PROCESS ON-VALUE-REQUEST request in the program and add a field statement for the field that should trigger the F4 help. In the module called from PROCESS ON-VALUE-REQUEST request, call function module F4IF_FIELD_VALUE_REQUEST.
Example Code :
process before output.
process after input.
PROCESS ON VALUE-REQUEST.
FIELD sflight-carrid MODULE f4_help_for_carrid.
MODULE f4_help_for_carrid INPUT.
NOTE:
Tabname/fieldname is the name of the table and field
for which F4 should be shown.
Dynprog/Dynpnr/Dynprofield are the names of the Progran/Dynpro/Field
in which the f4 value should be returned.
Value: The value of the Dynpro field when calling the F4 help.
You can limit the values shown, by inseting a value in this parameter
e.g 'A*' to show only values beginning with A
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
tabname = 'SFLIGHT'
fieldname = 'CARRID'
SEARCHHELP = ' '
SHLPPARAM = ' '
dynpprog = 'ZDANY_F4_OWN_CALL'
dynpnr = '0100'
dynprofield = 'SFLIGHT-CARRID'
STEPL = 0
value = 'A*'
MULTIPLE_CHOICE = ' '
DISPLAY = ' '
SUPPRESS_RECORDLIST = ' '
CALLBACK_PROGRAM = ' '
CALLBACK_FORM = ' '
TABLES
RETURN_TAB =
EXCEPTIONS
FIELD_NOT_FOUND = 1
NO_HELP_FOR_FIELD = 2
INCONSISTENT_HELP = 3
NO_VALUES_FOUND = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDMODULE. " F4_help_for_carrid
To control F4 help in a selection screen use the AT SELECTION-SCREEN ON VALUE-REQUEST FOR event.Note that for ranges both the low and high value of the field must have there own ON VALUE-REQUEST
Example:
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_prctr-low.
PERFORM f4_help_carrid.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_prctr-high.
PERFORM f4_help_carrid
Rewards all helpfull answers.
Regards.
Jay

Does LTE use more data usage than 4G?

Does LTE use more data usage than 4G?

The question makes no sense.
LTE and 4G are types of connections. They do not use Data, they allow your apps and services on the iPhone or iPad to use the Data access.
In most cases 4G is slightly slower than LTE.

Retreiving data from external DB using cursors (Native SQL)

Hi experts,
Iu2019m trying to use some functionality based on the Native SQL on an Oracle Server. Iu2019m facing some difficulties using cursors and fetching data from the external database.
Basically the synonym its zfisicc_c_dblink, and Iu2019m running the for the following code:
TRY.
      OPEN CURSOR WITH HOLD c1 FOR SELECT *
                            FROM zfisicc_c_dblink
                            WHERE estado_sif = 'I'.
    CATCH cx_sql_exception INTO sqlerr_ref.
      PERFORM handle_sql_exception USING sqlerr_ref.
ENDTRY.
DO.
* "Move the data from the Cursor into the target area.
    FETCH NEXT CURSOR c1 APPENDING TABLE tab.
    IF sy-subrc 0.
      EXIT.
    ENDIF.
ENDDO.
CLOSE CURSOR c1.
The cursor C1 it's cursor type and the table tab it's ZFISICC_C_DBLINK type, but every time i run it it's giving me the ORA-932 error.
Database error text........: "ORA-00932: inconsistent datatypes: expected %s
got %s"
Can anyone help me on this error? What Iu2019m doing wrong when fetching the data ?
Another doubt that Iu2019ve it's when using pl/Sql procedure. Can anyone tell how I can retrieve data from the external database with the following code?
**Select Directo com Cursor
EXEC SQL.
    CONNECT TO :gv_db_name AS 'dblink_con'
ENDEXEC.
IF sy-subrc NE 0.
    WRITE: 'Não foi possível fazer a ligação à DBCON: ', gv_db_name.
ELSE.
    EXEC SQL.
      DECLARE CURSOR c_1 IS SELECT tipo_operacao FROM movimento_contribuicao
             WHERE ROWNUM <= 10000;
          wa movimento_contribuicao.tipo_operacao%type;
BEGIN
       OPEN c_1;
     LOOP
        FETCH c_1 INTO wa; "Not able to return data to SAP system
         EXIT WHEN c_1%NOTFOUND;
      END LOOP;
END;
    ENDEXEC.
      EXEC SQL.
      DISCONNECT 'dblink_con'
    ENDEXEC.
ENDIF.
On the FETCH c_1 INTO wa; code Iu2019m moving the data to an Oracle variable, wa movimento_contribuicao.tipo_operacao%type;, and not to an program variable. Can anyone explain me this how this is +possible using this PL/SQL procedure?
Thanks in advance,
Best Regards
João Martins
Edited by: Rob Burbank on May 7, 2010 10:25 AM

Hi Joao,
Regarding your first question: It looks like there's a conversion problem (with one or more columns) from your Oracle table to your ABAP internal table.
In the following link you can see (in your case in the SELECT section) the type conversions used for each type combination.
Some combinations lead to an oracle error (specified in the "Result" column), like in your case (error 932).
http://help.sap.com/saphelp_470/helpdata/EN/a3/74caa1d9c411d1950e0000e8353423/content.htm
Regarding your second question: You can use the PERFORMING addition in the EXEC SQL statement.
You can see an example in the following link:
http://help.sap.com/saphelp_470/helpdata/EN/fc/eb3b8b358411d1829f0000e829fbfe/content.htm
Hope it helps.
Regards,
Ana Luisa.

What is native Sql data types and does oracle support this?

what is native Sql data types
Does oracle support this?

http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#g31099

Loading data from SQL Datasource using more complex sql such as GROUP BY

Hi,
Essbase's Open Sql Data Sources dialog box allows you to build an sql for loading, but it doesn't allow GROUP BY clause. The only other way I can think of is to build a view in SQL server to provide proper data groupings (aggregated fields). Is there an easier way to do this that doesn't require me to add stuff on the SQL server? Thx.

never mind. just need to check the formatted sql in app log. doesn't format exactly as typed - it didn't add all the necessary spaces.

Native SQL Execution- Dump Table Does Not Exists in DB

Hi Experts,
we have created a table in the Oracle Database DBTAB by logging into oracle directly.
Now I need to insert records in this table from ABAP report by using EXEC- ENDEXEC block.
But I am getting a dump saying-- "Table doesnot exists in the Database" alothough table has been created.
EXEC SQL.
INSERT INTO DBTAB@ifsap
       (A,
        B,
        C,
        D)
        VALUES
        (:a,
         :b,
         :c,
         :d)
ENDEXEC.
I have tried table name as DBTAB as well as DBTAB@ifsapc also but the same error is coming.
Could you suggest?
Thanks
Depesh

Hello Depesh,
please let's start at the beginning again.
> we have created a table in the Oracle Database DBTAB by logging into oracle directly
In which schema was the table DBTAB created?
Was this table created in the same oracle database on which the SAP system is running?
> I have tried table name as DBTAB as well as DBTAB@ifsapc also but the same error is coming.
Again .. in which schema was the table created?
If you don't know the answers of the questions from above .. please run the following query and post the output:
shell> sqlplus / as sysdba
SQL> SELECT OWNER, TABLESPACE_NAME FROM DBA_TABLES WHERE TABLE_NAME = 'DBTAB';
Regards
Stefan
P.S.: By the way .. if you purchase the oracle license by SAP ... please keep sapnote #581312 (Point 3 and solution) in your mind.

Who to use Native SQL statements in ABAP

hi all,
who to use native sql staements in abap bypassing Application server.
with regards,
suresh babu aluri.

Hi
Native SQL statements define an area in an ABAP program in which one or more Native SQL statements are to be carried out. The area between EXEC and ENDEXEC is not completely checked by the syntax check. The statements entered there are passed to the Native SQL interface and processed there as follows:
Almost all SQL statements that are valid for the addressed database system can be included between EXEC and ENDEXEC, in particular the DDL statements. These SQL statements are passed from the Native SQL interface to the database system largely unchanged. The syntax rules are specified by the database system, in particular the case sensitivity rules for database objects. If the syntax allows a separator character between individual statements, you can include several Native SQL statements between EXEC and ENDEXEC. Generally, the semicolon ( is used as the separator character.
You can also include SAP-specific Native SQL language elements between EXEC and ENDEXEC. These statements are not passed directly from the Native SQL interface to the database, but are converted appropriately.
All Native SQL statements bypass SAP buffering.
The ENDEXEC statement sets sy-dbcnt to the number of table rows processed in the last Native SQL statement. After implicit cursor processing with PERFORMING, sy-dbcnt contains the total number of lines read.
Programs with Native SQL statements are generally dependent on the database system used, so that they cannot be executed in all ABAP systems. This is especially true for the examples in this section, which was written for Informix database systems.
Example
Inserting two rows in the database table SCARR. If neither of these rows exists, sy-subrc is set to 0 by ENDEXEC and sy-dbcnt to 1. Otherwise, an exception is raised and handled.
DATA: exc_ref    TYPE REF TO cx_sy_native_sql_error,
      error_text TYPE string.
TRY.
    EXEC SQL.
      INSERT INTO scarr
                  (MANDT, CARRID, CARRNAME, CURRCODE, URL)
        VALUES ('000', 'FF', 'Funny Flyers', 'EUR',
                'http://www.ff.com');
      INSERT INTO scarr
                 (MANDT, CARRID, CARRNAME, CURRCODE, URL)
        VALUES ('000', 'EF', 'Easy Flyers', 'EUR',
                'http://www.ef.com');
    ENDEXEC.
CATCH cx_sy_native_sql_error INTO exc_ref.
    error_text = exc_ref->get_text( ).
    MESSAGE error_text TYPE 'I'.
ENDTRY.
Reward points if useful
Regards
Anji

Using native sql

I have a program, which will using native to query data. The following is db connection.
   EXEC SQL.
     connect to :lv_qtn
   ENDEXEC.
   EXEC SQL.
     SET CONNECTION :lv_qtn
   ENDEXEC.
Can i locate the database structure in sap, like using se11. Thanks!

Hi
see this and do accordingly
Native SQL statements define an area in an ABAP program in which one or more Native SQL statements are to be carried out. The area between EXEC and ENDEXEC is not completely checked by the syntax check. The statements entered there are passed to the Native SQL interface and processed there as follows:
Almost all SQL statements that are valid for the addressed database system can be included between EXEC and ENDEXEC, in particular the DDL statements. These SQL statements are passed from the Native SQL interface to the database system largely unchanged. The syntax rules are specified by the database system, in particular the case sensitivity rules for database objects. If the syntax allows a separator character between individual statements, you can include several Native SQL statements between EXEC and ENDEXEC. Generally, the semicolon ( is used as the separator character.
You can also include SAP-specific Native SQL language elements between EXEC and ENDEXEC. These statements are not passed directly from the Native SQL interface to the database, but are converted appropriately.
All Native SQL statements bypass SAP buffering.
The ENDEXEC statement sets sy-dbcnt to the number of table rows processed in the last Native SQL statement. After implicit cursor processing with PERFORMING, sy-dbcnt contains the total number of lines read.
Programs with Native SQL statements are generally dependent on the database system used, so that they cannot be executed in all ABAP systems. This is especially true for the examples in this section, which was written for Informix database systems.
Example
Inserting two rows in the database table SCARR. If neither of these rows exists, sy-subrc is set to 0 by ENDEXEC and sy-dbcnt to 1. Otherwise, an exception is raised and handled.
DATA: exc_ref    TYPE REF TO cx_sy_native_sql_error,
      error_text TYPE string.
TRY.
    EXEC SQL.
      INSERT INTO scarr
                  (MANDT, CARRID, CARRNAME, CURRCODE, URL)
        VALUES ('000', 'FF', 'Funny Flyers', 'EUR',
                'http://www.ff.com');
      INSERT INTO scarr
                 (MANDT, CARRID, CARRNAME, CURRCODE, URL)
        VALUES ('000', 'EF', 'Easy Flyers', 'EUR',
                'http://www.ef.com');
    ENDEXEC.
CATCH cx_sy_native_sql_error INTO exc_ref.
    error_text = exc_ref->get_text( ).
    MESSAGE error_text TYPE 'I'.
ENDTRY.
Regards
Anji

About use native sql

how to use the native sql get the following value
REPORT YXLIU0010.
DATA: exc_ref TYPE REF TO cx_sy_native_sql_error,
      error_text TYPE string.
DATA: BEGIN OF ITAB OCCURS 0 ,
F_BH(30) TYPE C,
F_NCYEJE TYPE p DECIMALS 2,
END OF ITAB.
TRY.
    EXEC SQL PERFORMING eout.
      select ZFIITKMJE.F_KMBH as F_BH,SUM(F_SNJZ) as F_NCYEJE into :itab from ZFIITKMJE
    ENDEXEC.
CATCH cx_sy_native_sql_error
    INTO exc_ref.
    error_text = exc_ref->get_text( ).
    ROLLBACK WORK.
ENDTRY.
FORM eout.
write / ITAB-f_bh .
ENDFORM.
it seems than native sql not suppot alias column

ok!, the last code can work. but i don`t know what happen with "fetch next" or with other thing....
because now the problem is when call the function: DB02_GET_TB_DETL_ANALYSIS_DB2.
this send a dump:
Table does not exist in database.
The termination occurred in line 26 of the source code of the (Include)
program "LDB02_DB2U20"
of the source code of program "LDB02_DB2U20" (when calling the editor 260).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "DB02_GET_TB_DETL_ANALYSIS_DB2" "(FUNCTION)" but was not handled
locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLDB02_DB2 ". Its source code starts in line
7
of the (Include) program "LDB02_DB2$20 ".
and indicate this part in the code of the function:
000240 ?
000250 ?   EXEC SQL.
     > ?     SELECT NAME, CREATOR,
000270 ?            TYPE, DBNAME,
000280 ?            TSNAME, COLCOUNT,
000290 ?            NPAGES, KEYCOLUMNS,

Querying using Native SQL

Hi Pals,
I have a requirement which I would like to brief.
I have an internal table with columns FIELD1 and FIELD2. For all the values in FIELD1 I have to query a table MSI(which does not form a part of the R/3 framework) through Native SQL statement and get the corresponding values for FIELD2.
Could anybody suggest how I must proceed writing my statements between EXEC and ENDEXEC.
Do I have to query the database table for each entry in my internal table or is it possible to use for all entries in my SQL statemnt.
Your inputs would be highly appreciated.
Thank You in advance.
Regards,
Gayathri N.

Hai Gayathri
check this document
EXEC SQL.
Addition
... PERFORMING form
Effect
Executes the Native SQL command enclosed by the statements EXEC SQL and ENDEXEC . In contrast to Open SQL , addressed database tables do not have to be known to the ABAP/4 Dictionary and the ABAP/4 program does not have to contain appropriate TABLES statements.
Example
Create the table AVERI_CLNT :
EXEC SQL.
CREATE TABLE AVERI_CLNT (
         CLIENT   CHAR(3) NOT NULL,
         ARG1     CHAR(3) NOT NULL,
         ARG2     CHAR(3) NOT NULL,
         FUNCTION CHAR(10) NOT NULL,
         PRIMARY KEY (CLIENT, ARG1, ARG2)
ENDEXEC.
With Native SQL commands, passing data between an ABAP/4 program and the database is achieved using host variables . A host variable is an ABAP/4 variable prefixed by a "*" in the Native SQL statement.
Example
Display a section of the table AVERI_CLNT :
DATA: F1(3), F2(3), F3(3).
F3 = ' 1 '
EXEC SQL.
SELECT CLIENT, ARG1 INTO :F1, :F2 FROM AVERI_CLNT
         WHERE ARG2 = :F3
ENDEXEC.
WRITE: / F1, F2.
To simplify the spelling of INTO lists in the SELECT command, you can specify a single structure as the target area as in Open SQL .
Example
Display a section of the table AVERI_CLNT :
DATA: BEGIN OF WA,
        CLIENT(3), ARG1(3), ARG2(3),
      END OF WA.
DATA F3(3).
F3 = ' 1 '
EXEC SQL.
SELECT CLIENT, ARG1 INTO :WA FROM AVERI_CLNT
         WHERE ARG2 = :F3
ENDEXEC.
WRITE: / WA-CLIENT, WA-ARG1.
Notes
In contrast to Open SQL , a client field in Native SQL is a field like any other and must be specified explicitly in calls.
Authorization checks cannot be properly realized in EXEC SQL . You should perform these in the program.
When you start the R/3 System, a CONNECT to the current database is executed automatically. An explicit CONNECT is unnecessary.
A Native SQL command can (but does not have to) end with a ";". Under no circumstances should it end with a ".".
Some database systems allow upper and lower case in table names and field names. If you want to take advantage of this, you must ensure that the spelling of names is correct. To enable entry of lower case letters in names in the ABAP/4 editor, you must set the attribute for upper/lower case in the report.
Since there are no arrays in ABAP/4 , array operations are not possible in Native SQL . If the result of a SELECT command is a table, you can read this table line by line either with the Native SQL command FETCH or with the addition ... PERFORMING form .
Unlike in ABAP/4 programs, the character " in a Native SQL statement does not introduce a comment until the end of the editor line.
Addition
... PERFORMING form
Effect
If the result of a SELECT command is a table, you can read this table line by line in a processing loop. The subroutine form is called once for each line. In this subroutine, you can leave the loop by using EXIT FROM SQL . If the result of the selection is a single record, the subroutine is called only once.
Example
Display a section of the table AVERI_CLNT :
DATA: F1(3), F2(3), F3(3).
F3 = ' 1 '
EXEC SQL PERFORMING WRITE_AVERI_CLNT.
SELECT CLIENT, ARG1 INTO :F1, :F2 FROM AVERI_CLNT
         WHERE ARG2 = :F3
ENDEXEC.
FORM WRITE_AVERI_CLNT.
WRITE: / F1, F2.
ENDFORM.
Note
This addition is allowed only with a SELECT command.
Related SELECT , INSERT , UPDATE , MODIFY , DELETE , OPEN CURSOR , FETCH , CLOSE CURSOR, COMMIT WORK and ROLLBACK WORK .
go to se38
type 'EXEC' and put cursor on 'EXEC' press f1-function key
then you get help for EXEC
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Native sql DBCO, CONNECT statement short dump

Hi ALL ,
I am facing the problem here. please help me out in this.
i am trying to connce to the external database MSS, i made all the entries in the DBCO t-code and writing the follwoing native sql statement.
EXEC SQL.
CONNECT TO 'AAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
The above statement is not giving any error when i activate it but when i execute it is giving me shortdump error .
I already maintan   entries in DBCON table or DBCO t-code
And also tel me once it is connect how can i access the data from MSS (Microsoft sql server)i mean what kind of statement.
helpfull answer will be rewarded.
Anees
9886358645
Message was edited by:
        anees jawad

Native SQL
Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.
As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.
Native SQL Statements in ABAP Programs
To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:
EXEC SQL [PERFORMING )
The parameters are separated by commas. You must also specify whether the parameter is for input (IN), output (OUT) or input and output (INOUT). For further information, refer to SAP Note 44977.
EXEC SQL
   EXECUTE PROCEDURE proc1 ( IN , OUT :y )
ENDEXEC.
Cursor Processing
Cursor processing in Native SQL is similar to that in Open SQL:
OPEN
ENDIF.
ENDDO.
EXEC SQL.
CLOSE c1
ENDEXEC.
This example opens a cursor, reads data line by line, and closes the cursor again. As in Open SQL, SY-SUBRC indicates whether a line could be read.
Data Types and Conversions
Using Native SQL, you can
Transfer values from ABAP fields to the database
Read data from the database and process it in ABAP programs.
Native SQL works without the administrative data about database tables stored in the ABAP Dictionary. Consequently, it cannot perform all of the consistency checks used in Open SQL. This places a larger degree of responsibility on application developers to work with ABAP fields of the correct type. You should always ensure that the ABAP data type and the type of the database column are identical.
If the database table is not defined in the ABAP Dictionary, you cannot refer directly to its data type. In this case, you should create a uniform type description in the ABAP Dictionary, which can then be used by all application programs.
If the table is defined in the ABAP Dictionary, you should remember that the sequence of fields in the ABAP Dictionary definition may not be the same as the actual sequence of fields in the database. Using the asterisk (*) in the SELECT clause to read all columns into a corresponding work area would lead to meaningless results. In the worst case, it would cause an error.
The Native SQL module of the database interface passes a description of the type, size, and memory location of the ABAP fields used to the database system. The relevant database system operations are usually used to access and convert the data. You can find details of these operations in the manuals for the programming interface of the relevant database system. In some cases, Native SQL also performs other compatibility checks.
The documentation from the various database manufacturers provides detailed lists of combinations of ABAP data types and database column types, both for storing ABAP field values in database tables (INSERT, UPDATE) and for reading database contents into ABAP fields (SELECT). You can also apply these descriptions for the input and output parameters of database procedures. Any combinations not listed there are undefined, and should not be used.
The following sections provide details of the data types and conversions for individual databases. Although they are database-specific, there are also some common features.
Recommended type combinations are underlined. Only for these combinations is behavior guaranteed from release to release. For any other combinations, you should assume that the description only applies to the specified release.
The results of conversions are listed in a results column:
"OK": The conversion can be performed without loss of data.
Operations that fail are indicated by their SQL error code. Errors of this kind always lead to program termination and an ABAP short dump.
In some cases, data is transferred without an SQL error occurring. However, the data is truncated, rounded, or otherwise unusable:
Right truncation.
"Left" or "right" applies to the normal way of writing a value. So, for example, if a number is truncated, its decimal places are affected.
: Left truncation
: Number is rounded up or down during conversion
: A number that was "too small" is rounded to 0 (underflow)
: The conversion result is undefined.
There are several possible results. The concrete result is either not known at all, or can only be described using a set of rules that is too complicated for practical use.
: The conversion returns the SQL value NULL.
: The conversion is performed without fields and unchecked.
The original data is converted, but without its format being checked. The result may therefore be a value invalid for the result type, which cannot be processed further. An example of this is a date field containing the value "99999999" or "abcdefgh" after conversion.
Combinations of ABAP data type and database column type can be divided into finer subcategories. Here, for example, using the transfer direction ABAP ® database (INSERT, UPDATE):
If the width of the ABAP field is greater than that of the database column, the ABAP field may contain values for which there is not enough space in the database column. This can produce other cases: The concrete data value in ABAP finds space in the database column, or not.
If the ABAP field is at most as long as the database column, there is always space for the ABAP value in the database column.
Some types, such as numeric columns, expect values in a particular format. This is particularly important in connection with character types, for example, when you want to write an ABAP character field (type C) into an integer column.
Native SQL for Oracle
Native SQL for Informix
Native SQL for DB2 Common Server
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3b8b358411d1829f0000e829fbfe/content.htm

Native SQL Regarding

Hai Experts,
I need To Insert Values Into Sql Server Table Using EXEC And ENDEXEC Commands.
Can Any one Give Some Suggestion.
<REMOVED BY MODERATOR>
Thanks In Adv,
Jai.M
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 4:38 PM

Hi,
EXEC SQl statement does Native SQL .Normally we use OPEN sql statement.
This is not database specific.So datbase convetor converts into database specific sql statements for our sql statements.This is slow fetching compared to Native sql.
Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.
As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.
Native SQL Statements in ABAP Programs
To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:
REPORT demo_native_sql.
DATA: BEGIN OF wa,
connid TYPE spfli-connid,
cityfrom TYPE spfli-cityfrom,
cityto TYPE spfli-cityto,
END OF wa.
DATA c1 TYPE spfli-carrid VALUE 'LH'.
EXEC SQL PERFORMING loop_output.
SELECT connid, cityfrom, cityto
INTO :wa
FROM spfli
WHERE carrid = :c1
ENDEXEC.
FORM loop_output.
WRITE: / wa-connid, wa-cityfrom, wa-cityto.
ENDFORM.
<REMOVED BY MODERATOR>
Cheers,
Chandra Sekhar.
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 4:40 PM

Open & Native SQL

Hai all !
Can anybody give me the exact Difference between Open SQL & Native SQL.
Thanks in Advance,
Swapna.

Hii!
Open SQL is basically SAP specific Structured Query language.Open SQL consists of a set of ABAP statements that perform operations on the central database in the R/3 System. The results of the operations and any error messages are independent of the database system in use. Open SQL thus provides a uniform syntax and semantics for all of the database systems supported by SAP. ABAP programs that only use Open SQL statements will work in any R/3 System, regardless of the database system in use. Open SQL statements can only work with database tables that have been created in the ABAP Dictionary.
Native SQL is basically a database specific language.
Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.
As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.
To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:
EXEC SQL [PERFORMING <form>].
<Native SQL statement>
ENDEXEC.

BW uses more Native SQL than R/3 does?

Similar Messages

Maybe you are looking for