SAP CFG_API_GET_DISPLAY_DATA Function Module for Get language dependent cstic information









CFG_API_GET_DISPLAY_DATA is a standard cfg api get display data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get language dependent cstic information 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 cfg api get display data FM, simply by entering the name CFG_API_GET_DISPLAY_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_CFG_API_ENGINE_COMMAND
Program Name: SAPLCOM_CFG_API_ENGINE_COMMAND
Main Program: SAPLCOM_CFG_API_ENGINE_COMMAND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled JAVA Module
Update:



Function CFG_API_GET_DISPLAY_DATA 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 'CFG_API_GET_DISPLAY_DATA'"Get language dependent cstic information
  EXPORTING
   KB_NAME =  "KB Name
   KB_VERSION =  "KB Version
   KB_LOGSYS =  "Logical System
   LANGUAGE =  "Language Key

CHANGING
   OBJ =  "table of product / classes
   CSTIC =  "table of  language dependent names of cstics
   VALUE =  "table of language dependent values of cstics
   CSTIC_INFO =  "table of additional information of cstic

EXCEPTIONS
   PARAMETER_EXCEPTION = 1    COMMAND_EXCEPTION = 2
.



IMPORTING Parameters details for CFG_API_GET_DISPLAY_DATA

KB_NAME - KB Name

Data type: COMT_CFGD_KBNAME
Optional: No
Call by Reference: No ( called with pass by value option)

KB_VERSION - KB Version

Data type: COMT_CFGD_KBVERSION
Optional: No
Call by Reference: No ( called with pass by value option)

KB_LOGSYS - Logical System

Data type: COMT_CFGD_KBLOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

LANGUAGE - Language Key

Data type: LANGU
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for CFG_API_GET_DISPLAY_DATA

OBJ - table of product / classes

Data type: COMT_CFGM_OBJ_I
Optional: No
Call by Reference: No ( called with pass by value option)

CSTIC - table of language dependent names of cstics

Data type: COMT_CFGM_CSTIC_LNAME_I
Optional: No
Call by Reference: No ( called with pass by value option)

VALUE - table of language dependent values of cstics

Data type: COMT_CFGM_LANG_DEP_VALUE_I
Optional: No
Call by Reference: No ( called with pass by value option)

CSTIC_INFO - table of additional information of cstic

Data type: COMT_CFGM_CSTIC_INFO_I
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PARAMETER_EXCEPTION - Problem in using an import parameter

Data type:
Optional: No
Call by Reference: Yes

COMMAND_EXCEPTION - Problem in executing the configuration command

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CFG_API_GET_DISPLAY_DATA 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_obj  TYPE COMT_CFGM_OBJ_I, "   
lv_kb_name  TYPE COMT_CFGD_KBNAME, "   
lv_parameter_exception  TYPE COMT_CFGD_KBNAME, "   
lv_cstic  TYPE COMT_CFGM_CSTIC_LNAME_I, "   
lv_kb_version  TYPE COMT_CFGD_KBVERSION, "   
lv_command_exception  TYPE COMT_CFGD_KBVERSION, "   
lv_value  TYPE COMT_CFGM_LANG_DEP_VALUE_I, "   
lv_kb_logsys  TYPE COMT_CFGD_KBLOGSYS, "   
lv_language  TYPE LANGU, "   
lv_cstic_info  TYPE COMT_CFGM_CSTIC_INFO_I. "   

  CALL FUNCTION 'CFG_API_GET_DISPLAY_DATA'  "Get language dependent cstic information
    EXPORTING
         KB_NAME = lv_kb_name
         KB_VERSION = lv_kb_version
         KB_LOGSYS = lv_kb_logsys
         LANGUAGE = lv_language
    CHANGING
         OBJ = lv_obj
         CSTIC = lv_cstic
         VALUE = lv_value
         CSTIC_INFO = lv_cstic_info
    EXCEPTIONS
        PARAMETER_EXCEPTION = 1
        COMMAND_EXCEPTION = 2
. " CFG_API_GET_DISPLAY_DATA




ABAP code using 7.40 inline data declarations to call FM CFG_API_GET_DISPLAY_DATA

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!