SAP VANLA1_READ_BLOCK Function Module for
VANLA1_READ_BLOCK is a standard vanla1 read block 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 vanla1 read block FM, simply by entering the name VANLA1_READ_BLOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABLR
Program Name: SAPLABLR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VANLA1_READ_BLOCK 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 'VANLA1_READ_BLOCK'".
EXPORTING
F_ANLN1 = "
F_ANLN2 = "
* F_GOON = 'X' "
I_BUKRS = "
* I_DEAKT = '00000000' "
* I_ZUJHR = '9999' "
IMPORTING
F_ANLN1 = "
F_ANLN2 = "
F_GOON = "
TABLES
R_ANLN1 = "
R_ANLN2 = "
T_VANLA1 = "
IMPORTING Parameters details for VANLA1_READ_BLOCK
F_ANLN1 -
Data type: ANLA-ANLN1Optional: No
Call by Reference: No ( called with pass by value option)
F_ANLN2 -
Data type: ANLA-ANLN2Optional: No
Call by Reference: No ( called with pass by value option)
F_GOON -
Data type: ANLA-EIGKZDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: ANLA-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_DEAKT -
Data type: ANLA-DEAKTDefault: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ZUJHR -
Data type: ANLA-ZUJHRDefault: '9999'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VANLA1_READ_BLOCK
F_ANLN1 -
Data type: ANLA-ANLN1Optional: No
Call by Reference: No ( called with pass by value option)
F_ANLN2 -
Data type: ANLA-ANLN2Optional: No
Call by Reference: No ( called with pass by value option)
F_GOON -
Data type: ANLA-EIGKZOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for VANLA1_READ_BLOCK
R_ANLN1 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
R_ANLN2 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
T_VANLA1 -
Data type: V_ANLA_1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VANLA1_READ_BLOCK 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_f_anln1 | TYPE ANLA-ANLN1, " | |||
| lv_f_anln1 | TYPE ANLA-ANLN1, " | |||
| lt_r_anln1 | TYPE STANDARD TABLE OF ANLA, " | |||
| lv_f_anln2 | TYPE ANLA-ANLN2, " | |||
| lv_f_anln2 | TYPE ANLA-ANLN2, " | |||
| lt_r_anln2 | TYPE STANDARD TABLE OF ANLA, " | |||
| lv_f_goon | TYPE ANLA-EIGKZ, " | |||
| lv_f_goon | TYPE ANLA-EIGKZ, " 'X' | |||
| lt_t_vanla1 | TYPE STANDARD TABLE OF V_ANLA_1, " | |||
| lv_i_bukrs | TYPE ANLA-BUKRS, " | |||
| lv_i_deakt | TYPE ANLA-DEAKT, " '00000000' | |||
| lv_i_zujhr | TYPE ANLA-ZUJHR. " '9999' |
|   CALL FUNCTION 'VANLA1_READ_BLOCK' " |
| EXPORTING | ||
| F_ANLN1 | = lv_f_anln1 | |
| F_ANLN2 | = lv_f_anln2 | |
| F_GOON | = lv_f_goon | |
| I_BUKRS | = lv_i_bukrs | |
| I_DEAKT | = lv_i_deakt | |
| I_ZUJHR | = lv_i_zujhr | |
| IMPORTING | ||
| F_ANLN1 | = lv_f_anln1 | |
| F_ANLN2 | = lv_f_anln2 | |
| F_GOON | = lv_f_goon | |
| TABLES | ||
| R_ANLN1 | = lt_r_anln1 | |
| R_ANLN2 | = lt_r_anln2 | |
| T_VANLA1 | = lt_t_vanla1 | |
| . " VANLA1_READ_BLOCK | ||
ABAP code using 7.40 inline data declarations to call FM VANLA1_READ_BLOCK
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 ANLN1 FROM ANLA INTO @DATA(ld_f_anln1). | ||||
| "SELECT single ANLN1 FROM ANLA INTO @DATA(ld_f_anln1). | ||||
| "SELECT single ANLN2 FROM ANLA INTO @DATA(ld_f_anln2). | ||||
| "SELECT single ANLN2 FROM ANLA INTO @DATA(ld_f_anln2). | ||||
| "SELECT single EIGKZ FROM ANLA INTO @DATA(ld_f_goon). | ||||
| "SELECT single EIGKZ FROM ANLA INTO @DATA(ld_f_goon). | ||||
| DATA(ld_f_goon) | = 'X'. | |||
| "SELECT single BUKRS FROM ANLA INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single DEAKT FROM ANLA INTO @DATA(ld_i_deakt). | ||||
| DATA(ld_i_deakt) | = '00000000'. | |||
| "SELECT single ZUJHR FROM ANLA INTO @DATA(ld_i_zujhr). | ||||
| DATA(ld_i_zujhr) | = '9999'. | |||
Search for further information about these or an SAP related objects