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

Function FVD_GEN_DISB_API_CHANGE 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_GEN_DISB_API_CHANGE'"Wrapper API for Create Disbursement.
EXPORTING
I_STR_RDISB_API = "API Interface Structure and Control Data for Disbursement
* I_TAB_ADDFLOWS = "Table Type for RBOBEPP_API (Standard)
* I_STR_POST_INFO = "Posting Information
* I_CALLN_APPLN = 'INT' "Calling Application
* I_COMPLETION_REQD = ' ' "Should it be posted directly?
* I_STR_BPCA = "Business Process Chain Assignment
IMPORTING
E_STR_DISB = "Details of Single Disbursement
E_TAB_ADDFLOWS = "Table Type for RBOBEPP_API_GEN
E_TAB_VDAUSZ = "Table Type for VDAUSZ (Standard Table)
E_TAB_VDBEKI = "Table Type for Table VDBEKI
E_TAB_VDBEPI = "Table Type for Table VDBEPI
E_TAB_VDBEPP = "Table Type for Table VDBEPP
E_TAB_BAPIERR = "Table Types for Error Handling
EXCEPTIONS
FATAL_ERROR = 1 ERROR_RELEASE_PROCEDURE = 2 ERROR_IN_IMPORT = 3
IMPORTING Parameters details for FVD_GEN_DISB_API_CHANGE
I_STR_RDISB_API - API Interface Structure and Control Data for Disbursement
Data type: RDISB_API_GENOptional: No
Call by Reference: Yes
I_TAB_ADDFLOWS - Table Type for RBOBEPP_API (Standard)
Data type: TRTY_RBOBEPP_API_GENOptional: Yes
Call by Reference: Yes
I_STR_POST_INFO - Posting Information
Data type: RBO_POSTINFO_UIOptional: 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)
I_COMPLETION_REQD - Should it be posted directly?
Data type: FLAGDefault: ' '
Optional: Yes
Call by Reference: Yes
I_STR_BPCA - Business Process Chain Assignment
Data type: FVD_STR_BPCAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_GEN_DISB_API_CHANGE
E_STR_DISB - Details of Single Disbursement
Data type: RDISB_DETAILOptional: No
Call by Reference: Yes
E_TAB_ADDFLOWS - Table Type for RBOBEPP_API_GEN
Data type: TRTY_RBOBEPP_API_GENOptional: No
Call by Reference: Yes
E_TAB_VDAUSZ - Table Type for VDAUSZ (Standard Table)
Data type: TRTY_VDAUSZ_BOptional: 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_VDBEPP - Table Type for Table VDBEPP
Data type: TRTY_VDBEPPOptional: No
Call by Reference: Yes
E_TAB_BAPIERR - Table Types for Error Handling
Data type: BAPIERR_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
FATAL_ERROR - Serious Error has occured
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_RELEASE_PROCEDURE - Error in Release procedure
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_IMPORT - Invalid Loan Details
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_GEN_DISB_API_CHANGE 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_e_str_disb | TYPE RDISB_DETAIL, " | |||
| lv_fatal_error | TYPE RDISB_DETAIL, " | |||
| lv_i_str_rdisb_api | TYPE RDISB_API_GEN, " | |||
| lv_e_tab_addflows | TYPE TRTY_RBOBEPP_API_GEN, " | |||
| lv_i_tab_addflows | TYPE TRTY_RBOBEPP_API_GEN, " | |||
| lv_error_release_procedure | TYPE TRTY_RBOBEPP_API_GEN, " | |||
| lv_e_tab_vdausz | TYPE TRTY_VDAUSZ_B, " | |||
| lv_error_in_import | TYPE TRTY_VDAUSZ_B, " | |||
| lv_i_str_post_info | TYPE RBO_POSTINFO_UI, " | |||
| lv_e_tab_vdbeki | TYPE TRTY_VDBEKI, " | |||
| lv_i_calln_appln | TYPE TB_CALLNG_APPLN, " 'INT' | |||
| lv_e_tab_vdbepi | TYPE TRTY_VDBEPI, " | |||
| lv_i_completion_reqd | TYPE FLAG, " ' ' | |||
| lv_i_str_bpca | TYPE FVD_STR_BPCA, " | |||
| lv_e_tab_vdbepp | TYPE TRTY_VDBEPP, " | |||
| lv_e_tab_bapierr | TYPE BAPIERR_T. " |
|   CALL FUNCTION 'FVD_GEN_DISB_API_CHANGE' "Wrapper API for Create Disbursement |
| EXPORTING | ||
| I_STR_RDISB_API | = lv_i_str_rdisb_api | |
| I_TAB_ADDFLOWS | = lv_i_tab_addflows | |
| I_STR_POST_INFO | = lv_i_str_post_info | |
| I_CALLN_APPLN | = lv_i_calln_appln | |
| I_COMPLETION_REQD | = lv_i_completion_reqd | |
| I_STR_BPCA | = lv_i_str_bpca | |
| IMPORTING | ||
| E_STR_DISB | = lv_e_str_disb | |
| E_TAB_ADDFLOWS | = lv_e_tab_addflows | |
| E_TAB_VDAUSZ | = lv_e_tab_vdausz | |
| E_TAB_VDBEKI | = lv_e_tab_vdbeki | |
| E_TAB_VDBEPI | = lv_e_tab_vdbepi | |
| E_TAB_VDBEPP | = lv_e_tab_vdbepp | |
| E_TAB_BAPIERR | = lv_e_tab_bapierr | |
| EXCEPTIONS | ||
| FATAL_ERROR = 1 | ||
| ERROR_RELEASE_PROCEDURE = 2 | ||
| ERROR_IN_IMPORT = 3 | ||
| . " FVD_GEN_DISB_API_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_GEN_DISB_API_CHANGE
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'. | |||
| DATA(ld_i_completion_reqd) | = ' '. | |||
Search for further information about these or an SAP related objects