SAP FVD_PAY_DIP_USAGE_SAVE Function Module for Save differentiated incoming payment (DIP) usage data on database
FVD_PAY_DIP_USAGE_SAVE is a standard fvd pay dip usage save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save differentiated incoming payment (DIP) usage data on database 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 pay dip usage save FM, simply by entering the name FVD_PAY_DIP_USAGE_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRDZ_H
Program Name: SAPLTRDZ_H
Main Program: SAPLTRDZ_H
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_PAY_DIP_USAGE_SAVE 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_PAY_DIP_USAGE_SAVE'"Save differentiated incoming payment (DIP) usage data on database.
EXPORTING
* I_FLG_UPDATE_TASK = 'X' "'X' -> start in update task
EXCEPTIONS
VDBEPI_UPDATE_ERROR = 1
IMPORTING Parameters details for FVD_PAY_DIP_USAGE_SAVE
I_FLG_UPDATE_TASK - 'X' -> start in update task
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
VDBEPI_UPDATE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_PAY_DIP_USAGE_SAVE 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_flg_update_task | TYPE FLAG, " 'X' | |||
| lv_vdbepi_update_error | TYPE FLAG. " |
|   CALL FUNCTION 'FVD_PAY_DIP_USAGE_SAVE' "Save differentiated incoming payment (DIP) usage data on database |
| EXPORTING | ||
| I_FLG_UPDATE_TASK | = lv_i_flg_update_task | |
| EXCEPTIONS | ||
| VDBEPI_UPDATE_ERROR = 1 | ||
| . " FVD_PAY_DIP_USAGE_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_PAY_DIP_USAGE_SAVE
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_flg_update_task) | = 'X'. | |||
Search for further information about these or an SAP related objects