SAP FTE_BSM_EXT_STATEMENTDATA_GET Function Module for
FTE_BSM_EXT_STATEMENTDATA_GET is a standard fte bsm ext statementdata get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fte bsm ext statementdata get FM, simply by entering the name FTE_BSM_EXT_STATEMENTDATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTE_BSM
Program Name: SAPLFTE_BSM
Main Program: SAPLFTE_BSM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTE_BSM_EXT_STATEMENTDATA_GET 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 'FTE_BSM_EXT_STATEMENTDATA_GET'".
EXPORTING
* IT_BUKRS = "Company Code
I_STMNT_DATE = "
* IT_HOUSEBANK = "Short Key for a House Bank
* IT_HOUSEBANKACCT = "ID for Account Details
* I_STMNT_IMPORT_DATE = "
* I_STMNT_IMPORT_TIME = "Import time into bank data buffer
* IT_COUNTRYCODE = "FTE-BSM: Table Type for Bank Country
* IT_CURRENCY = "FTE-BSM: Table Type for Currencies
* I_USER = SY-UNAME "Changed By
IMPORTING
ET_STATEMENT = "FTE-BSM: Table Type for Bank Statement Display Structure
EXCEPTIONS
NO_BANK_FOUND = 1 NO_STATEMENT_FOUND = 2 NO_AUTHORITY = 3 NOTHING_FOUND = 4
IMPORTING Parameters details for FTE_BSM_EXT_STATEMENTDATA_GET
IT_BUKRS - Company Code
Data type: FTE_T_BUKRSOptional: Yes
Call by Reference: Yes
I_STMNT_DATE -
Data type: AZDAT_EBOptional: No
Call by Reference: Yes
IT_HOUSEBANK - Short Key for a House Bank
Data type: FTE_T_HBKIDOptional: Yes
Call by Reference: Yes
IT_HOUSEBANKACCT - ID for Account Details
Data type: FTE_T_HKTIDOptional: Yes
Call by Reference: Yes
I_STMNT_IMPORT_DATE -
Data type: EDATE_EBOptional: Yes
Call by Reference: Yes
I_STMNT_IMPORT_TIME - Import time into bank data buffer
Data type: ETIME_EBOptional: Yes
Call by Reference: Yes
IT_COUNTRYCODE - FTE-BSM: Table Type for Bank Country
Data type: FTE_T_BANKSOptional: Yes
Call by Reference: Yes
IT_CURRENCY - FTE-BSM: Table Type for Currencies
Data type: FTE_T_CURRENCYOptional: Yes
Call by Reference: Yes
I_USER - Changed By
Data type: USERDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FTE_BSM_EXT_STATEMENTDATA_GET
ET_STATEMENT - FTE-BSM: Table Type for Bank Statement Display Structure
Data type: FTE_BSM_T_STATEMENTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_BANK_FOUND -
Data type:Optional: No
Call by Reference: Yes
NO_STATEMENT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - You are not authorized to display this
Data type:Optional: No
Call by Reference: Yes
NOTHING_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTE_BSM_EXT_STATEMENTDATA_GET 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_it_bukrs | TYPE FTE_T_BUKRS, " | |||
| lv_et_statement | TYPE FTE_BSM_T_STATEMENT, " | |||
| lv_no_bank_found | TYPE FTE_BSM_T_STATEMENT, " | |||
| lv_i_stmnt_date | TYPE AZDAT_EB, " | |||
| lv_no_statement_found | TYPE AZDAT_EB, " | |||
| lv_it_housebank | TYPE FTE_T_HBKID, " | |||
| lv_no_authority | TYPE FTE_T_HBKID, " | |||
| lv_nothing_found | TYPE FTE_T_HBKID, " | |||
| lv_it_housebankacct | TYPE FTE_T_HKTID, " | |||
| lv_i_stmnt_import_date | TYPE EDATE_EB, " | |||
| lv_i_stmnt_import_time | TYPE ETIME_EB, " | |||
| lv_it_countrycode | TYPE FTE_T_BANKS, " | |||
| lv_it_currency | TYPE FTE_T_CURRENCY, " | |||
| lv_i_user | TYPE USER. " SY-UNAME |
|   CALL FUNCTION 'FTE_BSM_EXT_STATEMENTDATA_GET' " |
| EXPORTING | ||
| IT_BUKRS | = lv_it_bukrs | |
| I_STMNT_DATE | = lv_i_stmnt_date | |
| IT_HOUSEBANK | = lv_it_housebank | |
| IT_HOUSEBANKACCT | = lv_it_housebankacct | |
| I_STMNT_IMPORT_DATE | = lv_i_stmnt_import_date | |
| I_STMNT_IMPORT_TIME | = lv_i_stmnt_import_time | |
| IT_COUNTRYCODE | = lv_it_countrycode | |
| IT_CURRENCY | = lv_it_currency | |
| I_USER | = lv_i_user | |
| IMPORTING | ||
| ET_STATEMENT | = lv_et_statement | |
| EXCEPTIONS | ||
| NO_BANK_FOUND = 1 | ||
| NO_STATEMENT_FOUND = 2 | ||
| NO_AUTHORITY = 3 | ||
| NOTHING_FOUND = 4 | ||
| . " FTE_BSM_EXT_STATEMENTDATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM FTE_BSM_EXT_STATEMENTDATA_GET
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.| DATA(ld_i_user) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects