SAP UMC_PARALLEL_MDX_SETTINGS_SET Function Module for
UMC_PARALLEL_MDX_SETTINGS_SET is a standard umc parallel mdx settings set 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 umc parallel mdx settings set FM, simply by entering the name UMC_PARALLEL_MDX_SETTINGS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: UMC_UTILITIES
Program Name: SAPLUMC_UTILITIES
Main Program: SAPLUMC_UTILITIES
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMC_PARALLEL_MDX_SETTINGS_SET 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 'UMC_PARALLEL_MDX_SETTINGS_SET'".
EXPORTING
I_PARALLEL = "Flag (X or Blank)
* I_SERVER_GROUP = "Server Group for Parallel Processing
* I_MAX_NO_OF_TASKS = "
EXCEPTIONS
DB_ERROR = 1
IMPORTING Parameters details for UMC_PARALLEL_MDX_SETTINGS_SET
I_PARALLEL - Flag (X or Blank)
Data type: AS4FLAGOptional: No
Call by Reference: Yes
I_SERVER_GROUP - Server Group for Parallel Processing
Data type: SPTA_RFCGROptional: Yes
Call by Reference: Yes
I_MAX_NO_OF_TASKS -
Data type: SY-INDEXOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DB_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UMC_PARALLEL_MDX_SETTINGS_SET 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_db_error | TYPE STRING, " | |||
| lv_i_parallel | TYPE AS4FLAG, " | |||
| lv_i_server_group | TYPE SPTA_RFCGR, " | |||
| lv_i_max_no_of_tasks | TYPE SY-INDEX. " |
|   CALL FUNCTION 'UMC_PARALLEL_MDX_SETTINGS_SET' " |
| EXPORTING | ||
| I_PARALLEL | = lv_i_parallel | |
| I_SERVER_GROUP | = lv_i_server_group | |
| I_MAX_NO_OF_TASKS | = lv_i_max_no_of_tasks | |
| EXCEPTIONS | ||
| DB_ERROR = 1 | ||
| . " UMC_PARALLEL_MDX_SETTINGS_SET | ||
ABAP code using 7.40 inline data declarations to call FM UMC_PARALLEL_MDX_SETTINGS_SET
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 INDEX FROM SY INTO @DATA(ld_i_max_no_of_tasks). | ||||
Search for further information about these or an SAP related objects