SAP FVD_API_STOP_GET Function Module for Stop Management: Read All Stops for Loan in API Layer
FVD_API_STOP_GET is a standard fvd api stop get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Stop Management: Read All Stops for Loan in API Layer 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 api stop get FM, simply by entering the name FVD_API_STOP_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_API_STOP
Program Name: SAPLFVD_API_STOP
Main Program: SAPLFVD_API_STOP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_API_STOP_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 'FVD_API_STOP_GET'"Stop Management: Read All Stops for Loan in API Layer.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_GSART = "Product Type
I_APPLICATION = "Technical Key for Stop Application
* I_FLG_WITH_LOCK = "Checkbox
IMPORTING
E_TAB_STOP = "Table Type VDSTOP_VDARL_A with Additional Texts
E_CNT_STOPS_ACTIVE = "Number of Active Stops
E_CNT_STOPS_INACTIVE = "Number of Inactive Stops
E_CNT_STOPS_TOTAL = "Number of Stops in Total
EXCEPTIONS
PARAM_INVALID = 1 APPLICATION_INVALID = 2 NO_STOPS_FOUND = 3 LOCK_FAILED = 4 NOT_AUTHORIZED = 5 OTHER_ERROR = 6
IMPORTING Parameters details for FVD_API_STOP_GET
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
I_RANL - Contract Number
Data type: RANLOptional: No
Call by Reference: Yes
I_GSART - Product Type
Data type: VVSARTOptional: No
Call by Reference: Yes
I_APPLICATION - Technical Key for Stop Application
Data type: TB_STOP_APPLOptional: No
Call by Reference: Yes
I_FLG_WITH_LOCK - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_API_STOP_GET
E_TAB_STOP - Table Type VDSTOP_VDARL_A with Additional Texts
Data type: TRTY_VDSTOP_VDARL_A_TOptional: No
Call by Reference: Yes
E_CNT_STOPS_ACTIVE - Number of Active Stops
Data type: TB_STOP_CNT_ACTIVEOptional: No
Call by Reference: Yes
E_CNT_STOPS_INACTIVE - Number of Inactive Stops
Data type: TB_STOP_CNT_INACTIVEOptional: No
Call by Reference: Yes
E_CNT_STOPS_TOTAL - Number of Stops in Total
Data type: TB_STOP_CNT_TOTALOptional: No
Call by Reference: Yes
EXCEPTIONS details
PARAM_INVALID - Parameter Incorrect
Data type:Optional: No
Call by Reference: Yes
APPLICATION_INVALID - Application is invalid
Data type:Optional: No
Call by Reference: Yes
NO_STOPS_FOUND - Keine Stops gefunden
Data type:Optional: No
Call by Reference: Yes
LOCK_FAILED - Unable to set lock
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED - Benutzer hat keine Berechtigung zum Anzeigen eines Stopps
Data type:Optional: No
Call by Reference: Yes
OTHER_ERROR - Other Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_API_STOP_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_i_bukrs | TYPE BUKRS, " | |||
| lv_e_tab_stop | TYPE TRTY_VDSTOP_VDARL_A_T, " | |||
| lv_param_invalid | TYPE TRTY_VDSTOP_VDARL_A_T, " | |||
| lv_i_ranl | TYPE RANL, " | |||
| lv_e_cnt_stops_active | TYPE TB_STOP_CNT_ACTIVE, " | |||
| lv_application_invalid | TYPE TB_STOP_CNT_ACTIVE, " | |||
| lv_i_gsart | TYPE VVSART, " | |||
| lv_no_stops_found | TYPE VVSART, " | |||
| lv_e_cnt_stops_inactive | TYPE TB_STOP_CNT_INACTIVE, " | |||
| lv_lock_failed | TYPE TB_STOP_CNT_INACTIVE, " | |||
| lv_i_application | TYPE TB_STOP_APPL, " | |||
| lv_e_cnt_stops_total | TYPE TB_STOP_CNT_TOTAL, " | |||
| lv_not_authorized | TYPE TB_STOP_CNT_TOTAL, " | |||
| lv_i_flg_with_lock | TYPE XFELD, " | |||
| lv_other_error | TYPE XFELD. " |
|   CALL FUNCTION 'FVD_API_STOP_GET' "Stop Management: Read All Stops for Loan in API Layer |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_GSART | = lv_i_gsart | |
| I_APPLICATION | = lv_i_application | |
| I_FLG_WITH_LOCK | = lv_i_flg_with_lock | |
| IMPORTING | ||
| E_TAB_STOP | = lv_e_tab_stop | |
| E_CNT_STOPS_ACTIVE | = lv_e_cnt_stops_active | |
| E_CNT_STOPS_INACTIVE | = lv_e_cnt_stops_inactive | |
| E_CNT_STOPS_TOTAL | = lv_e_cnt_stops_total | |
| EXCEPTIONS | ||
| PARAM_INVALID = 1 | ||
| APPLICATION_INVALID = 2 | ||
| NO_STOPS_FOUND = 3 | ||
| LOCK_FAILED = 4 | ||
| NOT_AUTHORIZED = 5 | ||
| OTHER_ERROR = 6 | ||
| . " FVD_API_STOP_GET | ||
ABAP code using 7.40 inline data declarations to call FM FVD_API_STOP_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.Search for further information about these or an SAP related objects