SAP K_READ_T001 Function Module for
K_READ_T001 is a standard k read t001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 k read t001 FM, simply by entering the name K_READ_T001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: KOTB
Program Name: SAPLKOTB
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function K_READ_T001 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 'K_READ_T001'".
EXPORTING
I_BUKRS = "Company code
IMPORTING
E_T001 = "Table T001
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for K_READ_T001
I_BUKRS - Company code
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for K_READ_T001
E_T001 - Table T001
Data type: T001Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Entry not found in T001
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for K_READ_T001 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_t001 | TYPE T001, " | |||
lv_i_bukrs | TYPE T001-BUKRS, " | |||
lv_not_found | TYPE T001. " |
  CALL FUNCTION 'K_READ_T001' " |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
IMPORTING | ||
E_T001 | = lv_e_t001 | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " K_READ_T001 |
ABAP code using 7.40 inline data declarations to call FM K_READ_T001
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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
Search for further information about these or an SAP related objects