SAP FMKU_COM_ITEM_READ_SINGLE_DATA Function Module for Read & check commitment item for budgeting
FMKU_COM_ITEM_READ_SINGLE_DATA is a standard fmku com item read single data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read & check commitment item for budgeting processing and below is the pattern details for this FM, 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 fmku com item read single data FM, simply by entering the name FMKU_COM_ITEM_READ_SINGLE_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMKU
Program Name: SAPLFMKU
Main Program: SAPLFMKU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMKU_COM_ITEM_READ_SINGLE_DATA 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 'FMKU_COM_ITEM_READ_SINGLE_DATA'"Read & check commitment item for budgeting.
EXPORTING
I_FM_AREA = "Financial management area
* I_VARNT = '000' "Commitment Item Hierarchy Variant
I_FISCYEAR = "Fiscal year
I_CMMTITEM = "Commitment item
* I_FLG_TEXT = ' ' "Commitment item text
* I_FLG_HIERARCHY = ' ' "Hierarchy
IMPORTING
E_F_FMCI = "Commitment items master data
E_F_FMCIT = "Commitment items texts
E_F_FMHICI = "Commitment items hierarchy
EXCEPTIONS
MASTER_DATA_NOT_FOUND = 1 HIERARCHY_DATA_NOT_FOUND = 2 INPUT_ERROR = 3 BUDGETING_NOT_ALLOWED = 4
IMPORTING Parameters details for FMKU_COM_ITEM_READ_SINGLE_DATA
I_FM_AREA - Financial management area
Data type: FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_VARNT - Commitment Item Hierarchy Variant
Data type: FM_VARNTDefault: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FISCYEAR - Fiscal year
Data type: GJAHROptional: No
Call by Reference: No ( called with pass by value option)
I_CMMTITEM - Commitment item
Data type: FM_FIPEXOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_TEXT - Commitment item text
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_HIERARCHY - Hierarchy
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMKU_COM_ITEM_READ_SINGLE_DATA
E_F_FMCI - Commitment items master data
Data type: FMCIOptional: No
Call by Reference: No ( called with pass by value option)
E_F_FMCIT - Commitment items texts
Data type: FMCITOptional: No
Call by Reference: No ( called with pass by value option)
E_F_FMHICI - Commitment items hierarchy
Data type: FMHICIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MASTER_DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
HIERARCHY_DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
INPUT_ERROR -
Data type:Optional: No
Call by Reference: Yes
BUDGETING_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMKU_COM_ITEM_READ_SINGLE_DATA 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_e_f_fmci | TYPE FMCI, " | |||
| lv_i_fm_area | TYPE FIKRS, " | |||
| lv_master_data_not_found | TYPE FIKRS, " | |||
| lv_i_varnt | TYPE FM_VARNT, " '000' | |||
| lv_e_f_fmcit | TYPE FMCIT, " | |||
| lv_hierarchy_data_not_found | TYPE FMCIT, " | |||
| lv_e_f_fmhici | TYPE FMHICI, " | |||
| lv_i_fiscyear | TYPE GJAHR, " | |||
| lv_input_error | TYPE GJAHR, " | |||
| lv_i_cmmtitem | TYPE FM_FIPEX, " | |||
| lv_budgeting_not_allowed | TYPE FM_FIPEX, " | |||
| lv_i_flg_text | TYPE XFELD, " SPACE | |||
| lv_i_flg_hierarchy | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FMKU_COM_ITEM_READ_SINGLE_DATA' "Read & check commitment item for budgeting |
| EXPORTING | ||
| I_FM_AREA | = lv_i_fm_area | |
| I_VARNT | = lv_i_varnt | |
| I_FISCYEAR | = lv_i_fiscyear | |
| I_CMMTITEM | = lv_i_cmmtitem | |
| I_FLG_TEXT | = lv_i_flg_text | |
| I_FLG_HIERARCHY | = lv_i_flg_hierarchy | |
| IMPORTING | ||
| E_F_FMCI | = lv_e_f_fmci | |
| E_F_FMCIT | = lv_e_f_fmcit | |
| E_F_FMHICI | = lv_e_f_fmhici | |
| EXCEPTIONS | ||
| MASTER_DATA_NOT_FOUND = 1 | ||
| HIERARCHY_DATA_NOT_FOUND = 2 | ||
| INPUT_ERROR = 3 | ||
| BUDGETING_NOT_ALLOWED = 4 | ||
| . " FMKU_COM_ITEM_READ_SINGLE_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FMKU_COM_ITEM_READ_SINGLE_DATA
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.| DATA(ld_i_varnt) | = '000'. | |||
| DATA(ld_i_flg_text) | = ' '. | |||
| DATA(ld_i_flg_hierarchy) | = ' '. | |||
Search for further information about these or an SAP related objects