Professional Documents
Culture Documents
Contents
Introduction to ABAP ABAP/4 Development Architecture Why Dialog programming Differences between report & Dialog programming Structure of a Dialog program with example transaction. Main components in Dialog programming. Screen painter in ABAP/4. Menu painter in ABAP/4. Interaction between screen painter and ABAP/4 modules. How communication is maintained in ABAP/4 modules. How to create simple dialog program with screen shots. Testing the transaction.
Introduction to ABAP
ABAP/4 Features
ABAP/4 is a programming language developed by SAP for the interactive development of application programs. ABAP/4 is a fourth-generation programming language that is the backbone of the R/3 System.
The language is event-driven with user actions and system events controlling the execution of the applications.
You can use the ABAP/4 programming language to create entirely new client/server applications, as well as extend existing R/3 modules, which is the most common use of the ABAP/4 language.
Reporting
R/3 Repository
Function Modules
ABAP/4 Development Workbench Architecture (cont) All programs are stored in the R/3 Repository.
A program is simply an object.
Double-clicking will navigate you to wherever the object is stored. Remote call functions let you access other systems.
2. Dialog programming
In dialog programming you use the Screen Painter to create screens and program the sequence in which they appear. You write an ABAP/4 program (ABAP/4 module pool) for your screens. This is a collection of dialog modules which are called by the flow logic of your screens. You use dialog programs for both reading and changing database tables.
ABAP/4 offers a variety of tools and language elements to meet the requirements for creating and running dialog programs
ABAP/4 module pool Each dynpro refers to exactly one ABAP/4 dialog program. Such a
dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
Sample Transaction
Transaction Explanation
This transaction consists of one dynpro only. The user enters the ID of an airline company and a flight number to request flight information. When the user chooses Display, the system retrieves the requested data from the database and displays it. SAP Transaction Screens An R/3 transaction is a series of business-related, logically consistent dialog steps. The transaction uses a program that conducts a dialog with the user. In a typical dialog, the system displays a screen on which the user can enter or request information. As a reaction on the the user input or request, the program executes the appropriate actions: it branches to the next screen, displays an output, or changes the database.
Transaction Flow
You use the Screen Painter and the Menu Painter to create and design screen templates and screen programs. You define the processing logic in an ABAP/4 program (module pool).
Data structures are defined in the ABAP/4 Dictionary. You can access these structures from the ABAP/4 program and when defining screen fields. The dialog processor controls the flow of your dialog program.
Dynpro
information. Fields can be text strings, input or output fields, radio buttons, checkboxes, or pushbuttons. An SAP dynpro consists of several components: Flow logic: Calls of the ABAP/4 modules for a screen. Screen layout: Positions of the texts, fields, pushbuttons, and so on for a screen. Screen attributes: Number of the screen, number of the subsequent screen, and others. Field attributes: Definition of the attributes of the individual fields on a screen.
DYNPRO PARTS
Parts of dynpro (screen) will be like this.
In its most simple form, a transaction is a collection of screens and ABAP/4 routines, controlled and executed by a dialog processor. The dialog processor processes screen after screen, thereby triggering the appropriate ABAP/4 processing for each screen.
For each screen, the system executes the flow logic that contains the corresponding ABAP/4 processing. The control passes from screen flow logic to ABAP/4 code and back.
Saving Program
Step 4 : Give the title and select the program attributes as TYPE : M Status : S. save it in the package.
Defining screens
Screen Attributes
Provide the details and save it.
Screen Layout
Click on lay out it will take to screen painter.
Screen Design
Transaction creation
Create transaction to test the report.
Test Transaction
Click on F8 to test the transaction on se93of transaction or give transaction name on command filed or on se80 right click on transaction->execute->direct processing. Provide the carrid and connid in the respective fields and click on display for result.
Result
The required details will be displayed on the corresponding fields in the same screen.
Conclusion
This is the way we will create dialog program . We can also insert, update the data from database with this screen by adding some other buttons and we can also Add table control on the screen by Using Dialog programming.
The PPT will cover the Basics ,I hope it will be helpful for beginners.
References
References: www.help.sap.com