We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!
CALL DIALOG dialog $[ ${AND SKIP FIRST SCREEN$}
$| ${USING bdc_tab $[MODE mode$]$} $]
$[EXPORTING p1 FROM a1 p2 FROM a2 ...$]
$[IMPORTING p1 TO a1 p2 TO a2 ...$].
1. ... AND SKIP FIRST SCREEN
2. ... USING bdc_tab $[MODE mode$]
3. ... EXPORTING p1 FROM a1 p2 FROM a2 ...
4. ... IMPORTING p1 TO a1 p2 TO a2 ...
The statement CALL DIALOG calls the dialog module whose name is contained in a flat character-like data object dialog. The data object dialog must contain the name in uppercase letters. The following can be specified for dialog:
When the statement is executed, dialog is not evaluated until runtime (in both cases). If the dialog module specified in dialog is not found, an uncatchable exception is raised.
When calling the dialog module, the assigned ABAP program is loaded into a new internal session. The session of the calling program is preserved. In contrast to CALL TRANSACTION, the called program runs in the same SAP LUW as the calling program.
After the ABAP program is loaded, the event LOAD-OF-PROGRAM
is triggered and the dynpro defined as the initial dynpro of the dialog module is called. The dialog module is terminated when the corresponding
dynpro sequence
terminates upon reaching the next dynpro with dynpro number 0 or the program is exited using the statement LEAVE PROGRAM.
... AND SKIP FIRST SCREEN
Under the same conditions as for the statement CALL TRANSACTION, this addition suppresses the display of the
screen layout of
the initial dynpro. If the called dialog module has input parameters for the mandatory input fields of the initial dynpro, they can also be filled using parameter passing instead of
SPA/GPA parameters.
... USING bdc_tab $[MODE mode$]
This addition controls the called program by specifying a
batch input
table bdc_tab of the line type BDCDATA like in the statement CALL
TRANSACTION. Only MODE can be used here as an addition to control the processing.
If a
message is sent
in the called program, this message is available in the system fields sy-msgid, sy-msgty, sy-msgno, sy-msgv1, ..., sy-msgv4 after the call.
... EXPORTING p1 FROM a1 p2 FROM a2 ...
... IMPORTING p1 TO a1 p2 TO a2 ...
These additions can be used to assign the appropriate actual parameters a1, a2, ... to
the formal parameters p1, p2, ... of the dialog module. The formal parameters of a dialog module are always optional. They can have all data types except for reference types.
When loading the called program, the values of the actual parameters are assigned to the global data objects of the called program that are defined as formal parameters. If this data is linked with identically named
dynpro fields, they are not overwritten by any SPA/GPA parameters.
If IMPORTING is specified, the system field sy-subrc is inherited implicitly by the called dialog module and unknown formal parameters are ignored by the system.
Outside of classes, the additions FROM a1, FROM a2, ... and TO a1, TO a2,
... in the parameter lists can be omitted if the formal parameters and actual parameters have the same names.
Non-Catchable Exceptions
Leave us your contact details and we will call you back. Fields marked with * are mandatory.
We offer holistic SAP solutions from a single source to shape digital change and develop new business areas.
Switzerland
Schaffhausen
Germany
Mannheim, Düsseldorf, Munich
USA
Haverhill
Greece
Thessaloniki