Dialog programming

[Former Member]

Hi,

In dialog programming, I want to place the link. That is I need one line with Underline In screen. If the user click the link means it will go to Other Page. Is It Possible?

Thanks.

[Santosh_Kezkhepatmelathil]

hi,

I think you Should Code that by using 'HTML' .

by using class : <b>cl_dd_document</b>

regards,

santosh

[RichHeilman]

Yes, it is and you don't really have to use HTML to do it. Simply create field in your screen and set the "Responds to double click" attribute and set the FCODE in the same dialog. Then in your PAI, you simply check for that FCODE, and fire the URL that you want using this coding.

call method cl_gui_frontend_services=>execute

EXPORTING

DOCUMENT = 'www.sap.com'.

Regards,

RIch Heilman

[Former Member]

Hi,

Thanks for your nice reply. I dont know the Function code for "Double Clicking".

Thanks.

[RichHeilman]

It can be anything you want. Just fill in the field in the dialog screen when you create the actually field in screen painter. Then in your PAI, you simply handle the function code.

case ok_code.
     when 'WHATEVER'.
*      Fire that static method I suggest above

endcase.

Regards,

RIch HEilman

[former_member491305]

Hi Viji,

For <b>double click</b> event in module pool program,You got to create one funtion code and attach that funtion code to Function key <b>'F2'</b> in GUI STATUS.

[Former Member]

Hi Viji,

Fcode for double click is &IC1

Reward points if helpful.

Regards,

Hemant

[Former Member]

DIALOG PROGRAMS

• You use dialog programs to execute transactions. The users of dialog programs in dialog sessions read and change database tables. Apart from the actual data processing (Open SQL), update and enqueue concepts are of great importance when programming dialogs.

• Dialog programs are not stand- alone

• To execute dialog programs, they must be linked to at least one screen that itself is linked to a transaction code. The transaction code determines the initial screen with which the dialog session starts.

• Dialog programs are controlled by screen flow logic

• The actual ABAP/4 dialog program is a so-called module pool. A module pool contains a collection of dialog modules that are called by the screen flow logic.

• To each module pool, at least one, but usually several screens are allocated. Each screen has flow logic. The flow logic consists of PBO (process Before output) and PAI (process After Input) blocks. This flow logic does not use the ABAP/4 programming language and the ABAP/4 Editor tool, but a special statement set and the Screen Painter tool, which you also use to layout screens. The flow logic mainly contains the chronologically ordered calls of the modules in the corresponding module pool.

• The collection of PBO flow logic, screen, and PAI flow logic is called Dynamic program (Dynpro). A module pool must have at least one dynpro. Each screen of a dialog session thus is the visible part of a dynpro, to which also the flow logic belongs. The processing logic of a dialog session is stored in the corresponding module pool in the form of ABAP/4 modules.

• The ABAP/4 modules in the module pool are separated into PBO and PAI modules. The PBO or PAI blocks of the flow logic of each dynpro of a module pool can call each PBO or PAI module of this module pool.

• You can use ABAP/4 statements in the processing logic of the module pool to control the chronology of the different dynpros. After starting a dialog session via the transaction code, which is firmly connected to a dynpro of the module pool, the screen flow logic passes user entries to the processing logic in the ABAP/4 module pool. The processing logic processes the user entries (database accesses) and, if required, defines the appropriate subsequent screens.