about dialog programming

Former Member — Thu, 13 Sep 2007 14:36:06 GMT

hi,

please any one tell me what actually ' call dialog'?

Re: about dialog programming

Former Member — Thu, 13 Sep 2007 14:39:47 GMT

<a href="http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9db635c111d1829f0000e829fbfe/content.htm">call_dialog</a>

Arya

Re: about dialog programming

Former Member — Thu, 13 Sep 2007 14:43:11 GMT

CALL DIALOG - Call a dialog module

&ABAP_BASIC_FORM4& CALL DIALOG dial.

Additions

1. ... AND SKIP FIRST SCREEN

2. ... EXPORTING f1 FROM g1 ... fn FROM gn

3. ... IMPORTING f1 TO g1 ... fn TO gn

4. ... USING itab ... MODE mode .

Effect

Calls the dialog module dial ; dial can be a literal or a variable.

To edit dialog modules, select Tools -> ABAP/4 Workbench -> Development -> Programming environ. -> Dialog modules .

Addition 1

... AND SKIP FIRST SCREEN

Effect

Processes the first screen of the dialog module in the background, if all required entry fields have been filled.

Addition 2

... EXPORTING f1 FROM g1 ... fn FROM gn

Effect

Specifies all data objects (fields, field strings, internal tables) to be passed to the dialog module. If the names in the calling and called programs are identical, you can omit " FROM g1 ". Otherwise, fi refers to the field in the dialog module, while gi specifies the field in the calling program.

Addition 3

... IMPORTING f1 TO g1 ... fn TO gn

Effect

Specifies all data objects (fields, field strings, internal tables) to be returned from the dialog module. If the names in the calling and called programs are identical, you can omit " TO g1 ". Otherwise, fi refers to the field in the dialog module, while gi specifies the field in the calling program.

Examples

DATA: BEGIN OF ITAB,

LINE(72),

END OF ITAB,

TITLE LIKE SY-TITLE.

CALL DIALOG 'RS_EDIT_TABLE'

EXPORTING SOURCETAB FROM ITAB

TITLE

IMPORTING SOURCETAB TO ITAB.

Notes

The system field SY-SUBRC is automatically exported and imported.

The unknown export/import data in the dialog module is ignored.

The data objects passed should have the same type or structure in the calling program and the dialog module.

Addition 4

... USING itab ... MODE mode

Effect

Calls the dialog module dial and also passes the internal table itab which contains one or more screens in batch input format.

If required, the dialog module may return a message to the system fields SY-MSGID , SY-MSGTY , SY-MSGNO , SY-MSGV1 , ..., SY-MSGV4 .

The specified processing mode mode mode can accept the following values:

'A' Display screen

'E' Display only if an error occurs

'N' No display

If the addition MODE is not specified, the processing mode is 'A' .

The return code value is set as follows:

SY-SUBRC = 0 The processing was successful.

SY-SUBRC <> 0 The dialog ended with an error.

Notes

All lock arguments are automatically exported and imported.

In contrast to a transaction, a dialog module does not form its own LUW (see Transaction processing ). Any update requests which occur there are not processed until the calling program executes a COMMIT WORK .

To return from the dialog module, use the key word LEAVE PROGRAM .

Note

Runtime errors

CALL_DIALOG_NOT_FOUND : The called dialog module is unknown.

CALL_DIALOG_WRONG_TDCT_MODE : The called dialopg module contains errors (incorrect entry in table TDCT ).

CALL_DIALOG_NAME_TOO_LONG : The name of a parameter is longer than permitted.

CALL_DIALOG_NO_CONTAINER : No memory for parameter transfer.

Regards

Vasu

Re: about dialog programming

Former Member — Thu, 13 Sep 2007 14:48:32 GMT

good

You call dialog modules using the CALL DIALOG statement:

CALL DIALOG <dialog>

[AND SKIP FIRST SCREEN]

[EXPORTING f1 FROM a1.... fn FROM an]

[IMPORTING f1 TO a1.... fn TO an]

[USING itab].

CALL DIALOG has the same syntax as CALL TRANSACTION. You can also pass values to the global data of the called program using the interface.

Although a dialog module occupies a new internal session, it runs in the same SAP LUW as the calling program. However, since they open a new session, they are less efficient than function modules in performance terms. Nevertheless, they are the only means of switching internal session without starting a new SAP LUW. You can only run an entire transaction within the SAP LUW of a calling program by linking the initial screen of the transaction with a dialog module.

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

thanks

mrutyun^

topic Re: about dialog programming in Application Development and Automation Discussions

about dialog programming

Re: about dialog programming

Re: about dialog programming

Re: about dialog programming