SAP GET_VERIFY_SU Function Module for Verify storage unit
GET_VERIFY_SU is a standard get verify su SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Verify storage unit 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 get verify su FM, simply by entering the name GET_VERIFY_SU into the relevant SAP transaction such as SE37 or SE38.
Function Group: LMGT
Program Name: SAPLLMGT
Main Program: SAPLLMGT
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_VERIFY_SU 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 'GET_VERIFY_SU'"Verify storage unit.
EXPORTING
I_WHS_ID = "Warehouse id
I_SU_ID = "Storage unit
TABLES
T_SU_RECORD = "SU data
EXCEPTIONS
NO_RECORD_FOUND = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLLMGT_001 Extension for barcode translation
EXIT_SAPLLMGT_083 User exit for print
IMPORTING Parameters details for GET_VERIFY_SU
I_WHS_ID - Warehouse id
Data type: LEIN-LGNUMOptional: No
Call by Reference: No ( called with pass by value option)
I_SU_ID - Storage unit
Data type: LEIN-LENUMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GET_VERIFY_SU
T_SU_RECORD - SU data
Data type: LEINOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RECORD_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_VERIFY_SU 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_whs_id | TYPE LEIN-LGNUM, " | |||
| lt_t_su_record | TYPE STANDARD TABLE OF LEIN, " | |||
| lv_no_record_found | TYPE LEIN, " | |||
| lv_i_su_id | TYPE LEIN-LENUM. " |
|   CALL FUNCTION 'GET_VERIFY_SU' "Verify storage unit |
| EXPORTING | ||
| I_WHS_ID | = lv_i_whs_id | |
| I_SU_ID | = lv_i_su_id | |
| TABLES | ||
| T_SU_RECORD | = lt_t_su_record | |
| EXCEPTIONS | ||
| NO_RECORD_FOUND = 1 | ||
| . " GET_VERIFY_SU | ||
ABAP code using 7.40 inline data declarations to call FM GET_VERIFY_SU
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 LGNUM FROM LEIN INTO @DATA(ld_i_whs_id). | ||||
| "SELECT single LENUM FROM LEIN INTO @DATA(ld_i_su_id). | ||||
Search for further information about these or an SAP related objects