SAP Function Modules
VC_UI_CONFIG_FRAME SAP Function module - Aufruf des Konfigurationsrahmens
VC_UI_CONFIG_FRAME is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name VC_UI_CONFIG_FRAME into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
VC_UI_CONFIG
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM VC_UI_CONFIG_FRAME - VC UI CONFIG FRAME
CALL FUNCTION 'VC_UI_CONFIG_FRAME' "Aufruf des Konfigurationsrahmens
EXPORTING
iv_object_type = 'MARA' " inob-robtab Name of database table of configurable object
iv_object_key = " inob-robjek Key of configurable object
* iv_object_logsys = " comt_cfgd_kblogsys Logical System
* iv_instance = " cuobj Configuration (internal object number)
* iv_owner_type = " inob-obtab Name of database table for object
* iv_owner_key = " inob-objek Key of Object to be Classified
* is_screen_design = " cut_screen_cust_s Structures for Calling with Screen Module
iv_simulation = 'F' " comt_cfgm_boolean Boolean (T = True, F = False, Blank = Unknown)
iv_date = " d
iv_ipc_caller = " string
iv_ipc_xcm_scenario = " string
* iv_display = 'F' " comt_cfgm_boolean Boolean (T = True, F = False, Blank = Unknown)
* iv_kb_name = " comt_cfgd_kbname KB Name
* iv_kb_version = " comt_cfgd_kbversion KB Version
* iv_kb_id = " comt_cfgd_kbid Internal identifier of a knowledge base
* iv_kb_logsys = " comt_cfgd_kblogsys Logical System
* iv_kb_profile = " comt_cfgd_profname Profile name
* iv_kb_uiname = " comt_cfgd_uiname User Interface Name
* it_context = " comt_cfgm_context_i Context for Calling Configuration (SCE)
* it_properties = " comt_cfgm_context_i Properties for Calling IPC (SCE)
* is_pricing_basics = " cfgcv_pricing_ctx
* is_pricing_basics_i = " cfgcv_pricing_ctx
IMPORTING
ev_return_with_function = " sy-ucomm Screens, function code triggered by PAI
* CHANGING
* cs_configuration = " comt_cfgm_config External Configuration Interface
EXCEPTIONS
CANCELLED_BY_USER = 1 "
UI_DESTINATION_NOT_FOUND = 2 "
. " VC_UI_CONFIG_FRAME
ABAP code example for Function Module VC_UI_CONFIG_FRAME
The ABAP code below is a full code listing to execute function module VC_UI_CONFIG_FRAME including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_ev_return_with_function | TYPE SY-UCOMM . |
DATA(ld_cs_configuration) = 'Check type of data required'.
SELECT single ROBTAB
FROM INOB
INTO @DATA(ld_iv_object_type).
SELECT single ROBJEK
FROM INOB
INTO @DATA(ld_iv_object_key).
DATA(ld_iv_object_logsys) = 'Check type of data required'.
DATA(ld_iv_instance) = 'some text here'.
SELECT single OBTAB
FROM INOB
INTO @DATA(ld_iv_owner_type).
SELECT single OBJEK
FROM INOB
INTO @DATA(ld_iv_owner_key).
DATA(ld_is_screen_design) = 'some text here'.
DATA(ld_iv_simulation) = 'some text here'.
DATA(ld_iv_date) = 'some text here'.
DATA(ld_iv_ipc_caller) = 'some text here'.
DATA(ld_iv_ipc_xcm_scenario) = 'some text here'.
DATA(ld_iv_display) = 'some text here'.
DATA(ld_iv_kb_name) = 'some text here'.
DATA(ld_iv_kb_version) = 'some text here'.
DATA(ld_iv_kb_id) = 'some text here'.
DATA(ld_iv_kb_logsys) = 'Check type of data required'.
DATA(ld_iv_kb_profile) = 'some text here'.
DATA(ld_iv_kb_uiname) = 'some text here'.
DATA(ld_it_context) = 'some text here'.
DATA(ld_it_properties) = 'some text here'.
DATA(ld_is_pricing_basics) = 'some text here'.
DATA(ld_is_pricing_basics_i) = 'some text here'. . CALL FUNCTION 'VC_UI_CONFIG_FRAME' EXPORTING iv_object_type = ld_iv_object_type iv_object_key = ld_iv_object_key * iv_object_logsys = ld_iv_object_logsys * iv_instance = ld_iv_instance * iv_owner_type = ld_iv_owner_type * iv_owner_key = ld_iv_owner_key * is_screen_design = ld_is_screen_design iv_simulation = ld_iv_simulation iv_date = ld_iv_date iv_ipc_caller = ld_iv_ipc_caller iv_ipc_xcm_scenario = ld_iv_ipc_xcm_scenario * iv_display = ld_iv_display * iv_kb_name = ld_iv_kb_name * iv_kb_version = ld_iv_kb_version * iv_kb_id = ld_iv_kb_id * iv_kb_logsys = ld_iv_kb_logsys * iv_kb_profile = ld_iv_kb_profile * iv_kb_uiname = ld_iv_kb_uiname * it_context = ld_it_context * it_properties = ld_it_properties * is_pricing_basics = ld_is_pricing_basics * is_pricing_basics_i = ld_is_pricing_basics_i IMPORTING ev_return_with_function = ld_ev_return_with_function * CHANGING * cs_configuration = ld_cs_configuration EXCEPTIONS CANCELLED_BY_USER = 1 UI_DESTINATION_NOT_FOUND = 2 . " VC_UI_CONFIG_FRAME
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_cs_configuration | TYPE COMT_CFGM_CONFIG , |
| ld_ev_return_with_function | TYPE SY-UCOMM , |
| ld_iv_object_type | TYPE INOB-ROBTAB , |
| ld_iv_object_key | TYPE INOB-ROBJEK , |
| ld_iv_object_logsys | TYPE COMT_CFGD_KBLOGSYS , |
| ld_iv_instance | TYPE CUOBJ , |
| ld_iv_owner_type | TYPE INOB-OBTAB , |
| ld_iv_owner_key | TYPE INOB-OBJEK , |
| ld_is_screen_design | TYPE CUT_SCREEN_CUST_S , |
| ld_iv_simulation | TYPE COMT_CFGM_BOOLEAN , |
| ld_iv_date | TYPE D , |
| ld_iv_ipc_caller | TYPE STRING , |
| ld_iv_ipc_xcm_scenario | TYPE STRING , |
| ld_iv_display | TYPE COMT_CFGM_BOOLEAN , |
| ld_iv_kb_name | TYPE COMT_CFGD_KBNAME , |
| ld_iv_kb_version | TYPE COMT_CFGD_KBVERSION , |
| ld_iv_kb_id | TYPE COMT_CFGD_KBID , |
| ld_iv_kb_logsys | TYPE COMT_CFGD_KBLOGSYS , |
| ld_iv_kb_profile | TYPE COMT_CFGD_PROFNAME , |
| ld_iv_kb_uiname | TYPE COMT_CFGD_UINAME , |
| ld_it_context | TYPE COMT_CFGM_CONTEXT_I , |
| ld_it_properties | TYPE COMT_CFGM_CONTEXT_I , |
| ld_is_pricing_basics | TYPE CFGCV_PRICING_CTX , |
| ld_is_pricing_basics_i | TYPE CFGCV_PRICING_CTX . |
ld_cs_configuration = 'some text here'.
SELECT single ROBTAB
FROM INOB
INTO ld_iv_object_type.
SELECT single ROBJEK
FROM INOB
INTO ld_iv_object_key.
ld_iv_object_logsys = 'Check type of data required'.
ld_iv_instance = 'some text here'.
SELECT single OBTAB
FROM INOB
INTO ld_iv_owner_type.
SELECT single OBJEK
FROM INOB
INTO ld_iv_owner_key.
ld_is_screen_design = 'some text here'.
ld_iv_simulation = 'some text here'.
ld_iv_date = 'some text here'.
ld_iv_ipc_caller = 'some text here'.
ld_iv_ipc_xcm_scenario = 'some text here'.
ld_iv_display = 'some text here'.
ld_iv_kb_name = 'some text here'.
ld_iv_kb_version = 'some text here'.
ld_iv_kb_id = 'some text here'.
ld_iv_kb_logsys = 'Check type of data required'.
ld_iv_kb_profile = 'some text here'.
ld_iv_kb_uiname = 'some text here'.
ld_it_context = 'some text here'.
ld_it_properties = 'some text here'.
ld_is_pricing_basics = 'some text here'.
ld_is_pricing_basics_i = 'some text here'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name VC_UI_CONFIG_FRAME or its description.