SAP Function Modules

UR_EXEC_CHECK_STATUS SAP Function module







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

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


Pattern for FM UR_EXEC_CHECK_STATUS - UR EXEC CHECK STATUS





CALL FUNCTION 'UR_EXEC_CHECK_STATUS' "
  EXPORTING
    io_realigner =              " cl_ur_realigner
    i_chgrun =                  " ur_chgrun
    i_status =                  " ur00_s_stat
    io_db_service =             " cl_ur_db_service
  IMPORTING
    et_bapiret =                " bapirettab
    e_subrc =                   " sysubrc
  EXCEPTIONS
    FAILED = 1                  "
    .  "  UR_EXEC_CHECK_STATUS

ABAP code example for Function Module UR_EXEC_CHECK_STATUS





The ABAP code below is a full code listing to execute function module UR_EXEC_CHECK_STATUS 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_et_bapiret  TYPE BAPIRETTAB ,
ld_e_subrc  TYPE SYSUBRC .

DATA(ld_io_realigner) = 'Check type of data required'.
DATA(ld_i_chgrun) = 'Check type of data required'.
DATA(ld_i_status) = 'Check type of data required'.
DATA(ld_io_db_service) = 'Check type of data required'. . CALL FUNCTION 'UR_EXEC_CHECK_STATUS' EXPORTING io_realigner = ld_io_realigner i_chgrun = ld_i_chgrun i_status = ld_i_status io_db_service = ld_io_db_service IMPORTING et_bapiret = ld_et_bapiret e_subrc = ld_e_subrc EXCEPTIONS FAILED = 1 . " UR_EXEC_CHECK_STATUS
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_et_bapiret  TYPE BAPIRETTAB ,
ld_io_realigner  TYPE CL_UR_REALIGNER ,
ld_e_subrc  TYPE SYSUBRC ,
ld_i_chgrun  TYPE UR_CHGRUN ,
ld_i_status  TYPE UR00_S_STAT ,
ld_io_db_service  TYPE CL_UR_DB_SERVICE .

ld_io_realigner = 'Check type of data required'.
ld_i_chgrun = 'Check type of data required'.
ld_i_status = 'Check type of data required'.
ld_io_db_service = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name UR_EXEC_CHECK_STATUS or its description.