SAP CUD0_GET_SETTING_EXTERNAL_LOAD Function Module for NOTRANSL: Konfiguration Entscheidung Laden Konfiguration aus externer Quel
CUD0_GET_SETTING_EXTERNAL_LOAD is a standard cud0 get setting external load 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: Konfiguration Entscheidung Laden Konfiguration aus externer Quel 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 cud0 get setting external load FM, simply by entering the name CUD0_GET_SETTING_EXTERNAL_LOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUD0
Program Name: SAPLCUD0
Main Program: SAPLCUD0
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CUD0_GET_SETTING_EXTERNAL_LOAD 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 'CUD0_GET_SETTING_EXTERNAL_LOAD'"NOTRANSL: Konfiguration Entscheidung Laden Konfiguration aus externer Quel.
EXPORTING
* CFG_INSTANCE = "
CFG_ROOT_OBJECT_TABLE = "
CFG_ROOT_OBJECT_KEY = "
CFG_DATE = "
* CFG_DISPLAY_MODE = "
IMPORTING
CFG_GO_EXTERNAL = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCUD0_001 Configuration Decision to Load Configuration from External Source
EXIT_SAPLCUD0_002 Reaction Option to Conflicts When Finding Objects in Class Node
EXIT_SAPLCUD0_003 Time of Initialization for Variant Function Program Environment
IMPORTING Parameters details for CUD0_GET_SETTING_EXTERNAL_LOAD
CFG_INSTANCE -
Data type: INOB-CUOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
CFG_ROOT_OBJECT_TABLE -
Data type: INOB-ROBTABOptional: No
Call by Reference: No ( called with pass by value option)
CFG_ROOT_OBJECT_KEY -
Data type: INOB-ROBJEKOptional: No
Call by Reference: No ( called with pass by value option)
CFG_DATE -
Data type: CABN-DATUVOptional: No
Call by Reference: No ( called with pass by value option)
CFG_DISPLAY_MODE -
Data type: RCURS-CHECKEDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CUD0_GET_SETTING_EXTERNAL_LOAD
CFG_GO_EXTERNAL -
Data type: RCURS-CHECKEDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUD0_GET_SETTING_EXTERNAL_LOAD 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_cfg_instance | TYPE INOB-CUOBJ, " | |||
| lv_cfg_go_external | TYPE RCURS-CHECKED, " | |||
| lv_cfg_root_object_table | TYPE INOB-ROBTAB, " | |||
| lv_cfg_root_object_key | TYPE INOB-ROBJEK, " | |||
| lv_cfg_date | TYPE CABN-DATUV, " | |||
| lv_cfg_display_mode | TYPE RCURS-CHECKED. " |
|   CALL FUNCTION 'CUD0_GET_SETTING_EXTERNAL_LOAD' "NOTRANSL: Konfiguration Entscheidung Laden Konfiguration aus externer Quel |
| EXPORTING | ||
| CFG_INSTANCE | = lv_cfg_instance | |
| CFG_ROOT_OBJECT_TABLE | = lv_cfg_root_object_table | |
| CFG_ROOT_OBJECT_KEY | = lv_cfg_root_object_key | |
| CFG_DATE | = lv_cfg_date | |
| CFG_DISPLAY_MODE | = lv_cfg_display_mode | |
| IMPORTING | ||
| CFG_GO_EXTERNAL | = lv_cfg_go_external | |
| . " CUD0_GET_SETTING_EXTERNAL_LOAD | ||
ABAP code using 7.40 inline data declarations to call FM CUD0_GET_SETTING_EXTERNAL_LOAD
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 CUOBJ FROM INOB INTO @DATA(ld_cfg_instance). | ||||
| "SELECT single CHECKED FROM RCURS INTO @DATA(ld_cfg_go_external). | ||||
| "SELECT single ROBTAB FROM INOB INTO @DATA(ld_cfg_root_object_table). | ||||
| "SELECT single ROBJEK FROM INOB INTO @DATA(ld_cfg_root_object_key). | ||||
| "SELECT single DATUV FROM CABN INTO @DATA(ld_cfg_date). | ||||
| "SELECT single CHECKED FROM RCURS INTO @DATA(ld_cfg_display_mode). | ||||
Search for further information about these or an SAP related objects