SAP K41C_RUN_ID_UPDATE Function Module for









K41C_RUN_ID_UPDATE is a standard k41c run id update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for k41c run id update FM, simply by entering the name K41C_RUN_ID_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: K41C
Program Name: SAPLK41C
Main Program: SAPLK41C
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K41C_RUN_ID_UPDATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'K41C_RUN_ID_UPDATE'"
  EXPORTING
*  ID_RUN_ID =  "
*  ID_RUN_TEXT =  "
*  ID_RUN_LOG =  "Application Log: Log Handle
*  IS_COK41C_ID =  "Identification Table for Posting Runs

EXCEPTIONS
   ERROR_UPDATING_ID_RECORD = 1    INVALID_INPUT = 2
.



IMPORTING Parameters details for K41C_RUN_ID_UPDATE

ID_RUN_ID -

Data type: GUID
Optional: Yes
Call by Reference: Yes

ID_RUN_TEXT -

Data type: RUN_TEXT
Optional: Yes
Call by Reference: Yes

ID_RUN_LOG - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: Yes
Call by Reference: Yes

IS_COK41C_ID - Identification Table for Posting Runs

Data type: COK41C_ID
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR_UPDATING_ID_RECORD -

Data type:
Optional: No
Call by Reference: Yes

INVALID_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for K41C_RUN_ID_UPDATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_id_run_id  TYPE GUID, "   
lv_error_updating_id_record  TYPE GUID, "   
lv_id_run_text  TYPE RUN_TEXT, "   
lv_invalid_input  TYPE RUN_TEXT, "   
lv_id_run_log  TYPE BALLOGHNDL, "   
lv_is_cok41c_id  TYPE COK41C_ID. "   

  CALL FUNCTION 'K41C_RUN_ID_UPDATE'  "
    EXPORTING
         ID_RUN_ID = lv_id_run_id
         ID_RUN_TEXT = lv_id_run_text
         ID_RUN_LOG = lv_id_run_log
         IS_COK41C_ID = lv_is_cok41c_id
    EXCEPTIONS
        ERROR_UPDATING_ID_RECORD = 1
        INVALID_INPUT = 2
. " K41C_RUN_ID_UPDATE




ABAP code using 7.40 inline data declarations to call FM K41C_RUN_ID_UPDATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!