Documents 3357-ABAP+NOTES

ABAP - ADVANCED BUSINESS APPLICATION PROGRAMMING LANGUAGE.
It is 4th generation language and it is a proprietary language of SAP.
TRANSACTION CODE :- It is flow of screens. Every screen is called a session.

Maximum number of sessions allowed 6.It is also called T-Code. In short we can say that
it is a short form or short cut key to execute a program.
ABAP is not case sensitive. We can use upper case or lower case or combination
also. But is space sensitive. All user defined object names in SAP should start with either
‘Z’ or ‘Y’. If we don’t start object name with either ‘Z’ or ‘Y’ it will ask for access key.
Hence we can say that as a user we don’t have the access to create an object name
without starting with ‘Z’ or ―Y’.
All statements in ABAP should be terminated with a period (full stop or dot). There
are 5 types of programs available in ABAP. They are….
1) Executable Program
2) Function Group
3) Modulepool Program
4) Include Program
5) Subroutinepool Program.
To create all these programs T-Code is SE38. It is also called ABAP Editor.
EXECUTABLE PROGRAM:- A program which takes input from the user and gives
output is called Executable Program or Report Program. Input screen of report program is
called SELECTION-SCREEN. Output screen of report program is called LIST. By
default for every report program Selection-screen number will be 1000.
Whenever you login into SAP first screen you get is called SAP Easy access
screen. In that screen top one is called Menu bar. After that we have standard Tool bar
and after Application tool bar. On Standard tool bar we have command filed where we
enter Transaction code.
ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 1

If you want to create any of the above 5 types of programs, in command prompt
type SE38 T-Code and press enter. You will go to ABAP Editor screen. There you enter a
program name starting with either ‘Z’ or ‘Y’. For example just say ZSAMPLE. After
entering the program name press create button. Immediately you will get next screen
where you have to enter title. Title is the meaningful description to the program. That is
what is the purpose for which you are writing the program.

Hence in the title you enter some meaningful description. Let us say MY FIRST
PROGRAM. Then in type you have to choose Executable program because right now we
want to create Executable Program. Then press save button. Immediately you get another
screen where you have to actually enter Package. But later we discuss about package.
Time being press Local object button. Immediately you enter into next screen where you
can write the program.

First line will be given by system. You start writing the program from second line
onwards. As I said before you have to remember that every line should be terminated
with a period. First we start writing a simple program.

In ABAP Write is an output statement. If you want to write something in the
output you have to use write statement. When ever write statement is used remember that
hard coded value or text you want to display should be in single codes. Here is first
sample program which displays hello in the output.

After writing the program we usually check the errors. Ctrl+F2 is used to check
the errors. You can also use the button shown below.

After checking the errors we activate the program. Activation gives runtime
object. Ctrl+F3 is used to activate the program. You also use the button shown below.

After activating the program you will get next screen where your program is
automatically selected by the system. There you simply press enter or tick mark button
present at the left hand corner of the screen. Now your program becomes active.

Now you can execute the program. F8 is used to execute the program. You can
also use the button shown in the bottom picture.

You will get the following output.

This screen is called list. Here in this program we are not giving any input. Hence
there is no selection-screen. The program what we have written is…..
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
WRITE 'HELLO'.
Let us assume that I have written the following program.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
WRITE 'HELLO'.
WRITE 'HAI'.

You will get following output.
In this output we are getting HELLO and HAI in the same line. But my
requirement is that I should HAI in the next line. For that we have to use new line
character ‘/’. In ABAP / is called new line character.
The modified program is like this.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
WRITE 'HELLO'.
WRITE / 'HAI'.
The output will be.

In the above program what we have two write statements simultaneously.
Unnecessarily we are increasing the code. When ever we are using two similar statements
simultaneously my requirement is use the statement only once and get the required out
what we got earlier. That is I want to combine two similar statements writing
simultaneously. For combination of statements use : (column) after the statement
and at the end of the line use , (comma). Comma symbolizes continuation of
statement and dot symbolizes termination of statement. The same syntax has to be
followed when ever you want to combine different similar statements.
The above program can be written like this with combination of statements.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
WRITE: 'HELLO',
/ 'HAI'.

Now we try to input data into program. In C language if we want to input data
into program we use the key word scanf. Similarly here in ABAP also we are having a
key word called PARAMETERS.
PARAMETERS: - It is a keyword used to declare a variable of particular type which

allows the user to input the data at runtime using keyboard.
The syntax is ……
PARAMETERS A TYPE I.
Here A is a variable name. I stands for integer type variable. That means A is a
variable that is going to hold integer type variable. When ever integer type variable is
declared system automatically allocates 14 digits memory.
Screen shot of the program is as follows.
When you execute the program you will get the selection –screen. The screen shot
is as follows.

After entering data into that screen any numeric value (say 123) you press F8 or
execute button present on the application tool bar of the screen. You will get the list like
this.

The program written is as follows.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS A TYPE I.
WRITE: / 'ENTERED NUMBER IS',A.
One more important thing you have to remember in this write statement is that the
hard coded text (i.e. ENTERED NUMBER IS) should be in codes and the declared
variable (i.e.A) should not be in codes. That you have to keep in mind.
Let us see how we can declare character type data. For declaring character type
data we have to use C.

Syntax is ……
PARAMETERS A TYPE C.
C stands for character type variable. When ever character type variable is
declared system allocates single character memory. If many characters are needed to be
given as input specify the length.
Syntax is ……
PARAMETERS A(10) TYPE C.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS A(10) TYPE C.
WRITE: / 'ENTERED STRING IS', A.
In this case we can input 10 characters at a time.
In character type variables the input given is automatically converted to Upper

case. To avoid this use lower case key word.
Syntax is………..
PARAMETERS A(10) TYPE C LOWER CASE.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS A(10) TYPE C LOWER CASE.
In other programming languages if data type is not mentioned system gives error.
But in ABAP if no data type is mentioned system allows you input character type data.
That means if no data type is mentioned the default data type assigned is Character type
data.

*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS A(10).
And one more important to remember is character type data in ABAP can also
hold numeric values and we can do all mathematical operations with those variables.
Now we look into a simple program to add two numbers.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS: A TYPE I,
B TYPE I.
DATA C TYPE I.
C = A + B.
WRITE: / 'THE SUM OF TWO NUMBERS IS', C.
In the above program I have used one more keyword DATA to declare the
variable.
DATA:- It is a keyword used to declare a variable of particular type which allows the
user to pass the variables that are generated by system at run time. But user is not allowed
to input the data using key board.
If PARAMETERS keyword is used to declare the variable, the values to that

variable can be given at run time using key board. But if DATA keyword is used to
declare the variable for that variable we can not give the values using keyboard. But we
can pass the values that are generated by system at runtime. In the above program I have
passed (A+B) value into C variable.
If you see the selection-screen of above program it will be like this.

You can clearly see that only A and B variable are present on the selection screen
and C variable is not present there. Because I have used Parameters keyword to declare
A and B variables and Data keyword to declare C variable.
You can clearly see on the selection-screen that what ever variables that I have
declared in the program using Parameters keyword are coming directly on selection-
screen. But in real time developer develops the program end user will use the application
or program. If variables names are directly coming on the selection-screen, the end user
will not be knowing what to enter there. So I want to have meaningful description to the
selection-screen fields. This is done using selection-texts.
SELECTION-TEXT: Selection-text is a text used to give meaningful identity to

selection-screen fields.
Navigation is GOTO ----> TEXT ELEMENTS --- > SELECTION TEXTS.

After clicking the Selection texts you will get the following screen where you can
enter the text that is needed to be printed on the selection-screen instead of variable
names.

You can enter text in any case. Here text case will not be changed. What ever you
enter that will come in the output. After entering the text just activate the screen by
pressing activate button.
Come back to the program by pressing back button or F3 and execute the
program. Now selection-screen looks like this.

COMMENTING A LINE
When ever a line is commented in any programming language, the line will not be
checked for errors and that line will not be executed while execution.
If you want to comment whole line you have to keep * (start) in the first position
or first column of the line. If you want to comment from particular position of a line you
have to use “(double quotes) and write the comment. You see the syntax present in the
bottom.
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
* THIS IS THE COMMENTED LINE.
WRITE / 'RAMESH'. " THIS STATEMENT IS USED TO DISPLAY RAMESH IN OUTPUT

MOVING TO ANOTHER TRANSACTION
If your control is present in the easy access screen and if it is needed to move to a
transaction we directly type transaction code in command field and press enter to move to
the transaction. If your control is not present in the easy access screen (let us say if it is
present in ABAP editor screen) and if it is needed to go to another transaction , if we
directly type transaction code in the command field system will prompt you saying
Function code xyz is not supported. Actually that Transaction code exits in SAP. To
solve this or over come this we have to either use /n or /o before the T-code.
/n -- Terminates present T-code and opens a new T-code.

/o -- Without terminating the present T-code opens a new T-code.
/nex -- It is used to close all the sessions at a time and to logout. But the problem
with this is unsaved data will be lost.

SYSTEM VARIABLES
1. sy-datum -- Date
2. sy-uzeit -- Time
3. sy-mandt -- Logon client number
4. sy-uname -- Logon user name
5. sy-repid -- Report program name
6. sy-cprog -- Current program name
7. sy-dynnr -- Screen number
8. sy-tcode -- Transaction code
9. sy-pagno -- Page number
Sample program with these system variable is…….

*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& SYSTEM VARIABLES *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
write / sy-datum.
write / sy-uzeit.
write / sy-uname.
write / sy-repid.
write / sy-cprog.
write / sy-mandt.
write / sy-dynnr.
write / sy-pagno.
Write / sy-tcode.
CONTROL STATEMENTS
Control statements are nothing but loops. The property of the loop is to rotate by
it self until loop is terminated. There are 4 types of control statements in SAP. They are
1. DO.
………..
………..
ENDDO.
2. DO N TIMES.
………..
………..
ENDDO.
3. WHILE <CONDITION>.
………..
………..
ENDWHILE.
4. CASE <VARIABLE>.
WHEN <VALUE1>.
………..
………..
WHEN <VALUE2>.
………..
…………
WHEN OTHERS.
………..
…………
ENDCASE.

Exit statement is used to terminate the loop. SY-INDEX is a system variable
which gives present loop iteration number. These both things we use in coming program
to see how they act in the loop.
DO LOOP SAMPLE PROGRAM
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
DO.
WRITE / SY-INDEX.
IF SY-INDEX EQ 10.
EXIT.
ENDIF.
ENDDO.
In this program the control comes out of the program when sy-index value
becomes 11. That means at 11th iteration the control comes out of the loop.
For aligning the program lines use PRETTY PRINTER button present on the
application tool bar of the ABAP editor.
Good I have written the above program and I will get the following output and I
am happy.

But my requirement is to see how the variable’s values are changing while
execution of the program. This technique is called Debugging. To see how control is
moving while execution of a program we have to stop the control at some point or at
some line in the program. That point is called Break Point.
DEBUGGING:- It is a technique to see how control is moving while execution of a

program.
BREAK POINT:- It is a line in the program where control is needed to be stopped

while execution.
To keep the break point in the program at particular line, keep the cursor on that
particular line and press STOP button. That line immediately turns to yellow color and
at the status bar you will get a message saying that Breakpoint set. When you execute the
program the control goes to that particular line and program execution is stopped there.
To execute the program further you have to use the following keys.
F5 --- > FOR LINE BY LINE EXECUTION.

F6 --- > TO COME OUT OF LOOP.
F7 --- > TO COME OUT OF FUNCTION MODULE.

F8 --- > TO GOTO NEXT BREAK POINT IF EXISTS OR TO EXECUTE THE
PROGRAM COMPLETELY.
Maximum number of break points allowed are 30. Sap has given option to
keep these many break points to easily debug a program which is having many lines.
When you execute the program in debugging mode the screen will be in this format.

What ever the fields value you want to find out while execution you double click
on the filed name. Immediately field name comes under Field names and value comes
under Field contents. Otherwise you can also type the Filed name under Field names and
press enter.
If you want to delete the break point that is set, keep cursor on the line where
break point is set and once again press STOP button. The break point will be deleted.
One more thing you have to remember is break points can be set in a program if program
is active. That means we can not keep break point in a program if program is inactive.
The break points that are set using Stop button are automatically deleted when you
logout. You cannot see those break points once you login.
If you want to keep permanent break points use keyword BREAK-POINT. This
keyword is used to keep permanent break points. Where you want to stop the control
before that line use this break-point key word.
Sometimes a requirement may come to set the break point for a particular user. In
that case BREAK <USER NAME> key board. Let us assume that you have logged in
with sapuser and if you want to set break point to that particular use only then syntax will
be …….
BREAK SAPUSER.

If you execute the program in that sapuser only the program goes to debug mode.
If you execute the program in others the program will be executed in normal mode.
From now onwards what ever the program you write you try to execute the
program in debug mode. So that you will understand the program well.
One more thing you have to remember is that whenever do loop is used it is
mandatory to use Exit statement. Other wise the program will be in infinite loop and you
never get the output.
MATHEMATICAL OPERATORS RELEVENT SAP OPERATORS
= EQ
< LT
> GT
<= LE
>= GE
<> NE
We can also use mathematical operators or relevant sap operators in

ABAP programming. But SAP is recommending you to use relevant SAP operators only.
If you see SAP standard programs they have also used all relevant SAP operators.
DO N TIMES SAMPLE PROGRAM
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
DO 10 TIMES.
WRITE / SY-INDEX.
ENDDO.
The output of this program will also be the same as above i.e. 1 to 10. In Do n
times loop there is need to use Exit statement because the loop will be rotated for those
many times and then the control comes out of the loop.

WHILE LOOP SAMPLE PROGRAM
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
WHILE SY-INDEX LE 10.

WRITE / SY-INDEX.
ENDWHILE.
The output of this program is also same as above two programs i.e. 1 to 10.
Now we discuss about the differences between DO loop and WHILE loop a
famous question in C language.
In Do loop we enter into the loop and check the condition, but in While loop first we
check the condition then only we enter in to the loop.
Minimum number of number of times Do loop executed is one time, but while loop
minimum number of times executed is Zero. If condition is wrong the control will
not enter into the loop.
CASE STATEMENT SAMPLE PROGRAM
*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS Z.
CASE Z.
WHEN 'A'.
WRITE / 'YOU ENTERED A'.
WHEN 'B'.
WRITE 'YOU ENTERED B'.
WHEN OTHERS.
WRITE 'YOU ENTERED OTHER ALPHABIT'.
ENDCASE.
If A is given as input to this program we get YOU ENTERED A as out. If B is

given as input we get YOU ENTERED B AS OUTPUT. If other than A or B is given as
input we get YOU ENTERED OTHER ALPHABIT as output.
Now my question is if you write the following program…..

*&---------------------------------------------------------------------*
*& Report ZSAMPLE *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZSAMPLE .
PARAMETERS Z.
CASE Z.
WHEN 'a'.
WRITE / 'YOU ENTERED A'.
WHEN 'B'.
WRITE 'YOU ENTERED B'.
WHEN OTHERS.
WRITE 'YOU ENTERED OTHER ALPHABIT'.
ENDCASE.
Here in this program in when condition ‘A’ is changed to ’a’. What will be the out
if enter a in the selection-screen. Think it and read the following lines.
The output will be YOU ENTERED OTHER ALPHABIT. But why? Because
the input characters in the selection-screen are automatically converted to upper case.
This we have discussed earlier. This is the property of selection-screen. Here my
intension is to specify that what ever you give in the case statement in when condition,
give with in quotes only upper case letters. Other wise you get abnormal results. That you
have to remember it. You can try this thing.
LOOP TERMINATING STATEMENTS
EXIT
STOP
CONTINUE
CHECK
1. EXIT :- We have already discussed about it. Exit statement is used to terminate
the loop. The statements after the loop will be executed normally. Let us analyse
the following program.
*&---------------------------------------------------------------------*
*& Report ZLOOPS *
*& *
*&---------------------------------------------------------------------*
*& *
*& *
*&---------------------------------------------------------------------*
REPORT ZLOOPS .
do.
write / sy-index.
if sy-index eq 10.
exit.
endif.
enddo.
write / 'HELLO'.

The output of the above program will be …..
When sy-index becomes 11 the loop will be terminated and we are having a write
statement after the loop. That will be executed normally. That is the reason why we
are getting HELLO in the output along with the numbers.
2. STOP:- Whenever stop statement is used in the program, immediately after the
execution of the STOP statement the whole program will be terminated. That
means no statement after execution of STOP will be executed. STOP statement
completely terminates the program.
Try to analyze the following program.
REPORT ZLOOPS .
do.
write / sy-index.
if sy-index eq 10.
stop.
endif.
enddo.
write / 'HELLO'.
The output of this program will be …..

You can see that the write statement which we have written the after the
loop is not executed. That is the reason why we are not getting HELLO in the
output. When system enters in to if statement when sy-index becomes 10, system
executes STOP statement which immediately terminates whole program. STOP
can be used out side the loop also. Remember no statement after execution of
STOP will be executed.
3. CONTINUE:- This statement terminates present loop iteration and goes to

next loop iteration. Analyze this program.
REPORT ZLOOPS .
do.
if sy-index eq 2.
continue.
endif.
write / sy-index.
if sy-index eq 10.
exit.
endif.
enddo.
The output of this program will be ……..

You can clearly see that there is no 2 in the output. Because in the program I have
written the logic that the system should execute continue statement when sy-index
becomes 2. The write statement is written after if statement containing continue
statement. That is the reason write statement is not executed when sy-index is 2 and it is
not printed in the output. You debug this program then you understand it better.
3. CHECK:- This statement returns true or false. If check returns true the
statements after it will be executed. If it returns false the statements after it will
not be executed. Even though check returns false value the loop will be continued.
Analyze this following example.
REPORT ZLOOPS .
do.
write / sy-index.
if sy-index eq 10.
exit.
endif.
check sy-index eq 2.
write / sy-index.
enddo.
The output of this program will be ……..

2 is printed two times. Check condition in this program returns true value when
sy-index becomes 2. Then only the write statement written after the check will be
executed.
Let us assume that the CHECK statement is written outside the loop and it is
writtening false value. Then all the statements written after it will not be executed. That
means it acts like STOP. That is If CHECK is written outside the loop and if it
returns false value it acts like STOP.
STRING OPERATIONS
TRANSLATE:- This keyword is used to convert character type variables from one case
to another case.
Syntax is …….
TRANSLATE <VARIABLE NAME> TO LOWER CASE/UPPER CASE.
Sample program is ………..

REPORT ZLOOPS .
PARAMETERS A(10).
TRANSLATE A TO LOWER CASE.
If RAMESH is given as input to this program output will be ramesh. You can
also use upper case key word with translate. But there is no use because what ever we
give in selection-screen will be automatically converted to upper case by default.
STRING LENGTH:- STRLEN keyword is used to find out string length.
Syntax is….. STRLEN( VARIABLE NAME ).
Sample program is……..
REPORT ZLOOPS .
parameters: a(20).
data len type i.
len = strlen( a ).
write len.
If I give RAMESH as input to this program I will get 6 as output, because

RAMESH string is containing 6 characters.
CONCATENATION OF STRINGS:- CONCATENATE key word id used to

concatenate strings into a single string.
Syntax is ….. CONCATENATE <STRING1> <STRING2> INTO <STRING3>

SEPARATED BY SPACE/<’CHARACTER’>.
Sample program is …..
REPORT ZLOOPS .
parameters: a(10),
b(10).
data c(20).
concatenate a b into c.
write c.
If I give input RAMESH for A and REDDY for B I get output as

RAMESHREDDY. Let us assume that I want space between two strings, i.e. space
between RAMESH and REDDY I should write program like this.
REPORT ZLOOPS .
parameters: a(10),
b(10).
data c(20).
concatenate a b into c separated by space.
write c.

If I give input RAMESH for A and REDDY for B I get output as
RAMESH REDDY. Space will come between the strings. If I want , between the strings
I should use following line in the program instead of concatenate line present in the
above program.
concatenate a b into c separated by ‘,’.
If I use this line in the program I will get comma between the strings.
When ever we are giving space in the concatenate syntax it should not be in the
quotes, because space is a key word. If any other character is required between the
strings other than space that character should be given in the quotes.
SPLITTING A STRING:- Let us assume that I require to split a string at a particular

character. Let us say that I want to split a string at comma (,). For this I have to use
SPLIT keyword. Syntax is ….
SPLIT <STRING> AT <‘CHARACTER’> INTO <STRING1>

<STRING2>…….<STRINGN>.
Sample program is ……
REPORT ZLOOPS .
parameters: a(20).
data: b(10),
c(10).
split a at ',' into b c.
write : / b,
/ c.
If to the above program if I give input as RAMESH,REDDY. It will be splitted

into 2 variables B and C. In to B it will push RAMESH and into C it will push REDDY.
In to the above program if give input as INDIA,USA,UK,AUS. Till INDIA it will be
moved to B and USA,UK,AUS will be moved to C variable. That means when ever we
say that particular string should be splitted into N number of variables, the system will
search for (N-1) commas and accordingly it will split the string.
REPLACING A CHARACTER WITH SOME OTHER CHARACTER:- For this

purpose we have to use REPLACE keyword. The syntax is as follows…..
REPLACE <’CHARACTER’> WITH <’CHARACTER1’> INTO <STRING>.
Sample program can be seen below. This program is used to replace all characters
present in a string A with space.

REPORT ZLOOPS .
parameters: a(20).
do.
if a ca ','.
replace ',' with space into a.
else.
exit.
endif.
enddo.
write a.
Here in the above program we used a keyword CA which means contains any.
You can debug the program you will understand better about the logic.
If you want to see documentation for any keyword present in ABAP just type the
keyword in ABAP editor and keep cursor on the keyword and press F1. It will open
beautiful documentation regarding the keyword.
OFFSETTING:- It is a mechanism used to move the control to particular position of a

string. That means let us assume that I want 3rd character form the string. Then I can go
for offsetting. The system interprets string positions as below.
R A M E S H
0 1 2 3 4 5
Instead of starting from 1 system gives the positions from 0. That means if I want
3 character physically I should search for the 2nd character as per system representation.
rd
The syntax for offsetting is ……
<DESTINATION STRING > = <SOURCE STRING>+<SYTEM REP CHAR

POSITION><(NO OF CHARS REQUIRED)>.
Here + is called offsetting mechanism. The difference between mathematical operate +

and this offsetting mechanism + is that, when ever we use mathematical operator + we
give space before and after the + but in this offsetting mechanism + the is no space before
and after the +. That is the difference.
Consider the following example. I give the input as RAMESH into variable A. I
want to move 3rd character from this variable into B variable.Then
A = RAMESH
B = A+2(1).
Then M will be move to B.
If I want 3rd and 4th characters into B, Then I have to change above statement as ….
B = A+2(2). Both ME will be moved into B.

If I want to move all character from third position ( I am talking about physical positions)
into B, Then I have to say..
B = a+2. Don’t give any thing in brackets.
If I want entire string into B, I have to say…
B = A+0. whole RAMESH will be moved into B.
Execute the following program and analyze the things.
REPORT ZLOOPS .
parameters: a(20).
data b(20).
b = a+2(1).
write b.
LOGIC FOR FINDING THE LAST CHARACTER OF A STRING.
REPORT ZLOOPS .
parameters: a(20).
data len type i.
data b.
len = strlen( a ).
len = len - 1.
b = a+len.
write b.
SY-FDPOS:- It is a system variable used to find the position where the search is
successful. Let us assume that you are searching for a comma in a string and you want to
find out the position where comma is present in the string. Then we can use this system
variable. But it acts abnormally. If string is not containing the particular character for
which you are searching sy-fdpos system variable takes the declared length of a
string which you are searching.
You can execute the following program and see the results.
REPORT ZLOOPS .
parameters: a(30).
if a ca ','.
write sy-fdpos.
else.
write sy-fdpos.
endif.

TYPES OF DATA IN SAP
There are three types of data in SAP.
1. Customized data
2. Master data
3. Transactional data.
CUSTOMIZED DATA:- The data which never changes is called Customised data. This
data is not created but configured by functional consultant using SPRO tranction.
MASTER DATA: The data which changes very rarely is called Master data.
TRANSACTIONAL DATA:- The data which changes very frequently is called

Transactional data.
TYPES OF TABLES
There are three types of tables.

1. Transparent Tables
2. Clustered Tables
3. Pooled Tables.
TRANSPARENT TABLES:- For every table created in Data dictionary (DDIC) there
will be table created in database with same name, same no of fields, fields having same
names and the order of the fields will be same. That means for every same replica of table
or mirror image will be created in Data base. That means it is having one to one relation.
By default every table created will be Transparent Table.
CLUSTERED TABLES:- Many tables created in DDIC are stored in single table in data
base called table cluster. That means it is having many to one relation. All the tables
present in table cluster will have primary key in common.
POOLED TABLES:- In case also many tables created in DDIC are stored in single
table in database called table pool. Hence it also having many to one relation. Here the
tables present in table pool many have primary key in common.
SE11 T-Code is used to create data base objects which includes tables.
A table can be client dependent or client independent. Table data only client dependent or
client independent, but table structure is client independent.
CLIENT:- Client is SAP specific which contains it’s own master data and it’s own set of
records. All SE38 programs are client independent programs. That means if a program is
written in one client it can be seen all the clients present in the system.

To see all the clients present in a system T-code is SCC4.
If first field of the table is MANDT the table becomes client dependent table,
otherwise it becomes client independent table. If the table is client dependent table the
data that you enter in one client can not be seen in other clients. If the table is client
independent table the data that is entered in one client can be seen all other clients. That
means if the table is client independent all table in all clients contain same data.
Every table should have at least one primary key or foreign key. All primary key
fields and foreign key fields of a table should be declared first.
Every table field should have DATA ELEMENT and DOMAIN.
DATA ELEMENT:- It gives semantic attributes of table field.

Eg:- Short description of table field.
DOMAIN:- It gives technical attributes of the table fields. Domain is the more reusable
component than data element.
Eg:- Type of data it is going to hold.
DATA BROWSERS
These are set of Transaction codes used to main data base objects. The T-codes are.
SE11
SE12
SE16
SE17
SM30
SE54
All these T-codes are used to maintain data base objects. But some of the options
may be present in one T-code and some of the options may not be present in other T-
codes. You can use any of them.
All report programs are stored in TRDIR table. All tables are stored in
DD02L Table. It is table of tables.
SOME IMPORTANT STANDARD TABLES IN SAP
1. MARA MATERIAL MASTER TABLE

2. MARC MATERIAL PLANT
3. MAKT MATERIAL DESCRIPTION
4. MARD MATERIAL STORAGE LOCATION
5. KNA1 CUSTOMER MASTER TABLE
6. LFA1 VENDOR MASTER TABLE
7. EKKO PURCHASE ORDER HEADER
8. EKPO PURCHASE ORDER ITEM

9. VBAK SALES ORDER HEADER
10. VBAP SALES ORDER ITEM
11. VBRK BILLING DOCUMENT HEADER
12. VBRP BILLING DOCUMENT ITEM
13. LIKP DELIVERY HEADER
14. LIPS DELIVERY ITEM
WRITING SELECT QUERIES
Now we discuss about the programs to get the data from Data base tables. Now I take
MARA (Material master table) table as example to get the data. Practice only getting
data from standard tables.
Important fields in MARA table are.
1. MATNR ---- MATERIAL NUMBER
2. MBRSH ---- INDUSTRY SECTOR
3. MTART ---- MATERIAL TYPE
4. MEINS ---- UNIT OF MEASURE
5. NTGEW---- NET WEIGHT
6. BRGEW---- GROSS WEIGHT
My requirement is here I want to give MATNR as input to the program and I
want to get MATNR,MBRSH,MTART,MEINS for the particular material number I give
as input. We see how to declare the variables and How to write the select query.
When ever some input is needed to be given into a program we have to use the
PARAMETERS keyword. Here in this program I want to give material number i.e.
MATNR as input to the program. So I have to go to data base table MARA where
MATNR field is present and I have to find out the data type from there and I have to give
in the program. It is a big process. If want to declare many fields I have to go to many
times into the table and see the data type and I have to give in the program. I don’t want
to follow all this lengthy process. Only with the single statement the data type should be
assigned to the variable from data base field and with this statement The F1 and F4 helps
should be assigned to the variable.
F1 help is used to see documentation.

F4 help is used to see possible values.
For this we use this syntax in declaration.
Parameters p_matnr type mara-matnr.
Give assign the data type to a variable we have to refer to table name and field name.
Here in this example p_matnr is a variable which will take the characteristics from mara
table and matnr field. Instead of P-matnr we can give any name what ever we want. But
here I want to follow industry notation. Where p Stands for Parameters and matnr stands

for the field for which we are declaring the variable. From now onwards we follow this
notation. Sample program is as follows.
REPORT YSELECT9 .
PARAMETERS P_MATNR TYPE MARA-MATNR.
DATA: D_MATNR TYPE MARA-MATNR,
D_MBRSH TYPE MARA-MBRSH,
D_MTART TYPE MARA-MTART,
D_MEINS TYPE MARA-MEINS.
SELECT MATNR
MBRSH
MTART
MEINS
FROM MARA
INTO (D_MATNR,D_MBRSH,D_MTART,D_MEINS)
WHERE MATNR EQ P_MATNR.
ENDSELECT.
WRITE: / D_MATNR,
D_MBRSH,
D_MTART,
D_MEINS.
In this above program I am able to give single material number as input. But my
requirement is I want to give range of materials as input and I want to get the records in
that range. For that we have to use the keyword SELECT-OPTIONS.
SELECT-OPTIONS:- It allows you to input multiple values or range of values into the
program. But when ever select-options is used the program syntax changes like this.
REPORT YSELECT9 .
TABLES MARA.
SELECT-OPTIONS S_MATNR FOR MARA-MATNR.
SELECT MATNR
MBRSH
MTART
MEINS
FROM MARA
WHERE MATNR IN S_MATNR.
WRITE: / D_MATNR,
D_MBRSH,
D_MTART,
D_MEINS.
ENDSELECT.

If in select-options no input is given in the selection-screen system fetches all the
data from database from the table for which select query is written. Some times I may get
a requirement where this should not happen. That means I want to make the input
compulsory. For this use the keyword obligatory. Obligatory keyword makes the input
compulsory. The syntax is.
Select-options s_matnr for mara-matnr obligatory.
Some times I may get a requirement to get single record from data base for the
given input. That means I want to get first single matching record for the input what ever
I give. For that use select single.
Select single is used to get fetch first single matching record for the given
input. when ever select single is used you should not use end select.
The sample program is as follows…..

REPORT YSELECT9 .
TABLES MARA.
SELECT SINGLE MATNR

MBRSH
MTART
MEINS
FROM MARA
WRITE: / D_MATNR,
D_MBRSH,
D_MTART,
D_MEINS.
Some times a requirement may come where I need to fetch n no of records from
data base. For that we use select up to n rows. It should contain endselect. The program
is as follows
If I write select up to 1 rows it will fetch single record from data base. This is
what is done when we write select single also. Then what is the difference between
select single and select up to 1 rows. The differences are
1. Select single doesn’t require endselect but select up to 1 rows requires endselect.
2. Use select single when all the primary key fields of a table are used in the select
query where condition. Otherwise use select up to 1 rows. Performance wise SAP
is recommending you to use this way. Even though you use interchangingly
nothing will happen but performance comes down.

REPORT YSELECT9 .
TABLES MARA.
SELECT MATNR
MBRSH
MTART
MEINS
FROM MARA
UP TO 10 ROWS
WRITE: / D_MATNR,
D_MBRSH,
D_MTART,
D_MEINS.
ENDSELECT.
This program will fetch first 10 matching records from database for the given
input. If there are no 10 records to be fetched for the given input system fetches what ever
the records that are there for the given input.
In the above program we are getting the data record by record only. That means if
we want 1 lakh records from data base we are hitting data base 1 lakh times. The
performance of the program is low and the network traffic as also high. So my
requirement is I want to get all the matching records from data base in single shot and I
want to place it in the memory. The memory that we have created in the above programs
by those declarations can only hold single record at a time. To over come these problems
SAP has come up with a concept of internal tables.
INTERNAL TABLES
Internal table is an intermediate table. It can hold multiple records at a time. It is a

temporary table. The memory for the internal table will be allocated at runtime and de
allocated after the execution of the program automatically by the system. The changes
that made to the records of internal table are temporary. The changes are not reflected in
data base until some DML commands are written. Hence original data is retained in data
base. There are three types of internal tables.
1. Standard Internal Tables

2. Sorted Internal Tables
3. Hashed Internal Tables.
There two ways to declare the Internal tables.
Internal Tables with Header line.

Internal tables without Header line.
INTERNAL TABLE WITH HEADER LINE
Header of the internal table can contain only single record and body can contain
multiple records. If we are writing the logic to move record by record by record from DB
table to header of internal table, after record comes into header it has to be moved to
body of internal table by saying append <table name>. If it is needed to write the
records present in the body of internal table into list, record by record has to be moved to
header and written out. For this we have to write loop at <internal table>. When ever it
is needed to make the changes in the records present in the body of internal table, every
record has to be moved to header and modified. We can not do any operations on the
records directly present in the body of the internal table. These things we have to keep in
mind.
Syntax for declaring internal table with header line is…..
Data: begin of <internal table name> occurs 0,

<Fieldname> type <tablename-filedname>,
<Fieldname1> type <tablename-filedname>,
-------------,
-------------,
End of <internal table name>.
Sample program is as follows………………
REPORT YSELECT9 .
TABLES MARA.
data: begin of itab occurs 0,
matnr type mara-matnr,
mbrsh type mara-mbrsh,
mtart type mara-mtart,
end of itab.
select matnr
mbrsh
mtart from mara
into itab
where matnr in s_matnr.
append itab.
endselect.
loop at itab.
write: / itab-matnr,
itab-mbrsh,
itab-mtart.
endloop.

This program is also performance wise very poor. Because here also we are getting
the records one by one only. That means here network traffic will be more and the burden
on the server will be high. My requirement is I want to get the data from data base in
single shot and directly I want to place the records in the body of the internal table. For
this we have to modify the select query like this.
Sample program is like this…….
REPORT YSELECT9 .
TABLES MARA.
end of itab.
select matnr
mbrsh
mtart from mara
into table itab
*append itab.
*endselect.
loop at itab.
itab-mbrsh,
itab-mtart.
endloop.
In the above select query I have used select into table. Into table statement
fetches all the matching required records from database in single shot and directly places
into the body of internal table. Hence in the above program I have commented append
and endselect. Always when ever you use internal tables try to use into table which
improves the performance of the program.
Begin of itab occurs 0 statement creates an internal table with name itab with
header line.
SY-TABIX:- It is a system variable which gives present processing record number.
SY-DBCNT:- It is also a system variable which gives no of records fetched from

data base table.
SY-SUBRC:- It is an important system variable. It is used to find out where previous

ABAP statement is executed successfully or not. If it is successfully executed SY-
SUBRC value will be 0. If it is not executed successfully it’s value can be 4 or 8 or 12 or
16. If you want to check whether previous statement executed successfully or not always
check whether SY-SUBRC equal to 0 or not equal to 0. If equal to 0 statement executed
successfully, otherwise not executed successfully.

You can see a sample program with all these variables.
REPORT ZINTERNAL .
tables mara.
select-options s_matnr for mara-matnr.
end of itab.
select matnr
mbrsh
mtart from mara
into table itab where matnr in s_matnr.
if sy-subrc eq 0.
write: / 'no of records fetched from db', sy-dbcnt.
loop at itab.
write: / sy-tabix,
itab-matnr,
itab-mbrsh,
itab-mtart.
endloop.
else.
write: / 'no data to display'.
endif.
FORMATTING TECHNIQUES
These techniques are used to beautify the output.
INPUT:- This keyword is used to make a particular field in out as editable.

Which field you want to make as editable after that field in write statement use
keyword INPUT. See the sample program.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
loop at itab.
write: / itab-matnr input,
itab-mbrsh,
itab-mtart.
endloop.

In the above program only MATNR field in the output becomes editable because
only for that field I have used input keyword.
My requirement is I want to make all fields in the output as editable. After each
and every field I have to write input keyword. That unnecessarily increases the code. My
requirement is with single statement every field should become editable. For that use
FORAMT INPUT ON before write statement.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
format input on.

loop at itab.
itab-mbrsh,
itab-mtart.
endloop.
HOTSPOT: - This keyword is used to display hand symbol when ever cursor is
placed on a particular field in the output.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
loop at itab.
write: / itab-matnr hotspot ,
itab-mbrsh,
itab-mtart.
endloop.
To display hand symbol when ever cursor is placed on any field of output use
FORMAT HOTSPOT ON.

REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
format hotspot on.

loop at itab.
write: / itab-matnr ,
itab-mbrsh,
itab-mtart.
endloop.
COLORS:- For giving color to any field present in the output after the write statement
give color <color name/color number>. No direct colors like red, blue, green etc in SAP.
We are having following colors.
1 COL_HEADING Headers(grayish blue)

2 COL_NORMAL List body (bright gray)
3 COL_TOTAL Totals (yellow)
4 COL_KEY Key columns (bluish green)
5 COL_POSITIVE Positive threshold value (green)
6 COL_NEGATIVE Negative threshold value (red)
7 COL_GROUP Control levels (violet )
You can use the color names or the numbers present beside the color name in the
above list.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
loop at itab.
write: / itab-matnr color col_heading ,
itab-mbrsh color col_positive ,
itab-mtart color col_negative .
endloop.

If you execute above program you get matnr field values in blue color, mbrsh
field in green color and mtart field in red color. If you want same color to all fields of
output use FORMAT COLOR <COLOR NAME/COLOR NUMBER> before the
write statement.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
format color col_heading.

loop at itab.
itab-mbrsh ,
itab-mtart .
endloop.
All fields in the output will be displayed in blue color.

SKIP:- This keyword is used to generate a blank line in the output list.
SKIP N is used to generate n blank lines in the output list.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
loop at itab.
itab-mbrsh ,
itab-mtart .
endloop.
skip 5.
write / 'hai'.
BACK:- This keyword is used to move the control to first line first column of the output
list. Let us assume the requirement. I have displayed around 10 lines in the output and the

next write statement what I am going to write should display the contents in first line of
the list. If I write simply write statement it will be displayed after those lines which are
already displayed in the output. But my requirement is I have to take the control to first
line of the output. For this use BACK keyword. But the problem with back is that what
ever that is written previously in first line and first column will be over written. To avoid
this specify position in write statement so that the contents will be written in that
particular position instead of writing in the first column.
Write <position> <’statement’>.
Eg:- write 45 ‘hello’.
REPORT ZINTERNAL .
tables mara.
end of itab.
select matnr
mbrsh
mtart from mara
loop at itab.
itab-mbrsh ,
itab-mtart .
endloop.
back.
write /45 'hai'.
INTERNAL TABLES WITHOUT HEADER LINE
When ever begin of <internal table name> occurs 0 is used to create an internal table
system by default allocates 8KB of memory. If no of records fetched from database table
are more, that memory system initially allocated may not be sufficient. Hence system will
allocate extra memory. The extra memory allocated will be in multiples of 8KB only.
Hence in this case there is a possibility that memory may be wasted. Since memory is
allocated in pockets of 8KB the performance of the program comes down. To avoid all
these problems SAP has come up with a concept of internal tables without header line. In
this case internal table directly contains body without header. When ever internal table is
created without header line we have to create a work area. Here work area acts like a
header which can contain single record. The condition is the structure of work area and
internal table should be same or at least it should be compatible.
When ever it is needed to create an internal table without header line we use

TYPES keyword in the program. This keyword is used to create a structure. Using this
structure create an internal table as well as work area. We see a sample program which
creates an internal without header line.
REPORT YSELECT9 .
TABLES MARA.
types: begin of ty_itab,
end of ty_itab.
data itab type standard table of ty_itab.

data wa type ty_itab.
select matnr
mbrsh
mtart from mara
into wa where
matnr in s_matnr.
append wa to itab.
endselect.
loop at itab into wa.

write: / wa-matnr,
wa-mbrsh,
wa-mtart.
endloop.
In this above program first I have created a structure ty_itab using types statement
( Structure internally contains fields). Using this structure I have created an internal table
(ITAB) and as well as work area (WA). When ever type standard table of syntax is used
it creates an internal table. If we use only type in the syntax it creates work area. But in
the above program first record by record is coming into work area and then it is appended
into the body of the internal. This program is not good performance wise. Because we
have to get the records in single shot from database and have to place directly into the
body of internal table. For that purpose we can write the program like this which
improves the performance.
REPORT YSELECT9 .
TABLES MARA.
types: begin of ty_itab,
end of ty_itab.
data itab type standard table of ty_itab.

data wa type ty_itab.
select matnr
mbrsh
mtart from mara
into table itab where
matnr in s_matnr.

* append wa to itab.
* endselect.
loop at itab into wa.

write: / wa-matnr,
wa-mbrsh,
wa-mtart.
endloop.
CLEAR:- This keyword clears/deletes the contents from the header of internal table or
from the variable memory.
Syntax:- CLEAR <TABLE NAME>/<VARIABLE NAME>.
REFRESH:- This keyword deletes the contents from the body of the internal table.
Syntax:- REFRESH < TABLE NAME>.

Instead of this we can also use the syntax CLEAR <TABLE NAME[]> .This
statement also deletes the contents from the body of the internal table.
In SAP [] indicates the body of internal table.
Eg:- itab[] indicates the body of the internal table itab.
FREE:- This keyword is used to deallocate the memory allocated for internal table as
well as any variable .
Syntax:- FREE <TABLE NAME>/<VARIABLE NAME>.
Till now we are only getting the data from single table. If I want to get the data
from multiple tables, we have to go for joins. There are two types of joins available in
SAP. They are…
1. Inner join
2. Left outer join
It is very important to remember that when ever you want to join the tables it is
mandatory that there should be at least one common field between them. Without a
common field between the tables we can’t join the tables. For taking the common field
we should not consider MANDT field. Common field may be primary key field or other
field.
INNER JOIN:- It is exactly like intersection or logical AND operator. This inner join
will fetch the data from the tables if the record is available in all the tables that you are
joining. If it is not available in one of the tables, the data will not be fetched.
LEFT OUTER JOIN:- It is like union. But it is not exactly like union. When ever left
outer join is used in select query, it will fetch all the records from left side table and the
common records from right side table.

Inner join between table 1 and table 2, where column D in both tables in the join condition is set
the same:
Table 1 Table 2
|----|----|----|----| |----|----|----|----|----|
| A | B | C | D | | D | E | F | G | H |
|----|----|----|----| |----|----|----|----|----|
| a1 | b1 | c1 | 1 | | 1 | e1 | f1 | g1 | h1 |
| a2 | b2 | c2 | 1 | | 3 | e2 | f2 | g2 | h2 |
| a3 | b3 | c3 | 2 | | 4 | e3 | f3 | g3 | h3 |
| a4 | b4 | c4 | 3 | |----|----|----|----|----|
|----|----|----|----|
\ /
\ /
\ /
\ /
\/
Inner Join
|----|----|----|----|----|----|----|----|----|
| A | B | C | D | D | E | F | G | H |
|----|----|----|----|----|----|----|----|----|
| a1 | b1 | c1 | 1 | 1 | e1 | f1 | g1 | h1 |
| a2 | b2 | c2 | 1 | 1 | e1 | f1 | g1 | h1 |
| a4 | b4 | c4 | 3 | 3 | e2 | f2 | g2 | h2 |
|----|----|----|----|----|----|----|----|----|
Left outer join between table 1 and table 2 where column D in both tables set the join condition:
Table 1 Table 2
|----|----|----|----| |----|----|----|----|----|
| A | B | C | D | | D | E | F | G | H |
|----|----|----|----| |----|----|----|----|----|
| a1 | b1 | c1 | 1 | | 1 | e1 | f1 | g1 | h1 |
| a2 | b2 | c2 | 1 | | 3 | e2 | f2 | g2 | h2 |
| a3 | b3 | c3 | 2 | | 4 | e3 | f3 | g3 | h3 |
| a4 | b4 | c4 | 3 | |----|----|----|----|----|
|----|----|----|----|
\ /
\ /
\ /
\ /
\/

Left Outer Join
|----|----|----|----|----|----|----|----|----|
| A | B | C | D | D | E | F | G | H |
|----|----|----|----|----|----|----|----|----|
| a1 | b1 | c1 | 1 | 1 | e1 | f1 | g1 | h1 |
| a2 | b2 | c2 | 1 | 1 | e1 | f1 | g1 | h1 |
| a3 | b3 | c3 | 2 |NULL|NULL|NULL|NULL|NULL|
| a4 | b4 | c4 | 3 | 3 | e2 | f2 | g2 | h2 |
|----|----|----|----|----|----|----|----|----|
See the sample program to join two tables using inner join..
REPORT ZJOINS1 .
TABLES MARA.
TYPES: BEGIN OF TY_MARA,
MATNR TYPE MARA-MATNR,
MBRSH TYPE MARA-MBRSH,
MTART TYPE MARA-MTART,
WERKS TYPE MARC-WERKS,
END OF TY_MARA.
DATA: IMARA TYPE STANDARD TABLE OF TY_MARA,

WA_MARA TYPE TY_MARA.
SELECT MARA~MATNR
MARA~MBRSH
MARA~MTART
MARC~WERKS
INTO TABLE IMARA
FROM MARA INNER JOIN MARC
ON MARA~MATNR EQ MARC~MATNR
WHERE MARA~MATNR IN S_MATNR.
LOOP AT IMARA INTO WA_MARA.

WRITE: / WA_MARA-MATNR,
WA_MARA-MBRSH,
WA_MARA-MTART,
WA_MARA-WERKS.
ENDLOOP.
The out put will be …..

See the sample program to join three tables using inner join..
REPORT ZJOINS1 .
TABLES MARA.
MAKTX TYPE MAKT-MAKTX,
END OF TY_MARA.

SELECT MARA~MATNR
MARA~MBRSH
MARA~MTART
MARC~WERKS
MAKT~MAKTX
INTO TABLE IMARA
FROM MARA INNER JOIN MARC
INNER JOIN MAKT
ON MARA~MATNR EQ MAKT~MATNR
WHERE MARA~MATNR IN S_MATNR
AND MAKT~SPRAS EQ 'EN'.

WA_MARA-MBRSH,
WA_MARA-MTART,
WA_MARA-WERKS,
WA_MARA-MAKTX.
ENDLOOP.
See the sample program joining two tables using left outer join.
REPORT ZJOINS1 .
TABLES MARA.
END OF TY_MARA.

SELECT MARA~MATNR
MARA~MBRSH
MARA~MTART
MARC~WERKS
INTO TABLE IMARA
FROM MARA LEFT OUTER JOIN MARC
WHERE MARA~MATNR IN S_MATNR.

WA_MARA-MBRSH,
WA_MARA-MTART,
WA_MARA-WERKS.
ENDLOOP.
The out will be ……

You can clearly see the difference in output. In inner join we are not getting
Material number 98 because material number 98 is only present in MARA table but not
MARC table, but material number 98 is coming in left outer join because it will display
all the records present in left side table i.e. MARA and common records from right side
table i.e. MARC.
FOR ALL ENTRIES
Joining of many tables decreases the performance of the program. In real time you
will not be allowed to join more than 4 or 5 tables. FOR ALL ENTRIES is used as
substitute for joins. When ever for all entries is used it is needed to declare separate
internal tables for each data base table. After getting the data from each data base table
into respective internal tables move the records into another internal table which is
containing the fields from both the tables.
The sample program can be seen here.
REPORT ZFORALL .
tables mara.

data: begin of imara occurs 0,
end of imara.
data: begin of imarc occurs 0,

matnr type marc-matnr,
werks type marc-werks,
end of imarc.
data: begin of final occurs 0,
end of final.
select matnr
mbrsh
mtart from mara
into table imara
if not imara[] is initial.
select matnr
werks from marc
into table imarc
for all entries in imara
where matnr eq imara-matnr.
SORT IMARC BY MATNR.
loop at imara.
read table imarc with key matnr = imara-matnr BINARY SEARCH.
if sy-subrc eq 0.
move: imara-matnr to final-matnr,
imara-mbrsh to final-mbrsh.
move imara-mtart to final-mtart.
move imarc-werks to final-werks.
append final.
clear final.
clear imara.
clear imarc.
else.
continue.
endif.
endloop.
loop at final.
write: / final-matnr,
final-mbrsh,
final-mtart,
final-werks.
endloop.
else.
write: / 'no data to display'.
endif.
While using for all entries it is mandatory to check whether base internal table is
empty or not.. If base internal table is empty the second select query where for all entries
is used will fetch all the data from data base table for which select query is written. In the
above program if I don’t check the condition whether IMARA is empty or not , if
IMARA is empty the complete data from MARC table will come into IMARC internal

table.
To check whether base internal table is empty or not use this syntax
[] symbolizes body of the internal table.
See the sample program where we need not use third internal table and as
well as how to change or modify the existing records of the internal table.
REPORT ZFORALL2 .
tables mara.
types: begin of ty_mara,
end of ty_mara.
types: begin of ty_marc,
matnr type marc-matnr,
end of ty_marc.
data: imara type standard table of ty_mara,

wa_mara type ty_mara,
imarc type standard table of ty_marc,
wa_marc type ty_marc.
DATA INDEX TYPE SY-TABIX.
select matnr
mbrsh
mtart from mara
into table imara

*IF SY-SUBRC EQ 0
select matnr
werks from marc
into table imarc
for all entries in imara
where matnr eq imara-matnr.
loop at imara into wa_mara.

INDEX = SY-TABIX.
read table imarc into wa_marc with key matnr = wa_mara-matnr.
if sy-subrc eq 0.
move wa_marc-werks to wa_mara-werks.
modify imara FROM WA_MARA index INDEX.
clear wa_mara.
clear wa_marc.
else.
DELETE IMARA INDEX INDEX.
ENDIF.
ENDLOOP.
loop at imara into wa_mara.

write: / wa_mara-matnr,
wa_mara-mbrsh,

wa_mara-mtart,
wa_mara-werks.
endloop.
else.
write: / 'NO DATA TO DISPLAY'.
ENDIF.
MODULARIZATION
It is a technique of splitting larger code into smaller block of code. It is done for
easy understanding, easy debugging and to decrease the code. We can achieve this in
SAP using 4 concepts.
1. Events
2. Subroutines
3. Include programs
4. Function modules
5. Macros.
TYPES OF REPORTS
There are three types of reports.
1. Classical Reports
2. Interactive Reports
3. Drill down Reports
CLASSICAL REPORT:- A report which can generate only one list, that is Basic List,
is called classical report. First List of a report is called BASIC LIST.
INTERACTIVE REPORT:- A report which can generate one basic list and upto 20
interactive lists is called an interactive report. First list is called Basic List and
Interactive lists are called Secondary Lists.
DRILL DOWN REPORTS:- In these reports the output will be in tree format.

EVENTS IN CLASSICAL REPORTS
1. INITIALIZATION
2. AT SELECTION-SCREEN
(a) AT SELECTION-SCREEN ON <FIELD>
(b) AT SELECTION-SCREEN OUTPUT
(c) AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>
3. START-OF-SELECTION
4. TOP-OF-PAGE
5. END-OF-PAGE
6. END-OF-SELECTION
Now we will discuss what are the uses of these events.
INITIALIZATION:- This is the first event to be triggered. This event is triggered before
the selection-screen is displayed. This event is used to give default vales to selection-
screen fields.
AT SELECTION-SCREEN:- This event is triggered after giving input in selection-

screen fields. This event is used to handle the user actions on the screen. This is also used
to validate all the selection-screen fields.
AT SELECTION-SCREEN ON <FIELD>:- This event is used to validate a particular

field present on the selection-screen.
AT SELECTION-SCREEN OUTPUT:- This event is used to change the selection-

screen properties dynamically.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>:- This event is

used to give F4 help to a particular field resent on the selection-screen.
START-OF-SELECTION:- The main logic of the program is written in this event.

Usually write statement is recognized from this event.
TOP-OF-PAGE:- This event is used to write something on top of every page. The first
write statement or output statement (SKIP) of a page triggers this event.
END-OF-PAGE: - This event is used to write something at end of every page. Last line
of the page triggers this event. We have to allocate the line for end of page.
END-OF-SELECTION:- Usually program output is written in this event. This event is

used to handle abnormal termination of the program. The stop statement written in start-
of-selection event takes the control to end-of-selection event.
No event is mandatory. But default event is start-of-selection

Because ABAP is an event driven language there is no need to maintain the order
of the events. System will take care of the order of the events.
The write statement written in initialization event can not be seen if the program
is having selection-screen, because initialization event is triggered before the selection-
screen is displayed. If the program is not having the selection-screen we can see the write
statement written in Initialization event.
Starting of new event symbolizes ending of previous event.
The STOP statement in start-of-selection takes the control to end-of-selection
statement.
Skip statement also triggers top-of-page event.
Declarations should be written before initialization event.
See the following sample program which uses initialization event and write statement.
REPORT ZSAMPLE .
parameters p_matnr type mara-matnr.
initialization.
write : 'HELLO'.
I have written write statement in Initialization event and the program is having
selection-screen. The write statement can not be seen. Actually HELLO will be written
but that is immediately overwritten by selection-screen. That is the reason why we can
not see the write in output.
REPORT ZSAMPLE .
Initialization.
write : 'HELLO'.
If I execute the above program HELLO will be seen because this program is not
having selection-screen.
Now see the following program which is having all the above events.
REPORT ZEVENTS no standard page heading line-count 10(1) line-size 500.

tables mara.
data d_matnr type mara-matnr.
end of itab.
data count type i.
select-options s_matnr for mara-matnr no-extension no intervals.
at selection-screen on s_matnr.
select single matnr

from mara
into d_matnr
if sy-subrc ne 0.
message e000(zmsg) with s_matnr-low s_matnr-high.
endif.
start-of-selection.

select matnr
mbrsh
mtart from mara
into table itab
stop.
end-of-selection.
loop at itab.
itab-mbrsh,
itab-mtart.
endloop.
count = sy-linct - sy-linno - 1.
skip count.
top-of-page.
write / 'data from mara table'.
end-of-page.
write: /45 'page number: ', sy-pagno.
In the above program I have used a statement message e000(zmsg)

which is used to raise the message. The meaning of this statement is that raise an
error message from zmsg message class. The message number to be raised is 000.
MESSAGE CLASS:- Its is a collection of messages. Each message class can hold 1000
messages. (000 to 999). T-code for creation of message class is SE91.
There are 5 types of messages in SAP.
1. Error Message (E).
2. Warning Message (W).
3. Information Message (I).
4. Success Message (S).
5. Abend Message (A).
A Message created in a message class can be used as any of the above 5 types.
What ever the letter I have given in the brackets after each type of message should
be used to specify the system about which type message you are going to raise.
Error Message temporarily halts the program. That means once the errors
are corrected the control moves forward. But Abend message completely
terminates the program.
Information and Success messages give the message and move forward.
They won’t stop the control.
Warning message also temporarily terminates the program.
When ever you go for validations better you use Error message.
Now we look into statements that are new in the above program.
NO STANDARD PAGE HEADING:- This is used to suppress the default

heading given by system in output. That means first two lines in the output(i.e.
Text given in title of the program and the a horizontal line) will be suppressed.

LINE-COUNT 10(1):- Here 10 specifies no of lines per a page. If this is not
mentioned system takes 65,000 lines as single page. So when ever you want to
specify no of lines per a page you have to mention here. 1 that is written in
brackets indicates no of lines allocated for end-of-page. That means the complete
meaning is 10 lines per each page and in those 10 lines 1 line is allocated for end-
of-page.
LINE-SIZE 500:- Line-size specifies about how many characters should be

printed in a line. If it is not mentioned system will print only 255 characters in a
page. Maximum line-size allowed is 1023 characters. This is used in a program
when you want to display many fields in the output. Because in that case normal
output of 255 characters per a line may not be sufficient.
SY-LINCT:- This is a system variable which gives no of lines allocated per a

page. In the above program sy-linct value will be 10.
SY-LINNO:- This is also a system variable which gives no of lines printed in a

page.
In the program I have used count = sy-linct - sy-linno - 1. skip count.

This logic is used to trigger end-of-page event for last page also. If this logic is not used
page number for the last page will not come because end-of-page event is triggered by
last line of the page. If there no enough lines that means 9 lines to be printed in the last
page end-of-page will not be triggered. The logic used above will help in triggering the
end-of-page event even for the last page also. You can try the program without this logic
also. Then you will understand better. You also execute the program in debug mode to
understand better.
SY-LILLI:- It is a system variable which gives clicked line number in the list.
SY-LISEL:- It is a system variable which contains whole contents of clicked line.
Try these system variables in debug mode.
INTERACTIVE REPORTS:- A report which can generate one basic and up to 20

interactive lists is called an interactive report.
First list is called basic list and next lists are called interactive lists.
EVENTS IN INTERACTIVE REPORTS
1. INITIALIZATION
2. AT SELECTION-SCREEN
a. AT SELECTION-SCREEN ON <FIELD>
b. AT SELECTION-SCREEN OUTPUT
c. AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>
3. START-OF-SELECTION
4. TOP-OF-PAGE

5. END-OF-PAGE
6. AT LINE-SELECTION
7. AT USER-COMMAND
8. TOP-OF-PAGE DURING LINE-SELECTION
AT LINE-SELECTION:- This event is used to generate an interactive list when ever

particular in the out is double clicked.
TOP-OF-PAGE DURING LINE-SELECTION:- This event is used to write some
thing on top of every page of individual secondary lists. Top-of-page event is used
to write something on only basic list.
AT USER-COMMAND:- This is used to handle user action on the screen when ever
standard menu bar and application tool are changed.
In these interactive lists we take the help of HIDE table. Hide is an intermediate
memory area which is used to hold the values that are used for generation of next
secondary list. Hide statement should be used after write statement. Then only you will
get correct results. Other wise you will get wrong values. Hide table values you can’t see
even in debug mode.
SY-LSIND:- This is also a system variable which gives present processing list number.
It’s value will be 0 for basic list and 1 to 20 for secondary lists. We will make use of this
sy-lsind in our next program to tell the system about which logic should be executed
while going to a particular list..
SY-LILLI:- This is a system variable which will hold the clicked line number.
SY-LISEL:- This is also a system variable which will hold all the contents of clicked
line.
SY-UCOMM:- This system variable is used to hold the function code that is triggered
for the user actions on the screen.
REPORT ZEVENTS no standard page heading.

tables mara.

end of itab.
DATA: BEGIN OF ITAB1 OCCURS 0,
MATNR TYPE MARC-MATNR,
END OF ITAB1.

MATNR TYPE MAKT-MATNR,
MAKTX TYPE MAKT-MAKTX,
END OF ITAB2.

select-options s_matnr for mara-matnr." no-extension no intervals.
start-of-selection.
select matnr
mbrsh
mtart from mara
into table itab
loop at itab.
itab-mbrsh,
itab-mtart.
HIDE ITAB-MATNR.
endloop.
AT LINE-SELECTION.
CASE SY-LSIND.
WHEN 1.
SELECT MATNR
WERKS FROM MARC
INTO TABLE ITAB1
WHERE MATNR EQ ITAB-MATNR.
LOOP AT ITAB1.
WRITE: / ITAB1-MATNR,
ITAB1-WERKS.
HIDE ITAB1-MATNR.
ENDLOOP.
WHEN 2.
select MATNR
MAKTX FROM MAKT
INTO TABLE ITAB2
WHERE MATNR EQ ITAB1-MATNR.
LOOP AT ITAB2.
WRITE: / ITAB2-MATNR,
ITAB2-MAKTX.
ENDLOOP.
ENDCASE.
TOP-OF-PAGE.
WRITE / 'DATA FROM MARA TABLE'.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE SY-LSIND.
WHEN 1.
WRITE ' DATA FROM MARC TABLE'.
WHEN 2.
WRITE 'DATA FROM MAKT TABLE'.
ENDCASE.
SE41 T-code is used to create user defined GUI status or PF status for a program.
See the following program which is written to handle the user actions on the screen for
user defined GUI status.

REPORT ZEVENTS no standard page heading.
tables mara.

end of itab.
start-of-selection.
SET PF-STATUS 'ZPF1'.

select matnr
mbrsh
mtart from mara
into table itab
loop at itab.
itab-mbrsh,
itab-mtart.
endloop.
AT USER-COMMAND.
CASE SY-UCOMM.
WHEN 'TCODE'.
CALL TRANSACTION 'SE11'.
WHEN 'DISPLAY'.
WRITE: 'LIST NUMBER IS', SY-LSIND.
WHEN 'WRITE'.
WRITE 'HELLO'.
ENDCASE.
SUBROUTINES
When ever same logic is needed to be executed many times in a program, create a
subroutine and call the subroutine when ever the logic is needed to be executed.
Perform statement is used to create the subroutine and to call the subroutine.
A subroutine can be created with passing the variables and without passing the variables.
The logic of the subroutine is written between form and endform. It is not required to
start the subroutine name with Z OR Y.
The variables that are passed into subroutine are called global variables or actual
variables. The variables that are used to receive the values in subroutine from main
program are called local variables or formal variables.
There are 3 ways to pass the variables into subroutine.

1. CALL BY VALUE
2. CALL BY REFERENCE
3. CALL BY VALUE AND RESULT
CALL BY VALUE:- In this new memory area is allocated for the local variables
between form and endform. When the values of local variables are changed , they are
changed in only or reflected in only newly created memory area. The original values of
corresponding global variables are not changed.
CALL BY REFERENCE:- In this no new memory area is created for the local variables
between form and endform. They make use of memory of the corresponding global
variables. Hence when the values of local variables are changed between form and
endform immediately the corresponding global variables values are changed.
CALL BY VALUE AND RESULT:- In this new memory area is created for local
variables. When ever the values of local variables are changed between form and
endform, the changes are reflected in only newly created memory area. But when the
control is moving back from subroutine to main program, the values present in local
memory are copied back to the corresponding global variables memory area.
Hence we can say that in CALL BY VALUE the values of global variables are
never changed when corresponding local variables values are changed, in CALL BY
REFERENCE the values of global variables are changed immediately. In CALL BY
VALUE AND RESULT the values of corresponding global variables are changed
control moves from subroutine to main program.
First we will see how to create the subroutine with passing the variables.
See the following example.
REPORT ZSELECT20 .
parameters: a type i,
b type i.
data c type i.
perform add using a b

changing c.
write: / 'the sum of two numbers is', c.

*&---------------------------------------------------------------------*
*& Form add
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_A text
* -->P_B text
* <--P_C text
*----------------------------------------------------------------------*

FORM add USING A
B
CHANGING C.
c = a + b.
ENDFORM. " add
No need to write the form and endform manually. When you double click the
perform name written in perform statement (ADD) automatically system will create form
and endform. Between the form and endform write the logic what ever you want.
Now we will see how to create a subroutine without passing the variables.
REPORT ZSELECT20 .
tables mara.
end of itab.
perform select.
perform display.
*&---------------------------------------------------------------------*
*& Form select
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM select .
select matnr
mbrsh
mtart from mara
into table itab
ENDFORM. " select

*&---------------------------------------------------------------------*
*& Form display
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM display .
loop at itab.
itab-mbrsh,
itab-mtart.
endloop.
ENDFORM. " display
start-of-selection.
write 'hello'.

No statement after form and endform is accessible. After form and endform only
form and endform is accessible. If you want to access any statement after form and
endform we have to use start-of-selection event.
Usually subroutines are local to a program. They are not stored in database. They
are not self executable. If you want to call a subroutine ADD (say) created in some X
program from Y program , you have to write this syntax in Y program
Perform <perform name><(program name)>.

Perform add(X).
INCLUDE PROGRAMS
These programs are also used for reusability. Include program name should start with
either Z or Y. There are two ways to create include programs.
1. Directly from SE38 we can create include program. Here we have to choose
program type as include program.

2. Directly from the program also we can create include program. In the program
write Include <include program name>. Keep cursor on the include program
name and double click. If the program is not available, it will ask for the creation,
say yes and move forward.

After creation of include program if it is needed to call the include program from
another program use the statement include <Include program name>.
FUNCTION MODULES.
In modularization this is very important concept. Function module has to be saved

under a function group. That means function group is a must for creation of function
module. SE80 or SE37 T-codes are used to create function group. Function group is a
collection or pool of function modules.
There are 3 types of function modules.
1. Normal Function module
2. Remote enabled Function module
3. Update function module
By default every function created will be normal function module.
When ever function group is created system automatically creates 2 includes.

1. Top include
2. Uxx include

Top include is used for common declarations. That means the declarations made in
Top include can be accessed by all function modules present in that function group. The
declarations made in Top include will become Global variables. This is once again to
decrease the code.
Uxx include contains source code of the function modules. For each function
module one include will be added in Uxx include. On seeing the no of includes in Uxx
include we can know how many function modules are present in a particular function
group.
SE37 T-code is used to create a function module. Function module name need not
start with z or y. The variables that are needed to be sent from program or the variables
that are needed to be populated at run time should be given under Import. The values that
are needed to be sent from function modules to program should be given under export or
changing. When want to move the internal table data from function module to program or
vice versa it should be taken in tables. Exceptions can be written under exceptions. The
logic of the function module should be written under source code.
See the following function module which is written to add two numbers.

Function modules are self executable. We can execute them by pressing F8
button. All function modules are stored in TFDIR table.
If you want to call the function module from a program you have to use pattern
button which is present on application tool bar.
You see this sample program which is calling the previous function module
written.
REPORT ZADDITION .
parameters: x type i,
y type i.
data z type i.
CALL FUNCTION 'ADD'

EXPORTING
A = x
B = y
IMPORTING
C = z
.

write: 'the sum of two numbers is', z.
One thing you have to remember is that the left hand side variables data types and
right hand side variables data types should be same in call function. Otherwise system
gives type conflict error (Short dump). If a variable is not given as optional in function
module, it is mandatory to pass the value into the variable in call function. Other wise
system gives runtime error saying Incorrect parameter with call function. These two
things you have o keep in mind.
ALV (ABAP LIST VIEWER)
The output of the normal report and ALV will be same content wise. But after
getting the output in ALV we can interact with the list and we can perform many
operations on the output. The operations are like sorting the list, calculating totals and sub
totals, exporting list to excel sheet and text document, suppressing a particular field and
many more.
TYPE-POOLS:- Collection of similar types.
SLIS is an important type-pool used in ALVs for getting the output. This SLIS
type-pool is containing many structures internally. These structures will have fields.
These fields will have certain properties. If these fields are used in the program the
property assigned to that field will come to the program output.
SLIS_T_FILEDCAT-ALV is an important structure present in slis which should

be used for displaying output in ALV.
For getting the output using ALV we have to use function modules. All the
function modules will start with REUSE_ALV_.
Three types of displays are available in ALV.
1. Normal display
(a) Grid display
(b) List display
2. Block display
3. Hierarchical display
First we see the program to display the output in List.

REPORT ZALV1 .
TYPE-POOLS SLIS.
DATA FCAT TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.
TABLES MARA.
DATA: BEGIN OF ITAB OCCURS 0,

NTGEW TYPE MARA-NTGEW,
BRGEW TYPE MARA-BRGEW,
END OF ITAB.
SELECT MATNR
MBRSH
MTART
NTGEW
BRGEW FROM MARA
INTO TABLE ITAB
FCAT-SELTEXT_L = 'MATERIAL NUMBER'.

FCAT-COL_POS = '1'.
FCAT-TABNAME = 'ITAB'.
FCAT-FIELDNAME = 'MATNR'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'industry sector'.

FCAT-COL_POS = '2'.
FCAT-FIELDNAME = 'MBRSH'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'MATERIAL TYPE'.

FCAT-COL_POS = '3'.
FCAT-FIELDNAME = 'MTART'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'NET WEIGHT'.

FCAT-COL_POS = '4'.
FCAT-FIELDNAME = 'NTGEW'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'GROSS WEIGHT'.

FCAT-COL_POS = '5'.
FCAT-FIELDNAME = 'BRGEW'.
APPEND FCAT.
CLEAR FCAT.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING
* I_INTERFACE_CHECK = ' '
* I_BYPASSING_BUFFER =
* I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = sy-repid
* I_CALLBACK_PF_STATUS_SET = ' '
* I_CALLBACK_USER_COMMAND = ' '
* I_STRUCTURE_NAME =
* IS_LAYOUT =
IT_FIELDCAT = fcat[]
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =

* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* I_SAVE = ' '
* IS_VARIANT =
* IT_EVENTS =
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
TABLES
T_OUTTAB = itab
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
In the above program from the structure SLIS_T_FIELDCAT_ALV I have taken

fields SELTEXT_L whose property is to give heading for the columns in the output,
COL_POS to specify the column position, TABNAME to specify about the table from
which data has to be displayed (Internal table name), FIELDNAME to specify the field
to be displayed.
See the program for Grid display.
REPORT ZALV1 .
TYPE-POOLS SLIS.
TABLES MARA.
END OF ITAB.
SELECT MATNR
MBRSH
MTART
NTGEW
BRGEW FROM MARA
INTO TABLE ITAB

FCAT-COL_POS = '1'.
APPEND FCAT.

CLEAR FCAT.

FCAT-COL_POS = '2'.
APPEND FCAT.
CLEAR FCAT.

FCAT-COL_POS = '3'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'NET WEIGHT'.

FCAT-COL_POS = '4'.
FCAT-FIELDNAME = 'NTGEW'.
APPEND FCAT.
CLEAR FCAT.
FCAT-SELTEXT_L = 'GROSS WEIGHT'.

FCAT-COL_POS = '5'.
FCAT-FIELDNAME = 'BRGEW'.
APPEND FCAT.
CLEAR FCAT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING
* I_BYPASSING_BUFFER = ' '
I_CALLBACK_PROGRAM = sy-repid
* I_CALLBACK_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_END_OF_LIST = ' '
* I_BACKGROUND_ID = ' '
* I_GRID_TITLE =
* I_GRID_SETTINGS =
* IS_LAYOUT =
IT_FIELDCAT = fcat[]
* IT_EXCLUDING =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* I_SAVE = ' '
* IS_VARIANT =
* IT_EVENTS =
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =

* IT_ALV_GRAPHICS =
* IT_HYPERLINK =
* IT_ADD_FIELDCAT =
* IT_EXCEPT_QINFO =
* I_HTML_HEIGHT_TOP =
* I_HTML_HEIGHT_END =
* IMPORTING
TABLES
T_OUTTAB = itab
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
ENDIF.
Now we see some other fields present in SLIS_T_FIELDCAT_ALV

STRUCTURE.
EDIT:- It is used to edit a particular field in output.

Syntax:- FCAT-EDIT = ‘X’.
HOTSPOT:- To give hand symbol to a particular field in output.

Syntax:- FCAT-HOTSPOT = ‘X’.
EMPHASIZE:- To give color to the output

Syntax:- FCAT-EMPHASIZE = ‘CXYZ’.
C stands for color
X is used for colors. It can take values from 0 to 9
Y is used for Intensity. It can take values 0 or 1. 0—off, 1---on.
Z is used for inverse (Back ground color). It can take values 0 or 1.
REFTABNAME:- To take column heading directly from data base table

Syntax:- FCAT-REFTABNAME = ‘MARA’
KEY:- To fix a particular column in output

Syntax:- FCAT-KEY = ‘X’.
DO_SUM:- For getting the grand totals directly in output

Syntax:- FCAT-DO_SUM = ‘X’.
ZEBRA is the field present in SLIS_LAYOUT_ALV structure which is used to

display alternate fields in dark and light colors.
Syntax:- LAYOUT-ZEBRA = ‘X’

See the sample program which is displaying logo in the ALV report output.
REPORT ZALV .
TYPE-POOLS SLIS.
DATA LAYOUT TYPE SLIS_LAYOUT_ALV.
DATA EVENT TYPE SLIS_T_EVENT WITH HEADER LINE.
TABLES MARA.
END OF ITAB.
SELECT MATNR
MBRSH
MTART FROM MARA
INTO TABLE ITAB

FCAT-COL_POS = '1'.
APPEND FCAT.
CLEAR FCAT.

FCAT-COL_POS = '2'.
APPEND FCAT.
CLEAR FCAT.

FCAT-COL_POS = '3'.
APPEND FCAT.
CLEAR FCAT.
EVENT-NAME = 'TOP_OF_PAGE'.
EVENT-FORM = 'TOP'.
APPEND EVENT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING
* I_BYPASSING_BUFFER = ' '
I_CALLBACK_PROGRAM = SY-REPID
* I_CALLBACK_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_END_OF_LIST = ' '
* I_BACKGROUND_ID = ' '
* I_GRID_TITLE =

* I_GRID_SETTINGS =
* IS_LAYOUT =
IT_FIELDCAT = FCAT[]
* IT_EXCLUDING =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* I_SAVE = ' '
* IS_VARIANT =
IT_EVENTS = EVENT[]
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =
* IT_ALV_GRAPHICS =
* IT_HYPERLINK =
* IT_ADD_FIELDCAT =
* IT_EXCEPT_QINFO =
* I_HTML_HEIGHT_TOP =
* I_HTML_HEIGHT_END =
* IMPORTING
TABLES
T_OUTTAB = ITAB
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
ENDIF.
FORM TOP.
DATA HEADER TYPE SLIS_T_LISTHEADER WITH HEADER LINE.
HEADER-TYP = 'S'.
HEADER-INFO = 'DATA FROM MARA TABLE'.
HEADER-KEY = 'ALV REPORT'.
APPEND HEADER.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = HEADER[]
I_LOGO = 'ZSAP8'
* I_END_OF_LIST_GRID =
.
ENDFORM.
BLOCK DISPLAY

It is used to display multiple internal tables in single list out. If block display is
not used, one internal table will be over written by another internal table. At a time we
can see only one internal table. The sample program is …
REPORT ZALV .
TYPE-POOLS SLIS.
DATA FCAT1 TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.

DATA EVENT TYPE SLIS_T_EVENT WITH HEADER LINE.
TABLES MARA.
END OF ITAB.
MATNR TYPE MARC-MATNR,
END OF ITAB1.
SELECT MATNR
MBRSH
MTART FROM MARA
INTO TABLE ITAB
SELECT MATNR
WERKS
FROM MARC
INTO TABLE ITAB1

FCAT-COL_POS = '1'.
APPEND FCAT.
CLEAR FCAT.

FCAT-COL_POS = '2'.
APPEND FCAT.
CLEAR FCAT.

FCAT-COL_POS = '3'.
APPEND FCAT.
CLEAR FCAT.
FCAT1-SELTEXT_L = 'MATERIAL NUMBER'.

FCAT1-COL_POS = '1'.
FCAT1-TABNAME = 'ITAB1'.
FCAT1-FIELDNAME = 'MATNR'.
APPEND FCAT1.

CLEAR FCAT1.
FCAT1-SELTEXT_L = 'PLANT'.
FCAT1-COL_POS = '2'.
FCAT1-TABNAME = 'ITAB1'.
FCAT1-FIELDNAME = 'WERKS'.
APPEND FCAT1.
CLEAR FCAT1.
LAYOUT-ZEBRA = 'X'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'

EXPORTING
I_CALLBACK_PROGRAM = SY-REPID
* IT_EXCLUDING =
.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'

EXPORTING
IS_LAYOUT = LAYOUT
I_TABNAME = 'ITAB'
IT_EVENTS = EVENT[]
* IT_SORT =
* I_TEXT = ' '
TABLES
T_OUTTAB = ITAB
* EXCEPTIONS
* PROGRAM_ERROR = 1
* MAXIMUM_OF_APPENDS_REACHED = 2
* OTHERS = 3
.
IF SY-SUBRC <> 0.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'

EXPORTING
IS_LAYOUT = LAYOUT
IT_FIELDCAT = FCAT1[]
I_TABNAME = 'ITAB1'
IT_EVENTS = EVENT[]
* IT_SORT =
* I_TEXT = ' '
TABLES
T_OUTTAB = ITAB1
* EXCEPTIONS
* PROGRAM_ERROR = 1
* MAXIMUM_OF_APPENDS_REACHED = 2
* OTHERS = 3
.
IF SY-SUBRC <> 0.
ENDIF.

CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'
* EXPORTING
* IS_PRINT =
* IMPORTING
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
ENDIF.
In block display we have to use 3 function modules.
1. REUSE_ALV_BLOCK_LIST_INIT
2. REUSE_ALV_BLOCK_LIST_APPEND
3. REUSE_ALV_BLOCK_LIST_DISPLAY
These function modules should be used in the same order. Based on the no of
internal tables that are needed to be displayed those many times
REUSE_ALV_BLOCK_LIST_APPEND function module should be used.
HIERARCHIAL DISPLAY
See the sample program with hierarchical display.
REPORT ZALV .
TYPE-POOLS SLIS.
DATA KEY TYPE SLIS_KEYINFO_ALV.
TABLES VBAK.
SELECT-OPTIONS S_VBELN FOR VBAK-VBELN.
CH(1),
VBELN TYPE VBAK-VBELN,
ERDAT TYPE VBAK-ERDAT,
ERZET TYPE VBAK-ERZET,
END OF ITAB.
VBELN TYPE VBAP-VBELN,
POSNR TYPE VBAP-POSNR,
MATNR TYPE VBAP-MATNR,
END OF ITAB1.
SELECT VBELN

ERDAT
ERZET FROM VBAK
INTO CORRESPONDING FIELDS OF TABLE ITAB
WHERE VBELN IN S_VBELN.
SELECT VBELN
POSNR
MATNR FROM VBAP
INTO TABLE ITAB1
WHERE VBELN IN S_VBELN.
FCAT-REF_TABNAME = 'VBAK'.
FCAT-COL_POS = '1'.
FCAT-FIELDNAME = 'VBELN'.
APPEND FCAT.
CLEAR FCAT.
FCAT-COL_POS = '2'.
FCAT-FIELDNAME = 'ERDAT'.
APPEND FCAT.
CLEAR FCAT.
FCAT-COL_POS = '3'.
FCAT-FIELDNAME = 'ERZET'.
APPEND FCAT.
CLEAR FCAT.
FCAT-REF_TABNAME = 'VBAP'.
FCAT-COL_POS = '1'.
FCAT-TABNAME = 'ITAB1'.
FCAT-FIELDNAME = 'VBELN'.
APPEND FCAT.
CLEAR FCAT.
FCAT-COL_POS = '2'.
FCAT-FIELDNAME = 'POSNR'.
APPEND FCAT.
CLEAR FCAT.
FCAT-COL_POS = '3'.
APPEND FCAT.
CLEAR FCAT.
KEY-HEADER01 = 'VBELN'.
LAYOUT-EXPAND_FIELDNAME = 'CH'.
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'

EXPORTING
* I_CALLBACK_PROGRAM =

IS_LAYOUT = LAYOUT
* IT_EXCLUDING =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* I_SAVE = ' '
* IS_VARIANT =
* IT_EVENTS =
* IT_EVENT_EXIT =
I_TABNAME_HEADER = 'ITAB'
I_TABNAME_ITEM = 'ITAB1'
* I_STRUCTURE_NAME_HEADER =
* I_STRUCTURE_NAME_ITEM =
IS_KEYINFO = KEY
* IS_PRINT =
* IS_REPREP_ID =
* I_BYPASSING_BUFFER =
* I_BUFFER_ACTIVE =
* IMPORTING
TABLES
T_OUTTAB_HEADER = ITAB
T_OUTTAB_ITEM = ITAB1
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
ENDIF.
CONTROL BREAK STATEMENTS
Control break statements are usually used to find out totals and subtotals. The
control break statements are…
1. AT FIRST.
………..
………..
ENDAT.
2. AT LAST.
………..
………..
ENDAT.

3. AT NEW <FIELD>.
………..
………..
ENDAT.
4. AT END OF <FIELD>
………..
………..
ENDAT.
5. ON CHANGE OF <FIELD1> <FIELD2>…..<FIELD N>

………..
………..
ENDON.
Pre-requisites for using Control break statements Control break statements should be
used in side the loop but on change of can be used outside the loop. Before using the
control break statement the internal table should be sorted by the field on which control
break statement is going to be used.
AT FIRST:- This is triggered at the first record of the internal table. This is triggered
only once. It is usually used to write the heading to columns while displaying the records
of internal table.
AT LAST:- This is also triggered only once at the last record of the internal table. This is
used to find out grand totals of numeric values.
AT NEW <FIELD>:- This is triggered at the starting of every new record based on a
particular field. It is used to calculate sub totals.
AT END OF <FIELD>:- This is triggered at the end of every new record based on a
particular field. It is also used to find out sub totals.
DIFFERENCES BETWEEN AT NEW <FIELD> AND AT END OF <FIELD>.
Both are used to find out subtotals but the difference is point of triggering.
1. At new is triggered at the starting of new record, but at last is triggered at the end
of the record.
2. At new checks previous record, but at last checks next record.

DIFFERENCES BETWEEN AT NEW AND ON CHANGE OF
1. At new should be used inside the loop, but on change of can be used outside the
loop also.
2. At new takes only one field, but on change of can take multiple fields.
3. Let us assume that an internal table is having f1, f2, f3 , f4 and f5 fields and if at
new is applied on f3 field it will be triggered for every change in f1, f2 and f3
fields, but on change of will be triggered for only changes in f3.
MODULE POOL PROGRAM
Dialogue program is a screen with flow logic. Module pool program is used to
declare the variables that are needed in dialogue program and it is also used to write the
flow logic to handle user actions on the screen. For designing the screens the T-code is
SE51. For writing the module pool program the T-code is SE38, here the program type
should be chosen as module pool program. In module pool program it is mandatory that
the Module pool program name and dialogue program name should be same. Module
pool programs are not self executable. They should be executed using T-code. To create a
T-code we have to use T-code SE93.
EVENTS IN MODULE POOL PROGRAM
1. Process before output (PBO)

2. Process after input (PAI)
3. Process on value-request (POV)
4. Process on help-request (POH)
PROCESS BEFORE OUTPUT:- This event is triggered before the screen is displayed.
This event is used to assign some default values to screen fields. With those values the
field will be displayed.
PROCESS AFTER INPUT:- This event is triggered after giving input to the screen
fields. This is used to handle user action actions on the screen.
PROCESS ON VALUE-REQUEST:- This is used to give F4 help to screen fields.
PROCESS ON HELP-REQUEST:- This is used to give F1 help to screen fields.
The in the module pool program should be written between module and
endmodule.
AT EXIT-COMMAND:- It is used to go to the leave the screen or process some logic

even though some of the mandatory fields of a screen not filled.
SY-UCOMM:- It is a system variable used to catch the function code that is triggered
for user actions on the screen.

OK_CODE:- It is used as substitute for sy-ucomm.
BDC (BATCH DATA COMMUNICATION)
BDC programs are used to move the data from legacy system to SAP system. Old
system or non-SAP system is called legacy system. Most of the cases old data is used for
business analysis purpose, for taking intelligent business decisions. Some times it may be
used for reference purpose like paying taxes to the government or for paying dividends to
the share holders user etc.
Usually BDC programs are run in background. BDC programs take much time for
the execution which depends on the data to be uploaded. Basis people set the time for the
execution of a program. The program should be executed in the stipulated time set by the
basis people. If it is not executed in stipulated time the program goes to short dump. So
BDC programs can not be executed in the stipulated time set by basis people. By default
the standard time for the execution will be 10 minutes. There is no time constraint for
background jobs.
Second thing is BDC programs are not urgent programs. They are scheduled to
run at the time when server is usually free. Because of these two reasons BDC programs
are run in back ground.
SM36 T-code is used to run the programs in back ground. SM37 T-code is used
to see the output of back ground jobs. The output of back ground jobs is stored in spool
request number. SP01 T-code is used to see spool request numbers. Back ground jobs are
run at server level.
If the program is scheduled to run in background and if it is having the selection-

screen, it is mandatory to create a variant for the program. From the variant the back
ground job takes the input at run time.
VARIANT: - It is a selection-screen with filled in values. There is no restriction on no of

variants for a program. Usually all the test conditions of a program are saved as variants.
To create a variant for a program , enter the data in selection-screen fields and
press save button. System asks for name and description, give them and press save
button.

Variants are client dependent. We have earlier discussed that all SE38
programs are client independent, but a variant created for a program in one client can not
be seen in other clients. That is the meaning of client dependent. To move the variants
from one client to another client we have to run the standard program RSTRANSP.
When I say standard program you have to go to SE38 and run the program. All the
variants are stored in TVARV table.
There are 5 steps for uploading the data from legacy system to SAP system.
1. Identify the file to be uploaded.
2. Move the data from flat file to internal table
3. Move data from internal table to data sets or application layer
4. Move data from data set to internal table
5. Move data from internal table to database.
Steps 3 and 4 are used when the BDC program is scheduled in back ground. Other
wise directly 1, 2 and 5th step.
Usually what ever the data that is needed to be uploaded will come to the desk
top. From there we try to upload the file into SAP database. Background jobs can not
recognize user’s desk top area, because they run at server level. Because of this reason

only we are having 3rd and 4th steps in between where we move the data into application
layer and take the data from application layer.
Usually one program will be written combining 1st, 2nd and 3rd steps. This
program is run in foreground. In this program we will not move the data into database. So
this program will not take much time to execute even though we are having lacks of
records to be uploaded.
Using 4th and 5th steps another program will be written which is scheduled in back
ground. Because already data has come to application layer background job can take data
from there.
Usually we upload the following types of files.

1. DAT file (ASCII+Tabulor separator).
2. comma separated file.
3. Excel sheet.
The logic will change based on the file to be upload. We have to remember that the
internal table used in BDC programs to get the data from flat file ( The uploading file)
should have all the fields declared as character type only. Otherwise junk values will
be uploaded. System will take care of conversion of data while uploading into data
base.
First we see the program to upload DAT file into internal table.
REPORT ZBDC .
parameters p_file type rlgrap-filename.

matnr(18),
mbrsh(1),
mtart(4),
maktx(35),
meins(3),
end of itab.
at selection-screen on value-request for p_file.

CALL FUNCTION 'F4_FILENAME'
EXPORTING
PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
* FIELD_NAME = ' '
IMPORTING
FILE_NAME = p_file
.
start-of-selection.
data p_file1 type string.
p_file1 = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = p_file1
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
* HEADER_LENGTH = 0

* READ_BY_LINE = 'X'
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = itab
* EXCEPTIONS
* FILE_OPEN_ERROR = 1
* FILE_READ_ERROR = 2
* NO_BATCH = 3
* GUI_REFUSE_FILETRANSFER = 4
* INVALID_TYPE = 5
* NO_AUTHORITY = 6
* UNKNOWN_ERROR = 7
* BAD_DATA_FORMAT = 8
* HEADER_NOT_ALLOWED = 9
* SEPARATOR_NOT_ALLOWED = 10
* HEADER_TOO_LONG = 11
* UNKNOWN_DP_ERROR = 12
* ACCESS_DENIED = 13
* DP_OUT_OF_MEMORY = 14
* DISK_FULL = 15
* DP_TIMEOUT = 16
* OTHERS = 17
.
IF SY-SUBRC <> 0.
ENDIF.
loop at itab.
itab-mbrsh,
itab-mtart,
itab-maktx,
itab-meins.
endloop.
In this program I am trying to upload 5 fields into internal table. My input to this
program is file path. For declaration of file path variable I have used RLGRAP-
FILENAME as reference. RLGRAP is a structure and FILENAME is the filed present
in that structure which is 128 characters long. You can directly declare it as 128
characters variable. Why I am saying only 128 characters is in the function module
F4_FILENAME the file_name filed is declared as 128 characters field. Son the
receiving variable in the program should also be of 128 characters. Otherwise system
gives short dump saying type conflict error.
F4_FILENAME:- This function module is to get the file path directly from any part of
the computer by double clicking the file name. If this function module is not used we
have to give the file path manually.
GUI_UPLOAD:- This function module is used to upload the DAT file and comma
separated file into internal table.

While sending the file path in GUI_UPLOAD function module the file path
variable is converted into string type. Because the variable FILENAME in
GUI_UPLOAD function module is declared as string type. That is the reason it is
converted into string type data.
The following file I have prepared as DAT file to upload into internaltable.
Logic for uploading comma separated files.
REPORT ZBDC .
TEXT(70),
END OF ITAB1.
matnr(18),
mbrsh(1),
mtart(4),
maktx(35),
meins(3),
end of itab.

EXPORTING

* FIELD_NAME = ' '
IMPORTING
FILE_NAME = p_file
.
start-of-selection.
p_file1 = p_file.
EXPORTING
FILENAME = p_file1
* FILETYPE = 'ASC'
* HAS_FIELD_SEPARATOR = 'X'
* HEADER_LENGTH = 0
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = itab1
* EXCEPTIONS
* NO_BATCH = 3
* INVALID_TYPE = 5
* NO_AUTHORITY = 6
* UNKNOWN_ERROR = 7
* DISK_FULL = 15
* DP_TIMEOUT = 16
* OTHERS = 17
.
IF SY-SUBRC <> 0.
ENDIF.
LOOP AT ITAB1.
SPLIT ITAB1 AT ','
INTO ITAB-MATNR ITAB-MBRSH ITAB-MTART ITAB-MAKTX ITAB-MEINS.
APPEND ITAB.
CLEAR ITAB.
clear ITAB1.
ENDLOOP.
loop at itab.
itab-mbrsh,
itab-mtart,
itab-maktx,
itab-meins.
endloop.

In comma separated files the whole line of the file is uploaded as single
record into the internal table. That is the reason I have taken two internal tables in the
program. One with only one filed and the second internal table with the fields that are
needed to be uploaded. First the data will come to the internal table with single field
with comma present between the fields. Then each record has to be splitted at comma
to move into respect fields of the second internal table which is containing the fields
that are needed to be uploaded. You can execute the above program in debug mode
for better understanding.
For uploading excel sheet data into internal table use

ALSM_EXCEL_TO_INTERNAL_TABLE Function module instead of
GUI_UPLAOD function module.
SEQUENTIAL FILES.
Application layers files are called data sets or sequential files. All the application
layer files can be seen in AL11 Transaction code. If no path is given in the creation of
datasets the data will be stored in SAPUSERS directory. If path is given the data will be
stored in that path.
For moving the data or retrieving the data the sequential file or data set has to be
opened. The opened data set has to be close. For opening the data set the syntax is…
OPEN DATASET ‘<DATASET NAME/FILE PATH>’ FOR

OUTPUT/APPENDING/INPUT IN TEXT MODE/BINARY MODE ENCODING
DEFAULT.
OPEN DATASET ‘<DATASET NAME/FILE PATH>’:- This statement opens a

dataset with particular name in given path. If path is not given the dataset will be opened
in SAPUSERS directory. If file is already present in application layer the system opens
the file. If file is not present in that application layer it creates and opens.
FOR OUTPUT:- If data set is opened in this mode we can send the data from internal
table to data set. If file is opened in this mode and if it is already present in application
layer the existing data in that file or dataset will be deleted and new data from internal
table goes into it.
FOR APPENDING:- In this mode also we can send the data from internal table to data
set. But the difference is if dataset is already present in application layer and if it is
containing data in it that will not be deleted . New records from internal table are added
or appended at the bottom of the data set.
FOR INPUT:- The dataset has to be opened in this mode to move the data from dataset
to internal table.

TEXT MODE:- The data will be transferred line by line.
BINARY MODE:- The data will be transferred character by character.
ENCODING DEFAULT:- The data will be converted into system understandable

format.
A sample program with these operations can be seen here.
REPORT ZBDC .

matnr(18),
mbrsh(1),
mtart(4),
maktx(35),
meins(3),
end of itab.

EXPORTING
* FIELD_NAME = ' '
IMPORTING
FILE_NAME = p_file
.
start-of-selection.
p_file1 = p_file.

EXPORTING
FILENAME = P_FILE1
FILETYPE = 'ASC'
* HEADER_LENGTH = 0
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = ITAB
* EXCEPTIONS
* NO_BATCH = 3
* INVALID_TYPE = 5
* NO_AUTHORITY = 6
* UNKNOWN_ERROR = 7

* DISK_FULL = 15
* DP_TIMEOUT = 16
* OTHERS = 17
.
IF SY-SUBRC <> 0.
ENDIF.
OPEN dataset 'TEST' FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
LOOP AT ITAB.
TRANSFER ITAB TO 'TEST'.
CLEAR ITAB.
ENDLOOP.
CLOSE DATASET 'TEST'.

REFRESH ITAB.
OPEN DATASET 'TEST' FOR INPUT IN TEXT MODE ENCODING DEFAULT.
DO.
READ DATASET 'TEST' INTO ITAB.
IF SY-SUBRC EQ 0.
APPEND ITAB.
CLEAR ITAB.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE dataset 'TEST'.
LOOP AT ITAB.
WRITE: / ITAB-MATNR,
ITAB-MBRSH,
ITAB-MTART,
ITAB-MAKTX,
ITAB-MEINS.
ENDLOOP.
In this above program I did not give the file path for storing in application layer.
Hence it is stored in SAPUSERS directory.
If dataset is not closed and if it is opened in another mode the system goes to short
dump. Hence it is required to close the dataset after required operation is over. Then only
open in another mode.
Now we will see how to move the data into database.
There are 2 methods to upload the data into SAP.
Direct iput method
Batch input recording

DIRECT INPUT METHOD: In this method we use SAP standard programs to upload
the data into SAP.
BATCH INPUT RECORDING:- In this method we write our own programs to upload
the data into SAP.
In each of these methods we are internally having 3 more methods.

1. Call Transaction method
2. Session method
3. LSMW (Legacy system migration work bench)
For creation of any data in SAP, SAP has given standard transaction codes. Some
them are….
1. MM01 Material creation

2. XK01 Vendor creation
3. XD01 Customer creation
4. ME21 Purchase order creation
5. VA01 Sales order creation
6. VF01 Invoice creation
7. VL01 Delivery creation
So we run the required transaction to create any thing in SAP. In these transaction
codes we will be entering the data into screen fields. Once you save the transaction the
data entered into screen fields will go and sit in the respective tables where they are
needed to be saved.
Let us analyze with MM01 transaction code. Once you enter into MM01
transaction code in the first screen you can see material number, Industry
sector(MBRSH) and Material type(MTART). Material number is not mandatory. If you
give the material number with that material number material will be created. Other wise
system generates material number. So give mechanical engineering in industry sector
filed and finished product in material type filed.

When you press enter you will get the following screen with views where we have
to select the views. In that I have selected one view i.e. Basic data.

Once you press enter you enter into another screen where you have to give
material description (MAKTX) and unit of measure(MEINS) and press save.

In the above case system has created a material with material number 743. This is
the simple way to create a material. In this Transaction code we have given only
mandatory fields. Without giving these fields as input we can not create a material. In this
T-code we have entered MBRSH,MTART,MAKTX and MEINS fields.
We know that MBRSH, MTART and MEINS fields are present in MARA table.
When you open the MARA table, against material 743 we can find the data entered in
MBRSH, MTART and MEINS fields. But MAKTX is present MAKT table. If you open
the MAKT table, the description that I have given for the material i.e. TATA SAFARI
can be seen there against the material number 743.

In the above transaction code I have entered data into screen fields. The system
has taken care to move into respective tables.
Till now in the above programs we have seen how to move the data into internal
tables. So now our data has come into internal table. Our duty is to move the data present
in internal table into respective screen fields.
For this we require to know the program name of the T-code, Screen name and
filed name. If we know these things we can the send the data present in internal table into
screen fields. Finding all these things for individual fields to be uploaded is very difficult.
Because of this reason SAP has come up with a concept of recording. T-code for
recording is SHDB. Recording records every thing what we do on the screen. Recording
gives Program name, Screen number, Beginning of new screen indicator, Field name
and Field value. There should be a structure which is present with us which is containing
these 5 fields so that we can fill the values into those fields and send into recording steps.
The standard structure is BDCDATA.
BDCDATA structure is having following 5 fields.

1. Program
2. Dynpro
3. Dynbegin

4. Fnam
5. Fval.
There are 2 methods to upload the from legacy system to sap system.
1. Direct input method
2. Batch input recording
In each of these methods we are having internally 3 methods.
1. Call transaction method
2. Session Method
3. LSMW (Legacy System Migration Workbench)
Now we see the steps in recording.
1. SHDB
2. Press New Recording
3. Giving recording name
4. Give T-code to be recorded
5. Press start recording
6. Execute the T-code until save
7. Save the tabular format generated
8. Back
9. Select the recording name
10. Press program button
11. Give program (System will generate the program with that name)
12. Select radio button transfer from recording
13. Enter
14. Give Title
15. Press source code
16. Give package and save
17. Enter (You can see the program generated)
18. Select the program from the line after perform open_group.
19. Till a line above transaction code and copy
20. Paste it between loop at endloop in the program which you have written for
uploading the data from flat file to internal table.
21. Copy the from the include present in the recorded program and paste at the
bottom of the program.
CALL TRANSACTION
In this method we use one statement between loop and endloop after recording
steps.
Call transaction <’Transaction Name’> using BDCDATA Mode ‘<A/E/N>’ update

‘<S/A/L>’.

BDCDATA is the reference structure taken for moving the data into recording
program.
There are three modes available in call transaction method.
1. All screen mode (A).
2. Error screen mode (E)
3. No screen mode (N)
In all screen mode we can see all the screens in front of us with fields filled in with
values. In every screen we have to presenter. In Error screen mode we can see only error
screens. Correct the errors and press enter. In NO screen mode we can’t see any screen in
front of us.
There are three update modes available in call transaction method.
1. Synchronous (S).
2. Asynchronous (A)
3. Local (L)
Synchronous:- In this update mode for every the control will wait until all the main
tables and child tables are updated. Then only next starts moving into database.
Asynchronous:- In this mode the next record starts moving into database after previous
record is updated into some of the tables. The control will not wait until all the main
tables and child tables are updated for every record.
Local:- In this data is stored in local work process and then it is later updated into
database.
In call transaction method the user has to handle the errors while uploading the
data into database. You can see the following program with call transaction.
report ZBDC100 .
PARAMETERS P_FILE TYPE RLGRAP-FILENAME.
DATA BDCDATA TYPE BDCDATA OCCURS 0 WITH HEADER LINE.

MBRSH(1),
MTART(4),
MAKTX(35),
MEINS(3),
MATKL(9),
END OF ITAB.
DATA: INDEX(5),
TEXT(50).
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
EXPORTING
* FIELD_NAME = ' '
IMPORTING

FILE_NAME = P_FILE
.
START-OF-SELECTION.
DATA P_FILE1 TYPE STRING.
P_FILE1 = P_FILE.
EXPORTING
FILENAME = P_FILE1
FILETYPE = 'ASC'
* HEADER_LENGTH = 0
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = ITAB
* EXCEPTIONS
* NO_BATCH = 3
* INVALID_TYPE = 5
* NO_AUTHORITY = 6
* UNKNOWN_ERROR = 7
* DISK_FULL = 15
* DP_TIMEOUT = 16
* OTHERS = 17
.
IF SY-SUBRC <> 0.
ENDIF.
LOOP AT ITAB.
INDEX = SY-TABIX.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
'RMMG1-MATNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RMMG1-MBRSH'
ITAB-MBRSH.
perform bdc_field using 'RMMG1-MTART'
ITAB-MTART.
'MSICHTAUSW-DYTXT(01)'.
'=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
'X'.

'=BU'.
perform bdc_field using 'MAKT-MAKTX'
ITAB-MAKTX.
'MARA-MATKL'.
perform bdc_field using 'MARA-MEINS'
ITAB-MEINS.
perform bdc_field using 'MARA-MATKL'
ITAB-MATKL.
perform bdc_field using 'MARA-MTPOS_MARA'
'NORM'.
CALL TRANSACTION 'MM01' USING BDCDATA MODE 'A' UPDATE 'S'.

If sy-subrc ne 0.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
* ID = SY-MSGID
LANG = 'EN'
* NO = SY-MSGNO
* V1 = SY-MSGV1
* V2 = SY-MSGV2
* V3 = SY-MSGV3
* V4 = SY-MSGV4
IMPORTING
MSG = TEXT
* EXCEPTIONS
* NOT_FOUND = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
ENDIF.
CONCATENATE INDEX TEXT INTO TEXT SEPARATED BY '.'.

WRITE : / TEXT.
ENDIF.
REFRESH BDCDATA.
ENDLOOP.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.

CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
*----------------------------------------------------------------------*
* Insert field *
*----------------------------------------------------------------------*
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
* ENDIF.
ENDFORM.

FORMAT_MESSAGE:- This function module is used to catch all the messages that are
generated by system at runtime.
When ever there is an error in the record the call transaction statement written will
be failed. That is the reason I have used there sy-subrc.
SESSION METHOD.
Differences between call transaction and session method.
1. In call transaction updation is immediate but in session method updation is not

immediate.
2. In call transaction user has to handle errors but in session system handles the
errors.
3. In call transaction updation can be synchronous or asynchronous or local but in
session method updation by default synchronous.
4. Call transaction returns sy-subrc value but session will not return sy-subrc value.
In session method the data will be stored intermediately in session. After processing
the session only the data will be moved into data base. For processing the session the
T-code is SM35.
SESSION:- It is an intermediate memory area where data with flow logic is stored. It is
intermediate between internal table and data base table. A session can not be processed
on the date on which it is created. A session can not be processed if it is processed
successfully. If session is having error it can be processed any number of times.
In session method we have to use 3 function modules.

1. BDC_OPEN_GROUP
2. BDC_INSERT
3. BDC_CLOSE_GROUP
BDC_OPEN_GROUP: - This function module is used to create a session with

particular name.
BDC_INSERT:- This function module is used to move flow logic and data into session.
This function module should be called between the loop and endloop after recording
steps.
BDC_CLOSE_GROUP:- This function module should be used to close the session. If

this function module is not used the session will be created but we can’t process the
session.
The sample program by using session method is …….

REPORT ZBDC .

mbrsh(1),
mtart(4),
maktx(35),
meins(3),
matkl(10),
end of itab.
DATA DATE TYPE SY-DATUM.
DATA BDCDATA TYPE BDCDATA OCCURS 0 WITH HEADER LINE.

EXPORTING
* FIELD_NAME = ' '
IMPORTING
FILE_NAME = p_file
.
start-of-selection.
p_file1 = p_file.

EXPORTING
FILENAME = P_FILE1
FILETYPE = 'ASC'
* HEADER_LENGTH = 0
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = ITAB
* EXCEPTIONS
* NO_BATCH = 3
* INVALID_TYPE = 5
* NO_AUTHORITY = 6
* UNKNOWN_ERROR = 7
* DISK_FULL = 15
* DP_TIMEOUT = 16
* OTHERS = 17

.
IF SY-SUBRC <> 0.
ENDIF.
DATE = SY-DATUM - 1.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
* DEST = FILLER8
GROUP = 'ZUSA'
HOLDDATE = DATE
* KEEP = 'X'
USER = SY-UNAME
* RECORD = FILLER1
* PROG = SY-CPROG
* IMPORTING
* QID =
* EXCEPTIONS
* CLIENT_INVALID = 1
* DESTINATION_INVALID = 2
* GROUP_INVALID = 3
* GROUP_IS_LOCKED = 4
* HOLDDATE_INVALID = 5
* INTERNAL_ERROR = 6
* QUEUE_ERROR = 7
* RUNNING = 8
* SYSTEM_LOCK_ERROR = 9
* USER_INVALID = 10
* OTHERS = 11
.
IF SY-SUBRC <> 0.
ENDIF.
LOOP AT ITAB.

'RMMG1-MATNR'.
'/00'.
perform bdc_field using 'RMMG1-MBRSH'
ITAB-MBRSH.
perform bdc_field using 'RMMG1-MTART'
ITAB-MTART.
'MSICHTAUSW-DYTXT(01)'.
'=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
'X'.
'=BU'.
perform bdc_field using 'MAKT-MAKTX'
ITAB-MAKTX.
'MARA-MATKL'.

perform bdc_field using 'MARA-MEINS'
ITAB-MEINS.
perform bdc_field using 'MARA-MATKL'
ITAB-MATKL.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = 'MM01'
* POST_LOCAL = NOVBLOCAL
* PRINTING = NOPRINT
* SIMUBATCH = ' '
* CTUPARAMS = ' '
TABLES
DYNPROTAB = BDCDATA
* EXCEPTIONS
* INTERNAL_ERROR = 1
* NOT_OPEN = 2
* QUEUE_ERROR = 3
* TCODE_INVALID = 4
* PRINTING_INVALID = 5
* POSTING_INVALID = 6
* OTHERS = 7
.
IF SY-SUBRC <> 0.
ENDIF.
REFRESH BDCDATA.
ENDLOOP.
CALL FUNCTION 'BDC_CLOSE_GROUP'

* EXCEPTIONS
* NOT_OPEN = 1
* QUEUE_ERROR = 2
* OTHERS = 3
.
IF SY-SUBRC <> 0.
ENDIF.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.

CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
*----------------------------------------------------------------------*
* Insert field *
*----------------------------------------------------------------------*
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
* ENDIF.
ENDFORM.

After execution of this program a session with name ZUSA will be created.
Because it is given in the function module BDC_OPEN_GROUP under GROUP filed. I
have given holddate = date in the same function module. The date is reduced by 1
because I want to process it immediately today. If you don’t use that logic you can’t
process the session immediately after the execution of the program. You have to wait till
next day.
If you want to move the data into database you have to go to sm35 T-code and
process the session ZUSA. Then only the data will be moved into data base.
STEPS IN PROCESSING THE SESSION
1. Select the session to be processed.

2. Press process button
3. Select the mode radio button
4. Press process
STEPS IN VIEWING THE LOG
1. Select the session

2. Press log button
3. Select the session
4. Press Display
LSMW (LEGACY SYSTEM MIGRATION WORK BENCH)
This is the tool given by SAP to upload the data from legacy system to SAP
system. There are 4 methods available in this LSMW.
1. Direct input method
2. Batch input method
3. Business document method (BAPI)
4. Intermediate document method (IDOC)
In LSMW we have different steps. We have to run the steps sequentially
so that the data will move into data base. The below example will give you clear cut idea
about the steps present in LSMW, How to run them. In this example I have used direct
input method to upload customer master data into database using SAP standard program.
As an alternative to using ‘Transaction recording’, you could also use a standard

SAP object to update Customer Master Records. Business Object ‘0050’ is already
pre-defined in the system with standard Batch Input Interface Program ‘RFBIDE00’.
Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as
CUSTOMERS as shown in Figure 20.

Figure 20 LSMW Object with Standard SAP Object
Note! For the Demo example 2, I will list only those steps that are different from the first
demo example.
Step 1: Maintain Object attributes
You will be updating the customer master records with the help of Standard Batch Input;
therefore, choose radio-button Standard Batch/Direct Input as shown in Figure 21.
Enter Object ‘0050’ for Customer Master records and default method ‘0000’ and click on
Save.
Figure 21 Standard Batch/Direct Input Object Attributes
Step 2. Maintain Source Structures
Give a name and a description to the source structure (Figure 8).
Figure 8 Source Structure

Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest
way is to click on ‘Table Maintenance’ icon to enter Fieldname, Type and Length for
each field as shown in Figure 9.
Figure 9 Source fields of source Structure
Note that your input file will have four fields as key fields and you need to update three
fields in the system.
Step 4: Maintain Structure Relations
Sales view of Customer Master is stored in table KNVV. Accordingly, you need to
update structure BKNVV. However, in addition, the Standard Object ‘0050’ also requires
updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure
relations for mandatory entries, you might get a message such as ‘Target structure
BKNA1 needs a relation to a source structure’.)
Even though you don’t want to update any fields in these structures, you need to create a
relationship with source structures. In all, you need to create relationship for four target
structures.
Create relationship between source structures XD02S with these target structures with
icon ‘Create Relationship’
Keep Cursor on these four target structures and click on icon ‘Create Relation’ and
structure relations are maintained as shown in Figure 22.

Figure 22 Structure Relation
Step 5: Maintain field mapping and conversion rules
-- Keep your cursor on ‘TCODE’ field and click on ‘Insert Rule’ icon

Figure 23 LSMW Conversion Rules
Choose radio button ‘Constant’ (Figure 23) to enter value ‘XD02’ transaction code.
-- Keep your cursor on field ‘KUNNR’ and click on ‘Assign source field’
icon
Choose source field ‘Customer’ from source structure ‘XD02S’. (See Figure 24.)

Figure 24 Assign Source fields
-- Similarly, choose source fields for Sales Organization, Distribution Channel, and
Division. (See Figure 25.)
Figure 25 Field Mapping and Conversion Rules
-- Scroll down to structure BKNVV fields and assign source fields to three fields Sales
Office, Sales Group, and Customer Group (Figure 26).

Figure 26 Field Mapping and Conversion Rules
Save and go back to main screen.
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be
used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab]
delimited with the first row as field names. It is present on my PC (local drive) as
C:\XD02.txt. (See Figure 13.)

Figure 13 File attributes
Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on
your local drive (C:\) and name it XD02.txt.

Figure 14 Source data in Excel file (saved as Tab delimited file)
Step 8: Assign files
Execute step ‘Assign Files’ (Figure 15) and the system automatically defaults the
filename to the source structure.
Figure 15 Assign file to Source Structure
Step 9: Read data
In this step, LSMW reads the data (Figure 16) from the source file (from your PC’s local
drive). You have the option to read only selected rows and convert data values to Internal
format.
Figure 16 Read Data
Step 10: Display read data
This step (Figure 17) is optional. If required, you can review the field contents for the

rows of data read.
Figure 17 Display Read Data
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format.
Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
When you convert data, LSMW automatically converts into the appropriate structure
layouts, as required by Standard program (RFBIDE00). (See Figure 27).
Figure 27 Converted data into multiple structures
Note that if you had only one record in source file, the converted file has four records.

Earlier, creating this input file, so that the standard interface program can read it, was a
big nightmare, the primary reason being that it could have multiple record layouts. Even
for a simple conversion with one input record, you would have to create this complex file
with many record layouts. The advantage of LSMW is that it prepares these multi-layout
files automatically.
Step 13: Create batch input session
Once source data is converted in internal format, you can create a BDC session to process
the updates (Figures 28 and 29).
Figure 28 Create BDC Session
Figure 29 BDC Session ‘CUST_OBJ’ created

Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input
session is a standard SM35 transaction for managing BDC sessions. Once you have
successfully executed the batch input session, the customer master records are updated in
the system. You can confirm this by viewing the customer master records (XD03).
No where in LSMW steps system asked for package. If package is asked , if we give the
package name system gives Transport request number (TRN). Using this TRN we can
move the object from one server to another server. But for LSMW we have to create
TRN manually. For that we have to follow the following path.

SCRIPTS
It is the integrated text management system of SAP. The output of scripts and
normal report will be same. But formatting is very easy using scripts. Usually scripts are
used for external purpose and reports are used for internal purpose. When specific format
is required in output we go for scripts.
In scripts we require layout set and print program. Layout set is used for
designing the output. That is page designing is done here. For this Transaction code is
SE71 (form painter).
Print program is used for writing the logic to get the data from data base. It is an
executable program which is written in SE38 T-code.
Attributes of form painter (SE71)

1. Header
2. Pages
3. Windows
4. Page windows
5. Paragraph Formats
6. Character Formats

HEADER:- It contains Basic settings and administrative data. Administrative data gives
history of the form and basic settings gives technical information about the form.
PAGES:- It is a logical memory area where output is formatted. It is a repository of

pages.
WINDOWS:- I t is a place on the page where output or data is formatted. Page has to be
divided into windows in order to hold the output. We can’t format the output outside the
windows. Windows is repository of windows.
Paragraph formats and Character formats are used for alignment or beautifying the
output.
TYPES OF WINDOWS
There are 3 types of windows.

1. Main window
2. Constant window
3. Variable window
MAIN WINDOW:- The window which can hold continuous text or which can call
page break is called main windows. When ever you are not sure of how much data you
are going to get into a window that window has to be created as main window.
CONSTANT WINDOW:- A window whose size and contents will not change from
page to page is called Constant window.
VARIABLE WINDOW:- A window whose size or contents will change from page to
page is called variable window.
Constant window and variable window can be used interchangingly.

Every script or layout should have at least one page. Every page should have at
least one main window and paragraph format.
STEPS TO BE FOLLOWED IN CREATION OF LAYOUTSET ( PAGE)
1. T-code SE71
2. Give form name
3. Give language
4. Press create button
5. Give description
6. Press page button
7. Give page name
8. Press enter
9. Give page description
10. Give next page name

11. Press page windows button
12. To copy main window Edit -- Create element
13. Double click main window. ( main window will be copied to the page)
14. Give some window width and height (eg. 10 cm and 10 cm)
15. To see the page format Settings -- Form Painter
16. Check the check box Graphical Form Painter
17. Press enter
18. To adjust the main window , drag it to the place where you want. You can change
the size also.
19. To create new windows right click create window.
20. Move the window to the position where it is needed and adjust the size.
21. To rename window Right click Rename.
22. To close page format Settings- Form painter
23. Un check the check box Graphical Form Painter
24. Press enter
25. To create paragraph format Press Paragraph formats push button
26. Give paragraph format name
27. Press enter
28. Give description
29. Press header
30. Press Basic settings
31. Give first page and Default paragraph
32. Save
33. To check errors form- check- Definition
34. To activate form - Activate.
This is how we have to design the page. The no of windows in the page depends
on page layout. Now I want to keep a logo in one of the windows of page. For that we
first have to upload the logo into sap. For uploading logo into sap the T-code is SE78.
It is used to upload only Bitmap images.
STEPS IN UPLOADING LOGO INTO SAP
1. Prepare a Bitmap Image

2. T-Code SE78
3. Expand graphics
4. Double click BMP.
5. Press import button
6. Give the path where image is present in you system
7. Give name to logo
8. Give description
9. Specify color image or Black and white image’
10. Press enter
The image will be uploaded into SAP with the name you have given in 7th step.

If the image is of .TIF format we have to run the standard program
RSTXLDMC to upload the image into SAP. The image will be stored on
document server. All the images will be stored in STXBITMAPS table.
Now my requirement is to insert the logo in one of the windows of the

form that I have designed .
STEPS IN INSERTING THE LOGO IN A PARTICULAR WINDOW
1. Go to Se71
2. Open the form in change mode
3. Select the window where you need to insert the logo ( for selecting double click)
4. Press text elements button
5. Insert Graphics
6. Press tab stored on document server
7. Give the logo name
8. Choose Black and white or color
9. Enter
10. System by default gives this code
11. BITMAP 'ENJOY' OBJECT GRAPHICS ID BMAP TYPE BCOL
12. Here enjoy is the logo name I have given
Now we will discuss how to write the print program. Print program is used to get
the data from data base and move the page windows of the form. In writing the print
program we have to take the help of 3 function modules.
1. OPEN_FORM:- This function module is used to open a layout set printing.

2. WRITE_FORM:- This function module is used to move the data from print
program to page windows. The movement of data is done using element.
3. CLOSE_FORM:- This function module is used to close the layout set printing. If
this is not used there will be no output and no printout.
The sample program is as follows.
REPORT ZFORM .
TABLES MARA.
END OF ITAB.
SELECT MATNR
MBRSH
MTART
NTGEW

BRGEW FROM MARA
INTO TABLE ITAB
CALL FUNCTION 'OPEN_FORM'

EXPORTING
* APPLICATION = 'TX'
* ARCHIVE_INDEX =
* ARCHIVE_PARAMS =
* DEVICE = 'PRINTER'
* DIALOG = 'X'
FORM = 'ZFORM10'
LANGUAGE = SY-LANGU
* OPTIONS =
* MAIL_SENDER =
* MAIL_RECIPIENT =
* MAIL_APPL_OBJECT =
* RAW_DATA_INTERFACE = '*'
* IMPORTING
* LANGUAGE =
* NEW_ARCHIVE_PARAMS =
* RESULT =
* EXCEPTIONS
* CANCELED = 1
* DEVICE = 2
* FORM = 3
* OPTIONS = 4
* UNCLOSED = 5
* MAIL_OPTIONS = 6
* ARCHIVE_ERROR = 7
* INVALID_FAX_NUMBER = 8
* MORE_PARAMS_NEEDED_IN_BATCH = 9
* SPOOL_ERROR = 10
* CODEPAGE = 11
* OTHERS = 12
.
IF SY-SUBRC <> 0.
ENDIF.
LOOP AT ITAB.
CALL FUNCTION 'WRITE_FORM'

EXPORTING
ELEMENT = 'ELE'
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
* IMPORTING
* PENDING_LINES =
* EXCEPTIONS
* ELEMENT = 1
* FUNCTION = 2
* TYPE = 3
* UNOPENED = 4
* UNSTARTED = 5
* WINDOW = 6
* BAD_PAGEFORMAT_FOR_PRINT = 7
* SPOOL_ERROR = 8
* CODEPAGE = 9
* OTHERS = 10

.
IF SY-SUBRC <> 0.
ENDIF.
ENDLOOP.
CALL FUNCTION 'CLOSE_FORM'

* IMPORTING
* RESULT =
* RDI_RESULT =
* TABLES
* OTFDATA =
* EXCEPTIONS
* UNOPENED = 1
* BAD_PAGEFORMAT_FOR_PRINT = 2
* SEND_ERROR = 3
* SPOOL_ERROR = 4
* CODEPAGE = 5
* OTHERS = 6
.
IF SY-SUBRC <> 0.
ENDIF.
In the above program I have used element in write_form function module. When
we are moving the data into form windows there should be something to receive it. We
are sending using element ELE. The receiving element name should be ELE. The code
that is to be written in form window text element where it is needed to be printed is…..

To get the output execute the print program. It will ask for the printer name. There
you enter LP01. It is a default printer.
STNADARD TEXT:- It is a reusable component. If same text is needed to be printed

in many forms, it is recommended to create a standard text and insert the text where
ever it is needed. If you want the text to be changed, change only standard text. The
change will be reflected in all the forms where this standard text is used. The T-code
to create a standard text is SO10.
We see the detailed use of standard text. Let us assume that my company wants to
give 10% discount on sales. In my implementation let us assume that I am having
100 forms. In these 100 forms I want DISCOUNT ALLOWED 10% at the bottom
of every form. So I write this statement in every form. Let us assume that the discount
is now changed to 20% instead of 10%. So now I have to go to every form and I have
to change discount 20%. But this is a laborious job. If you insert the standard text in
100 forms instead of hard coding., we can simply change the standard text when ever
the text is changed. The changes will be reflected in every form where the standard
text is used.

Standard text is client dependent. To move the standard or to transport standard
text run the standard program RSTXTRAN.
Standard text will be stored in the table STXH.
STEPS IN CREATION OF STANDARD TEXT
1. T-code SO10
2. Give name and press create
3. Give the text
4. Press save
STES IN INSERTING THE STANDARD TEXT IN FOR WINDOW
1. Go to Se71
2. Open form in change mode
3. Select the window where standard text is needed to be inserted
4. Press Text elements button
5. Insert text standard
6. Give text name
7. Press enter
System adds this code in the editor

SMART FORMS
It is enhanced version to SAP scripts. Transaction code is smartforms.
First we discuss about the differences scripts and smart forms.
1. Scripts are client dependent but smart forms are client independent.
2. Scripts are not self executable i.e. print program is compulsory, but smart forms
are self executable. On executing the smart form system generates function
module.
3. We can not write the logic in scripts but we can write the logic in smart forms.
4. Main window is compulsory in scripts but it is optional in smart forms.
5. Background logo is not possible in scripts but it is possible in smart forms.
6. There are character and paragraph formats in scripts but there are no character and
paragraph formats in smart forms
7. Labels are present in scripts but no labels in smart forms.
When ever you enter into smartforms under global settings you get three things.
1. Form attributes
2. Form interface
3. Global definitions

FORM ATTRIBUTES:- It gives the history and technical attributes of smart form
FORM INTERFACE: - The variables that are needed to be populated at run time should
be declared here.
GLOBAL DEFINITIONS:- The variables that are needed in the smart form should be
declared here.
Now we discuss about the steps in creation of smart forms.
1. T-code smartforms
3. To create logo window right click o page create Graphic
4. Give the logo name
5. The variables that are needed to be populated at run time should be declared under
form interface
6. The variables that are needed to be populated at run time should be declared under
Global definitions.
7. To write the select query or logic select the window right click create flow
logic  program lines
8. It is mandatory to give input parameters and output parameters
9. To write loop select the code Right click create flow logic - loop
10. To write the output select loop Right click Create  Text
11. Check for errors
12. Activate and Execute
13. Function module will be generated. Execute it
14. Give printer name LP01 (Default Printer)
15. Press print preview to see output
ENHANCEMENTS
These are used to add extra intelligence to SAP standard programs to suit the
business requirements. If we want to add extra code to SAP standard programs, if we go
for change mode system asks for access key. Instead of this, SAP has provided hooks
where we can write the code. These hooks are enhancement spots. If a code is written in
theses spots along with the normal program the code written in these spots is also
executed. There are two ways to enhance the SAP standard code.
1. User Exits
2. BADIS (Business Addins)
If user exits are used one time in any project it can not be reused. But Badis can
be used any no of times.

There are 4 types user exits.
1. Function module exit
2. Field exit
3. screen exit
4. Menu exit
Exits are defined at package level. So we want to enhance any T-code first we
have to find out the package for that T-code. Then we have to find out the exits present in
that package. For finding the exits present in a package we have to use SMOD T-code.
After finding the suitable exit for writing the code we have to use CMOD T-code.
STEPS IN FINDING THE PACAKGE
1. Go to the T-code to be enhanced

2. System  status
3. Double click program
4. Go to attributes
There you can find the package
STEPS IN SMOD
1. T-code SMOD
2. Press F4
3. Press information system
4. Give the package name found out previously
5. Press enter
6. Based on the description choose the relevant Exit
STEPS IN CMOD
1. T-code CMOD
2. Give project name
4. Give description
5. Press enhancement Assignments button
6. Give the exit name you have found in SMOD
7. Press components button
8. Double click exit
9. Double click include starting with Z
10. Press enter
11. Write the logic
12. check for errors and activate
13. Come back to the first screen of CMOD and activate the project.

BADIS (BUSINESS ADDINS)
Badis are also used to enhance SAP standard programs. These are based on OOPs
concepts. In these BADIs we take the help of SE18 and SE19 T-codes.
SE18 T-code is like SMOD which is used to find out the relevant BADI and SE19
T-code is used to write the logic. Like user exits BADIs are also defined at package level.
If you want to find out the BADI for any program first we have to find out the package in
which the program is stored, as we have found out in our exits.
STEPS IN SE18
1. T-code SE18
2. Press F4
3. Press In formation system
4. Give the Package
5. Press enter
6. Choose the relevant BADI.
STEPS IN SE19
1. T-code SE19
2. Give some implementation name
4. Under definition give the BADI name found out in SE18
5. Give description
6. Press interface Tab
7. Double click method
8. Write the code between method and endmethod and save
9. Press back
10. Double click name of implementation class
11. Activate
12. Press back
13. Active the Implementation
ALE AND IDOCS
ALE:- APPLICATION LINKING AND ENABLING

IDOC:- INTERMEDIATE DOCUMENT
ALE:- It is set of configurations made to transfer data from one system to another
system. Actually ALE forms a route between two systems. In that route Idoc will
travel.

IDOC:- It is a data container which contains the data that is to be transferred from
one system to another system.
The information sending system is called sender or source system or outbound
system. The information receiving system is called receiver or destination system or
inbound system. The Idoc which is taking the information from sending system is
called out bound Idoc and the Idoc which is bring the information to the destination
system is called inbound Idoc.
STRUCTURE OF IDOC
Every Idoc contains three types of records.

11. Control Record (EDIDC)
12. Data Records (EDIDD)
3. Status Records (EDIDS)
CONTROL RECORD:- It is like address on the post card which gives the information
about sender, receiver and type of data the idoc is holding. It will be always single record.
DATA RECORDS:- The actual data that is to be transferred is contained by data

records. It can be single or multiple records. Actually the data records internally contain
the segments and segments contain fields and fields contain values.
STATUS RECORDS:- It specifies about the actual position of the idoc. As idoc travels
different mile stones system gives different statuses. Using the status of the idoc we can
find out the position of the idoc.
1 to 49 statuses are used for out bound idoc

50 to 99 statuses are used for inbound idoc.
Important statuses are….

01 --- outbound idoc just created
30 --- ALE settings are ok
03 --- Idoc reached port
50 --- Inbound Idoc just created
51 --- Error in posting the document into data base
53 --- Document successfully posted in to data base
There are 2 types of Idocs.

1. Master Idoc
2. Communication Idoc
MASTER IDOC: - The data that is to be transferred is fetched from data base and
formatted into Idoc format. This Idoc is called master Idoc. This Idoc is not stored in data
base. This Idoc is not transferred. It’s life span is until communication Idocs are created.

COMMUNICATION IDOCS:- The recipient specific Idocs are called communication
Idocs. These Idocs are stored in data base. These Idocs are moved from source system to
destination system.
MESSAGE TYPE:- This specifies about the type of data the Idoc is holding. The
standard message types are …
1. MATMAS Material master data
2. CREMAS Vendor master data
3. DEBMAS Customer master data
PORT:- it specifies about how the data should be transferred from source system to
destination system. Transaction code for Port creation is WE21.Two important ports are..
1. T-RFC Port (Transactional RFC Port)
2. File Port
In T-RFC port the data will be moved in the form of memory buffers. In file port the
data will be transferred in the form of files.
REMOTE FUNCTION CALL (RFC):- It is used to define the character of

communication link between two system where the remote enabled function module is
intended to be executed. In ALE this RFC will be used to connect to the remote system.
Transaction for RFC is SM59.
For generation of Idocs SAP has given standard T-codes based on the type of data
you are going to transfer. The important T-codes are.
1. BD10 Material master push
2. BD11 Material master pull
3. BD12 Customer master push
4. BD13 Customer master pull
5. BD14 Vendor master push
6. BD15 Vendor master pull
You have to either run push or pull T-code. No need to run both the programs. If
you want to send the data from source system run push T-code. If you want to get the
data from destination system run pull T-code.
TRANSACTION CODES IN ALE
1. BD54 Create logical systems

2. SCC4 Assign logical systems to client
3. SM59 Create RFC
4. WE21 Create Port
5. WE20 Create partner Profiles
6. BD64 To create Distribution Model view

All these T-codes should be run in the same order. All these T-codes should be
run in both source and destination systems. If it is needed to transfer the data from one
client to another client run steps 1 to 5 in source system, run 5th step in destination system
and run 6th step in source system. The order should also be same.
To view the idocs use either WE02 or WE05 T-codes. T-code WE19 is the
testing tool for Idoc. T-code BD87 for mass processing of Idocs.


Documents 3357-ABAP+NOTES

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Documents 3357-ABAP+NOTES

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Documents 3357-ABAP+NOTES

Uploaded by

Copyright:

Available Formats

ABAP - ADVANCED BUSINESS APPLICATION PROGRAMMING LANGUAGE.

It is 4th generation language and it is a proprietary language of SAP.

TRANSACTION CODE :- It is flow of screens. Every screen is called a session.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 1

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 2

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 4

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 6

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 7

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 8

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 9

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 10

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 11

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 12

Let us assume that I have written the following program.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 13

The modified program is like this.

The output will be.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 14

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 15

PARAMETERS: - It is a keyword used to declare a variable of particular type which

Screen shot of the program is as follows.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 16

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 18

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 19

PARAMETERS A(10) TYPE C.

In this case we can input 10 characters at a time.

In character type variables the input given is automatically converted to Upper

PARAMETERS A(10) TYPE C LOWER CASE.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 20

Now we look into a simple program to add two numbers.

If PARAMETERS keyword is used to declare the variable, the values to that

If you see the selection-screen of above program it will be like this.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 21

SELECTION-TEXT: Selection-text is a text used to give meaningful identity to

Navigation is GOTO ----> TEXT ELEMENTS --- > SELECTION TEXTS.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 22

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 23

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 24

* THIS IS THE COMMENTED LINE.

WRITE / 'RAMESH'. " THIS STATEMENT IS USED TO DISPLAY RAMESH IN OUTPUT

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 25

/n -- Terminates present T-code and opens a new T-code.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 26

Sample program with these system variable is…….

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 27

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 28

DO LOOP SAMPLE PROGRAM

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 29

DEBUGGING:- It is a technique to see how control is moving while execution of a

BREAK POINT:- It is a line in the program where control is needed to be stopped

F5 --- > FOR LINE BY LINE EXECUTION.

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 30

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 31

ABAP NOTES | Ashik Shah. J | (+91) 9066094396 Page 32

MATHEMATICAL OPERATORS RELEVENT SAP OPERATORS

We can also use mathematical operators or relevant sap operators in

DO N TIMES SAMPLE PROGRAM