SAP QEH2_READ_BY_APPLICATION Function Module for NOTRANSL: QEWL zu Anwendung und User einlesen
QEH2_READ_BY_APPLICATION is a standard qeh2 read by 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 NOTRANSL: QEWL zu Anwendung und User einlesen 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 qeh2 read by application FM, simply by entering the name QEH2_READ_BY_APPLICATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: QEH2
Program Name: SAPLQEH2
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QEH2_READ_BY_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 'QEH2_READ_BY_APPLICATION'"NOTRANSL: QEWL zu Anwendung und User einlesen.
EXPORTING
APPLICATION = "QM Handheld: Application
* USER = "Name of the inspector
EXCEPTIONS
NO_ENTRIES = 1
IMPORTING Parameters details for QEH2_READ_BY_APPLICATION
APPLICATION - QM Handheld: Application
Data type: QEWL-HHANWOptional: No
Call by Reference: Yes
USER - Name of the inspector
Data type: QEWL-PRUEFEROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRIES - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for QEH2_READ_BY_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.| DATA: | ||||
| lv_no_entries | TYPE STRING, " | |||
| lv_application | TYPE QEWL-HHANW, " | |||
| lv_user | TYPE QEWL-PRUEFER. " |
|   CALL FUNCTION 'QEH2_READ_BY_APPLICATION' "NOTRANSL: QEWL zu Anwendung und User einlesen |
| EXPORTING | ||
| APPLICATION | = lv_application | |
| USER | = lv_user | |
| EXCEPTIONS | ||
| NO_ENTRIES = 1 | ||
| . " QEH2_READ_BY_APPLICATION | ||
ABAP code using 7.40 inline data declarations to call FM QEH2_READ_BY_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.| "SELECT single HHANW FROM QEWL INTO @DATA(ld_application). | ||||
| "SELECT single PRUEFER FROM QEWL INTO @DATA(ld_user). | ||||
Search for further information about these or an SAP related objects