GRW_EXTRACT_SUBMIT SAP Function module - Output Stored Report

GRW_EXTRACT_SUBMIT 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 GRW_EXTRACT_SUBMIT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM GRW_EXTRACT_SUBMIT - GRW EXTRACT SUBMIT

CALL FUNCTION 'GRW_EXTRACT_SUBMIT' "Output Stored Report
  EXPORTING
    is_extract_key =            " extract_key   Name of Stored Report
*   it_params =                 " grw_t_params  Report Writer: Table Type for Parameters and Select Options
*   i_to_sap_spool =            " flag          General Flag
*   is_pri_params =             " pri_params    Structure for Passing Print Parameters
*   is_arc_params =             " arc_params    ImageLink Structure
  EXCEPTIONS
    EXTRACT_INVALID = 1         "               Report Saved does not Exist
    NO_AUTHORITY = 2            "               No Authorization
    EXTRACT_LOCKED = 3          "               Extract cannot be Locked
    SUBMIT_NOT_POSSIBLE = 4     "               Extract cannot be Called
    .  "  GRW_EXTRACT_SUBMIT

ABAP code example for Function Module GRW_EXTRACT_SUBMIT

The ABAP code below is a full code listing to execute function module GRW_EXTRACT_SUBMIT 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_is_extract_key) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'GRW_EXTRACT_SUBMIT'
  EXPORTING
    is_extract_key =             ld_is_extract_key
*   it_params =                  ld_it_params
*   i_to_sap_spool =             ld_i_to_sap_spool
*   is_pri_params =              ld_is_pri_params
*   is_arc_params =              ld_is_arc_params
  EXCEPTIONS
    EXTRACT_INVALID =            1
    NO_AUTHORITY =               2
    EXTRACT_LOCKED =             3
    SUBMIT_NOT_POSSIBLE =        4
    .  "  GRW_EXTRACT_SUBMIT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_is_extract_key
 
 TYPE EXTRACT_KEY ,
ld_it_params
 
 TYPE GRW_T_PARAMS ,
ld_i_to_sap_spool
 
 TYPE FLAG ,
ld_is_pri_params
 
 TYPE PRI_PARAMS ,
ld_is_arc_params
 
 TYPE ARC_PARAMS .


ld_is_extract_key = 'Check type of data required'.
ld_it_params = 'Check type of data required'.
ld_i_to_sap_spool = 'Check type of data required'.
ld_is_pri_params = 'Check type of data required'.
ld_is_arc_params = 'Check type of data required'.