SAP FVD_API_STOP_REM Function Module for Stop Management: Remove a Stop for Loan in API Layer









FVD_API_STOP_REM is a standard fvd api stop rem 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: Remove a Stop 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 rem FM, simply by entering the name FVD_API_STOP_REM 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_REM 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_REM'"Stop Management: Remove a Stop for Loan in API Layer
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_GSART = "Product Type
* I_STOP = "Technical Key for Stop
I_APPLICATION = "Technical Key for Stop Application
* I_STOP_GUID = "GUID in 'RAW' Format
* I_FLG_REMOVE_ALL_STOPS = "Checkbox

IMPORTING
E_STOP_INDICATOR = "Stop Indicator
E_FLG_STOP_NOT_ACTIVE = "Checkbox

EXCEPTIONS
PARAM_INVALID = 1 APPLICATION_INVALID = 2 UPDATE_ERROR = 3 NO_STOP_SPECIFIED = 4 NOT_AUTHORIZED = 5 LOCK_FAILED = 6 FAILED = 7 OTHER_ERROR = 8
.



IMPORTING Parameters details for FVD_API_STOP_REM

I_BUKRS - Company Code

Data type: BUKRS
Optional: No
Call by Reference: Yes

I_RANL - Contract Number

Data type: RANL
Optional: No
Call by Reference: Yes

I_GSART - Product Type

Data type: VVSART
Optional: No
Call by Reference: Yes

I_STOP - Technical Key for Stop

Data type: TB_STOP
Optional: Yes
Call by Reference: Yes

I_APPLICATION - Technical Key for Stop Application

Data type: TB_STOP_APPL
Optional: No
Call by Reference: Yes

I_STOP_GUID - GUID in 'RAW' Format

Data type: GUID_16
Optional: Yes
Call by Reference: Yes

I_FLG_REMOVE_ALL_STOPS - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FVD_API_STOP_REM

E_STOP_INDICATOR - Stop Indicator

Data type: TB_STOP_INDICATOR
Optional: No
Call by Reference: Yes

E_FLG_STOP_NOT_ACTIVE - Checkbox

Data type: XFELD
Optional: 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: No ( called with pass by value option)

UPDATE_ERROR - Fehler bei Aufruf Update Funktion

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_STOP_SPECIFIED - Kein Stop angegeben

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - Benutzer hat keine Berechtigung zum Entfernen eines angegebenen Stopps

Data type:
Optional: No
Call by Reference: Yes

LOCK_FAILED - Unable to set lock

Data type:
Optional: No
Call by Reference: Yes

FAILED - Funktion fehlerhaft

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_REM 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_param_invalid  TYPE BUKRS, "   
lv_e_stop_indicator  TYPE TB_STOP_INDICATOR, "   
lv_i_ranl  TYPE RANL, "   
lv_application_invalid  TYPE RANL, "   
lv_e_flg_stop_not_active  TYPE XFELD, "   
lv_i_gsart  TYPE VVSART, "   
lv_update_error  TYPE VVSART, "   
lv_i_stop  TYPE TB_STOP, "   
lv_no_stop_specified  TYPE TB_STOP, "   
lv_i_application  TYPE TB_STOP_APPL, "   
lv_not_authorized  TYPE TB_STOP_APPL, "   
lv_i_stop_guid  TYPE GUID_16, "   
lv_lock_failed  TYPE GUID_16, "   
lv_failed  TYPE GUID_16, "   
lv_i_flg_remove_all_stops  TYPE XFELD, "   
lv_other_error  TYPE XFELD. "   

  CALL FUNCTION 'FVD_API_STOP_REM'  "Stop Management: Remove a Stop for Loan in API Layer
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_RANL = lv_i_ranl
         I_GSART = lv_i_gsart
         I_STOP = lv_i_stop
         I_APPLICATION = lv_i_application
         I_STOP_GUID = lv_i_stop_guid
         I_FLG_REMOVE_ALL_STOPS = lv_i_flg_remove_all_stops
    IMPORTING
         E_STOP_INDICATOR = lv_e_stop_indicator
         E_FLG_STOP_NOT_ACTIVE = lv_e_flg_stop_not_active
    EXCEPTIONS
        PARAM_INVALID = 1
        APPLICATION_INVALID = 2
        UPDATE_ERROR = 3
        NO_STOP_SPECIFIED = 4
        NOT_AUTHORIZED = 5
        LOCK_FAILED = 6
        FAILED = 7
        OTHER_ERROR = 8
. " FVD_API_STOP_REM




ABAP code using 7.40 inline data declarations to call FM FVD_API_STOP_REM

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!