SAP CUDUI_CHECK_UI_LOCK Function Module for NOTRANSL: Oberflächendesign auf Sperre prüfen

Search SAP Function Modules

CUDUI_CHECK_UI_LOCK is a standard cudui check ui 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: Oberflächendesign auf Sperre prüfen 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 cudui check ui lock FM, simply by entering the name CUDUI_CHECK_UI_LOCK into the relevant SAP transaction such as SE37 or SE38.

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

Function CUDUI_CHECK_UI_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 'CUDUI_CHECK_UI_LOCK'"NOTRANSL: Oberflächendesign auf Sperre prüfen
  EXPORTING
   DESIGN_NAME =  "Design Name
*  BAPI_MODE = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   P_DSINT =  "Internal design no.
   P_MSGID =  "Message Identification
   P_MSGNO =  "System Message Number
   P_MSGV1 =  "Messages, Message Variable
   P_MSGV2 =  "Messages, Message Variable
   P_MSGV3 =  "Messages, Message Variable

EXCEPTIONS
   UI_NOT_AVAILABLE = 1    NO_UI_NAME = 2 

.

IMPORTING Parameters details for CUDUI_CHECK_UI_LOCK

DESIGN_NAME - Design Name

Data type: CECUSD-CE_DESIGN
Optional: No
Call by Reference: Yes

BAPI_MODE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: C
Default: ' '
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CUDUI_CHECK_UI_LOCK

P_DSINT - Internal design no.

Data type: CECUSD-DSINT
Optional: No
Call by Reference: Yes

P_MSGID - Message Identification

Data type: BALMI-MSGID
Optional: No
Call by Reference: Yes

P_MSGNO - System Message Number

Data type: BALMI-MSGNO
Optional: No
Call by Reference: Yes

P_MSGV1 - Messages, Message Variable

Data type: SYMSGV
Optional: No
Call by Reference: Yes

P_MSGV2 - Messages, Message Variable

Data type: SYMSGV
Optional: No
Call by Reference: Yes

P_MSGV3 - Messages, Message Variable

Data type: SYMSGV
Optional: No
Call by Reference: Yes

EXCEPTIONS details

UI_NOT_AVAILABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_UI_NAME - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUDUI_CHECK_UI_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.

ABAP code using 7.40 inline data declarations to call FM CUDUI_CHECK_UI_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.

Search for further information about these or an SAP related objects