SAP L_BIN_LOCATION_DEQUEUE Function Module for NOTRANSL: Entsperren Lagerplatz
L_BIN_LOCATION_DEQUEUE is a standard l bin location dequeue 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: Entsperren Lagerplatz 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 l bin location dequeue FM, simply by entering the name L_BIN_LOCATION_DEQUEUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: L03A
Program Name: SAPLL03A
Main Program: SAPLL03A
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function L_BIN_LOCATION_DEQUEUE 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 'L_BIN_LOCATION_DEQUEUE'"NOTRANSL: Entsperren Lagerplatz.
EXPORTING
I_LGNUM = "Warehouse number
I_LGTYP = "Storage Type
I_LGPLA = "Storage Bin
I_LENUM = "Storage Unit
* I_ENQUE = ' ' "
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
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_SAPLL03A_001 Internal Putaway Strategy: Find Storage Bin
EXIT_SAPLL03A_002 Internal Putaway Strategy: Check Specified Storage Bin
EXIT_SAPLL03A_003 Internal Putaway Strategy: Update New Items in Internal Tables
EXIT_SAPLL03A_004 Internal Putaway Strategy: Update Internal Tables of Deleted Items
EXIT_SAPLL03A_005 Internal Stock Removal Strategy: Determine and Sort Stocks
EXIT_SAPLL03A_006 Internal Stock Removal Strategy: Check Default Bin
EXIT_SAPLL03A_007 Internal Stock Removal Strategy: Update Internal Tables of New Items
EXIT_SAPLL03A_008 Internal Stock Removal Strategy: Update Internal Tables of Deleted Items
EXIT_SAPLL03A_009 Overdelivery and if Necessary Underdelivery Via User Exit
EXIT_SAPLL03A_010 Exit: Calculation of Total Planned TO Processing Time
EXIT_SAPLL03A_011 Adjustment of Planned TO Item Processing Time for TO Confirmation
EXIT_SAPLL03A_012 Adjustment of Transfer Order Split for Transfer Order Creation
EXIT_SAPLL03A_013 User Exit for Picking: Strict FIFO
IMPORTING Parameters details for L_BIN_LOCATION_DEQUEUE
I_LGNUM - Warehouse number
Data type: LTAK-LGNUMOptional: No
Call by Reference: No ( called with pass by value option)
I_LGTYP - Storage Type
Data type: LQUA-LGTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_LGPLA - Storage Bin
Data type: LQUA-LGPLAOptional: No
Call by Reference: No ( called with pass by value option)
I_LENUM - Storage Unit
Data type: LQUA-LENUMOptional: No
Call by Reference: No ( called with pass by value option)
I_ENQUE -
Data type: T340D-ENQUEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK - Locked by another user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - System error occurred during blocking
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for L_BIN_LOCATION_DEQUEUE 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_lgnum | TYPE LTAK-LGNUM, " | |||
| lv_foreign_lock | TYPE LTAK, " | |||
| lv_i_lgtyp | TYPE LQUA-LGTYP, " | |||
| lv_system_failure | TYPE LQUA, " | |||
| lv_i_lgpla | TYPE LQUA-LGPLA, " | |||
| lv_i_lenum | TYPE LQUA-LENUM, " | |||
| lv_i_enque | TYPE T340D-ENQUE. " SPACE |
|   CALL FUNCTION 'L_BIN_LOCATION_DEQUEUE' "NOTRANSL: Entsperren Lagerplatz |
| EXPORTING | ||
| I_LGNUM | = lv_i_lgnum | |
| I_LGTYP | = lv_i_lgtyp | |
| I_LGPLA | = lv_i_lgpla | |
| I_LENUM | = lv_i_lenum | |
| I_ENQUE | = lv_i_enque | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " L_BIN_LOCATION_DEQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM L_BIN_LOCATION_DEQUEUE
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 LTAK INTO @DATA(ld_i_lgnum). | ||||
| "SELECT single LGTYP FROM LQUA INTO @DATA(ld_i_lgtyp). | ||||
| "SELECT single LGPLA FROM LQUA INTO @DATA(ld_i_lgpla). | ||||
| "SELECT single LENUM FROM LQUA INTO @DATA(ld_i_lenum). | ||||
| "SELECT single ENQUE FROM T340D INTO @DATA(ld_i_enque). | ||||
| DATA(ld_i_enque) | = ' '. | |||
Search for further information about these or an SAP related objects