SAP ANALYSE_VW Function Module for Interpretation of the Payment Note Lines of the Electronic Bank Statement
ANALYSE_VW is a standard analyse vw SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Interpretation of the Payment Note Lines of the Electronic 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 analyse vw FM, simply by entering the name ANALYSE_VW into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZV
Program Name: SAPLFVZV
Main Program: SAPLFVZV
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ANALYSE_VW 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 'ANALYSE_VW'"Interpretation of the Payment Note Lines of the Electronic Bank Statement.
EXPORTING
I_FEBEP = "Electronic Bank Statement Line Items
I_FEBKO = "Kopfsatz des elektronischen Kontoauszugs
IMPORTING
E_FEBEP = "Electronic Bank Statement Line Items
E_FEBKO = "Kopfsatz des elektronischen Kontoauszugs
E_MSGTEXT = "Message, die ausgegeben werden soll
E_MSGTYP = "Messagetyp (E,S,W,I)
E_UPDATE = "Kennzeichen: Daten im Programm ändern
TABLES
T_FEBCL = "Clearing-Daten zu einem Einzelposten
T_FEBRE = "Referenzsätze Verwendungszwecke zu einem Einzelp
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFVZV_002 User Exit for Plausibility Checks, VWL, Block/Levy upon Property...
IMPORTING Parameters details for ANALYSE_VW
I_FEBEP - Electronic Bank Statement Line Items
Data type: FEBEPOptional: No
Call by Reference: No ( called with pass by value option)
I_FEBKO - Kopfsatz des elektronischen Kontoauszugs
Data type: FEBKOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ANALYSE_VW
E_FEBEP - Electronic Bank Statement Line Items
Data type: FEBEPOptional: No
Call by Reference: No ( called with pass by value option)
E_FEBKO - Kopfsatz des elektronischen Kontoauszugs
Data type: FEBKOOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGTEXT - Message, die ausgegeben werden soll
Data type: FEBMKA-MESSGOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGTYP - Messagetyp (E,S,W,I)
Data type: FEBMKA-MSTYPOptional: No
Call by Reference: No ( called with pass by value option)
E_UPDATE - Kennzeichen: Daten im Programm ändern
Data type: FEBMKA-MSTYPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ANALYSE_VW
T_FEBCL - Clearing-Daten zu einem Einzelposten
Data type: FEBCL_BFOptional: No
Call by Reference: Yes
T_FEBRE - Referenzsätze Verwendungszwecke zu einem Einzelp
Data type: FEBRE_BFOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ANALYSE_VW 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_febep | TYPE FEBEP, " | |||
| lv_i_febep | TYPE FEBEP, " | |||
| lt_t_febcl | TYPE STANDARD TABLE OF FEBCL_BF, " | |||
| lv_e_febko | TYPE FEBKO, " | |||
| lv_i_febko | TYPE FEBKO, " | |||
| lt_t_febre | TYPE STANDARD TABLE OF FEBRE_BF, " | |||
| lv_e_msgtext | TYPE FEBMKA-MESSG, " | |||
| lv_e_msgtyp | TYPE FEBMKA-MSTYP, " | |||
| lv_e_update | TYPE FEBMKA-MSTYP. " |
|   CALL FUNCTION 'ANALYSE_VW' "Interpretation of the Payment Note Lines of the Electronic Bank Statement |
| EXPORTING | ||
| I_FEBEP | = lv_i_febep | |
| I_FEBKO | = lv_i_febko | |
| IMPORTING | ||
| E_FEBEP | = lv_e_febep | |
| E_FEBKO | = lv_e_febko | |
| E_MSGTEXT | = lv_e_msgtext | |
| E_MSGTYP | = lv_e_msgtyp | |
| E_UPDATE | = lv_e_update | |
| TABLES | ||
| T_FEBCL | = lt_t_febcl | |
| T_FEBRE | = lt_t_febre | |
| . " ANALYSE_VW | ||
ABAP code using 7.40 inline data declarations to call FM ANALYSE_VW
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 MESSG FROM FEBMKA INTO @DATA(ld_e_msgtext). | ||||
| "SELECT single MSTYP FROM FEBMKA INTO @DATA(ld_e_msgtyp). | ||||
| "SELECT single MSTYP FROM FEBMKA INTO @DATA(ld_e_update). | ||||
Search for further information about these or an SAP related objects