SAP FVD_CAPTR_OL_GET_CUSTOMIZING Function Module for Read General and BO-Specific Customizing
FVD_CAPTR_OL_GET_CUSTOMIZING is a standard fvd captr ol get customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read General and BO-Specific Customizing 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 get customizing FM, simply by entering the name FVD_CAPTR_OL_GET_CUSTOMIZING 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_GET_CUSTOMIZING 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_GET_CUSTOMIZING'"Read General and BO-Specific Customizing.
EXPORTING
* I_LOGHANDLE = "Application Log: Log Handle
* I_BUKRS = "Company Code
* I_GSART = "Product Type
* I_MIN_MSGTY = 'I' "nur Messages ab diesem Typ bringen
CHANGING
* C_TAB_GSTEER = "General Control Data of Capital Transfer
* C_TAB_POSTPR = "Indicator Manual Postprocessing
* C_TAB_REASON = "Capital Transfer Reasons
* C_TAB_REPCH = "Repayment Change Indicator Capital Transfer
* C_TAB_TRANSB = "Transfer Behavior Capital Transfer
* C_TAB_TZPLP = "Table Type for TZPLP
IMPORTING Parameters details for FVD_CAPTR_OL_GET_CUSTOMIZING
I_LOGHANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
I_BUKRS - Company Code
Data type: T001-BUKRSOptional: Yes
Call by Reference: Yes
I_GSART - Product Type
Data type: VDARL-GSARTOptional: Yes
Call by Reference: Yes
I_MIN_MSGTY - nur Messages ab diesem Typ bringen
Data type: MSGTYDefault: 'I'
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for FVD_CAPTR_OL_GET_CUSTOMIZING
C_TAB_GSTEER - General Control Data of Capital Transfer
Data type: TRTY_TDCAPTR_GSTEEROptional: Yes
Call by Reference: Yes
C_TAB_POSTPR - Indicator Manual Postprocessing
Data type: TRTY_TDCAPTR_POSTPROptional: Yes
Call by Reference: Yes
C_TAB_REASON - Capital Transfer Reasons
Data type: TRTY_TDCAPTR_REASONOptional: Yes
Call by Reference: Yes
C_TAB_REPCH - Repayment Change Indicator Capital Transfer
Data type: TRTY_TDCAPTR_REPCHOptional: Yes
Call by Reference: Yes
C_TAB_TRANSB - Transfer Behavior Capital Transfer
Data type: TRTY_TDCAPTR_TRANSBOptional: Yes
Call by Reference: Yes
C_TAB_TZPLP - Table Type for TZPLP
Data type: TRTY_TZPLPOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FVD_CAPTR_OL_GET_CUSTOMIZING 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_loghandle | TYPE BALLOGHNDL, " | |||
| lv_c_tab_gsteer | TYPE TRTY_TDCAPTR_GSTEER, " | |||
| lv_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_c_tab_postpr | TYPE TRTY_TDCAPTR_POSTPR, " | |||
| lv_i_gsart | TYPE VDARL-GSART, " | |||
| lv_c_tab_reason | TYPE TRTY_TDCAPTR_REASON, " | |||
| lv_c_tab_repch | TYPE TRTY_TDCAPTR_REPCH, " | |||
| lv_i_min_msgty | TYPE MSGTY, " 'I' | |||
| lv_c_tab_transb | TYPE TRTY_TDCAPTR_TRANSB, " | |||
| lv_c_tab_tzplp | TYPE TRTY_TZPLP. " |
|   CALL FUNCTION 'FVD_CAPTR_OL_GET_CUSTOMIZING' "Read General and BO-Specific Customizing |
| EXPORTING | ||
| I_LOGHANDLE | = lv_i_loghandle | |
| I_BUKRS | = lv_i_bukrs | |
| I_GSART | = lv_i_gsart | |
| I_MIN_MSGTY | = lv_i_min_msgty | |
| CHANGING | ||
| C_TAB_GSTEER | = lv_c_tab_gsteer | |
| C_TAB_POSTPR | = lv_c_tab_postpr | |
| C_TAB_REASON | = lv_c_tab_reason | |
| C_TAB_REPCH | = lv_c_tab_repch | |
| C_TAB_TRANSB | = lv_c_tab_transb | |
| C_TAB_TZPLP | = lv_c_tab_tzplp | |
| . " FVD_CAPTR_OL_GET_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CAPTR_OL_GET_CUSTOMIZING
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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single GSART FROM VDARL INTO @DATA(ld_i_gsart). | ||||
| DATA(ld_i_min_msgty) | = 'I'. | |||
Search for further information about these or an SAP related objects