SAP V45CU_CONFIGURATION Function Module for NOTRANSL: Aufruf Konfiguration oder Direktablage in CBASE
V45CU_CONFIGURATION is a standard v45cu configuration 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: Aufruf Konfiguration oder Direktablage in CBASE 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 v45cu configuration FM, simply by entering the name V45CU_CONFIGURATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: V45CU
Program Name: SAPLV45CU
Main Program: SAPLV45CU
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function V45CU_CONFIGURATION 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 'V45CU_CONFIGURATION'"NOTRANSL: Aufruf Konfiguration oder Direktablage in CBASE.
EXPORTING
IV_INSTANCE = "Configuration (internal object number)
* IV_NO_DIALOG = ' ' "Generic Type
* IV_MATERIAL_VARIANT = "Material Number
* IV_NO_F8 = ' ' "Generic Type
* IV_NO_F11 = ' ' "Generic Type
* IV_SUB_TYPE = "Application ID for configuration
* IV_SIMULATION = ' ' "Generic Type
* IV_TYPE = 'S' "Generic Type
* IV_EFFECTIVITY = "Parameter Variant/Standard Variant
* IV_INITIALIZATION = ' ' "Generic Type
* IV_CALLED_FROM_SALES = ' ' "Generic Type
* IV_REFERENCE_INSTANCE = "Configuration (internal object number)
* IV_BOM_APPLICATION = "Application
IV_DATE = "ABAP System Field: Current Date of Application Server
* IV_DISPLAY = ' ' "Generic Type
IV_OBJECT_ID = "Name of database table of configurable object
IV_OBJECT = "Key of configurable object
* IV_OWNER_ID = "Name of database table for object
* IV_HEADER_SCREEN = "Structures for Calling with Screen Module
* IV_PLANT = "Plant
IMPORTING
EV_RETURN_WITH_FUNCTIONKEY = "ABAP System Field: PAI-Triggering Function Code
EV_NEW_INSTANCE = "Configuration (internal object number)
TABLES
* IT_APPLICATION_INPUT = "Transfer Object to Value Assignment for Object Characts
* ET_APPLICATION_OUTPUT = "Transfer Object to Value Assignment for Object Characts
* ET_RETURN = "Return parameter table
EXCEPTIONS
INTERNAL_ERROR = 1 INTERNAL_ERROR_ECM = 10 EOASL_NOT_ALLOWED = 11 MAXASL_NOT_ALLOWED = 12 NO_PROFILE_SELECTION = 13 INSTANCE_NOT_FOUND = 2 REFERENCE_INSTANCE_NOT_FOUND = 3 INSTANCE_IS_A_CLASSIFICATION = 4 NO_PLANT = 5 NO_QUANTITY = 6 NO_CONNECTION_TO_CONFIGURATION = 7 PLANT_NOT_ALLOWED = 8 MATERIAL_VARIANT_NOT_ALLOWED = 9
IMPORTING Parameters details for V45CU_CONFIGURATION
IV_INSTANCE - Configuration (internal object number)
Data type: INOB-CUOBJOptional: No
Call by Reference: No ( called with pass by value option)
IV_NO_DIALOG - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MATERIAL_VARIANT - Material Number
Data type: MARA-MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_F8 - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_F11 - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUB_TYPE - Application ID for configuration
Data type: RCUKO-APPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SIMULATION - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TYPE - Generic Type
Data type: CDefault: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_EFFECTIVITY - Parameter Variant/Standard Variant
Data type: INOB-TECHSOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_INITIALIZATION - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CALLED_FROM_SALES - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_REFERENCE_INSTANCE - Configuration (internal object number)
Data type: INOB-CUOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BOM_APPLICATION - Application
Data type: RCUKO-CAPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DATE - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
IV_DISPLAY - Generic Type
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_ID - Name of database table of configurable object
Data type: INOB-ROBTABOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJECT - Key of configurable object
Data type: INOB-ROBJEKOptional: No
Call by Reference: No ( called with pass by value option)
IV_OWNER_ID - Name of database table for object
Data type: INOB-OBTABOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_HEADER_SCREEN - Structures for Calling with Screen Module
Data type: INCL_BILDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PLANT - Plant
Data type: MARC-WERKSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for V45CU_CONFIGURATION
EV_RETURN_WITH_FUNCTIONKEY - ABAP System Field: PAI-Triggering Function Code
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EV_NEW_INSTANCE - Configuration (internal object number)
Data type: INOB-CUOBJOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for V45CU_CONFIGURATION
IT_APPLICATION_INPUT - Transfer Object to Value Assignment for Object Characts
Data type: CLTABLEOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_APPLICATION_OUTPUT - Transfer Object to Value Assignment for Object Characts
Data type: CLTABLEOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR_ECM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EOASL_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MAXASL_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PROFILE_SELECTION -
Data type:Optional: No
Call by Reference: Yes
INSTANCE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REFERENCE_INSTANCE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INSTANCE_IS_A_CLASSIFICATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PLANT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_QUANTITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CONNECTION_TO_CONFIGURATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANT_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATERIAL_VARIANT_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for V45CU_CONFIGURATION 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 INOB-CUOBJ, " | |||
| lv_internal_error | TYPE INOB, " | |||
| lt_it_application_input | TYPE STANDARD TABLE OF CLTABLE, " | |||
| lv_ev_return_with_functionkey | TYPE SY-UCOMM, " | |||
| lv_iv_no_dialog | TYPE C, " ' ' | |||
| lv_internal_error_ecm | TYPE C, " | |||
| lv_eoasl_not_allowed | TYPE C, " | |||
| lv_iv_material_variant | TYPE MARA-MATNR, " | |||
| lv_iv_no_f8 | TYPE C, " ' ' | |||
| lv_maxasl_not_allowed | TYPE C, " | |||
| lv_iv_no_f11 | TYPE C, " ' ' | |||
| lv_no_profile_selection | TYPE C, " | |||
| lv_iv_sub_type | TYPE RCUKO-APPID, " | |||
| lv_iv_simulation | TYPE C, " ' ' | |||
| lv_iv_type | TYPE C, " 'S' | |||
| lv_iv_effectivity | TYPE INOB-TECHS, " | |||
| lv_iv_initialization | TYPE C, " ' ' | |||
| lv_iv_called_from_sales | TYPE C, " ' ' | |||
| lv_ev_new_instance | TYPE INOB-CUOBJ, " | |||
| lv_instance_not_found | TYPE INOB, " | |||
| lt_et_application_output | TYPE STANDARD TABLE OF CLTABLE, " | |||
| lv_iv_reference_instance | TYPE INOB-CUOBJ, " | |||
| lv_iv_bom_application | TYPE RCUKO-CAPID, " | |||
| lv_iv_date | TYPE SY-DATUM, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2_T, " | |||
| lv_reference_instance_not_found | TYPE BAPIRET2_T, " | |||
| lv_iv_display | TYPE C, " ' ' | |||
| lv_instance_is_a_classification | TYPE C, " | |||
| lv_no_plant | TYPE C, " | |||
| lv_iv_object_id | TYPE INOB-ROBTAB, " | |||
| lv_iv_object | TYPE INOB-ROBJEK, " | |||
| lv_no_quantity | TYPE INOB, " | |||
| lv_iv_owner_id | TYPE INOB-OBTAB, " | |||
| lv_no_connection_to_configuration | TYPE INOB, " | |||
| lv_iv_header_screen | TYPE INCL_BILD, " | |||
| lv_plant_not_allowed | TYPE INCL_BILD, " | |||
| lv_iv_plant | TYPE MARC-WERKS, " | |||
| lv_material_variant_not_allowed | TYPE MARC. " |
|   CALL FUNCTION 'V45CU_CONFIGURATION' "NOTRANSL: Aufruf Konfiguration oder Direktablage in CBASE |
| EXPORTING | ||
| IV_INSTANCE | = lv_iv_instance | |
| IV_NO_DIALOG | = lv_iv_no_dialog | |
| IV_MATERIAL_VARIANT | = lv_iv_material_variant | |
| IV_NO_F8 | = lv_iv_no_f8 | |
| IV_NO_F11 | = lv_iv_no_f11 | |
| IV_SUB_TYPE | = lv_iv_sub_type | |
| IV_SIMULATION | = lv_iv_simulation | |
| IV_TYPE | = lv_iv_type | |
| IV_EFFECTIVITY | = lv_iv_effectivity | |
| IV_INITIALIZATION | = lv_iv_initialization | |
| IV_CALLED_FROM_SALES | = lv_iv_called_from_sales | |
| IV_REFERENCE_INSTANCE | = lv_iv_reference_instance | |
| IV_BOM_APPLICATION | = lv_iv_bom_application | |
| IV_DATE | = lv_iv_date | |
| IV_DISPLAY | = lv_iv_display | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_OBJECT | = lv_iv_object | |
| IV_OWNER_ID | = lv_iv_owner_id | |
| IV_HEADER_SCREEN | = lv_iv_header_screen | |
| IV_PLANT | = lv_iv_plant | |
| IMPORTING | ||
| EV_RETURN_WITH_FUNCTIONKEY | = lv_ev_return_with_functionkey | |
| EV_NEW_INSTANCE | = lv_ev_new_instance | |
| TABLES | ||
| IT_APPLICATION_INPUT | = lt_it_application_input | |
| ET_APPLICATION_OUTPUT | = lt_et_application_output | |
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| INTERNAL_ERROR_ECM = 10 | ||
| EOASL_NOT_ALLOWED = 11 | ||
| MAXASL_NOT_ALLOWED = 12 | ||
| NO_PROFILE_SELECTION = 13 | ||
| INSTANCE_NOT_FOUND = 2 | ||
| REFERENCE_INSTANCE_NOT_FOUND = 3 | ||
| INSTANCE_IS_A_CLASSIFICATION = 4 | ||
| NO_PLANT = 5 | ||
| NO_QUANTITY = 6 | ||
| NO_CONNECTION_TO_CONFIGURATION = 7 | ||
| PLANT_NOT_ALLOWED = 8 | ||
| MATERIAL_VARIANT_NOT_ALLOWED = 9 | ||
| . " V45CU_CONFIGURATION | ||
ABAP code using 7.40 inline data declarations to call FM V45CU_CONFIGURATION
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_iv_instance). | ||||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_ev_return_with_functionkey). | ||||
| DATA(ld_iv_no_dialog) | = ' '. | |||
| "SELECT single MATNR FROM MARA INTO @DATA(ld_iv_material_variant). | ||||
| DATA(ld_iv_no_f8) | = ' '. | |||
| DATA(ld_iv_no_f11) | = ' '. | |||
| "SELECT single APPID FROM RCUKO INTO @DATA(ld_iv_sub_type). | ||||
| DATA(ld_iv_simulation) | = ' '. | |||
| DATA(ld_iv_type) | = 'S'. | |||
| "SELECT single TECHS FROM INOB INTO @DATA(ld_iv_effectivity). | ||||
| DATA(ld_iv_initialization) | = ' '. | |||
| DATA(ld_iv_called_from_sales) | = ' '. | |||
| "SELECT single CUOBJ FROM INOB INTO @DATA(ld_ev_new_instance). | ||||
| "SELECT single CUOBJ FROM INOB INTO @DATA(ld_iv_reference_instance). | ||||
| "SELECT single CAPID FROM RCUKO INTO @DATA(ld_iv_bom_application). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_iv_date). | ||||
| DATA(ld_iv_display) | = ' '. | |||
| "SELECT single ROBTAB FROM INOB INTO @DATA(ld_iv_object_id). | ||||
| "SELECT single ROBJEK FROM INOB INTO @DATA(ld_iv_object). | ||||
| "SELECT single OBTAB FROM INOB INTO @DATA(ld_iv_owner_id). | ||||
| "SELECT single WERKS FROM MARC INTO @DATA(ld_iv_plant). | ||||
Search for further information about these or an SAP related objects