controls in abap: General guidelines: The include name displayed for each type (Form, PBO, PAI, TOP)

should not be cha nged. Remember to give the OK-CODE field variable. All the global variable declarations need to be done in TOP include. Clear the screen contents as and when required. Give messages wherever required. Use any message class already created. Place the action (code) for each function code under a perform. Reuse the above performs if possible. --------------------------------------------------------------------------------------------------------------------1. Program Name: SAPMZnn_01 Create a screen 9000. Create two check boxes and I/O field next to it in display mode. See fig below. A pushbutton to display is provided. If any check box is checked and the pushbuttons clicked, display in the field Ch eck Box 1 or Check Box 2 respectively. Group two-radio buttons and place a single field next to it. Place a pushbutton with display. If clicked, then display in the field Radio Bu tton X where X is the radio button number. Place a push button EXIT to exit from program. Create a Transaction Znn_01 and execute the program . 2. Program Name: SAPMZnn_02 Create a screen 9000. Use the Tables: ZnnSFLIGHT, ZnnSBOOK. Accept Carrier Id, Connection Id & flight date. On pressing Display button, display details from ZnnSFLIGHT and accept Booking det ails. On Save, update ZnnSBOOK accordingly from the entered values. Place a push button EXIT to exit from program. Create a Transaction Znn_02 and execute the program Use 2 screens (9000 & 9001): Screen 9000 should be used for querying seat availability (Check for Seatsmax an d seatsocc in SFLIGHT) Scr 9001 should be called from Scr 9000 (if seats are available) and used for ca pturing booking details) Save in Scr 9001 should generate a BOOKID and save the entry in SBOOK, and also update the SEATSOCC in SFLIGHT. 3. Exercise 3 Repeat the previous exercise (flight booking) using a single screen and GUI-stat us. To begin with, the key fields relating to Flight (mandatory) should be in CHANGE mode, and the booking details should be in DISP mode. Also the SAVE button should not be visible at this stage After the Flight fields are entered and Check clicked, the flight fields should be in DISP mode and the booking fields should be in CHANGE mode. Also, the SAVE button should be activated in the Stand ard tool bar (No need for CHECK button). Area Menu: Create an Area menu consisting of all the previous reports/module-poo ls created by you 4. Table Control Create a Screen 9100 for the module pool SAPMZnn_TCTRL.

 The screen should have a table control and a header line. Screen Layout: Employee code Name DOB Date-of-Join Grade Department Application Toolbar: CHOOSE, DELETE. Standard Toolbar: SAVE, BACK, EXIT, CANCEL. Use table control to: Show a list of all Employee records. The list should be in display mode. Unless SAVED, no operation done on the list should be reflected in the database t able. Should allow selection of only one record at a time. 5 Tab Strip .Display the Flight Information (Flight details, Customer details, Booking detai ls and Schedule of flight) in a single screen using Tab strip. The screen should ask for a flight no. and the correspon ding details should be displayed in the table control. Create a screen 9000. Create a Tab strip with 2 tabs (for Flight details, Customer details) Create 2 sub screens (9001, 9002) for displaying Flight details, Customer details . Add the necessary program code and flow logic to process the TabStrip and alterna te between the 2 tabs. Create a transaction to test your tab strip. Use tables: ZnnSCUSTOM, ZnnSPFLI, ZnnSFLIGHT, ZnnSBOOK