SAP READ_CONFIRMATION_RESERVE Function Module for









READ_CONFIRMATION_RESERVE is a standard read confirmation reserve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 read confirmation reserve FM, simply by entering the name READ_CONFIRMATION_RESERVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CORP
Program Name: SAPLCORP
Main Program: SAPLCORP
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function READ_CONFIRMATION_RESERVE 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 'READ_CONFIRMATION_RESERVE'"
  EXPORTING
   AFORI_IMP =  "Origin Indicator of PDC Message (Application)
*  AFRUV_IMP = ' ' "Confirmation pool
*  RVALL_IMP = ' ' "All Operations from Confirmation Pool
*  RVCLO_IMP = ' ' "Confirmed Operations from the Confirmation Pool
*  RVOPE_IMP = 'X' "Operations outstanding from the confirmation pool
*  LOCK_FLAG = 'X' "Selection indicator

 IMPORTING
   AFRH_EXP =  "Header information for confirmation pool

TABLES
   AFRV_TAB =  "Confirmation pool

EXCEPTIONS
   NOT_FOUND = 1    UPDATE_ACTIV = 2    WRONG_APPL = 3
.



IMPORTING Parameters details for READ_CONFIRMATION_RESERVE

AFORI_IMP - Origin Indicator of PDC Message (Application)

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

AFRUV_IMP - Confirmation pool

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

RVALL_IMP - All Operations from Confirmation Pool

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

RVCLO_IMP - Confirmed Operations from the Confirmation Pool

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

RVOPE_IMP - Operations outstanding from the confirmation pool

Data type: AFRU_WF-RVOPE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCK_FLAG - Selection indicator

Data type: RC27X-FLG_SEL
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for READ_CONFIRMATION_RESERVE

AFRH_EXP - Header information for confirmation pool

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

TABLES Parameters details for READ_CONFIRMATION_RESERVE

AFRV_TAB - Confirmation pool

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

EXCEPTIONS details

NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

UPDATE_ACTIV -

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

WRONG_APPL -

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

Copy and paste ABAP code example for READ_CONFIRMATION_RESERVE 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_afrh_exp  TYPE AFRH, "   
lt_afrv_tab  TYPE STANDARD TABLE OF AFRV, "   
lv_afori_imp  TYPE AFRV-AFORI, "   
lv_not_found  TYPE AFRV, "   
lv_afruv_imp  TYPE AFRV-AFRUV, "   SPACE
lv_update_activ  TYPE AFRV, "   
lv_rvall_imp  TYPE AFRU_WF-RVALL, "   SPACE
lv_wrong_appl  TYPE AFRU_WF, "   
lv_rvclo_imp  TYPE AFRU_WF-RVCLO, "   SPACE
lv_rvope_imp  TYPE AFRU_WF-RVOPE, "   'X'
lv_lock_flag  TYPE RC27X-FLG_SEL. "   'X'

  CALL FUNCTION 'READ_CONFIRMATION_RESERVE'  "
    EXPORTING
         AFORI_IMP = lv_afori_imp
         AFRUV_IMP = lv_afruv_imp
         RVALL_IMP = lv_rvall_imp
         RVCLO_IMP = lv_rvclo_imp
         RVOPE_IMP = lv_rvope_imp
         LOCK_FLAG = lv_lock_flag
    IMPORTING
         AFRH_EXP = lv_afrh_exp
    TABLES
         AFRV_TAB = lt_afrv_tab
    EXCEPTIONS
        NOT_FOUND = 1
        UPDATE_ACTIV = 2
        WRONG_APPL = 3
. " READ_CONFIRMATION_RESERVE




ABAP code using 7.40 inline data declarations to call FM READ_CONFIRMATION_RESERVE

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 AFORI FROM AFRV INTO @DATA(ld_afori_imp).
 
 
"SELECT single AFRUV FROM AFRV INTO @DATA(ld_afruv_imp).
DATA(ld_afruv_imp) = ' '.
 
 
"SELECT single RVALL FROM AFRU_WF INTO @DATA(ld_rvall_imp).
DATA(ld_rvall_imp) = ' '.
 
 
"SELECT single RVCLO FROM AFRU_WF INTO @DATA(ld_rvclo_imp).
DATA(ld_rvclo_imp) = ' '.
 
"SELECT single RVOPE FROM AFRU_WF INTO @DATA(ld_rvope_imp).
DATA(ld_rvope_imp) = 'X'.
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_lock_flag).
DATA(ld_lock_flag) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!