SAP J_2GLOCK_DSD Function Module for Lock DSD
J_2GLOCK_DSD is a standard j 2glock dsd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lock DSD 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 j 2glock dsd FM, simply by entering the name J_2GLOCK_DSD into the relevant SAP transaction such as SE37 or SE38.
Function Group: J2GLPE1
Program Name: SAPLJ2GLPE1
Main Program: SAPLJ2GLPE1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_2GLOCK_DSD 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 'J_2GLOCK_DSD'"Lock DSD.
EXPORTING
I_BUKRS = "Company code
* I_ADDCA = "Additional DSD categorization
* I_SERIES = "Series
* I_DEVID = "Specific DSD to lock
IMPORTING
E_DSD = "DSD locked record
EXCEPTIONS
DSD_NOT_VALID = 1 DSD_NOT_AVAILABLE = 2 SYSTEM_LOCK_FAILURE = 3
IMPORTING Parameters details for J_2GLOCK_DSD
I_BUKRS - Company code
Data type: J_2GLPDSD-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_ADDCA - Additional DSD categorization
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SERIES - Series
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DEVID - Specific DSD to lock
Data type: J_2GLPDSD-DEVIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_2GLOCK_DSD
E_DSD - DSD locked record
Data type: J_2GLPDSDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DSD_NOT_VALID - No valid DSD(s) found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DSD_NOT_AVAILABLE - No available (running) DSD(s) found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_LOCK_FAILURE - Internal error from enqueue server
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_2GLOCK_DSD 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_e_dsd | TYPE J_2GLPDSD, " | |||
| lv_i_bukrs | TYPE J_2GLPDSD-BUKRS, " | |||
| lv_dsd_not_valid | TYPE J_2GLPDSD, " | |||
| lv_i_addca | TYPE J_2GLPDSD, " | |||
| lv_dsd_not_available | TYPE J_2GLPDSD, " | |||
| lv_i_series | TYPE J_2GLPDSD, " | |||
| lv_system_lock_failure | TYPE J_2GLPDSD, " | |||
| lv_i_devid | TYPE J_2GLPDSD-DEVID. " |
|   CALL FUNCTION 'J_2GLOCK_DSD' "Lock DSD |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_ADDCA | = lv_i_addca | |
| I_SERIES | = lv_i_series | |
| I_DEVID | = lv_i_devid | |
| IMPORTING | ||
| E_DSD | = lv_e_dsd | |
| EXCEPTIONS | ||
| DSD_NOT_VALID = 1 | ||
| DSD_NOT_AVAILABLE = 2 | ||
| SYSTEM_LOCK_FAILURE = 3 | ||
| . " J_2GLOCK_DSD | ||
ABAP code using 7.40 inline data declarations to call FM J_2GLOCK_DSD
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 BUKRS FROM J_2GLPDSD INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single DEVID FROM J_2GLPDSD INTO @DATA(ld_i_devid). | ||||
Search for further information about these or an SAP related objects