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

Function FVD_CAPTR_OL_RELEASE 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_CAPTR_OL_RELEASE'"Release Capital Transfer.
EXPORTING
I_S_VDARL_KEY = "VDARL Schlussel-Struktur
I_RBO = "Business operation number (loans)
* I_S_POST_INFO = "CAPTR: Save Information of Capital Transfer
I_OKCODE = "Screens, Function Code That Triggered PAI
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_FLG_TESTRUN = "Switch to Simulation Mode for Write BAPIs
* I_S_RCAPTR_API = "Screen Fields for Capital Transfer (API)
EXCEPTIONS
FAILED = 1 FATAL_ERROR = 2
IMPORTING Parameters details for FVD_CAPTR_OL_RELEASE
I_S_VDARL_KEY - VDARL Schlussel-Struktur
Data type: VDARL_KEYOptional: No
Call by Reference: Yes
I_RBO - Business operation number (loans)
Data type: RBOOptional: No
Call by Reference: Yes
I_S_POST_INFO - CAPTR: Save Information of Capital Transfer
Data type: RCAPTR_SAVEOptional: Yes
Call by Reference: Yes
I_OKCODE - Screens, Function Code That Triggered PAI
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
I_SWORKID - Processing Unit in the Business Operations
Data type: SWORKIDOptional: No
Call by Reference: Yes
I_LOGHANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
I_S_GDISPLAY_PROFILE - Application Log: Log Output Format Profile
Data type: BAL_S_PROFOptional: Yes
Call by Reference: Yes
I_FLG_TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: TESTRUNOptional: Yes
Call by Reference: Yes
I_S_RCAPTR_API - Screen Fields for Capital Transfer (API)
Data type: RCAPTR_API_STRUCTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FAILED - Release Not Possible
Data type:Optional: No
Call by Reference: Yes
FATAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_CAPTR_OL_RELEASE 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_failed | TYPE STRING, " | |||
| lv_i_s_vdarl_key | TYPE VDARL_KEY, " | |||
| lv_i_rbo | TYPE RBO, " | |||
| lv_fatal_error | TYPE RBO, " | |||
| lv_i_s_post_info | TYPE RCAPTR_SAVE, " | |||
| lv_i_okcode | TYPE SY-UCOMM, " | |||
| lv_i_sworkid | TYPE SWORKID, " | |||
| lv_i_loghandle | TYPE BALLOGHNDL, " | |||
| lv_i_s_gdisplay_profile | TYPE BAL_S_PROF, " | |||
| lv_i_flg_testrun | TYPE TESTRUN, " | |||
| lv_i_s_rcaptr_api | TYPE RCAPTR_API_STRUCT. " |
|   CALL FUNCTION 'FVD_CAPTR_OL_RELEASE' "Release Capital Transfer |
| EXPORTING | ||
| I_S_VDARL_KEY | = lv_i_s_vdarl_key | |
| I_RBO | = lv_i_rbo | |
| I_S_POST_INFO | = lv_i_s_post_info | |
| I_OKCODE | = lv_i_okcode | |
| I_SWORKID | = lv_i_sworkid | |
| I_LOGHANDLE | = lv_i_loghandle | |
| I_S_GDISPLAY_PROFILE | = lv_i_s_gdisplay_profile | |
| I_FLG_TESTRUN | = lv_i_flg_testrun | |
| I_S_RCAPTR_API | = lv_i_s_rcaptr_api | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| FATAL_ERROR = 2 | ||
| . " FVD_CAPTR_OL_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CAPTR_OL_RELEASE
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 UCOMM FROM SY INTO @DATA(ld_i_okcode). | ||||
Search for further information about these or an SAP related objects