SAP DELETE_VDZNB_PAYINFO Function Module for Delete Payments of a Payment Postprocessing Transaction
DELETE_VDZNB_PAYINFO is a standard delete vdznb payinfo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete Payments of a Payment Postprocessing Transaction 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 delete vdznb payinfo FM, simply by entering the name DELETE_VDZNB_PAYINFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRDZ_MANAGEMENT
Program Name: SAPLTRDZ_MANAGEMENT
Main Program: SAPLTRDZ_MANAGEMENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DELETE_VDZNB_PAYINFO 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 'DELETE_VDZNB_PAYINFO'"Delete Payments of a Payment Postprocessing Transaction.
EXPORTING
I_ZNB_KEY = "Business operation number (loans)
EXCEPTIONS
ERROR_DELETING_VDZNB_PAYINFO = 1
IMPORTING Parameters details for DELETE_VDZNB_PAYINFO
I_ZNB_KEY - Business operation number (loans)
Data type: VDZNB_HEAD-ZNB_KEYOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_DELETING_VDZNB_PAYINFO -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DELETE_VDZNB_PAYINFO 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_znb_key | TYPE VDZNB_HEAD-ZNB_KEY, " | |||
| lv_error_deleting_vdznb_payinfo | TYPE VDZNB_HEAD. " |
|   CALL FUNCTION 'DELETE_VDZNB_PAYINFO' "Delete Payments of a Payment Postprocessing Transaction |
| EXPORTING | ||
| I_ZNB_KEY | = lv_i_znb_key | |
| EXCEPTIONS | ||
| ERROR_DELETING_VDZNB_PAYINFO = 1 | ||
| . " DELETE_VDZNB_PAYINFO | ||
ABAP code using 7.40 inline data declarations to call FM DELETE_VDZNB_PAYINFO
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 ZNB_KEY FROM VDZNB_HEAD INTO @DATA(ld_i_znb_key). | ||||
Search for further information about these or an SAP related objects