FM_COM_ITEM_READ SAP Function module

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

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

Pattern for FM FM_COM_ITEM_READ - FM COM ITEM READ

CALL FUNCTION 'FM_COM_ITEM_READ' "
  EXPORTING
    i_fikrs =                   " fmci-fikrs    Financial Management Area
    i_gjahr =                   " fmci-gjahr    Fiscal Year
    i_fipex =                   " fmci-fipex
*   i_date =                    " budat
*   i_flg_buffer_all = SPACE    " fmdy-xfeld
*   i_flg_only_postable = SPACE  " fmdy-xfeld
  IMPORTING
    e_f_fmci =                  " fmci
  EXCEPTIONS
    MASTER_DATA_NOT_FOUND = 1   "               No Master Data Found
    INPUT_ERROR = 2             "               Wrong Input Parameter
    CMMT_ITEM_NOT_VALID = 3     "
    .  "  FM_COM_ITEM_READ

ABAP code example for Function Module FM_COM_ITEM_READ

The ABAP code below is a full code listing to execute function module FM_COM_ITEM_READ 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_e_f_fmci  
 
 TYPE FMCI
.

 

SELECT single FIKRS 
  FROM FMCI 
  INTO @DATA(ld_i_fikrs).

 

SELECT single GJAHR 
  FROM FMCI 
  INTO @DATA(ld_i_gjahr).

 

SELECT single FIPEX 
  FROM FMCI 
  INTO @DATA(ld_i_fipex).


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


DATA(ld_i_flg_buffer_all) = some text here


DATA(ld_i_flg_only_postable) = some text here
.

CALL FUNCTION 'FM_COM_ITEM_READ'
  EXPORTING
    i_fikrs =                    ld_i_fikrs
    i_gjahr =                    ld_i_gjahr
    i_fipex =                    ld_i_fipex
*   i_date =                     ld_i_date
*   i_flg_buffer_all =           ld_i_flg_buffer_all
*   i_flg_only_postable =        ld_i_flg_only_postable
  IMPORTING
    e_f_fmci =                   ld_e_f_fmci
  EXCEPTIONS
    MASTER_DATA_NOT_FOUND =      1
    INPUT_ERROR =                2
    CMMT_ITEM_NOT_VALID =        3
    .  "  FM_COM_ITEM_READ

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_e_f_fmci
 
 TYPE FMCI ,
ld_i_fikrs
 
 TYPE FMCI-FIKRS ,
ld_i_gjahr
 
 TYPE FMCI-GJAHR ,
ld_i_fipex
 
 TYPE FMCI-FIPEX ,
ld_i_date
 
 TYPE BUDAT ,
ld_i_flg_buffer_all
 
 TYPE FMDY-XFELD ,
ld_i_flg_only_postable
 
 TYPE FMDY-XFELD .



SELECT single FIKRS 
  FROM FMCI 
  INTO ld_i_fikrs.


SELECT single GJAHR 
  FROM FMCI 
  INTO ld_i_gjahr.


SELECT single FIPEX 
  FROM FMCI 
  INTO ld_i_fipex.

ld_i_date = 'Check type of data required'.

ld_i_flg_buffer_all = some text here

ld_i_flg_only_postable = some text here