SAP CONFIRMATION_IN_APPLICATION Function Module for Release in Application

Search SAP Function Modules

CONFIRMATION_IN_APPLICATION is a standard confirmation in application SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release in Application 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 confirmation in application FM, simply by entering the name CONFIRMATION_IN_APPLICATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVZL
Program Name: SAPLFVZL
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONFIRMATION_IN_APPLICATION 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 'CONFIRMATION_IN_APPLICATION'"Release in Application
  EXPORTING
   FGOBJ =  "Release Object
   KEY1 =  "Schlüssel (40 Stellen)
*  KEY2 = ' ' "Schlüssel-Ergänzung

 IMPORTING
   FGKZ =  "Freigabe(-sperr)kennzeichen
   FGST =  "Freigabestatus (für interne Verwaltung)

EXCEPTIONS
   CONFIRMED_BEFORE = 1    DATA_NOT_FOUND = 2    NOT_AUTORIZED = 3    REFUSED = 4    USER_EQUAL = 5 

.

IMPORTING Parameters details for CONFIRMATION_IN_APPLICATION

FGOBJ - Release Object

Data type: VZFGD-SFGOBJ
Optional: No
Call by Reference: No ( called with pass by value option)

KEY1 - Schlüssel (40 Stellen)

Data type: VZFGD-SKEY1
Optional: No
Call by Reference: No ( called with pass by value option)

KEY2 - Schlüssel-Ergänzung

Data type: VZFGD-SKEY2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CONFIRMATION_IN_APPLICATION

FGKZ - Freigabe(-sperr)kennzeichen

Data type: VZFGD-SFGKZ
Optional: No
Call by Reference: No ( called with pass by value option)

FGST - Freigabestatus (für interne Verwaltung)

Data type: VZFGD-SFGST
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CONFIRMED_BEFORE - bereits freigegeben

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATA_NOT_FOUND - keine Freigabe(-info)daten vorhanden

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_AUTORIZED - Benutzer nicht berechtigt für Freigabe

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REFUSED - Daten abgelehnt, Freigabe nicht möglich

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

USER_EQUAL - Benutzer sind nicht verschieden

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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