SAP CUDUI_CREATE_UI Function Module for NOTRANSL: Anlegen von Oberflächendesign









CUDUI_CREATE_UI is a standard cudui create ui 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: Anlegen von Oberflächendesign 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 create ui FM, simply by entering the name CUDUI_CREATE_UI 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_CREATE_UI 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_CREATE_UI'"NOTRANSL: Anlegen von Oberflächendesign
EXPORTING
DESIGN_NAME = "Design Name
* IMP_DSINT = '0000000000' "Internal design no.
T_BAPI_CECUSD = "Table Type: Basic Data of Characteristics Groups
T_BAPI_CECUSDT = "Table Type: Language-Dependent Data of Characteristics Grps
T_BAPI_CECUFM = "Table Type: Format of Characteristics in Chars Groups
T_BAPI_CECUSF = "Table Type: Basic Data of Frame in Characteristics Groups
T_BAPI_CECUSFT = "Table Type: Language-Dependent Data of Frame

IMPORTING
T_CHAR_MISSED = "Table Type: Characteristic Names
P_CHAR_MISSED = "

EXCEPTIONS
NO_DESIGN_INFO = 1 DESIGN_EXIST = 2 NUMBER_RANGE_PROBLEM = 3 NO_USAGE_PROFIL = 4
.



IMPORTING Parameters details for CUDUI_CREATE_UI

DESIGN_NAME - Design Name

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

IMP_DSINT - Internal design no.

Data type: CECUSD-DSINT
Default: '0000000000'
Optional: Yes
Call by Reference: Yes

T_BAPI_CECUSD - Table Type: Basic Data of Characteristics Groups

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

T_BAPI_CECUSDT - Table Type: Language-Dependent Data of Characteristics Grps

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

T_BAPI_CECUFM - Table Type: Format of Characteristics in Chars Groups

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

T_BAPI_CECUSF - Table Type: Basic Data of Frame in Characteristics Groups

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

T_BAPI_CECUSFT - Table Type: Language-Dependent Data of Frame

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

EXPORTING Parameters details for CUDUI_CREATE_UI

T_CHAR_MISSED - Table Type: Characteristic Names

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

P_CHAR_MISSED -

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

EXCEPTIONS details

NO_DESIGN_INFO - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

DESIGN_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NUMBER_RANGE_PROBLEM - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_USAGE_PROFIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUDUI_CREATE_UI 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_design_name  TYPE CECUSD-CE_DESIGN, "   
lv_t_char_missed  TYPE CUDUI_ATNAM, "   
lv_no_design_info  TYPE CUDUI_ATNAM, "   
lv_imp_dsint  TYPE CECUSD-DSINT, "   '0000000000'
lv_design_exist  TYPE CECUSD, "   
lv_p_char_missed  TYPE C, "   
lv_t_bapi_cecusd  TYPE CUDUI_BAPI_CECUSD, "   
lv_number_range_problem  TYPE CUDUI_BAPI_CECUSD, "   
lv_t_bapi_cecusdt  TYPE CUDUI_BAPI_CECUSDT, "   
lv_no_usage_profil  TYPE CUDUI_BAPI_CECUSDT, "   
lv_t_bapi_cecufm  TYPE CUDUI_BAPI_CECUFM, "   
lv_t_bapi_cecusf  TYPE CUDUI_BAPI_CECUSF, "   
lv_t_bapi_cecusft  TYPE CUDUI_BAPI_CECUSFT. "   

  CALL FUNCTION 'CUDUI_CREATE_UI'  "NOTRANSL: Anlegen von Oberflächendesign
    EXPORTING
         DESIGN_NAME = lv_design_name
         IMP_DSINT = lv_imp_dsint
         T_BAPI_CECUSD = lv_t_bapi_cecusd
         T_BAPI_CECUSDT = lv_t_bapi_cecusdt
         T_BAPI_CECUFM = lv_t_bapi_cecufm
         T_BAPI_CECUSF = lv_t_bapi_cecusf
         T_BAPI_CECUSFT = lv_t_bapi_cecusft
    IMPORTING
         T_CHAR_MISSED = lv_t_char_missed
         P_CHAR_MISSED = lv_p_char_missed
    EXCEPTIONS
        NO_DESIGN_INFO = 1
        DESIGN_EXIST = 2
        NUMBER_RANGE_PROBLEM = 3
        NO_USAGE_PROFIL = 4
. " CUDUI_CREATE_UI




ABAP code using 7.40 inline data declarations to call FM CUDUI_CREATE_UI

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 CE_DESIGN FROM CECUSD INTO @DATA(ld_design_name).
 
 
 
"SELECT single DSINT FROM CECUSD INTO @DATA(ld_imp_dsint).
DATA(ld_imp_dsint) = '0000000000'.
 
 
 
 
 
 
 
 
 
 


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!