SAP CS_CL_BGR_LOCK Function Module for NOTRANSL: Setzen von Sperren auf Stücklistengruppe









CS_CL_BGR_LOCK is a standard cs cl bgr 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 NOTRANSL: Setzen von Sperren auf Stücklistengruppe 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 cs cl bgr lock FM, simply by entering the name CS_CL_BGR_LOCK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CSCL_BOM
Program Name: SAPLCSCL_BOM
Main Program: SAPLCSCL_BOM
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CS_CL_BGR_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 'CS_CL_BGR_LOCK'"NOTRANSL: Setzen von Sperren auf Stücklistengruppe
EXPORTING
* MODE_BGR_CLASS_LOCK = 'E' "Lock mode
* MANDT = SY-MANDT "Client
* STLTY = "BOM category
* STLNR = "Bill of material
* X_STLTY = ' ' "
* X_STLNR = ' ' "
* _WAIT = ' ' "
* _COLLECT = ' ' "Only collect locks initially?

IMPORTING
E_NAME = "ABAP System Field: Message Variable

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for CS_CL_BGR_LOCK

MODE_BGR_CLASS_LOCK - Lock mode

Data type: DD26E-ENQMODE
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDT - Client

Data type: BOM_CLASS_DATA-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

STLTY - BOM category

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

STLNR - Bill of material

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

X_STLTY -

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

X_STLNR -

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

_WAIT -

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

_COLLECT - Only collect locks initially?

Data type: DDENQ_LIKE-COLLECT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CS_CL_BGR_LOCK

E_NAME - ABAP System Field: Message Variable

Data type: SY-MSGV1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FOREIGN_LOCK -

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

SYSTEM_FAILURE -

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

Copy and paste ABAP code example for CS_CL_BGR_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_e_name  TYPE SY-MSGV1, "   
lv_foreign_lock  TYPE SY, "   
lv_mode_bgr_class_lock  TYPE DD26E-ENQMODE, "   'E'
lv_mandt  TYPE BOM_CLASS_DATA-MANDT, "   SY-MANDT
lv_system_failure  TYPE BOM_CLASS_DATA, "   
lv_stlty  TYPE BOM_CLASS_DATA-STLTY, "   
lv_stlnr  TYPE BOM_CLASS_DATA-STLNR, "   
lv_x_stlty  TYPE BOM_CLASS_DATA, "   SPACE
lv_x_stlnr  TYPE BOM_CLASS_DATA, "   SPACE
lv__wait  TYPE BOM_CLASS_DATA, "   SPACE
lv__collect  TYPE DDENQ_LIKE-COLLECT. "   ' '

  CALL FUNCTION 'CS_CL_BGR_LOCK'  "NOTRANSL: Setzen von Sperren auf Stücklistengruppe
    EXPORTING
         MODE_BGR_CLASS_LOCK = lv_mode_bgr_class_lock
         MANDT = lv_mandt
         STLTY = lv_stlty
         STLNR = lv_stlnr
         X_STLTY = lv_x_stlty
         X_STLNR = lv_x_stlnr
         _WAIT = lv__wait
         _COLLECT = lv__collect
    IMPORTING
         E_NAME = lv_e_name
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " CS_CL_BGR_LOCK




ABAP code using 7.40 inline data declarations to call FM CS_CL_BGR_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 MSGV1 FROM SY INTO @DATA(ld_e_name).
 
 
"SELECT single ENQMODE FROM DD26E INTO @DATA(ld_mode_bgr_class_lock).
DATA(ld_mode_bgr_class_lock) = 'E'.
 
"SELECT single MANDT FROM BOM_CLASS_DATA INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single STLTY FROM BOM_CLASS_DATA INTO @DATA(ld_stlty).
 
"SELECT single STLNR FROM BOM_CLASS_DATA INTO @DATA(ld_stlnr).
 
DATA(ld_x_stlty) = ' '.
 
DATA(ld_x_stlnr) = ' '.
 
DATA(ld__wait) = ' '.
 
"SELECT single COLLECT FROM DDENQ_LIKE INTO @DATA(ld__collect).
DATA(ld__collect) = ' '.
 


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!