SAP FMSU_READ Function Module for FIFM: Read File FMSU









FMSU_READ is a standard fmsu read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FIFM: Read File FMSU 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 fmsu read FM, simply by entering the name FMSU_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function FMSU_READ 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 'FMSU_READ'"FIFM: Read File FMSU
  EXPORTING
*  I_BUKRS = ' ' "Company code
*  I_TWAER = ' ' "Trans. currency
*  I_VORGA = ' ' "Transaction
*  I_WRTTP = ' ' "Val.type
*  I_GEBER = ' ' "Fund
   I_GJAHR =  "Fiscal year
*  I_GSBER = ' ' "Business area
   I_LEDNR =  "Ledgers
   I_OBJNR =  "Object number
*  I_OBJNRZ = ' ' "CO account assignment object number
*  I_PERIO =  "Period (three-character)
*  I_POSIT = ' ' "Internal commitment item number

TABLES
   T_FMSUTAB =  "Actual/commitment
.



IMPORTING Parameters details for FMSU_READ

I_BUKRS - Company code

Data type: FMSU-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TWAER - Trans. currency

Data type: FMSU-TWAER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VORGA - Transaction

Data type: FMSU-VORGA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_WRTTP - Val.type

Data type: FMSU-WRTTP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GEBER - Fund

Data type: FMSU-GEBER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GJAHR - Fiscal year

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

I_GSBER - Business area

Data type: FMSU-GSBER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LEDNR - Ledgers

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

I_OBJNR - Object number

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

I_OBJNRZ - CO account assignment object number

Data type: FMSU-OBJNRZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PERIO - Period (three-character)

Data type: FMFMSU1-PERIO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_POSIT - Internal commitment item number

Data type: FMSU-POSIT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FMSU_READ

T_FMSUTAB - Actual/commitment

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

Copy and paste ABAP code example for FMSU_READ 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_bukrs  TYPE FMSU-BUKRS, "   SPACE
lt_t_fmsutab  TYPE STANDARD TABLE OF FMFMSU2, "   
lv_i_twaer  TYPE FMSU-TWAER, "   SPACE
lv_i_vorga  TYPE FMSU-VORGA, "   SPACE
lv_i_wrttp  TYPE FMSU-WRTTP, "   SPACE
lv_i_geber  TYPE FMSU-GEBER, "   SPACE
lv_i_gjahr  TYPE FMSU-GJAHR, "   
lv_i_gsber  TYPE FMSU-GSBER, "   SPACE
lv_i_lednr  TYPE FMSU-LEDNR, "   
lv_i_objnr  TYPE FMSU-OBJNR, "   
lv_i_objnrz  TYPE FMSU-OBJNRZ, "   SPACE
lv_i_perio  TYPE FMFMSU1-PERIO, "   
lv_i_posit  TYPE FMSU-POSIT. "   SPACE

  CALL FUNCTION 'FMSU_READ'  "FIFM: Read File FMSU
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_TWAER = lv_i_twaer
         I_VORGA = lv_i_vorga
         I_WRTTP = lv_i_wrttp
         I_GEBER = lv_i_geber
         I_GJAHR = lv_i_gjahr
         I_GSBER = lv_i_gsber
         I_LEDNR = lv_i_lednr
         I_OBJNR = lv_i_objnr
         I_OBJNRZ = lv_i_objnrz
         I_PERIO = lv_i_perio
         I_POSIT = lv_i_posit
    TABLES
         T_FMSUTAB = lt_t_fmsutab
. " FMSU_READ




ABAP code using 7.40 inline data declarations to call FM FMSU_READ

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 BUKRS FROM FMSU INTO @DATA(ld_i_bukrs).
DATA(ld_i_bukrs) = ' '.
 
 
"SELECT single TWAER FROM FMSU INTO @DATA(ld_i_twaer).
DATA(ld_i_twaer) = ' '.
 
"SELECT single VORGA FROM FMSU INTO @DATA(ld_i_vorga).
DATA(ld_i_vorga) = ' '.
 
"SELECT single WRTTP FROM FMSU INTO @DATA(ld_i_wrttp).
DATA(ld_i_wrttp) = ' '.
 
"SELECT single GEBER FROM FMSU INTO @DATA(ld_i_geber).
DATA(ld_i_geber) = ' '.
 
"SELECT single GJAHR FROM FMSU INTO @DATA(ld_i_gjahr).
 
"SELECT single GSBER FROM FMSU INTO @DATA(ld_i_gsber).
DATA(ld_i_gsber) = ' '.
 
"SELECT single LEDNR FROM FMSU INTO @DATA(ld_i_lednr).
 
"SELECT single OBJNR FROM FMSU INTO @DATA(ld_i_objnr).
 
"SELECT single OBJNRZ FROM FMSU INTO @DATA(ld_i_objnrz).
DATA(ld_i_objnrz) = ' '.
 
"SELECT single PERIO FROM FMFMSU1 INTO @DATA(ld_i_perio).
 
"SELECT single POSIT FROM FMSU INTO @DATA(ld_i_posit).
DATA(ld_i_posit) = ' '.
 


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!