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

Function FVD_CAPTR_API_CREATE_AND_POST 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_API_CREATE_AND_POST'"Create and Post Capital Transfer.
EXPORTING
I_STR_RCAPTR_API = "CAPTR: API Interface Structure and Control Data
* I_TAB_ADDFLOWS = "Table Type for RBOBEPP_API (Standard)
* I_STR_POST_INFO = "CAPTR: Save Information of Capital Transfer
* I_CALLN_APPLN = 'INT' "Calling Application
IMPORTING
E_STR_VDCAPTR = "Capital Transfer Master Data
E_RBO = "Business operation number (loans)
E_TAB_VDBEKI = "Table Type for Table VDBEKI
E_TAB_VDBEPI = "Table Type for Table VDBEPI
E_TAB_BAPIERR = "Data of Application Log
EXCEPTIONS
FATAL_ERROR = 1 MANDATE_NOT_VALID = 2 SEPA_ERROR = 3
IMPORTING Parameters details for FVD_CAPTR_API_CREATE_AND_POST
I_STR_RCAPTR_API - CAPTR: API Interface Structure and Control Data
Data type: RCAPTR_APIOptional: No
Call by Reference: Yes
I_TAB_ADDFLOWS - Table Type for RBOBEPP_API (Standard)
Data type: TRTY_RBOBEPP_APIOptional: Yes
Call by Reference: Yes
I_STR_POST_INFO - CAPTR: Save Information of Capital Transfer
Data type: RCAPTR_SAVEOptional: Yes
Call by Reference: Yes
I_CALLN_APPLN - Calling Application
Data type: TB_CALLNG_APPLNDefault: 'INT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_CAPTR_API_CREATE_AND_POST
E_STR_VDCAPTR - Capital Transfer Master Data
Data type: VDCAPTROptional: No
Call by Reference: Yes
E_RBO - Business operation number (loans)
Data type: RBOOptional: No
Call by Reference: Yes
E_TAB_VDBEKI - Table Type for Table VDBEKI
Data type: TRTY_VDBEKIOptional: No
Call by Reference: Yes
E_TAB_VDBEPI - Table Type for Table VDBEPI
Data type: TRTY_VDBEPIOptional: No
Call by Reference: Yes
E_TAB_BAPIERR - Data of Application Log
Data type: BAPIERR_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
FATAL_ERROR - Serious error has occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MANDATE_NOT_VALID - Invalid SEPA Mandate for an EDD Payment Method
Data type:Optional: No
Call by Reference: Yes
SEPA_ERROR - SEPA Information Cannot Be Processed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_CAPTR_API_CREATE_AND_POST 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_e_str_vdcaptr | TYPE VDCAPTR, " | |||
| lv_i_str_rcaptr_api | TYPE RCAPTR_API, " | |||
| lv_e_rbo | TYPE RBO, " | |||
| lv_i_tab_addflows | TYPE TRTY_RBOBEPP_API, " | |||
| lv_mandate_not_valid | TYPE TRTY_RBOBEPP_API, " | |||
| lv_sepa_error | TYPE TRTY_RBOBEPP_API, " | |||
| lv_e_tab_vdbeki | TYPE TRTY_VDBEKI, " | |||
| lv_i_str_post_info | TYPE RCAPTR_SAVE, " | |||
| lv_e_tab_vdbepi | TYPE TRTY_VDBEPI, " | |||
| lv_i_calln_appln | TYPE TB_CALLNG_APPLN, " 'INT' | |||
| lv_e_tab_bapierr | TYPE BAPIERR_T. " |
|   CALL FUNCTION 'FVD_CAPTR_API_CREATE_AND_POST' "Create and Post Capital Transfer |
| EXPORTING | ||
| I_STR_RCAPTR_API | = lv_i_str_rcaptr_api | |
| I_TAB_ADDFLOWS | = lv_i_tab_addflows | |
| I_STR_POST_INFO | = lv_i_str_post_info | |
| I_CALLN_APPLN | = lv_i_calln_appln | |
| IMPORTING | ||
| E_STR_VDCAPTR | = lv_e_str_vdcaptr | |
| E_RBO | = lv_e_rbo | |
| E_TAB_VDBEKI | = lv_e_tab_vdbeki | |
| E_TAB_VDBEPI | = lv_e_tab_vdbepi | |
| E_TAB_BAPIERR | = lv_e_tab_bapierr | |
| EXCEPTIONS | ||
| FATAL_ERROR = 1 | ||
| MANDATE_NOT_VALID = 2 | ||
| SEPA_ERROR = 3 | ||
| . " FVD_CAPTR_API_CREATE_AND_POST | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CAPTR_API_CREATE_AND_POST
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.| DATA(ld_i_calln_appln) | = 'INT'. | |||
Search for further information about these or an SAP related objects