G_EXPORT_PARAMETERS_GET SAP Function module

G_EXPORT_PARAMETERS_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name G_EXPORT_PARAMETERS_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GRWO
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM G_EXPORT_PARAMETERS_GET - G EXPORT PARAMETERS GET

CALL FUNCTION 'G_EXPORT_PARAMETERS_GET' "
* EXPORTING
*   no_device_change = SPACE    "               Indicator: No change of output device
*   display_only = SPACE        "               Indicator: Only display
*   flag_allow_save = SPACE     "               Indicator: Saving parameters is possible
*   flag_maintain_defaults = SPACE  "
*   flag_clear_vars = SPACE     "
  IMPORTING
    flag_save_parameters =      " lgrwo-save_parms  Indicator: Save parameters as default values
* CHANGING
*   device = ' '                " rgrwa-out_devi  Output Medium
*   format = ' '                " rgrwa-out_form  Output Format
*   format1 = ' '               " out_form1     Output Format (Addition)
*   file_name = SPACE           " lgrwo-out_file  File Name
*   pc_format = SPACE           " lgrwo-pc_format
*   pc_program = SPACE          " lgrwo-rw_program
*   pc_command = SPACE          " lgrwo-rw_command
*   pc_export_only = SPACE      " lgrwo-rw_exponly
  EXCEPTIONS
    CANCELED = 1                "               Processing terminated
    .  "  G_EXPORT_PARAMETERS_GET

ABAP code example for Function Module G_EXPORT_PARAMETERS_GET

The ABAP code below is a full code listing to execute function module G_EXPORT_PARAMETERS_GET including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_flag_save_parameters  
 
 TYPE LGRWO-SAVE_PARMS
.



DATA(ld_device) = some text here


DATA(ld_format) = some text here

DATA(ld_format1) = 'Check type of data required'.


DATA(ld_file_name) = some text here


DATA(ld_pc_format) = some text here


DATA(ld_pc_program) = some text here


DATA(ld_pc_command) = some text here


DATA(ld_pc_export_only) = some text here

DATA(ld_no_device_change) = 'some text here'.

DATA(ld_display_only) = 'some text here'.

DATA(ld_flag_allow_save) = 'some text here'.

DATA(ld_flag_maintain_defaults) = 'some text here'.

DATA(ld_flag_clear_vars) = 'some text here'.
.

CALL FUNCTION 'G_EXPORT_PARAMETERS_GET'
* EXPORTING
*   no_device_change =           ld_no_device_change
*   display_only =               ld_display_only
*   flag_allow_save =            ld_flag_allow_save
*   flag_maintain_defaults =     ld_flag_maintain_defaults
*   flag_clear_vars =            ld_flag_clear_vars
  IMPORTING
    flag_save_parameters =       ld_flag_save_parameters
* CHANGING
*   device =                     ld_device
*   format =                     ld_format
*   format1 =                    ld_format1
*   file_name =                  ld_file_name
*   pc_format =                  ld_pc_format
*   pc_program =                 ld_pc_program
*   pc_command =                 ld_pc_command
*   pc_export_only =             ld_pc_export_only
  EXCEPTIONS
    CANCELED =                   1
    .  "  G_EXPORT_PARAMETERS_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_device
 
 TYPE RGRWA-OUT_DEVI ,
ld_flag_save_parameters
 
 TYPE LGRWO-SAVE_PARMS ,
ld_no_device_change
 
 TYPE STRING ,
ld_format
 
 TYPE RGRWA-OUT_FORM ,
ld_display_only
 
 TYPE STRING ,
ld_format1
 
 TYPE OUT_FORM1 ,
ld_flag_allow_save
 
 TYPE STRING ,
ld_file_name
 
 TYPE LGRWO-OUT_FILE ,
ld_flag_maintain_defaults
 
 TYPE STRING ,
ld_pc_format
 
 TYPE LGRWO-PC_FORMAT ,
ld_flag_clear_vars
 
 TYPE STRING ,
ld_pc_program
 
 TYPE LGRWO-RW_PROGRAM ,
ld_pc_command
 
 TYPE LGRWO-RW_COMMAND ,
ld_pc_export_only
 
 TYPE LGRWO-RW_EXPONLY .



ld_device = some text here
ld_no_device_change = 'some text here'.

ld_format = some text here
ld_display_only = 'some text here'.
ld_format1 = 'Check type of data required'.
ld_flag_allow_save = 'some text here'.

ld_file_name = some text here
ld_flag_maintain_defaults = 'some text here'.

ld_pc_format = some text here
ld_flag_clear_vars = 'some text here'.

ld_pc_program = some text here

ld_pc_command = some text here

ld_pc_export_only = some text here