SAP QAPOVE_FETCH_MEMORY_FROM_DB Function Module for NOTRANSL: read data from DB









QAPOVE_FETCH_MEMORY_FROM_DB is a standard qapove fetch memory from db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: read data from DB 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 qapove fetch memory from db FM, simply by entering the name QAPOVE_FETCH_MEMORY_FROM_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function QAPOVE_FETCH_MEMORY_FROM_DB 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 'QAPOVE_FETCH_MEMORY_FROM_DB'"NOTRANSL: read data from DB
EXPORTING
I_PRUEFLOS = "Inspection Lot Number
* I_VORGLFNR = "Current Node Number from Order Counter APLZL
* I_KZART = "Inspection Lot, Partial Lot, Single Unit, Interval
* I_ZAEHLER = "Counter for Usage Decision

IMPORTING
E_QAVETAB = "
E_QAVE = "

EXCEPTIONS
NO_ENTRY_FOUND = 1
.



IMPORTING Parameters details for QAPOVE_FETCH_MEMORY_FROM_DB

I_PRUEFLOS - Inspection Lot Number

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

I_VORGLFNR - Current Node Number from Order Counter APLZL

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

I_KZART - Inspection Lot, Partial Lot, Single Unit, Interval

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

I_ZAEHLER - Counter for Usage Decision

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

EXPORTING Parameters details for QAPOVE_FETCH_MEMORY_FROM_DB

E_QAVETAB -

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

E_QAVE -

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

EXCEPTIONS details

NO_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for QAPOVE_FETCH_MEMORY_FROM_DB 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_e_qavetab  TYPE STRING, "   
lv_i_prueflos  TYPE QPLOS, "   
lv_no_entry_found  TYPE QPLOS, "   
lv_e_qave  TYPE QPLOS, "   
lv_i_vorglfnr  TYPE QLFNKN, "   
lv_i_kzart  TYPE QKZART, "   
lv_i_zaehler  TYPE QVEZAEHLER. "   

  CALL FUNCTION 'QAPOVE_FETCH_MEMORY_FROM_DB'  "NOTRANSL: read data from DB
    EXPORTING
         I_PRUEFLOS = lv_i_prueflos
         I_VORGLFNR = lv_i_vorglfnr
         I_KZART = lv_i_kzart
         I_ZAEHLER = lv_i_zaehler
    IMPORTING
         E_QAVETAB = lv_e_qavetab
         E_QAVE = lv_e_qave
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " QAPOVE_FETCH_MEMORY_FROM_DB




ABAP code using 7.40 inline data declarations to call FM QAPOVE_FETCH_MEMORY_FROM_DB

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



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!