SAP FVD_SKIP_OL_MAINTAIN Function Module for Edit Extension









FVD_SKIP_OL_MAINTAIN is a standard fvd skip ol maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Edit Extension 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 skip ol maintain FM, simply by entering the name FVD_SKIP_OL_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVD_SKIP_OL
Program Name: SAPLFVD_SKIP_OL
Main Program: SAPLFVD_SKIP_OL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FVD_SKIP_OL_MAINTAIN 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_SKIP_OL_MAINTAIN'"Edit Extension
EXPORTING
I_S_VDARL_KEY = "VDARL Key Structure
* I_OKCODE = ' ' "Screens, Function Code That Triggered PAI
* I_S_EXTSKIP_API = "Interface Structure and Control Data Extension and Skip
* I_RBO = "Business operation number (loans)
* I_MTEMPLNO = "Capital Transfer Template Key
I_SWORKID = "Processing Unit in the Business Operations
* I_LOGHANDLE = "Application Log: Log Handle
* I_S_GDISPLAY_PROFILE = "Application Log: Log Output Format Profile
I_MODUS = "Session for Payment Data
I_CALL_APPL = "EXTENS: Applikationen des Verlängerungen
* I_FLG_TESTRUN = "Switch to Simulation Mode for Write BAPIs

EXCEPTIONS
FATAL_ERROR = 1
.



IMPORTING Parameters details for FVD_SKIP_OL_MAINTAIN

I_S_VDARL_KEY - VDARL Key Structure

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

I_OKCODE - Screens, Function Code That Triggered PAI

Data type: RCAPTR_STEER-GOKCODE
Default: ' '
Optional: Yes
Call by Reference: Yes

I_S_EXTSKIP_API - Interface Structure and Control Data Extension and Skip

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

I_RBO - Business operation number (loans)

Data type: VDBOHEAD-RBO
Optional: Yes
Call by Reference: Yes

I_MTEMPLNO - Capital Transfer Template Key

Data type: TDCAPTR_TEMPL-MTEMPLNO
Optional: Yes
Call by Reference: Yes

I_SWORKID - Processing Unit in the Business Operations

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

I_LOGHANDLE - Application Log: Log Handle

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

I_S_GDISPLAY_PROFILE - Application Log: Log Output Format Profile

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

I_MODUS - Session for Payment Data

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

I_CALL_APPL - EXTENS: Applikationen des Verlängerungen

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

I_FLG_TESTRUN - Switch to Simulation Mode for Write BAPIs

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

EXCEPTIONS details

FATAL_ERROR - Internal Error

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

Copy and paste ABAP code example for FVD_SKIP_OL_MAINTAIN 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_fatal_error  TYPE STRING, "   
lv_i_s_vdarl_key  TYPE VDARL_KEY, "   
lv_i_okcode  TYPE RCAPTR_STEER-GOKCODE, "   ' '
lv_i_s_extskip_api  TYPE REXTSKIP_API, "   
lv_i_rbo  TYPE VDBOHEAD-RBO, "   
lv_i_mtemplno  TYPE TDCAPTR_TEMPL-MTEMPLNO, "   
lv_i_sworkid  TYPE SWORKID, "   
lv_i_loghandle  TYPE BALLOGHNDL, "   
lv_i_s_gdisplay_profile  TYPE BAL_S_PROF, "   
lv_i_modus  TYPE TB_PAY_MODUS, "   
lv_i_call_appl  TYPE TB_EXTSKIP_APPLICATION, "   
lv_i_flg_testrun  TYPE TESTRUN. "   

  CALL FUNCTION 'FVD_SKIP_OL_MAINTAIN'  "Edit Extension
    EXPORTING
         I_S_VDARL_KEY = lv_i_s_vdarl_key
         I_OKCODE = lv_i_okcode
         I_S_EXTSKIP_API = lv_i_s_extskip_api
         I_RBO = lv_i_rbo
         I_MTEMPLNO = lv_i_mtemplno
         I_SWORKID = lv_i_sworkid
         I_LOGHANDLE = lv_i_loghandle
         I_S_GDISPLAY_PROFILE = lv_i_s_gdisplay_profile
         I_MODUS = lv_i_modus
         I_CALL_APPL = lv_i_call_appl
         I_FLG_TESTRUN = lv_i_flg_testrun
    EXCEPTIONS
        FATAL_ERROR = 1
. " FVD_SKIP_OL_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM FVD_SKIP_OL_MAINTAIN

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 GOKCODE FROM RCAPTR_STEER INTO @DATA(ld_i_okcode).
DATA(ld_i_okcode) = ' '.
 
 
"SELECT single RBO FROM VDBOHEAD INTO @DATA(ld_i_rbo).
 
"SELECT single MTEMPLNO FROM TDCAPTR_TEMPL INTO @DATA(ld_i_mtemplno).
 
 
 
 
 
 
 


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!