Hello,
CALL DIALOG - Call a dialog module
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.
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See No Implicit Field Names When Calling Dialog Modules
Effect
Calls the dialog module dial; dial can be a literal or a variable.
To edit dialog modules, choose Tools → ABAP Workbench, Repository Browser, Other objects → dialog modules.
Notes
Please consult Data Area and Modularization Unit Organization documentation as well.
You can use a namespace prefix with 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 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 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 dialog module contains errors (incorrect entry in table TDCT).
CALL_DIALOG_NAME_TOO_LONG: The name of a parameter is longer than permitted.
If useful reward.
Vasanth
Bluesky
