SAP EB_BANK_STATEMENT_INSERT Function Module for Update account statement (manual) in tables FEBxx (VW,KO,EP,CL,RE)









EB_BANK_STATEMENT_INSERT is a standard eb bank statement insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update account statement (manual) in tables FEBxx (VW,KO,EP,CL,RE) 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 eb bank statement insert FM, simply by entering the name EB_BANK_STATEMENT_INSERT into the relevant SAP transaction such as SE37 or SE38.

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



Function EB_BANK_STATEMENT_INSERT 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 'EB_BANK_STATEMENT_INSERT'"Update account statement (manual) in tables FEBxx (VW,KO,EP,CL,RE)
  EXPORTING
*  I_ERLEDIGT = ' ' "' '=at least 1 p. not yet completed/ 'X'= 1 p. completed manually
*  I_FEBKO = ' ' "Header record
*  I_FEBMKA = ' ' "Control fields and so on
*  I_FEBVW = ' ' "Control record
*  I_NACHBARB_FLAG = ' ' "Statement is already entered
*  I_ST_AEND_FLAG = ' ' "

TABLES
   TAB1 =  "INTTAB for individual items
   TAB2 =  "INTTAB for clearing information
.



IMPORTING Parameters details for EB_BANK_STATEMENT_INSERT

I_ERLEDIGT - SPACE=at least 1 p. not yet completed/ 'X'= 1 p. completed manually

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

I_FEBKO - Header record

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

I_FEBMKA - Control fields and so on

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

I_FEBVW - Control record

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

I_NACHBARB_FLAG - Statement is already entered

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

I_ST_AEND_FLAG -

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

TABLES Parameters details for EB_BANK_STATEMENT_INSERT

TAB1 - INTTAB for individual items

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

TAB2 - INTTAB for clearing information

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

Copy and paste ABAP code example for EB_BANK_STATEMENT_INSERT 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:
lt_tab1  TYPE STANDARD TABLE OF RF40KB1, "   
lv_i_erledigt  TYPE FEBMKA-VTYPM, "   SPACE
lt_tab2  TYPE STANDARD TABLE OF RF40KB2, "   
lv_i_febko  TYPE FEBKO, "   SPACE
lv_i_febmka  TYPE FEBMKA, "   SPACE
lv_i_febvw  TYPE FEBVW, "   SPACE
lv_i_nachbarb_flag  TYPE FEBMKA-VTYPM, "   SPACE
lv_i_st_aend_flag  TYPE FEBMKA-VTYPM. "   SPACE

  CALL FUNCTION 'EB_BANK_STATEMENT_INSERT'  "Update account statement (manual) in tables FEBxx (VW,KO,EP,CL,RE)
    EXPORTING
         I_ERLEDIGT = lv_i_erledigt
         I_FEBKO = lv_i_febko
         I_FEBMKA = lv_i_febmka
         I_FEBVW = lv_i_febvw
         I_NACHBARB_FLAG = lv_i_nachbarb_flag
         I_ST_AEND_FLAG = lv_i_st_aend_flag
    TABLES
         TAB1 = lt_tab1
         TAB2 = lt_tab2
. " EB_BANK_STATEMENT_INSERT




ABAP code using 7.40 inline data declarations to call FM EB_BANK_STATEMENT_INSERT

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 VTYPM FROM FEBMKA INTO @DATA(ld_i_erledigt).
DATA(ld_i_erledigt) = ' '.
 
 
DATA(ld_i_febko) = ' '.
 
DATA(ld_i_febmka) = ' '.
 
DATA(ld_i_febvw) = ' '.
 
"SELECT single VTYPM FROM FEBMKA INTO @DATA(ld_i_nachbarb_flag).
DATA(ld_i_nachbarb_flag) = ' '.
 
"SELECT single VTYPM FROM FEBMKA INTO @DATA(ld_i_st_aend_flag).
DATA(ld_i_st_aend_flag) = ' '.
 


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!