SAP CU_SINGLE_CFG_CANCEL Function Module for NOTRANSL: Beenden der Konfiguration im API-Modus
CU_SINGLE_CFG_CANCEL is a standard cu single cfg cancel 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: Beenden der Konfiguration im API-Modus 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 cu single cfg cancel FM, simply by entering the name CU_SINGLE_CFG_CANCEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: CU_SINGLE
Program Name: SAPLCU_SINGLE
Main Program: SAPLCU_SINGLE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CU_SINGLE_CFG_CANCEL 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 'CU_SINGLE_CFG_CANCEL'"NOTRANSL: Beenden der Konfiguration im API-Modus.
EXPORTING
IV_INSTANCE = "CUIB: System-Dependent Configuration Reference
EXCEPTIONS
INSTANCE_NOT_LOADED = 1
IMPORTING Parameters details for CU_SINGLE_CFG_CANCEL
IV_INSTANCE - CUIB: System-Dependent Configuration Reference
Data type: CUIB_CUOBJOptional: No
Call by Reference: Yes
EXCEPTIONS details
INSTANCE_NOT_LOADED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CU_SINGLE_CFG_CANCEL 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_instance | TYPE CUIB_CUOBJ, " | |||
| lv_instance_not_loaded | TYPE CUIB_CUOBJ. " |
|   CALL FUNCTION 'CU_SINGLE_CFG_CANCEL' "NOTRANSL: Beenden der Konfiguration im API-Modus |
| EXPORTING | ||
| IV_INSTANCE | = lv_iv_instance | |
| EXCEPTIONS | ||
| INSTANCE_NOT_LOADED = 1 | ||
| . " CU_SINGLE_CFG_CANCEL | ||
ABAP code using 7.40 inline data declarations to call FM CU_SINGLE_CFG_CANCEL
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