GRMG_BATCH_SCHEDULING SAP Function module - GRMG in Hintergrundverarbeitung verlegen/zurückholen

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

Associated Function Group: GRMG
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM GRMG_BATCH_SCHEDULING - GRMG BATCH SCHEDULING

CALL FUNCTION 'GRMG_BATCH_SCHEDULING' "GRMG in Hintergrundverarbeitung verlegen/zurückholen
  EXPORTING
*   job_freq_in_min =           " i
*   nr_parallel_tasks = 0       " i
*   server_group_name =         " rzlli_apcl    Logon/Server Gruppennamen
    move_grmg_to_batch =        " flag          'X' - GRMG ins Batch verlegen; Initial - GRMG-Ausführung ins DIA zurückholen
*   adjust_parallel_tasks =     " flag          'X' - Änderung in der Anzahl paralleler Tasks
  IMPORTING
    return_code =               " i             0 = okay, 1 mode already set, 2 user abort, 3 CCMS error, 4 batch error
    .  "  GRMG_BATCH_SCHEDULING

ABAP code example for Function Module GRMG_BATCH_SCHEDULING

The ABAP code below is a full code listing to execute function module GRMG_BATCH_SCHEDULING 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_return_code  
 
 TYPE I
.


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

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

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

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

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

CALL FUNCTION 'GRMG_BATCH_SCHEDULING'
  EXPORTING
*   job_freq_in_min =            ld_job_freq_in_min
*   nr_parallel_tasks =          ld_nr_parallel_tasks
*   server_group_name =          ld_server_group_name
    move_grmg_to_batch =         ld_move_grmg_to_batch
*   adjust_parallel_tasks =      ld_adjust_parallel_tasks
  IMPORTING
    return_code =                ld_return_code
    .  "  GRMG_BATCH_SCHEDULING

IF SY-SUBRC EQ 0.
  "All OK
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_return_code
 
 TYPE I ,
ld_job_freq_in_min
 
 TYPE I ,
ld_nr_parallel_tasks
 
 TYPE I ,
ld_server_group_name
 
 TYPE RZLLI_APCL ,
ld_move_grmg_to_batch
 
 TYPE FLAG ,
ld_adjust_parallel_tasks
 
 TYPE FLAG .


ld_job_freq_in_min = 'Check type of data required'.
ld_nr_parallel_tasks = 'Check type of data required'.
ld_server_group_name = 'Check type of data required'.
ld_move_grmg_to_batch = 'Check type of data required'.
ld_adjust_parallel_tasks = 'Check type of data required'.