HI

Dialog-driven programs, or any program started using a transaction code, are known as SAP transactions, or just transactions. The term "transaction" is used in several different contexts in the IT world. In OLTP (Online Transaction Processing), where several users are working in one system in dialog mode, the term "transaction" stands for a user request. In conjunction with database updates, it means a change in state in the database.

Programs with type M can only be started using a transaction code, in which an initial screen is defined. Programs with type 1 can be started either using a transaction code, or by entering the program name in one of the transactions SE38 or SA38. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for dialog modules, and are therefore known as module pools. Type 1 programs, or function modules can also switch to dialog mode by calling screens using the CALL SCREEN statement. The program code of the corresponding executable program or function pool must then contain the corresponding dialog modules.

Programs that are partially or wholly dialog-driven cannot be executed in the background. They are therefore sometimes referred to as dialog programs.

Components of a Dialog Program

A dialog-driven program consists of the following basic components:

Transaction code

The transaction code starts a screen sequence. You create transaction codes in the Repository Browser in the ABAP Workbench or using Transaction SE93. A transaction code is linked to an ABAP program and an initial screen. As well as using a transaction code, you can start a screen sequence from any ABAP program using the CALL SCREEN statement.

Screens

Each dialog in an SAP system is controlled by one or more screens. These screens consist of a screen mask and its flow logic. Since the flow logic influences the program flow, screens are sometimes referred to as "dynamic programs". You create screens using the Screen Painter in the ABAP Workbench. Each screen belongs to an ABAP program.

The screen has a layout that determines the positions of input/output fields and other graphical elements such as checkboxes and radio buttons. The flow logic consists of two parts:

Process Before Output (PBO). This defines the processing that takes place before the screen is displayed.

Process After Input (PAI). This defines the processing that takes place after the user has chosen a function on the screen.

All of the screens that you call within an ABAP program must belong to that program. The screens belonging to a program are numbered. For each screen, the system stores the number of the screen which is normally displayed next. This screen sequence can be either linear or cyclic. From within a screen chain, you can even call another screen chain and, after processing it, return to the original chain. You can also override the statically-defined next screen from within the dialog modules of the ABAP program.

GUI status

Each screen has a GUI status. This controls the menu bars, standard toolbar, and application toolbar, with which the user can choose functions in the application. Like screens, GUI statuses are independent components of an ABAP program. You create them in the ABAP Workbench using the Menu Painter.

ABAP Program

Each screen and GUI status in the R/3 System belongs to one ABAP program. The ABAP program contains the dialog modules that are called by the screen flow logic, and also process the user input from the GUI status. ABAP programs that use screens are also known as dialog programs. In a module pool (type M program); the first processing block to be called is always a dialog module. However, you can also use screens in other ABAP programs, such as executable programs or function modules. The first processing block is then called differently; for example, by the runtime environment or a procedure call. The screen sequence is then started using the CALL SCREEN statement.

Dialog modules are split into PBO modules and PAI modules. Dialog modules called in the PBO event are used to prepare the screen, for example by setting context-specific field contents or by suppressing fields from the display that are not needed. Dialog modules called in the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.

Passing Data Between ABAP Programs and Screens

How are fields from ABAP programs displayed on the screen? And how is user input on the screen passed back to the ABAP program? Unlike in list programming, you cannot write field data to the screen using the WRITE statement. Instead, the system transfers the data by comparing the names of screen fields with the names of the ABAP fields in the program. If it finds a pair of matching names, the data is transferred between the screen and the ABAP program. This happens immediately before and immediately after displaying the screen.

Field Attributes

For all screen fields of a dialog screen, field attributes are defined in the Screen Painter. If a field name in the screen corresponds to the name of an ABAP Dictionary field, the system automatically establishes a reference between these two fields. Thus, a large number of field attributes for the screen are automatically copied from the ABAP Dictionary. The field attributes together with data element and domain of the assigned Dictionary field form the basis for the standard functions the screen executes in a dialog (automatic format check for screen fields, automatic value range check, online help, and so on).

Error Dialogs

Another task of the screen processor is to conduct error dialogs. Checking the input data is carried out either automatically using check tables of the ABAP Dictionary or by the ABAP program itself. The screen processor includes the error message into the received screen and returns the screen to the user. The message may be context-sensitive, that is, the system replaces placeholders in the message text with current field contents. In addition, only fields whose contents is related to the error and for which a correction may solve the error can accept input. See also Messages on Screens.

Data Consistency

To keep data consistent within complex applications, ABAP offers techniques for optimizing database updates that operate independent of the underlying database and correspond to the special requests of dialog programming. See also Programming Database Updates.

check these links

http://sap.mis.cmich.edu/sap-abap/abap09/index.htm

http://www.planetsap.com/Tips_and_Tricks.htm

http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm

TRANSACTION CODES

MENU PAINTER : SE 41.

SCREEN PAINTER : SE 51 .

BOTH : SE 80 .

? ONLY EXISTING PROGRAMS CAN BE VIEWED IN SE 41 , SO USE SE 38 .

CONCEPT :

STEPS :

1. GIVE TRANSACTION CODE SE 38 , CREATE A REPORT NAMED

" ZVRPRDIALOGTEST2 " . SAVE , CHECK , ACTIVATE IT .

2. THEN GIVE CODE SE 51. GIVE SAME PROGRAM NAME AS SE38 .

GIVE SCREEN NUMBER , PRESS CREATE .

3. GIVE SHORT DESCRIPTION . THEN CLICK ELEMENT LIST .

4. THE SCREEN COMES , TYPE " OKCODE " .

5. CLICK FLOW LOGIC , THE SCREEN COMES .

6. one screen will come.

7. SAVE . CHECK , ACTIVATE .

8. CLICK LAYOUT . SCREN PAINTER SCREEN COMES .

9. PRESS " F6 " . TYPE TABLE NAME , PRESS ENTER . THE SCREEN COMES .

10 . TO SELECT THE DESIRED FIELDS , CLICK THE " TO SELECT " AREA IN

EACH ROW , PRESS ENTER .

11 . AFTER CLICKING , PRESS ENTER .

12. THE FINAL SELECTION WIL COME

13 . GIVE THE NESSARY BUTTONS IN THE SCREEN PAINTER .

14 . DOUBLE CLICK IN EACH BUTTON GIVE LABLE , FUNCTION CODE .

15 . THE FINAL SCREEN WIL COME

16 . SAVE . CHECK .ACTIVATE. TO CHECK SCREEN PRESS F8.

17 . TO WRITE CODING : PRESS FLOW LOGIG .

18 . THE SCREEN COMES .

19 . DOUBLE CLICK FIRST EVENT ( MODULE STATUS _ 3000 ).

20 . PBO MODULE WINDOW COMES , PRESS TICK MARK .

21 . EDITOR COMES . SAVE .

TYPING PROGRAM IN THE EDITOR

Steps :

THE EDITOR WILL BE AS SHOWN ABOVE , NOW TYPE THE FOLLOWING CODE .

NOTE :

BEFORE TYPING CODE : TAKE COMMENTS FROM , THEN TYPE LIKE :

SET PF_STATUS ' PRSTATUS '

SET TITLEBAR 'PRTITLE' .

THE COMPLETE REPORT

&----

*& Module STATUS_3000 OUTPUT

&----

text

----

TABLES : ZVTIKFS.

DATA BEGIN OF INT_TAB OCCURS 0.

INCLUDE STRUCTURE ZVTIKFS.

DATA END OF INT_TAB.

DATA OKCODE LIKE SY-UCOMM.

DATA INDEX TYPE I VALUE 1.

----

MODULE STATUS_3000 OUTPUT *

----

........ *

----

MODULE STATUS_3000 OUTPUT.

SET PF-STATUS 'PRSTATUS'. "COMMENTS TOOK

SET TITLEBAR 'PRTITLE1'. " COMMENTS TOOK

SELECT * FROM ZVTIKFS INTO TABLE INT_TAB.

READ TABLE INT_TAB INDEX INDEX.

ZVTIKFS-NAME = INT_TAB-NAME.

ZVTIKFS-ADDRESS = INT_TAB-ADDRESS.

ZVTIKFS-PHONE = INT_TAB-PHONE.

ZVTIKFS-AREA = INT_TAB-AREA.

ENDMODULE. " STATUS_3000 OUTPUT

&----

*& Module USER_COMMAND_3000 INPUT

&----

text

----

MODULE USER_COMMAND_3000 INPUT.

CASE OKCODE.

WHEN 'INS'.

INSERT ZVTIKFS.

WHEN 'DEL'.

DELETE ZVTIKFS.

WHEN 'PRE'.

INDEX = INDEX - 1.

IF INDEX < 1.

INDEX = 1.

ENDIF.

WHEN 'NEX'.

INDEX = INDEX + 1.

IF INDEX > SY-DBCNT.

INDEX = SY-DBCNT.

ENDIF.

WHEN 'EXI'.

LEAVE PROGRAM.

ENDCASE.

ENDMODULE. " USER_COMMAND_3000 INPUT

TO COME TO DESIGN MENU

STEPS :

1 . TRANSACTION CODE : SE 80 . OBJECT NAVIGATOR WINDOW COMES .

NOTE : IF YOUR REOORT DOSENOT COME DO THE FOLLOWING PROCESS :

Vey useful link:

http://sap.mis.cmich.edu/sap-abap/abap09/index.htm

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

HI