SAP MSS_CREATE_CS_INDEX Function Module for









MSS_CREATE_CS_INDEX is a standard mss create cs index SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 mss create cs index FM, simply by entering the name MSS_CREATE_CS_INDEX into the relevant SAP transaction such as SE37 or SE38.

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



Function MSS_CREATE_CS_INDEX 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 'MSS_CREATE_CS_INDEX'"
EXPORTING
TABNAME = "
* INDEXID = 'CS' "
* IS_CLUSTERED = ABAP_FALSE "
* NO_EXEC = ABAP_FALSE "
* MAXDOP = 8 "

IMPORTING
SQL_TEXT = "
DBINDEX = "
STATEMENTS = "

EXCEPTIONS
INDEX_EXISTS = 1 TABLE_ALREADY_HAS_CS_INDEX = 2 INDEX_NOT_DEFINED = 3 NOT_SUPPORTED_CS_INDEX = 4 NOT_SUPPORTED_DATA_TYPE = 5 INDEX_NOT_CREATED = 6 TABLE_DOES_NOT_EXIST = 7
.



IMPORTING Parameters details for MSS_CREATE_CS_INDEX

TABNAME -

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

INDEXID -

Data type: INDEXID
Default: 'CS'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_CLUSTERED -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_EXEC -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MAXDOP -

Data type: I
Default: 8
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MSS_CREATE_CS_INDEX

SQL_TEXT -

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

DBINDEX -

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

STATEMENTS -

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

EXCEPTIONS details

INDEX_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

TABLE_ALREADY_HAS_CS_INDEX -

Data type:
Optional: No
Call by Reference: Yes

INDEX_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: Yes

NOT_SUPPORTED_CS_INDEX -

Data type:
Optional: No
Call by Reference: Yes

NOT_SUPPORTED_DATA_TYPE -

Data type:
Optional: No
Call by Reference: Yes

INDEX_NOT_CREATED -

Data type:
Optional: No
Call by Reference: Yes

TABLE_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MSS_CREATE_CS_INDEX 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_tabname  TYPE TABNAME, "   
lv_sql_text  TYPE STRING, "   
lv_index_exists  TYPE STRING, "   
lv_dbindex  TYPE DBINDEX_D, "   
lv_indexid  TYPE INDEXID, "   'CS'
lv_table_already_has_cs_index  TYPE INDEXID, "   
lv_statements  TYPE RSSOURCET, "   
lv_is_clustered  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_index_not_defined  TYPE ABAP_BOOL, "   
lv_no_exec  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_not_supported_cs_index  TYPE ABAP_BOOL, "   
lv_maxdop  TYPE I, "   8
lv_not_supported_data_type  TYPE I, "   
lv_index_not_created  TYPE I, "   
lv_table_does_not_exist  TYPE I. "   

  CALL FUNCTION 'MSS_CREATE_CS_INDEX'  "
    EXPORTING
         TABNAME = lv_tabname
         INDEXID = lv_indexid
         IS_CLUSTERED = lv_is_clustered
         NO_EXEC = lv_no_exec
         MAXDOP = lv_maxdop
    IMPORTING
         SQL_TEXT = lv_sql_text
         DBINDEX = lv_dbindex
         STATEMENTS = lv_statements
    EXCEPTIONS
        INDEX_EXISTS = 1
        TABLE_ALREADY_HAS_CS_INDEX = 2
        INDEX_NOT_DEFINED = 3
        NOT_SUPPORTED_CS_INDEX = 4
        NOT_SUPPORTED_DATA_TYPE = 5
        INDEX_NOT_CREATED = 6
        TABLE_DOES_NOT_EXIST = 7
. " MSS_CREATE_CS_INDEX




ABAP code using 7.40 inline data declarations to call FM MSS_CREATE_CS_INDEX

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.

 
 
 
 
DATA(ld_indexid) = 'CS'.
 
 
 
DATA(ld_is_clustered) = ABAP_FALSE.
 
 
DATA(ld_no_exec) = ABAP_FALSE.
 
 
DATA(ld_maxdop) = 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!