SAP QAPOVE_POST_DATA Function Module for NOTRANSL: post data
QAPOVE_POST_DATA is a standard qapove post data 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: post data 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 post data FM, simply by entering the name QAPOVE_POST_DATA 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: 1

Function QAPOVE_POST_DATA 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_POST_DATA'"NOTRANSL: post data.
EXPORTING
I_QAVE = "Inspection processing: Usage decision
I_UPSL = "Data Base Access
I_QALS = "Inspection lot record
IMPORTING Parameters details for QAPOVE_POST_DATA
I_QAVE - Inspection processing: Usage decision
Data type: QAVEOptional: No
Call by Reference: No ( called with pass by value option)
I_UPSL - Data Base Access
Data type: QUPSLOptional: No
Call by Reference: No ( called with pass by value option)
I_QALS - Inspection lot record
Data type: QALSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QAPOVE_POST_DATA 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_qave | TYPE QAVE, " | |||
| lv_i_upsl | TYPE QUPSL, " | |||
| lv_i_qals | TYPE QALS. " |
|   CALL FUNCTION 'QAPOVE_POST_DATA' "NOTRANSL: post data |
| EXPORTING | ||
| I_QAVE | = lv_i_qave | |
| I_UPSL | = lv_i_upsl | |
| I_QALS | = lv_i_qals | |
| . " QAPOVE_POST_DATA | ||
ABAP code using 7.40 inline data declarations to call FM QAPOVE_POST_DATA
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