SAP FVD_TABLE_SET_VDBEPP Function Module for Transfer New and Old Transactions to the Update
FVD_TABLE_SET_VDBEPP is a standard fvd table set vdbepp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer New and Old Transactions to the Update 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 fvd table set vdbepp FM, simply by entering the name FVD_TABLE_SET_VDBEPP into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_TABLE_UPDATE
Program Name: SAPLFVD_TABLE_UPDATE
Main Program: SAPLFVD_TABLE_UPDATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_TABLE_SET_VDBEPP 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 'FVD_TABLE_SET_VDBEPP'"Transfer New and Old Transactions to the Update.
EXPORTING
* I_UPDATE_FUNCTION = "Name des Verbuchungsbausteines
* I_FLG_UPDATE_USER = 'X' "'X' = Aktualisierung der Benutzerangaben
* I_FLG_TAB_INIT = ' ' "'X' = Initialisierung des Verbuchungsobjektes der Tabelle
* I_UPDATE_GROUP = 0 "Grouping Of Entries Within an Update Object
* I_FLG_CHANGEDOCUMENT = ' ' "'X' = Berücksichtigung der Einträge bei Änderungsbelegen
I_TAB_VDBEPP_OLD = "Tabelleneinträge auf der Datenbank
I_TAB_VDBEPP_NEW = "New Table Entries
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FVD_TABLE_SET_VDBEPP
I_UPDATE_FUNCTION - Name des Verbuchungsbausteines
Data type: FUNCNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATE_USER - 'X' = Aktualisierung der Benutzerangaben
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_TAB_INIT - 'X' = Initialisierung des Verbuchungsobjektes der Tabelle
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDATE_GROUP - Grouping Of Entries Within an Update Object
Data type: SUPDATE_GROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_CHANGEDOCUMENT - 'X' = Berücksichtigung der Einträge bei Änderungsbelegen
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_VDBEPP_OLD - Tabelleneinträge auf der Datenbank
Data type: TRTY_VDBEPPOptional: No
Call by Reference: Yes
I_TAB_VDBEPP_NEW - New Table Entries
Data type: TRTY_VDBEPPOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Fehler bei der Übergabe der Daten
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_TABLE_SET_VDBEPP 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_error | TYPE STRING, " | |||
| lv_i_update_function | TYPE FUNCNAME, " | |||
| lv_i_flg_update_user | TYPE FLAG, " 'X' | |||
| lv_i_flg_tab_init | TYPE FLAG, " SPACE | |||
| lv_i_update_group | TYPE SUPDATE_GROUP, " 0 | |||
| lv_i_flg_changedocument | TYPE FLAG, " SPACE | |||
| lv_i_tab_vdbepp_old | TYPE TRTY_VDBEPP, " | |||
| lv_i_tab_vdbepp_new | TYPE TRTY_VDBEPP. " |
|   CALL FUNCTION 'FVD_TABLE_SET_VDBEPP' "Transfer New and Old Transactions to the Update |
| EXPORTING | ||
| I_UPDATE_FUNCTION | = lv_i_update_function | |
| I_FLG_UPDATE_USER | = lv_i_flg_update_user | |
| I_FLG_TAB_INIT | = lv_i_flg_tab_init | |
| I_UPDATE_GROUP | = lv_i_update_group | |
| I_FLG_CHANGEDOCUMENT | = lv_i_flg_changedocument | |
| I_TAB_VDBEPP_OLD | = lv_i_tab_vdbepp_old | |
| I_TAB_VDBEPP_NEW | = lv_i_tab_vdbepp_new | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FVD_TABLE_SET_VDBEPP | ||
ABAP code using 7.40 inline data declarations to call FM FVD_TABLE_SET_VDBEPP
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_flg_update_user) | = 'X'. | |||
| DATA(ld_i_flg_tab_init) | = ' '. | |||
| DATA(ld_i_flg_changedocument) | = ' '. | |||
Search for further information about these or an SAP related objects