SAP MSS_PARTITION_STORAGE_PUT Function Module for

Search SAP Function Modules

MSS_PARTITION_STORAGE_PUT is a standard mss partition storage put 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 partition storage put FM, simply by entering the name MSS_PARTITION_STORAGE_PUT 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_PARTITION_STORAGE_PUT 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_PARTITION_STORAGE_PUT'"
  EXPORTING
   PART_TABNAME =  "Table Name
   PART_COLNAME =  "Field Name
*  LEFT_RIGHT = 'RIGHT' "
*  VALUE_TYPE = 'INT4' "
*  VALUE_LENGTH = 0 "
*  VALUE_DECIMALS = 0 "
*  PART_TYPE = 'RANGE' "
*  KEYFLAG = ' ' "

TABLES
   PART_VALUES_IN =  "
*  FILEGROUPS_IN =  "
*  PART_NAMES_IN =  "
*  STORAGE_IN =  "

EXCEPTIONS
   WRONG_DATABASE_PLATFORM = 1    INVALID_RANGELIST = 2    PARAMETER_INCONSISTENCY = 3 

.

IMPORTING Parameters details for MSS_PARTITION_STORAGE_PUT

PART_TABNAME - Table Name

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

PART_COLNAME - Field Name

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

LEFT_RIGHT -

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

VALUE_TYPE -

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

VALUE_LENGTH -

Data type: DD03L-LENG
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALUE_DECIMALS -

Data type: DD03L-DECIMALS
Optional: Yes
Call by Reference: No ( called with pass by value option)

PART_TYPE -

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

KEYFLAG -

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

TABLES Parameters details for MSS_PARTITION_STORAGE_PUT

PART_VALUES_IN -

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

FILEGROUPS_IN -

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

PART_NAMES_IN -

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

STORAGE_IN -

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

EXCEPTIONS details

WRONG_DATABASE_PLATFORM -

Data type:
Optional: No
Call by Reference: Yes

INVALID_RANGELIST -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_INCONSISTENCY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MSS_PARTITION_STORAGE_PUT 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_PARTITION_STORAGE_PUT

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