SAP TQ34_READ Function Module for NOTRANSL: Lesen der TQ34
TQ34_READ is a standard tq34 read 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: Lesen der TQ34 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 tq34 read FM, simply by entering the name TQ34_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CQTA
Program Name: SAPLCQTA
Main Program: SAPLCQTA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TQ34_READ 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 'TQ34_READ'"NOTRANSL: Lesen der TQ34.
EXPORTING
I_ART = "Inspection Type
IMPORTING
E_TQ34 = "Default values for inspection type
EXCEPTIONS
NO_ENTRY = 1
IMPORTING Parameters details for TQ34_READ
I_ART - Inspection Type
Data type: TQ30-ARTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TQ34_READ
E_TQ34 - Default values for inspection type
Data type: TQ34Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ENTRY - No Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TQ34_READ 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_art | TYPE TQ30-ART, " | |||
| lv_e_tq34 | TYPE TQ34, " | |||
| lv_no_entry | TYPE TQ34. " |
|   CALL FUNCTION 'TQ34_READ' "NOTRANSL: Lesen der TQ34 |
| EXPORTING | ||
| I_ART | = lv_i_art | |
| IMPORTING | ||
| E_TQ34 | = lv_e_tq34 | |
| EXCEPTIONS | ||
| NO_ENTRY = 1 | ||
| . " TQ34_READ | ||
ABAP code using 7.40 inline data declarations to call FM TQ34_READ
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 ART FROM TQ30 INTO @DATA(ld_i_art). | ||||
Search for further information about these or an SAP related objects