Re: what is difference between report programming ...

Former Member · ‎2008 May 23

hi,

what is difference between report programming and dialog programming? plz provide some example code

bye

Former Member · ‎2008 May 23

Hi,

Welcome to SDN.

Report programming: Mostly involves around fetching data from tables as per user selection and displaying in user desired fashion.

Dialog programming: More of user active screens and data can be entered.

Over all you can say that Report program is displaying data

and dialog program is entering data in database table.. (Not alwayz..)

hope this helps..

search SDN and read more.. that way you will learn more than asking questions..

if you have doubt on any particular topic the you should ask questions and SDN will be happy to help you out..

thnx,

Ags...

Former Member · ‎2008 May 23

Hi,

go thru these links.

abap online links

Important link.

http://www.esnips.com/web/SAPAbapCertificationDocs/

http://www.esnips.com/web/SAPABAP

http://www.esnips.com/web/saparun-ebooks

http://www.esnips.com/doc/2a4c274b-b5b9-46b7-8ab5-5af47700a6c7/Command-List

http://www.esnips.com/doc/6bdb820f-f533-4517-a043-b64641b00490/TABC43-Data-Transfer

http://www.esnips.com/_t_/abap

regards

Sandeep Reddy

Former Member · ‎2008 May 23

Here is that difference

Report Programs:

1. Reports are stand alone programs.

2. We use reports to read data base tables & represent results in Lists

3. Reports are collection of processing blocks, controlled by System calls depending on events.

4. Reports can use LDBs or SELECT STATEMENTS

defined by DEVELOPER.

5.Reports can call Dialogue programs and vice versa.

Dialog Programming

1.Dialogue programs are not stand alone programs. (we

have to link the dialogue programs to at least one or

more SCREENS & TRANSACTION CODES)

2. We use Dialogue Programs to read & change

Database tables.

3.Dialogue programs are controlled by Screen flow logic.

4.Dialogue program is also called as Module pool program

or TRANSACTION.

5.These module pools are separated in to PBO and PAI

events.

<REMOVED BY MODERATOR>

Edited by: Alvaro Tejada Galindo on May 23, 2008 6:11 PM

Former Member · ‎2008 May 23

Hi,

Other differences between report and dialog program are

1. Report selection screen is used for input and list is used as output screen, whereas Dialog prg single screen is used both for input and output.

2. Dialog prg has addditional events like PBO,PAI,POH

3. Report prg can be scheduled in bkg.

4. In dialog prg has additional controls like subscreen, table control etc.

5. Database Updates is available in Dialog prg.

regards

Ravisankar

Former Member · ‎2008 May 23

ABAP programming

Basically reports are used to read database and represent the results in lists.

Reports are collections of processing blocks that the system calls depending on events.

We can use reports to evaluate data from database tables.

Reports are stand alone programs and controlled by events.

A report itself never creates events

steps in report:

Processing the selection screen

Reading the database

Evaluating the data and creating lists

Outputting a list.

1st u write simple logics, after that u can enhance the code as step by step.

http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm

http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm

http://www.sapdev.co.uk/reporting/reportinghome.htm

Dialog Programming

Structure of a Dialog Program

A dialog program consists of the following basic components:

Screens (dynpros)

Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).

The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.

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.

All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.

Check this link for basics.

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

Check this link for Dialog Programming/Table Control

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

Check this SAP Help for Dialog Program doc.

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm

Check this SAP Help link for Subscreens.

http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm

Check this link for subscreen demo program.

http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html

Also check this link too.

http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html