SAP SCUI_GET_CUSTOMIZE_VALUE Function Module for Fetches key value from customizing table
SCUI_GET_CUSTOMIZE_VALUE is a standard scui get customize value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fetches key value from customizing table 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 scui get customize value FM, simply by entering the name SCUI_GET_CUSTOMIZE_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCUI
Program Name: SAPLSCUI
Main Program: SAPLSCUI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCUI_GET_CUSTOMIZE_VALUE 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 'SCUI_GET_CUSTOMIZE_VALUE'"Fetches key value from customizing table.
EXPORTING
IV_KEY = "
IMPORTING
OV_VALUE = "
EXCEPTIONS
NO_VALUE = 1
IMPORTING Parameters details for SCUI_GET_CUSTOMIZE_VALUE
IV_KEY -
Data type: TCUSCUST-CUSTOM_TYPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCUI_GET_CUSTOMIZE_VALUE
OV_VALUE -
Data type: TCUSCUST-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCUI_GET_CUSTOMIZE_VALUE 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_iv_key | TYPE TCUSCUST-CUSTOM_TYP, " | |||
| lv_no_value | TYPE TCUSCUST, " | |||
| lv_ov_value | TYPE TCUSCUST-VALUE. " |
|   CALL FUNCTION 'SCUI_GET_CUSTOMIZE_VALUE' "Fetches key value from customizing table |
| EXPORTING | ||
| IV_KEY | = lv_iv_key | |
| IMPORTING | ||
| OV_VALUE | = lv_ov_value | |
| EXCEPTIONS | ||
| NO_VALUE = 1 | ||
| . " SCUI_GET_CUSTOMIZE_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM SCUI_GET_CUSTOMIZE_VALUE
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 CUSTOM_TYP FROM TCUSCUST INTO @DATA(ld_iv_key). | ||||
| "SELECT single VALUE FROM TCUSCUST INTO @DATA(ld_ov_value). | ||||
Search for further information about these or an SAP related objects