SAP FKJO_BUILD_RUNID Function Module for
FKJO_BUILD_RUNID is a standard fkjo build runid 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 fkjo build runid FM, simply by entering the name FKJO_BUILD_RUNID into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKJO_CONTAINER
Program Name: SAPLFKJO_CONTAINER
Main Program: SAPLFKJO_CONTAINER
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKJO_BUILD_RUNID 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 'FKJO_BUILD_RUNID'".
EXPORTING
I_ID = "Container ID
I_START_DATE = "
I_START_TIME = "
IMPORTING
E_RUNID = "
IMPORTING Parameters details for FKJO_BUILD_RUNID
I_ID - Container ID
Data type: FKJO_CNTR_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_START_DATE -
Data type: DFK_JC_CNTR-START_DATEOptional: No
Call by Reference: No ( called with pass by value option)
I_START_TIME -
Data type: DFK_JC_CNTR-START_TIMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKJO_BUILD_RUNID
E_RUNID -
Data type: FKJO_RUNIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKJO_BUILD_RUNID 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_i_id | TYPE FKJO_CNTR_ID, " | |||
| lv_e_runid | TYPE FKJO_RUNID, " | |||
| lv_i_start_date | TYPE DFK_JC_CNTR-START_DATE, " | |||
| lv_i_start_time | TYPE DFK_JC_CNTR-START_TIME. " |
|   CALL FUNCTION 'FKJO_BUILD_RUNID' " |
| EXPORTING | ||
| I_ID | = lv_i_id | |
| I_START_DATE | = lv_i_start_date | |
| I_START_TIME | = lv_i_start_time | |
| IMPORTING | ||
| E_RUNID | = lv_e_runid | |
| . " FKJO_BUILD_RUNID | ||
ABAP code using 7.40 inline data declarations to call FM FKJO_BUILD_RUNID
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.| "SELECT single START_DATE FROM DFK_JC_CNTR INTO @DATA(ld_i_start_date). | ||||
| "SELECT single START_TIME FROM DFK_JC_CNTR INTO @DATA(ld_i_start_time). | ||||
Search for further information about these or an SAP related objects