SAP QET4_GET_INSPLOT Function Module for NOTRANSL: Liefert die Prüflose
QET4_GET_INSPLOT is a standard qet4 get insplot 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: Liefert die Prüflose 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 qet4 get insplot FM, simply by entering the name QET4_GET_INSPLOT into the relevant SAP transaction such as SE37 or SE38.
Function Group: QET4
Program Name: SAPLQET4
Main Program: SAPLQET4
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QET4_GET_INSPLOT 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 'QET4_GET_INSPLOT'"NOTRANSL: Liefert die Prüflose.
EXPORTING
I_NUMBER = "
IMPORTING
E_INSPLOT = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for QET4_GET_INSPLOT
I_NUMBER -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for QET4_GET_INSPLOT
E_INSPLOT -
Data type: BAPI2045D_IL0Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QET4_GET_INSPLOT 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_number | TYPE SY-TABIX, " | |||
| lv_e_insplot | TYPE BAPI2045D_IL0, " | |||
| lv_not_found | TYPE BAPI2045D_IL0. " |
|   CALL FUNCTION 'QET4_GET_INSPLOT' "NOTRANSL: Liefert die Prüflose |
| EXPORTING | ||
| I_NUMBER | = lv_i_number | |
| IMPORTING | ||
| E_INSPLOT | = lv_e_insplot | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " QET4_GET_INSPLOT | ||
ABAP code using 7.40 inline data declarations to call FM QET4_GET_INSPLOT
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 TABIX FROM SY INTO @DATA(ld_i_number). | ||||
Search for further information about these or an SAP related objects