SAP CRM_SCE_CREATE_DISPLAY_FORMAT Function Module for Konvertiert Konfigurationsdaten in Anzeigeformat









CRM_SCE_CREATE_DISPLAY_FORMAT is a standard crm sce create display format SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Konvertiert Konfigurationsdaten in Anzeigeformat 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 crm sce create display format FM, simply by entering the name CRM_SCE_CREATE_DISPLAY_FORMAT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_SCE_DATABASE
Program Name: SAPLCRM_SCE_DATABASE
Main Program: SAPLCRM_SCE_DATABASE
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CRM_SCE_CREATE_DISPLAY_FORMAT 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 'CRM_SCE_CREATE_DISPLAY_FORMAT'"Konvertiert Konfigurationsdaten in Anzeigeformat
EXPORTING
I_KBNAME = "Knowledge-Base Object
I_KBVERSION = "Runtime Version of SCE Knowledge Base
* I_LANGUAGE = SY-LANGU "Configuration Language
* I_WITH_INVISIBLE = ' ' "<> ' ': auch nicht angezeigte Merkmale
* I_VIEWS = ' ' "<> ' ': nur Merkmale in diesen Sichten

IMPORTING
E_RETCODE = "Fehler bei Datenzugriff

TABLES
U_TAB_INSTANCES = "CUX: Instance Data
U_TAB_PART_OF = "CUX: Part-Of Data
U_TAB_VALUES = "CUX: Characteristic Value Assignment

EXCEPTIONS
NOT_FOUND = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for CRM_SCE_CREATE_DISPLAY_FORMAT

I_KBNAME - Knowledge-Base Object

Data type: CUX_KBOBJNAME
Optional: No
Call by Reference: Yes

I_KBVERSION - Runtime Version of SCE Knowledge Base

Data type: CUX_RTVERSION
Optional: No
Call by Reference: Yes

I_LANGUAGE - Configuration Language

Data type: CUX_KBLANGUAGE
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

I_WITH_INVISIBLE - <> SPACE: auch nicht angezeigte Merkmale

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_VIEWS - <> SPACE: nur Merkmale in diesen Sichten

Data type: COMT_VIEWS
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CRM_SCE_CREATE_DISPLAY_FORMAT

E_RETCODE - Fehler bei Datenzugriff

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for CRM_SCE_CREATE_DISPLAY_FORMAT

U_TAB_INSTANCES - CUX: Instance Data

Data type: CUXT_CUINS_T
Optional: No
Call by Reference: Yes

U_TAB_PART_OF - CUX: Part-Of Data

Data type: CUXT_CUPRT_T
Optional: No
Call by Reference: Yes

U_TAB_VALUES - CUX: Characteristic Value Assignment

Data type: CUXT_CUVAL_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - Wissensbasis nicht bekannt

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

INTERNAL_ERROR - Internal Error

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

Copy and paste ABAP code example for CRM_SCE_CREATE_DISPLAY_FORMAT 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_i_kbname  TYPE CUX_KBOBJNAME, "   
lv_e_retcode  TYPE SY-SUBRC, "   
lv_not_found  TYPE SY, "   
lt_u_tab_instances  TYPE STANDARD TABLE OF CUXT_CUINS_T, "   
lv_i_kbversion  TYPE CUX_RTVERSION, "   
lt_u_tab_part_of  TYPE STANDARD TABLE OF CUXT_CUPRT_T, "   
lv_internal_error  TYPE CUXT_CUPRT_T, "   
lv_i_language  TYPE CUX_KBLANGUAGE, "   SY-LANGU
lt_u_tab_values  TYPE STANDARD TABLE OF CUXT_CUVAL_T, "   
lv_i_with_invisible  TYPE C, "   SPACE
lv_i_views  TYPE COMT_VIEWS. "   SPACE

  CALL FUNCTION 'CRM_SCE_CREATE_DISPLAY_FORMAT'  "Konvertiert Konfigurationsdaten in Anzeigeformat
    EXPORTING
         I_KBNAME = lv_i_kbname
         I_KBVERSION = lv_i_kbversion
         I_LANGUAGE = lv_i_language
         I_WITH_INVISIBLE = lv_i_with_invisible
         I_VIEWS = lv_i_views
    IMPORTING
         E_RETCODE = lv_e_retcode
    TABLES
         U_TAB_INSTANCES = lt_u_tab_instances
         U_TAB_PART_OF = lt_u_tab_part_of
         U_TAB_VALUES = lt_u_tab_values
    EXCEPTIONS
        NOT_FOUND = 1
        INTERNAL_ERROR = 2
. " CRM_SCE_CREATE_DISPLAY_FORMAT




ABAP code using 7.40 inline data declarations to call FM CRM_SCE_CREATE_DISPLAY_FORMAT

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 SUBRC FROM SY INTO @DATA(ld_e_retcode).
 
 
 
 
 
 
DATA(ld_i_language) = SY-LANGU.
 
 
DATA(ld_i_with_invisible) = ' '.
 
DATA(ld_i_views) = ' '.
 


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!