SAP SD_STORAGE_LOCATION_DETERMINE Function Module for Storage Location Determination









SD_STORAGE_LOCATION_DETERMINE is a standard sd storage location determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Storage Location Determination 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 sd storage location determine FM, simply by entering the name SD_STORAGE_LOCATION_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: V02V
Program Name: SAPLV02V
Main Program: SAPLV02V
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_STORAGE_LOCATION_DETERMINE 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 'SD_STORAGE_LOCATION_DETERMINE'"Storage Location Determination
EXPORTING
ILAGOF = "Import Structure for Storage Location Determination
* MATERIAL_READ = "Read Material Master?
* FLEPAD_PAKTI = "Determination Log

IMPORTING
ELGORT = "Storage Location Found

EXCEPTIONS
NO_RULE_FOUND = 1 NO_LGORT_FOUND = 2 PLANT_NOT_FOUND = 3 MATERIAL_NOT_FOUND = 4 OTHER_ERRORS = 5
.




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_SAPLV02V_001 User Exit for Sales Area Determination
EXIT_SAPLV02V_002 User Exit Storage Location Determination
EXIT_SAPLV02V_003 User Exit for Door and Staging Area Determination
EXIT_SAPLV02V_004 User Exit for Staging Area Determination - Delivery Item

IMPORTING Parameters details for SD_STORAGE_LOCATION_DETERMINE

ILAGOF - Import Structure for Storage Location Determination

Data type: LAGOF
Optional: No
Call by Reference: No ( called with pass by value option)

MATERIAL_READ - Read Material Master?

Data type: RWAKA-KRAUBE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FLEPAD_PAKTI - Determination Log

Data type: LEPAD_PAR-KZAKT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SD_STORAGE_LOCATION_DETERMINE

ELGORT - Storage Location Found

Data type: T001L-LGORT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_RULE_FOUND - No Determination Rule Found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_LGORT_FOUND - No Storage Location Found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PLANT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MATERIAL_NOT_FOUND - Material Not Found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OTHER_ERRORS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SD_STORAGE_LOCATION_DETERMINE 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_elgort  TYPE T001L-LGORT, "   
lv_ilagof  TYPE LAGOF, "   
lv_no_rule_found  TYPE LAGOF, "   
lv_material_read  TYPE RWAKA-KRAUBE, "   
lv_no_lgort_found  TYPE RWAKA, "   
lv_flepad_pakti  TYPE LEPAD_PAR-KZAKT, "   
lv_plant_not_found  TYPE LEPAD_PAR, "   
lv_material_not_found  TYPE LEPAD_PAR, "   
lv_other_errors  TYPE LEPAD_PAR. "   

  CALL FUNCTION 'SD_STORAGE_LOCATION_DETERMINE'  "Storage Location Determination
    EXPORTING
         ILAGOF = lv_ilagof
         MATERIAL_READ = lv_material_read
         FLEPAD_PAKTI = lv_flepad_pakti
    IMPORTING
         ELGORT = lv_elgort
    EXCEPTIONS
        NO_RULE_FOUND = 1
        NO_LGORT_FOUND = 2
        PLANT_NOT_FOUND = 3
        MATERIAL_NOT_FOUND = 4
        OTHER_ERRORS = 5
. " SD_STORAGE_LOCATION_DETERMINE




ABAP code using 7.40 inline data declarations to call FM SD_STORAGE_LOCATION_DETERMINE

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 LGORT FROM T001L INTO @DATA(ld_elgort).
 
 
 
"SELECT single KRAUBE FROM RWAKA INTO @DATA(ld_material_read).
 
 
"SELECT single KZAKT FROM LEPAD_PAR INTO @DATA(ld_flepad_pakti).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!