SAP FPB_EXP_DEQUEUE_LOCK Function Module for DEQUEUE lock for expressplanning
FPB_EXP_DEQUEUE_LOCK is a standard fpb exp dequeue lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DEQUEUE lock for expressplanning 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 fpb exp dequeue lock FM, simply by entering the name FPB_EXP_DEQUEUE_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPB_EXP_UTILITIES
Program Name: SAPLFPB_EXP_UTILITIES
Main Program: SAPLFPB_EXP_UTILITIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FPB_EXP_DEQUEUE_LOCK 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 'FPB_EXP_DEQUEUE_LOCK'"DEQUEUE lock for expressplanning.
EXPORTING
ID_SCENARIO = "Planning Scenario
ID_INSTANCE = "Express Planning Instance
* ID_UNAME = "User Name
* ID_PHASE = "Express Planning Phase
* ID_STEPGROUP = "Planning Step
* ID_STEP = "Planning Substep
* ID_OBJECT = "General Object
IMPORTING Parameters details for FPB_EXP_DEQUEUE_LOCK
ID_SCENARIO - Planning Scenario
Data type: FPB_EXP_STAT-SCENARIOOptional: No
Call by Reference: No ( called with pass by value option)
ID_INSTANCE - Express Planning Instance
Data type: FPB_EXP_STAT-INSTANCEOptional: No
Call by Reference: No ( called with pass by value option)
ID_UNAME - User Name
Data type: FPB_EXP_STAT-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_PHASE - Express Planning Phase
Data type: FPB_EXP_STAT-PHASEOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_STEPGROUP - Planning Step
Data type: FPB_EXP_STAT-STEPGROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_STEP - Planning Substep
Data type: FPB_EXP_STAT-STEPOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_OBJECT - General Object
Data type: FPB_EXP_STAT-OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FPB_EXP_DEQUEUE_LOCK 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_id_scenario | TYPE FPB_EXP_STAT-SCENARIO, " | |||
| lv_id_instance | TYPE FPB_EXP_STAT-INSTANCE, " | |||
| lv_id_uname | TYPE FPB_EXP_STAT-UNAME, " | |||
| lv_id_phase | TYPE FPB_EXP_STAT-PHASE, " | |||
| lv_id_stepgroup | TYPE FPB_EXP_STAT-STEPGROUP, " | |||
| lv_id_step | TYPE FPB_EXP_STAT-STEP, " | |||
| lv_id_object | TYPE FPB_EXP_STAT-OBJECT. " |
|   CALL FUNCTION 'FPB_EXP_DEQUEUE_LOCK' "DEQUEUE lock for expressplanning |
| EXPORTING | ||
| ID_SCENARIO | = lv_id_scenario | |
| ID_INSTANCE | = lv_id_instance | |
| ID_UNAME | = lv_id_uname | |
| ID_PHASE | = lv_id_phase | |
| ID_STEPGROUP | = lv_id_stepgroup | |
| ID_STEP | = lv_id_step | |
| ID_OBJECT | = lv_id_object | |
| . " FPB_EXP_DEQUEUE_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM FPB_EXP_DEQUEUE_LOCK
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 SCENARIO FROM FPB_EXP_STAT INTO @DATA(ld_id_scenario). | ||||
| "SELECT single INSTANCE FROM FPB_EXP_STAT INTO @DATA(ld_id_instance). | ||||
| "SELECT single UNAME FROM FPB_EXP_STAT INTO @DATA(ld_id_uname). | ||||
| "SELECT single PHASE FROM FPB_EXP_STAT INTO @DATA(ld_id_phase). | ||||
| "SELECT single STEPGROUP FROM FPB_EXP_STAT INTO @DATA(ld_id_stepgroup). | ||||
| "SELECT single STEP FROM FPB_EXP_STAT INTO @DATA(ld_id_step). | ||||
| "SELECT single OBJECT FROM FPB_EXP_STAT INTO @DATA(ld_id_object). | ||||
Search for further information about these or an SAP related objects