UR_EXEC_SCHEDULE SAP Function module

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

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

Pattern for FM UR_EXEC_SCHEDULE - UR EXEC SCHEDULE

CALL FUNCTION 'UR_EXEC_SCHEDULE' "
  EXPORTING
    i_progname =                " progname
    io_realigner =              " cl_ur_realigner
    o_msg_handler =             " cl_ur_easy_msg_handler
    i_chgrun =                  " ur_chgrun
    i_status_type =             " ur_status_type
  EXCEPTIONS
    SCHEDULE_NOT_POSSIBLE = 1   "
    FAILED = 2                  "
    .  "  UR_EXEC_SCHEDULE

ABAP code example for Function Module UR_EXEC_SCHEDULE

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

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

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

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

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

CALL FUNCTION 'UR_EXEC_SCHEDULE'
  EXPORTING
    i_progname =                 ld_i_progname
    io_realigner =               ld_io_realigner
    o_msg_handler =              ld_o_msg_handler
    i_chgrun =                   ld_i_chgrun
    i_status_type =              ld_i_status_type
  EXCEPTIONS
    SCHEDULE_NOT_POSSIBLE =      1
    FAILED =                     2
    .  "  UR_EXEC_SCHEDULE

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
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_i_progname
 
 TYPE PROGNAME ,
ld_io_realigner
 
 TYPE CL_UR_REALIGNER ,
ld_o_msg_handler
 
 TYPE CL_UR_EASY_MSG_HANDLER ,
ld_i_chgrun
 
 TYPE UR_CHGRUN ,
ld_i_status_type
 
 TYPE UR_STATUS_TYPE .


ld_i_progname = 'Check type of data required'.
ld_io_realigner = 'Check type of data required'.
ld_o_msg_handler = 'Check type of data required'.
ld_i_chgrun = 'Check type of data required'.
ld_i_status_type = 'Check type of data required'.