SAP MSS_EXISTS_PARTITION_SCHEME Function Module for

Search SAP Function Modules

MSS_EXISTS_PARTITION_SCHEME is a standard mss exists partition scheme 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 exists partition scheme FM, simply by entering the name MSS_EXISTS_PARTITION_SCHEME into the relevant SAP transaction such as SE37 or SE38.

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

Function MSS_EXISTS_PARTITION_SCHEME 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_EXISTS_PARTITION_SCHEME'"
  EXPORTING
   PART_TABNAME =  "Table Name
*  SCHEMA_NAME = ' ' "Template description
*  DB_NAME = ' ' "Database Name
*  DBSYS = SY-DBSYS "R/3 System, Name of Central Database System
*  QUICK_CHECK = ' ' "
*  SCHEME_NAME = ' ' "

TABLES
*  PART_SCHEME_INFO_TAB =  "

EXCEPTIONS
   WRONG_DATABASE_PLATFORM = 1    SCHEME_NOT_FOUND = 2    INTERNAL_ERROR = 3    DB_ERROR = 4    DB_NOT_FOUND = 5    NO_DB_ACCESS = 6    SCHEMA_NOT_FOUND = 7    INVALID_INPUT = 8    NOT_RUNNING_ON_MSSQL = 9 

.

IMPORTING Parameters details for MSS_EXISTS_PARTITION_SCHEME

PART_TABNAME - Table Name

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

SCHEMA_NAME - Template description

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

DB_NAME - Database Name

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

DBSYS - R/3 System, Name of Central Database System

Data type: SY-DBSYS
Default: SY-DBSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

QUICK_CHECK -

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

SCHEME_NAME -

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

TABLES Parameters details for MSS_EXISTS_PARTITION_SCHEME

PART_SCHEME_INFO_TAB -

Data type: MSSPARTSCHEMETAB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

WRONG_DATABASE_PLATFORM -

Data type:
Optional: No
Call by Reference: Yes

SCHEME_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DB_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_DB_ACCESS -

Data type:
Optional: No
Call by Reference: Yes

SCHEMA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INVALID_INPUT -

Data type:
Optional: No
Call by Reference: Yes

NOT_RUNNING_ON_MSSQL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MSS_EXISTS_PARTITION_SCHEME 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.

ABAP code using 7.40 inline data declarations to call FM MSS_EXISTS_PARTITION_SCHEME

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