SQL STATEMENTS IN SAP(ABAP)

SQL STATEMENTS

Under ABAP language we can work with SQL Statements

                     

OPEN SQL statements	NATIVE SQL
Syntax: Select * from emp . . . endselect. /*endselect is must 1)once executed prog(open sql), it can process the interface logic	Syntax: execsql Select * from emp . . . endexecsql. 1.) in case of native sql there is no interface logice b/w application server and database server

• NATIVE SQL doesn’t support cluster and pooled tables

Open SQL: while extracting data  in case of open SQL it can support for transparent cluster and pooled

• In case of Native SQL it can support Transparent tables only
• So OPEN SQL is better bcoz it supports all the tables

                                                 These are prog’s statements

Transparent tables : uses can work with Open Sql and native SQL it is cluster or pooled tables user can work with OPEN SQL only

Application  indicates a transparent tables.

Size category : 1 ………………….9

                            (G1000)          (9x61000)

2- indicated user can maintain max upto 6100 records.

* size category provides the size of the data which table maintains.

Buffering concept :

v     Buffering switched on

v     Buffering not allowed

v     Conditional buffering.

v     Buffering switched on but not allowed

            Buffering switched on means all records stored in application server and database server i.e. when buffering switched on that buffer maintains in application server.

In Real time conditional buffering is used for storing the records.

Maintenance allow : it provides authorization to the tables.

Enable the checkbox allows directly store records in Front-end as well as database.

Disable checkbox allows only front end.

1.) BUFFERING SWITCHED ON

§         Make it while creating database table once I switched on buffering

§         We have SAP R/3 imagine R/3 Application server, having R/3 Database server

§         If u look into Database server having zemp

§         under zemp having fields : eno &ename

§         and having data like eno:1,2,3 and in ename: rajendra, ravi, ajit

§         and emp1 is permanent employee, remaining are not permanent employees

NOTE:

Whenever Buffering is switched on

• respective buffer can maintain in Application server
• which Buffering is maintain in Application server holds a data parallels with R/3 database

DELIVERY CLASS functionality

Delivery class : provides type of date which tables maintains data there are 3 types.

1. master data (Eno. Ename etc)
2. Transactional data (salary data)
3. control data (Dept data)

A :  indicates master & transactional data.