SAP DYNPRO_CONFIRMATION Function Module for Display Screen for the Release (All Objects)
DYNPRO_CONFIRMATION is a standard dynpro confirmation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Screen for the Release (All Objects) 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 dynpro confirmation FM, simply by entering the name DYNPRO_CONFIRMATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZLWF
Program Name: SAPLFVZLWF
Main Program: SAPLFVZLWF
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DYNPRO_CONFIRMATION 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 'DYNPRO_CONFIRMATION'"Display Screen for the Release (All Objects).
EXPORTING
* I_SFGOBJ = "
* I_SKEY1 = "
* I_SKEY2 = "
I_MODE = "
* I_BSCHWRT = "Schwellwert Betrag (temp. für alte Auszahlung)
* I_WAERS = "Währungsschlüssel (temp. für alte Auszahlung)
* I_LOGHANDLE = "Application Log: Log Handle
IMPORTING
E_USERACTION = "
EXCEPTIONS
OBJECT_NOT_FOUND = 1 NO_CONTRACT_FOUND = 2
IMPORTING Parameters details for DYNPRO_CONFIRMATION
I_SFGOBJ -
Data type: VZFGD-SFGOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SKEY1 -
Data type: VZFGD-SKEY1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SKEY2 -
Data type: VZFGD-SKEY2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE -
Data type: VZFGD-SKEY1Optional: No
Call by Reference: No ( called with pass by value option)
I_BSCHWRT - Schwellwert Betrag (temp. für alte Auszahlung)
Data type: VZFGD-BSCHWRTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WAERS - Währungsschlüssel (temp. für alte Auszahlung)
Data type: VZFGD-WAERSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LOGHANDLE - Application Log: Log Handle
Data type: BALDAT-LOG_HANDLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DYNPRO_CONFIRMATION
E_USERACTION -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CONTRACT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DYNPRO_CONFIRMATION 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_sfgobj | TYPE VZFGD-SFGOBJ, " | |||
| lv_e_useraction | TYPE C, " | |||
| lv_object_not_found | TYPE C, " | |||
| lv_i_skey1 | TYPE VZFGD-SKEY1, " | |||
| lv_no_contract_found | TYPE VZFGD, " | |||
| lv_i_skey2 | TYPE VZFGD-SKEY2, " | |||
| lv_i_mode | TYPE VZFGD-SKEY1, " | |||
| lv_i_bschwrt | TYPE VZFGD-BSCHWRT, " | |||
| lv_i_waers | TYPE VZFGD-WAERS, " | |||
| lv_i_loghandle | TYPE BALDAT-LOG_HANDLE. " |
|   CALL FUNCTION 'DYNPRO_CONFIRMATION' "Display Screen for the Release (All Objects) |
| EXPORTING | ||
| I_SFGOBJ | = lv_i_sfgobj | |
| I_SKEY1 | = lv_i_skey1 | |
| I_SKEY2 | = lv_i_skey2 | |
| I_MODE | = lv_i_mode | |
| I_BSCHWRT | = lv_i_bschwrt | |
| I_WAERS | = lv_i_waers | |
| I_LOGHANDLE | = lv_i_loghandle | |
| IMPORTING | ||
| E_USERACTION | = lv_e_useraction | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| NO_CONTRACT_FOUND = 2 | ||
| . " DYNPRO_CONFIRMATION | ||
ABAP code using 7.40 inline data declarations to call FM DYNPRO_CONFIRMATION
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 SFGOBJ FROM VZFGD INTO @DATA(ld_i_sfgobj). | ||||
| "SELECT single SKEY1 FROM VZFGD INTO @DATA(ld_i_skey1). | ||||
| "SELECT single SKEY2 FROM VZFGD INTO @DATA(ld_i_skey2). | ||||
| "SELECT single SKEY1 FROM VZFGD INTO @DATA(ld_i_mode). | ||||
| "SELECT single BSCHWRT FROM VZFGD INTO @DATA(ld_i_bschwrt). | ||||
| "SELECT single WAERS FROM VZFGD INTO @DATA(ld_i_waers). | ||||
| "SELECT single LOG_HANDLE FROM BALDAT INTO @DATA(ld_i_loghandle). | ||||
Search for further information about these or an SAP related objects