SAP FINDE_ABGEBROCHENE_VB Function Module for Find terminated updates
FINDE_ABGEBROCHENE_VB is a standard finde abgebrochene vb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find terminated updates 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 finde abgebrochene vb FM, simply by entering the name FINDE_ABGEBROCHENE_VB into the relevant SAP transaction such as SE37 or SE38.
Function Group: VBFR
Program Name: SAPLVBFR
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FINDE_ABGEBROCHENE_VB 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 'FINDE_ABGEBROCHENE_VB'"Find terminated updates.
EXPORTING
* B_DATUM = SY-DATUM "Top limit of the selection date
* MANDT = SY-MANDT "Client
VB_ERROR = "Name of the function module which
VB_FINISH = "Name of the function module which
VB_NAME = "Name of the actual update function
* V_DATUM = SY-DATUM "Lower limit of the selection date
* I_XV1ONLY = 'X' "
EXCEPTIONS
NOTHING_FOUND = 1 READ_REPORT_ERROR = 2 WRONG_FB = 3 WRONG_PROGRAM = 4 GENERATE_REPORT_ERROR = 5
IMPORTING Parameters details for FINDE_ABGEBROCHENE_VB
B_DATUM - Top limit of the selection date
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
VB_ERROR - Name of the function module which
Data type: TFDIR-FUNCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
VB_FINISH - Name of the function module which
Data type: TFDIR-FUNCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
VB_NAME - Name of the actual update function
Data type: TFDIR-FUNCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
V_DATUM - Lower limit of the selection date
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XV1ONLY -
Data type: XV1ONLYDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOTHING_FOUND - No cancelled updates found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
READ_REPORT_ERROR - Error in reading the LxxxxVnn program
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_FB - Error in reading the TFDIR (functi
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PROGRAM - The program LxxxxVnn is incorrectl
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GENERATE_REPORT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FINDE_ABGEBROCHENE_VB 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_b_datum | TYPE SY-DATUM, " SY-DATUM | |||
| lv_nothing_found | TYPE SY, " | |||
| lv_mandt | TYPE SY-MANDT, " SY-MANDT | |||
| lv_read_report_error | TYPE SY, " | |||
| lv_vb_error | TYPE TFDIR-FUNCNAME, " | |||
| lv_wrong_fb | TYPE TFDIR, " | |||
| lv_vb_finish | TYPE TFDIR-FUNCNAME, " | |||
| lv_wrong_program | TYPE TFDIR, " | |||
| lv_vb_name | TYPE TFDIR-FUNCNAME, " | |||
| lv_generate_report_error | TYPE TFDIR, " | |||
| lv_v_datum | TYPE SY-DATUM, " SY-DATUM | |||
| lv_i_xv1only | TYPE XV1ONLY. " 'X' |
|   CALL FUNCTION 'FINDE_ABGEBROCHENE_VB' "Find terminated updates |
| EXPORTING | ||
| B_DATUM | = lv_b_datum | |
| MANDT | = lv_mandt | |
| VB_ERROR | = lv_vb_error | |
| VB_FINISH | = lv_vb_finish | |
| VB_NAME | = lv_vb_name | |
| V_DATUM | = lv_v_datum | |
| I_XV1ONLY | = lv_i_xv1only | |
| EXCEPTIONS | ||
| NOTHING_FOUND = 1 | ||
| READ_REPORT_ERROR = 2 | ||
| WRONG_FB = 3 | ||
| WRONG_PROGRAM = 4 | ||
| GENERATE_REPORT_ERROR = 5 | ||
| . " FINDE_ABGEBROCHENE_VB | ||
ABAP code using 7.40 inline data declarations to call FM FINDE_ABGEBROCHENE_VB
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 DATUM FROM SY INTO @DATA(ld_b_datum). | ||||
| DATA(ld_b_datum) | = SY-DATUM. | |||
| "SELECT single MANDT FROM SY INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_vb_error). | ||||
| "SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_vb_finish). | ||||
| "SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_vb_name). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_v_datum). | ||||
| DATA(ld_v_datum) | = SY-DATUM. | |||
| DATA(ld_i_xv1only) | = 'X'. | |||
Search for further information about these or an SAP related objects