Ans 2 : SE81

Ans 3: There are various ways of starting a program:

 You can start a program from the Object Navigator object list using the context menu or
using the 'Test' icon.
 If the program has a transaction code, then this can be added to a menu. Then all you have to
do is click on the menu option with the mouse.
 You can add programs to the favorites list on the initial screen. Programs can also be made
available using the activity groups on the initial screen. Then all you have to do is select the
program in the hierarchy on the initial screen.

 Ans 4: All Repository objects that are created or changed must be assigned to the change
request for their corresponding project. Assign all of your Repository objects (development
classes, programs, and so forth) to this change request.
You can display all change requests in which you have a task using the 'Own requests'
pushbutton.
.

Ans 5: Projects are always implemented in a development system and then transported to the next
system. A decisive criterion for the combination of projects is therefore which Repository objects
need to be transported together because of their dependencies. More detailed information on
project organization is available in the unit entitled Software Logistics and Software Adjustment.
Repository objects are automatically linked to correction and transport systems when they are
assigned to a transportable development class (not $TMP).
After development has ended, Repository objects are transported into the test systems or
production systems by way of certain prescribed pathways.
The ABAP Workbench tool Workbench Organizer (WBO) organizes all development tasks
pertaining to Repository objects.

Ans : 6: ABAP programs are made up of individual statements.

 Each statement ends with a period.
 The first word in a statement is called a keyword.
 Words must always be separated by at least one space.
 Statements can be indented.
 Statements can take up more than one line.
 You may have multiple statements in a single line.
7.1. Analyzing by executing a program:
7.1.1 You need to add the code for an airline to the program. This information
can be displayed from the input field using F1.
7.1.2 The values permitted here depend on the contents of database table
SCARR. You can display possible entries help from the input field using F4.
7.1.3 The program displays detailed information on the airline company
selected. This information is first displayed on the screen and then as a list.
7.1.4 The program contains a selection screen with screen number 1000, a
screen with number 100 and a list.
7.1.5 The field name of the input field on the selection screen is pa_car and
the names of the output fields on the screen are sbc400_carrier-
carrid, sbc400_carrier-carrname and sbc400_carrier-
currcode. You can display the field names using F1  technical info, then
see the box with the heading Field description for batch input.

7.2. Analyzing using the program's object list

7.2.1 The program has the structures sbc400_carrier and wa_sbc400
and the elementary data object pa_car.
7.2.2 The variable pa_car belongs to the input field of the same name.
7.2.3 Screen 100 is processed using the statement CALL SCREEN 100..
7.2.4 The field name appears in an input field above the area for the screen
layout.
7.3 Navigating the program source code
7.3.1. The list is structured using the WRITE statement. The symbol / after the
WRITE statement creates a line break.
7.3.2. The SELECT statement is responsible for the database dialog. The data is
read from the database table SCARR. The database table name is specified
in the FROM clause of the SELECT statement. The database table has the
fields MANDT, CARRID, CARRNAME, CURRCODE and URL.
7.3.3. The information on the line to be read is in data object pa_car. This is in
the WHERE clause of the SELECT statement. Data object pa_car is
automatically filled with the selection screen input value as soon as the
user chooses the Execute function on the selection screen.