SAP FVV_EXIT_SAPMF40K_001 Function Module for Process Input Lines in the Manual Bank Statement
FVV_EXIT_SAPMF40K_001 is a standard fvv exit sapmf40k 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process Input Lines in the Manual Bank Statement 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 fvv exit sapmf40k 001 FM, simply by entering the name FVV_EXIT_SAPMF40K_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDEB
Program Name: SAPLFDEB
Main Program: SAPLFDEB
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FVV_EXIT_SAPMF40K_001 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 'FVV_EXIT_SAPMF40K_001'"Process Input Lines in the Manual Bank Statement.
EXPORTING
I_BUKRS = "
I_DYKEY = "
I_HKONT = "
I_KWBTR = "
I_LINE = "
I_STATUS = "
I_WAERS = "
* I_OKCODE = "Area Not More Closely Defined, Possibly Used for Patchlevels
IMPORTING
E_GRPNR = "
E_LINE = "
E_UPDATE = "
TABLES
SEL_TAB = "
IMPORTING Parameters details for FVV_EXIT_SAPMF40K_001
I_BUKRS -
Data type: T012K-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_DYKEY -
Data type: T021F-VARNROptional: No
Call by Reference: No ( called with pass by value option)
I_HKONT -
Data type: T012K-HKONTOptional: No
Call by Reference: No ( called with pass by value option)
I_KWBTR -
Data type: FEBMKA-KWBTROptional: No
Call by Reference: No ( called with pass by value option)
I_LINE -
Data type: RF40KI1Optional: No
Call by Reference: No ( called with pass by value option)
I_STATUS -
Data type: RF40KI3Optional: No
Call by Reference: No ( called with pass by value option)
I_WAERS -
Data type: FEBKO-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
I_OKCODE - Area Not More Closely Defined, Possibly Used for Patchlevels
Data type: RF40KI1-VGMANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVV_EXIT_SAPMF40K_001
E_GRPNR -
Data type: FEBEP-GRPNROptional: No
Call by Reference: No ( called with pass by value option)
E_LINE -
Data type: RF40KI1Optional: No
Call by Reference: No ( called with pass by value option)
E_UPDATE -
Data type: FEBMKA-MSTYPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FVV_EXIT_SAPMF40K_001
SEL_TAB -
Data type: RF40KI2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVV_EXIT_SAPMF40K_001 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_grpnr | TYPE FEBEP-GRPNR, " | |||
lv_i_bukrs | TYPE T012K-BUKRS, " | |||
lt_sel_tab | TYPE STANDARD TABLE OF RF40KI2, " | |||
lv_e_line | TYPE RF40KI1, " | |||
lv_i_dykey | TYPE T021F-VARNR, " | |||
lv_i_hkont | TYPE T012K-HKONT, " | |||
lv_e_update | TYPE FEBMKA-MSTYP, " | |||
lv_i_kwbtr | TYPE FEBMKA-KWBTR, " | |||
lv_i_line | TYPE RF40KI1, " | |||
lv_i_status | TYPE RF40KI3, " | |||
lv_i_waers | TYPE FEBKO-WAERS, " | |||
lv_i_okcode | TYPE RF40KI1-VGMAN. " |
  CALL FUNCTION 'FVV_EXIT_SAPMF40K_001' "Process Input Lines in the Manual Bank Statement |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
I_DYKEY | = lv_i_dykey | |
I_HKONT | = lv_i_hkont | |
I_KWBTR | = lv_i_kwbtr | |
I_LINE | = lv_i_line | |
I_STATUS | = lv_i_status | |
I_WAERS | = lv_i_waers | |
I_OKCODE | = lv_i_okcode | |
IMPORTING | ||
E_GRPNR | = lv_e_grpnr | |
E_LINE | = lv_e_line | |
E_UPDATE | = lv_e_update | |
TABLES | ||
SEL_TAB | = lt_sel_tab | |
. " FVV_EXIT_SAPMF40K_001 |
ABAP code using 7.40 inline data declarations to call FM FVV_EXIT_SAPMF40K_001
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 GRPNR FROM FEBEP INTO @DATA(ld_e_grpnr). | ||||
"SELECT single BUKRS FROM T012K INTO @DATA(ld_i_bukrs). | ||||
"SELECT single VARNR FROM T021F INTO @DATA(ld_i_dykey). | ||||
"SELECT single HKONT FROM T012K INTO @DATA(ld_i_hkont). | ||||
"SELECT single MSTYP FROM FEBMKA INTO @DATA(ld_e_update). | ||||
"SELECT single KWBTR FROM FEBMKA INTO @DATA(ld_i_kwbtr). | ||||
"SELECT single WAERS FROM FEBKO INTO @DATA(ld_i_waers). | ||||
"SELECT single VGMAN FROM RF40KI1 INTO @DATA(ld_i_okcode). | ||||
Search for further information about these or an SAP related objects