Database View Projection View Maintenance View Help View

This is inner join Just retrieves some Helps in creating

This is used for search
1. view of one or more fields from a single maintaining data of the
help.
tables. table. application object.
Creation of Table
Table Maintenance Table Maintenance Creation of Table
Maintenance
2. Generator (TMG) Generator (TMG) can be Maintenance Generator
Generator (TMG)
can be made. made. (TMG) not possible.
not possible.
Here single table can Read, Delete, Insert and
Only Single table No operations possible
be read and changed Change operations
3. can be read and on single and multiple
but multiple tables possible on single and
changed. tables.
can only be read. multiple tables.
It supports both It supports both
It can support only It supports either tables
4. projection as well as projection as well as
projection of data. or views as input.
selection. selection.
Here Join condition It has single table Here Join conditions are
It maintains a
needs to be so there is no need Proposed by SAP itself
5. relationship of N:1 i.e.,
provided manually to maintain join i.e., show in the form of
a Left Outer Join.
(Inner Join). conditions. foreign key relationship.

Overview Screen Single Screen

• It contains only the key fields. • It contains all the fields.
• In this, we can delete and update. • In this, we can only maintain screen, Like
Delete and Insert. We cannot update from
single screen.

Include Structure Append Structure

• It can be included anywhere in the table. • It will be appended only at last.

• You cannot use this include structure • This is a mechanism to enhance the SAP
(Created by you) in standard table. Standard table.
 Database Table Structure
1. It must contain at least one field as 1. It doesn’t contain any primary fields.
primary field.
2. It contains the permanent data. 2. Structure doesn’t contain any data.

3. We must provide the size of the database 3. We only use to provide the size of the
table structure.
4. We must provide the delivery class to the 4. We no need to provide the delivery class to
table. the structure.
5. Foreign key is possible. 5. Foreign key is not possible.

Transparent Pool Cluster

Contain a single table. Used to They are used to hold a large They are used to hold data
store master data number of very small tables from a few numbers of large
(stores system data) tables (stores system data)

It has a one-to-one relationship It has a many-to-one relationship It has a many-to-one

with a table in the database with a table in the database relationship with table in the
database
For each transparent table It is stored with other pooled Many cluster tables are stored
there is one associated table in tables in a single table called in a single table in the database
the database table pool in the database called a table cluster

The database table has the The database table has different The database table has
same name, same number of name, different number of fields different name, different
fields and the fields have the and fields have different names number of fields and fields
same names have different names

There is only a single table Table pools contain more tables Contains less tables than table
than table clusters pools

Secondary indexes can be Secondary indexes cannot be Secondary indexes cannot be

created created created
 STANDARD SORTED HASHED
These are the default internal These are special ITAB's These are also special type of
tables which are created by us. where the data is ITAB which should be used
automatically sorted when working with large
whenever a new record is data sets (Bulk amount of
We use either key operation (or) added. data).
index operation to read a record. Here, we use only Key
We use either key(or) index operation, but not the index
We use either linear search (or) operation to read a record. operation.
Binary search for reading record.
We use only Binary search for It uses Hashed algorithm for
reading a record, bcoz the reading a record.
If use Binary Search, the response data is automatically sorted.
time will be
Resp.Time = Log(N). The Response Time will be
same. The Resp.Time is always
We can append, insert the records fixed regardless of the total
whenever we want. no of records.
The main disadvantage is, we
We can sort the data based on our cannot sort ITABS based on In Real-Time, we hashed
own conditions. our conditions, bcoz the data ITAB's only whenever we
is already sorted. work with server-to-server
communication like
transferring the data from
ABAP to BI server.
 INDEX EXTENSION INDEX
• An index is a sorted copy of selected • Extension Index are nothing but
database table fields. secondary indexes for the SAP standard
tables.
• We can create the index and it can be • It can be enhanced, but cannot be
modified. modified.
• After changing the version or updating • After changing the version or updating
the data, the previous data will be lost the data, the previous data will not be
during the process. lost during the process.

BDC LSMW
(BATCH DATA COMMUNICATION) (LEGACY SYSTEM MIGRATION WORKBENCH)
1. It is basically a program which is either 1. It is a more user-friendly tool, through
generated by SAP after a recording or which one can do the same work as the
programmed by a abaper. It’s like BDC. One just has to follow the 14 steps.
running the the transaction manually
but all the data is populated in the
screens automatically.
2. It simply makes use of recording. There 2. It provides various methods for migration
are two ways of implementing BDC, the of data, namely those of Direct Input,
call transaction method and the session Batch Input recording and IDOC.
method.
3. It is one has to provide explicit mapping 3. In this, mapping is taken care of with the
directors. help of SAP.
4. In this, we can schedule the job, so the 4. It has to be done at once only. So, through
uploading can be done at the same LSMW, we cannot upload huge amount of
time or later periodically. data.
5. We use BDC to upload records more 5. We use LSMW for updating or inserting
than 5000. below 5000 records.
6. BDC is mainly used by technical 6. LSMW is devised specially for functional
consultants, who perform coding. consultants who do not perform coding.

OR
 BDC LSMW
1. BDC is nothing but a Data Conversion
1. LSMW is a Data migration tool.
method.
2. BDC is User Defined program not 2. LSMW is R/3 Based Application tool provides
provided by SAP. by SAP.
3. In BDC’s the Data was Converted into SAP 3. In LSMW the Data was Imported/ Migrated
Database. into SAP Database.
4. In BDC’s we can Communicate the Data 4. In LSMW we can migrate the Data via 4
Via 3 methods, there are:
methods, there are: a. Direct Input
a. Direct Input method, b. Batch Input
b. Session method, c. BAPI’s
c. Call transaction method. d. IDOC’s
5. In BDC’s we can write Coding is Very
5. In LSMW we can’t write coding in Flexibly.
flexible.
6. In BDC the flat file is either .TXT file or
6. In LSMW the flat file must be .TXT file.
Excel sheet.
7. LSMW is only possible for standard transaction
7. BDC is possible for any transaction code.
code.

COMMIT WORK COMMIT WORK AND WAIT

(ASYNCHRONOUS UPDATE) (SYNCHRONOUS UPDATE)
1. In this type the call transaction screens 1. In this mode, the called transaction
will communicate with the update work communicates with the update work
process to update the data into process to update the data into
database. database.
2. It doesn’t wait for the update to be 2. It will wait for the update to be finished.
finished.
3. It immediately starts to process the 3. Once the update is finished, then it
next record without waiting for the continues to process the next record.
update to be finished.
4. That’s why this process is very fast. 4. That’s why this process is very slow.
5. It is generally not recommended for the 5. It is generally recommended for large
large amount of data, because the amount of data because it returns
called transaction doesn’t return any success and error messages.
success or error messages.
 Client Dependent Table Client Independent Table
I. If the first field is MANDT, then it is I. If the first field is not MANDT, then it
called as client dependent table. is called Client Independent Table.
II. This table stores data in specific client II. Data is stored in all Clients without
only Security.

CLASSICAL REPORTS INTERACTIVE REPORTS ALV REPORTS

 It is nothing but entire  It is nothing but  ALV reports are used to
information in the summarized display the output with Pre
single list. information in the basic defined functionalities.
list and detailed
information in the next
list.
 It is having only one  It having one primary list  These are two types: list
screens for the and 20 secondary list for and grid.
output. It has not any the outputs.
sub list.

Report Program Module Pool Program

1. Reports are stand-alone programs. 1. MPP are not stand-alone programs (We
have to link the dialogue programs to at
least one or more SCREENS &
TRANSACTION CODES).
2. We use reports to read database 2. We use MPP to read & change
tables & represent results in lists. Database tables.
3. Reports are collection of processing 3. MPP are controlled by Screen flow
blocks, controlled by system calls logic.
depending on events.
4. Reports can use LDBs or SELECT 4. MPP is also called as Dialogue program
STATEMENTS or TRANSACTION.
5. Reports can call Dialogue Programs 5. These module pools are separated in to
and vice versa. PBO and PAI events.
 List Display Grid Display
1. List display does not support OOPS ALV. 1. Grid display supports OOPS ALV.
2. Blocked and hierarchical ALV are possible 2. Blocked and hierarchical ALV are not
in list display. possible in grid display.
3. ALV, list it consumes more memory on 3. ALV grid uses Active x controls present on
the presentation server. presentation server.
4. List display is faster. 4. Grid display is the slower.
5. Edit and logo is not possible in list display. 5. Edit and logo is possible in grid display.
6. In list display [i] indicates number of 6. In the output [i] symbol indicates F1 help.
records is displayed.
7. Either by using write or commentary 7. By using ‘commentary write’ function
writes function module we can print the module only we can print the text on top or
text on top or bottom event. bottom event.
8. This is used to display the output in list 8. This is used to display the output in grid
format. format.

FUNCTION MODULE SUBROUTINE

1. Function Module can handle errors 1. Subroutine cannot handle errors.
through exceptions.
2. Function Module can be tested 2. Subroutine cannot be tested
independently. independently.
3. Function Module returns the 3. Subroutine may or may not returns the SY –
SY – SUBRC value. SUBRC value.
4. Function Module globally called 4. Subroutine always called before definition
anywhere in the ABAP programs. of the subroutine.
5. Function Module can be remote enabled. 5. Subroutine cannot be remote enabled.
6. In function module documentation is 6. Documentation is not possible in case of
possible. subroutine.
7. Function modules are defined in function 7. Subroutines are defined in ABAP-Editor.
builder SE37.
 User Exits Customer Exits

1) It is implemented for specific programs,

1) It is implemented in the form of
screens, and menu within standard
subroutine
applications

2) It is technically a modification as existing 2) It is technically an enhancement as this

code are changed provides add-on functionality

3) It refers to all modules like MM, SD, FICO,

3) It refers to SD module only
PP etc.

4) Only variables, structures, and tables that

4) All variables, structures, internal tables,
are passed into the function through the
etc. are exposed to be viewed and/or
interface are restricted to be viewed
changed
and/or changed

5) It requires an access key 5) It does not require any access key

6) Changes remain after the upgrade 6) Changes are lost after upgrade

7) It gets automatically activated whenever 7) To implement this, a project is created in

the application/program is activated CMOD then activated

8) User exits are created with SAP 8) Customer Exits are created by Custom
namespace only. namespace.
 COMMIT WORK ROLLBACK

COMMIT validates the modifications made by the ROLLBACK erases the modifications made by
current transaction. the current transaction.

Once ROLLBACK is executed database reaches

After execution of COMMIT statement, the
its previous state, i.e. before the execution of
transaction cannot be ROLLBACK.
the first statement of the transaction.

COMMIT occurs when the transaction gets ROLLBACK occurs when the transaction is
executed successfully. aborted in middle of the execution.

Report Program Module Pool Program

1. Reports are stand-alone programs. 1. MPP are not stand-alone programs (We
have to link the dialogue programs to at
least one or more SCREENS &
TRANSACTION CODES).
2. We use reports to read database tables & 2. We use MPP to read & change Database
represent results in lists. tables.
3. Reports are collection of processing 3. MPP are controlled by Screen flow logic.
blocks, controlled by system calls
depending on events.
4. Reports can use LDBs or SELECT 4. MPP is also called as Dialogue program or
STATEMENTS TRANSACTION.
5. Reports can call Dialogue Programs and 5. These module pools are separated in to
vice versa. PBO and PAI events.
 BDC Session Method BDC Call transaction Method
1. In Session method the processing of records 1. In Call transaction method the processing of
in Asynchronous. records in Synchronous.
2. Updating the records in Asynchronous 2. Updating the records in both Asynchronous
process. and Synchronous process.
3. In Session method ERROR log will be 3. In Call transaction method ERROR log will be
generated by System handled by Users.
4. Call transaction method does not
4. If we want to process huge volume of Data,
recommended to process Huge Volume of
prefer to go for Session method
Data.
5. Session method does not support to process 5. Call transaction method support to process for
for multiple transactions. Multiple transactions.
6. Session method can process any number 6. Call transaction method can process only one
of transactions at a time. transaction at a time.
7. This method is slower. 7. This method is fast.
8. In this method after processing the
session through SM35 only data base is 8. This is immediate data base updation.
updated.
9. Background scheduling is possible in this 9. Background scheduling isn’t possible in this
session. method.
10. It can’t return the SY-SUBRC value. 10. It returns the SY-SUBRC value.
 BDC BAPI
1. BDC is nothing but a Data Conversion
1. BAPI is nothing but an Interface method.
method.
2. BDC’s communicate the Data between 2. BAPI’s communicate the Data between SAP
Legacy to SAP system through screens. to SAP as well as Non-SAP systems directly.
3. BDC’s are Prefer to Use Communicate the
3. BAPI’s are Prefer to use Communicate the
Master Data.
Transactional Data.
ex: Material master, Customer Master, Vendor
Ex: Sales orders, Purchase orders etc.
master.
4. interface is used to communicate data
4. Data Conversion is a one-time activity.
between two systems continuously.
5. BDC is slower. 5. BAPI is faster.
6. Some times BDC_OPEN_GROUP, 6. BAPI never cause to terminate the program
BDC_INSERT, BDC_CLOSE_GROUP may cause to when ever error occur in the BAPI it simply
terminates the program. written those errors through written parameters.
7. In BDC we provide the authority check to
validate the user. 7. BAPI perform their own authorization checks
Authority – check <object name> id <name> to validate the user.
action <value>.
8. In BDC the flat files fields are fixed. 8. In the BAPI the flat file fields are varying.
9. When ever the version is changed some 9. When ever the version is changed we no need
times we need to change the code. to change the code.

ENHANCEMENTS MODIFICATIONS
1. Enhancements are provided by SAP. 1. Modifications does not provided by SAP.
2.In Enhancements, system does not ask any 2. In Modifications, system asks object access
object access key. key.
3. In Modification, SAP does not provide any
3.In Enhancements, SAP provides some options
options and directly go to the program and ADD
for Enhance to the standard logic.
or change the Standard logic.
3.Enhancement options are provided by SAP
3. Modifications does not support future up
and supports future up gradation of SAP
gradation of SAP software.
software.
4.In Enhancements we can easily identify the 4. In Modifications we can’t identify Impact of
Impact of changes. changes and only identify proper changes.
 CUSTOMER EXITS BADI’s
1. Customer exits are Old and Pure
1. BADI is an Interface.
enhancement technique.
2. Customer exits are available only in SAP level 2. BADI’s are available in Customer level,
and Customer Level. Company code level and Partner level.
3. Customer exit doesn’t support multiple
implementations. Implement in only one 3. BADI’s Supports multiple implementations
project
4. We can’t possible to create Custom
4. We can possible to create a Custom BADI’s.
Customer exits.
5. In Customer exits we can Implement the 5. In BADI’s we can Implement the Logic within
Logic within the Function modules exit. the Class
6. Customer exit is the procedural approach. 6. BADIs are object-oriented approach. So, it
So, it takes some extra time to enhancing. takes very less time to enhancing.
7. In the screen exit the screen number is fixed 7. In the screen BADI we provide our own screen
which is provide by SAP. number.
8. By using CMOD transaction we can 8. By using SE19 transaction we can implement
implement the customer exit. the BADI.

DATA BASE TABLE INTERNAL TABLE

1) Data base tables are permanent storage 1) Internal tables are temporary storage
location. location.
2) We can access the data base table from 2) We can access the internal table with in the
anywhere in SAP. program only.
3) We must provide the size of the data base 3) Internal tables are dynamic. So, we no need
tables. to provide the size.
 AT NEW ON CHANGE OF
1) AT NEW work within the loop of 1) ON CHANGE OF work within the any loop.
internal table.
2) The right-side fields of the mentioned 2) The right-side field values of mention fields
field values display as stars if it’s a never change.
character data type & display ‘0’s if it’s
numeric data type.
3) In the AT NEW we can’t use the logical 3) We can use logical operations.
operations (and, or, not)
4) This is used in ABAP objects. 4) This isn’t used in ABAP objects.

PARAMETER SELECT-OPTIONS
1) Parameter is the keyword which accepts 1) Select-options is the keyword which
the single value at run time. accept the single value, multiple single
values, single range & multiple ranges.
2) Without provide input parameter we 2) Without providing input select-options
can’t get data. we can get the entire data from
database.

SELECT SINGLE SELECT UP TO 1 ROWS

1) It fetches the only one record. 1) It also fetches only one record.
2) Here we must pass entire primary 2) Enough to pass part of key combination in
key combination in where condition. the where condition it always pick the first
record among the method once.
3) It hits the data base only once. 3) It hit the data base twice.
4) This is used to fetch the exact record. 4) This is used for validation.
 EXECUTABLE PROGRAM MODULE POOL PROGRAM
1) We can execute the executable program 1) We execute the module pool program only
either through transaction code or through transaction.
directly.
2) Type of the executable program is ‘1’. 2) Type of the module pool program is ‘M’.
3) All the standard reports are executable 3) All the standard transactions are module
programs. pool programs.
Ex: - ME2L, ME2K, ME2M Ex: - XK01, XD01

CALL SCREEN SET SCREEN

It calls the new screen in the new screen, if the It calls the new screen. The new screen acts like
user clicks on back button, then it come back to an indusial screen. If the user clicks on back
previous screen. button in the new screen, then it never come
back to previous screen.

MAIN WINDOW VARIABLE WINDOW

1) It’s used to print the continuous data. 1) Based on the window width & height only
we can print the data.
2) We can split the main window into 2) We can’t split the variable window.
smaller windows.
3) Without a main window we can’t design 3) Without a variable window we can design
SAP-SCRIPT. SAP-SCRIPT. We can create only variable
window.
4) Top & Bottom control commands only 4) Top & Bottom aren’t work in variable
work in main window. window.
5) Next page = 0 isn’t possible in main 5) Next page = 0 is possible in variable
window. window.
6) We must provide the text element name 6) We no need to provide the text element
to the main window. Otherwise, the first name in the variable window.
information will be printed twice.
 STATIC BREAK POINT DYNAMIC BREAK POINT
1) Static break points are placed by using 1) Dynamic break points are placed by using
BREAK-POINTS keyword. [Stop] button in the application tool bar.
2) Static break points aren’t a user specific. 2) Dynamic break points are user specific.
That means any user can execute the
program. Then the cursor stops at break
point keyword. (By using conditions, we
can set the static break points are user
specific).
3) In any version at the program 3) In an activate version of the program only
(Active/Inactive), we place static break we can place the dynamic break point.
point.

CLASSIC DEBUGGER NEW DEBUGGER

1) In this we have no desktops. 1) In this we have desktop1, desktop2,
desktop3 & standard.
2) By using this we can’t debug object- 2) By using this we can debug the object-
oriented program. oriented programs.
3) In this we can’t compare any two field 3) In this we can compare any two field
values. values.
4) In this it won’t show global & local 4) In this it provides the global & local
variables of the program. variables of the program.