what is the difference between Dialogue programming and report programming?

[Former Member]

i worked on reports like classical,interactive and ALV

and also worked on Dialogue programming.

we can retrive and also we can do update the database tables using the above all methods, then what is the difference between REPORTS and DIALOGUE PROGRAMMING.

thanks in advance

Gani

[Former Member]

Hi,

The main difference between report programming and Dialog programming is, In report programming input will be screen and output will be list, but in the case of Dialog programming input will be screen and output will be screen.

In report we cant use table control and update DB but in the case of Dialog Programming we can create table control and update DB dynamically.

There are some of the difference between Reports and Dialog programming.

If helpful please reward points.

Regards,

DVNS.

[Former Member]

hi,

report is a program that retrives data from database.groups\filters according to different creteria and presents it on screen or as a printed list.these pgms support logical databases. reports are called type 1 program and executable programs.

dialog pgms:

the system displays a screen where the user can i/p data. as a reaction to the user i/p.processing continues. the ABAp/4 code written to control the transaction is maintained in a collection of programs that together from the module pool. dialog pgms are called Type M pgms and dialog programs.

rewrd if its useful

Edited by: Rajasekhar Reddy on Jan 24, 2008 10:34 AM

[Former Member]

Hi

Hope it will help you.

reward if help.

Normal report can be run straight away by executing it and useually has a selection criteria – Attributes : 1 online program

Module pool program cannot be run straight away. It first needs to display a screen – attributes : M module pool program

[Former Member]

report program can't desizn screen easyly.

alv oops concept not possible in report type program.

report screen 1000.

Dialogue programming can desizn easy.

alv oops concept possible in report type program.

pbo and pai

report screen 1 to 999.

[Former Member]

Here is a clear difference between the two programmings.

Report programs follow a relatively simple programming model whereby a user optionally enters a set of parameters (e.g. a selection over a subset of data) and the program then uses the input parameters to produce a report in the form of an interactive list. The output from the report program is interactive because it is not a passive display; instead it enables the user, through ABAP language constructs, to obtain a more detailed view on specific data records via drill-down functions, or to invoke further processing through menu commands, for instance to sort the data in a different way or to filter the data according to selection criteria. This method of presenting reports has great advantages for users who must deal with large quantities of information and must also have the ability to examine this information in highly flexible ways, without being constrained by the rigid formatting or unmanageable size of "listing-like" reports. The ease with which such interactive reports can be developed is one of the most striking features of the ABAP language.

The term "report" is somewhat misleading in the sense that it is also possible to create report programs that modify the data in the underlying database instead of simply reading it.

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.

Reward if useful.