SAP FVD_GEN_DISB_API_CHANGE_POST Function Module for Change and Activate Created Disbursement

Search SAP Function Modules

FVD_GEN_DISB_API_CHANGE_POST is a standard fvd gen disb api change 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 Change and Activate Created 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 post FM, simply by entering the name FVD_GEN_DISB_API_CHANGE_POST 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_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_GEN_DISB_API_CHANGE_POST'"Change and Activate Created Disbursement
  EXPORTING
   I_STR_RDISB_API =  "DISB: API Oberflächenstruktur  und Steuerdaten
*  I_TAB_ADDFLOWS =  "Table Type for RBOBEPP_API_GEN
*  I_CALLN_APPLN = 'INT' "Calling Application
*  I_BPCA =  "Business Process Chain Assignment
*  I_STR_POST_INFO =  "Posting Information

 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_VDBEPP =  "Table Type for Table VDBEPP
   E_TAB_BAPIERR =  "Data of Application Log
   E_TAB_VDBEKI =  "Table Type for Table VDBEKI
   E_TAB_VDBEPI =  "Table Type for Table VDBEPI

EXCEPTIONS
   FATAL_ERROR = 1    INPUT_ERROR = 2 

.

IMPORTING Parameters details for FVD_GEN_DISB_API_CHANGE_POST

I_STR_RDISB_API - DISB: API Oberflächenstruktur und Steuerdaten

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

I_TAB_ADDFLOWS - Table Type for RBOBEPP_API_GEN

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

I_CALLN_APPLN - Calling Application

Data type: TB_CALLNG_APPLN
Default: 'INT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BPCA - Business Process Chain Assignment

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

I_STR_POST_INFO - Posting Information

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

EXPORTING Parameters details for FVD_GEN_DISB_API_CHANGE_POST

E_STR_DISB - Details of Single Disbursement

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

E_TAB_ADDFLOWS - Table Type for RBOBEPP_API_GEN

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

E_TAB_VDAUSZ - Table Type for VDAUSZ (Standard Table)

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

E_TAB_VDBEPP - Table Type for Table VDBEPP

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

E_TAB_BAPIERR - Data of Application Log

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

E_TAB_VDBEKI - Table Type for Table VDBEKI

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

E_TAB_VDBEPI - Table Type for Table VDBEPI

Data type: TRTY_VDBEPI
Optional: 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)

INPUT_ERROR - Error in input parameters

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_GEN_DISB_API_CHANGE_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.

ABAP code using 7.40 inline data declarations to call FM FVD_GEN_DISB_API_CHANGE_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.

Search for further information about these or an SAP related objects