K41C_RUN_ID_SELECT SAP Function module

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

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

Pattern for FM K41C_RUN_ID_SELECT - K41C RUN ID SELECT

CALL FUNCTION 'K41C_RUN_ID_SELECT' "
  EXPORTING
    id_user =                   " syuname       SAP System, User Logon Name
*   id_run_text =               " run_text
    id_run_date =               " sydatum
    id_run_time =               " syuzeit
    id_file_name =              " run_file      Character string - 128 user-defined characters
  IMPORTING
    ed_run_id =                 " guid          Globally Unique Identifier
  EXCEPTIONS
    RUN_ID_NOT_FOUND = 1        "
    .  "  K41C_RUN_ID_SELECT

ABAP code example for Function Module K41C_RUN_ID_SELECT

The ABAP code below is a full code listing to execute function module K41C_RUN_ID_SELECT 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_ed_run_id  
 
 TYPE GUID
.


DATA(ld_id_user) = 'some text here'.

DATA(ld_id_run_text) = 'some text here'.

DATA(ld_id_run_date) = '20210129'.

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

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

CALL FUNCTION 'K41C_RUN_ID_SELECT'
  EXPORTING
    id_user =                    ld_id_user
*   id_run_text =                ld_id_run_text
    id_run_date =                ld_id_run_date
    id_run_time =                ld_id_run_time
    id_file_name =               ld_id_file_name
  IMPORTING
    ed_run_id =                  ld_ed_run_id
  EXCEPTIONS
    RUN_ID_NOT_FOUND =           1
    .  "  K41C_RUN_ID_SELECT

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_ed_run_id
 
 TYPE GUID ,
ld_id_user
 
 TYPE SYUNAME ,
ld_id_run_text
 
 TYPE RUN_TEXT ,
ld_id_run_date
 
 TYPE SYDATUM ,
ld_id_run_time
 
 TYPE SYUZEIT ,
ld_id_file_name
 
 TYPE RUN_FILE .


ld_id_user = 'some text here'.
ld_id_run_text = 'some text here'.
ld_id_run_date = '20210129'.
ld_id_run_time = 'Check type of data required'.
ld_id_file_name = 'Check type of data required'.