SAP RSDU_PSA_PART_INSTANTIATE_MSS Function Module for Creates Database-Dependent Partition Properties in the SAP-DD
RSDU_PSA_PART_INSTANTIATE_MSS is a standard rsdu psa part instantiate mss SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates Database-Dependent Partition Properties in the SAP-DD 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 rsdu psa part instantiate mss FM, simply by entering the name RSDU_PSA_PART_INSTANTIATE_MSS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_PART_MSS
Program Name: SAPLRSDU_PART_MSS
Main Program: SAPLRSDU_PART_MSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDU_PSA_PART_INSTANTIATE_MSS 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 'RSDU_PSA_PART_INSTANTIATE_MSS'"Creates Database-Dependent Partition Properties in the SAP-DD.
EXPORTING
I_TABLNM = "PSA Table Name
I_PART_COLUMN = "Partitioning Column
* I_PART_TYPE = RSDU_C_PARTYPE-RANGE "
* I_USERAPP = "Name of the application using the PSA service
* I_ABAP_UNIT_CALL = RS_C_FALSE "
IMPORTING
E_PARTITIONED = "True if Partition Is Supported; False if Not
CHANGING
C_PROCESSED = "Boolean
EXCEPTIONS
PSA_INSTANTIATE_FAILED = 1
IMPORTING Parameters details for RSDU_PSA_PART_INSTANTIATE_MSS
I_TABLNM - PSA Table Name
Data type: RSD_TABLNMOptional: No
Call by Reference: Yes
I_PART_COLUMN - Partitioning Column
Data type: RSD_FIELDNMOptional: No
Call by Reference: Yes
I_PART_TYPE -
Data type: RSDU_PARTYPEDefault: RSDU_C_PARTYPE-RANGE
Optional: No
Call by Reference: Yes
I_USERAPP - Name of the application using the PSA service
Data type: RSUSERAPPOptional: Yes
Call by Reference: Yes
I_ABAP_UNIT_CALL -
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSDU_PSA_PART_INSTANTIATE_MSS
E_PARTITIONED - True if Partition Is Supported; False if Not
Data type: RS_BOOLOptional: No
Call by Reference: Yes
CHANGING Parameters details for RSDU_PSA_PART_INSTANTIATE_MSS
C_PROCESSED - Boolean
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
PSA_INSTANTIATE_FAILED - ERROR writing DDSTORAGE ENTRIES
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSDU_PSA_PART_INSTANTIATE_MSS 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_tablnm | TYPE RSD_TABLNM, " | |||
| lv_c_processed | TYPE RS_BOOL, " | |||
| lv_e_partitioned | TYPE RS_BOOL, " | |||
| lv_psa_instantiate_failed | TYPE RS_BOOL, " | |||
| lv_i_part_column | TYPE RSD_FIELDNM, " | |||
| lv_i_part_type | TYPE RSDU_PARTYPE, " RSDU_C_PARTYPE-RANGE | |||
| lv_i_userapp | TYPE RSUSERAPP, " | |||
| lv_i_abap_unit_call | TYPE RS_BOOL. " RS_C_FALSE |
|   CALL FUNCTION 'RSDU_PSA_PART_INSTANTIATE_MSS' "Creates Database-Dependent Partition Properties in the SAP-DD |
| EXPORTING | ||
| I_TABLNM | = lv_i_tablnm | |
| I_PART_COLUMN | = lv_i_part_column | |
| I_PART_TYPE | = lv_i_part_type | |
| I_USERAPP | = lv_i_userapp | |
| I_ABAP_UNIT_CALL | = lv_i_abap_unit_call | |
| IMPORTING | ||
| E_PARTITIONED | = lv_e_partitioned | |
| CHANGING | ||
| C_PROCESSED | = lv_c_processed | |
| EXCEPTIONS | ||
| PSA_INSTANTIATE_FAILED = 1 | ||
| . " RSDU_PSA_PART_INSTANTIATE_MSS | ||
ABAP code using 7.40 inline data declarations to call FM RSDU_PSA_PART_INSTANTIATE_MSS
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_i_part_type) | = RSDU_C_PARTYPE-RANGE. | |||
| DATA(ld_i_abap_unit_call) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects