SAP FM_COM_ITEM_READ_SINGLE_DATA Function Module for Read Commitment Item









FM_COM_ITEM_READ_SINGLE_DATA is a standard fm 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 Commitment Item 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 fm com item read single data FM, simply by entering the name FM_COM_ITEM_READ_SINGLE_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_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 'FM_COM_ITEM_READ_SINGLE_DATA'"Read Commitment Item
EXPORTING
I_FIKRS = "
* I_VARNT = '000' "
I_GJAHR = "
I_FIPEX = "
* I_DATE = "
* I_FLG_TEXT = ' ' "
* I_FLG_HIERARCHY = ' ' "

IMPORTING
E_F_FMCI = "
E_F_FMCIT = "
E_F_FMHICI = "

EXCEPTIONS
MASTER_DATA_NOT_FOUND = 1 HIERARCHY_DATA_NOT_FOUND = 2 INPUT_ERROR = 3 CMMT_ITEM_NOT_VALID = 4
.



IMPORTING Parameters details for FM_COM_ITEM_READ_SINGLE_DATA

I_FIKRS -

Data type: FMCI-FIKRS
Optional: No
Call by Reference: Yes

I_VARNT -

Data type: FMHICI-VARNT
Default: '000'
Optional: Yes
Call by Reference: Yes

I_GJAHR -

Data type: FMCI-GJAHR
Optional: No
Call by Reference: Yes

I_FIPEX -

Data type: FMCI-FIPEX
Optional: No
Call by Reference: Yes

I_DATE -

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

I_FLG_TEXT -

Data type: FMDY-XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_FLG_HIERARCHY -

Data type: FMDY-XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FM_COM_ITEM_READ_SINGLE_DATA

E_F_FMCI -

Data type: FMCI
Optional: No
Call by Reference: Yes

E_F_FMCIT -

Data type: FMCIT
Optional: No
Call by Reference: Yes

E_F_FMHICI -

Data type: FMHICI
Optional: No
Call by Reference: Yes

EXCEPTIONS details

MASTER_DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

HIERARCHY_DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CMMT_ITEM_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FM_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_i_fikrs  TYPE FMCI-FIKRS, "   
lv_e_f_fmci  TYPE FMCI, "   
lv_master_data_not_found  TYPE FMCI, "   
lv_i_varnt  TYPE FMHICI-VARNT, "   '000'
lv_e_f_fmcit  TYPE FMCIT, "   
lv_hierarchy_data_not_found  TYPE FMCIT, "   
lv_i_gjahr  TYPE FMCI-GJAHR, "   
lv_e_f_fmhici  TYPE FMHICI, "   
lv_input_error  TYPE FMHICI, "   
lv_i_fipex  TYPE FMCI-FIPEX, "   
lv_cmmt_item_not_valid  TYPE FMCI, "   
lv_i_date  TYPE BUDAT, "   
lv_i_flg_text  TYPE FMDY-XFELD, "   SPACE
lv_i_flg_hierarchy  TYPE FMDY-XFELD. "   SPACE

  CALL FUNCTION 'FM_COM_ITEM_READ_SINGLE_DATA'  "Read Commitment Item
    EXPORTING
         I_FIKRS = lv_i_fikrs
         I_VARNT = lv_i_varnt
         I_GJAHR = lv_i_gjahr
         I_FIPEX = lv_i_fipex
         I_DATE = lv_i_date
         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
        CMMT_ITEM_NOT_VALID = 4
. " FM_COM_ITEM_READ_SINGLE_DATA




ABAP code using 7.40 inline data declarations to call FM FM_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.

"SELECT single FIKRS FROM FMCI INTO @DATA(ld_i_fikrs).
 
 
 
"SELECT single VARNT FROM FMHICI INTO @DATA(ld_i_varnt).
DATA(ld_i_varnt) = '000'.
 
 
 
"SELECT single GJAHR FROM FMCI INTO @DATA(ld_i_gjahr).
 
 
 
"SELECT single FIPEX FROM FMCI INTO @DATA(ld_i_fipex).
 
 
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_text).
DATA(ld_i_flg_text) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_hierarchy).
DATA(ld_i_flg_hierarchy) = ' '.
 


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!