SAP MY_DEFAULT_PARAMETERS_SET Function Module for Set Default Values
MY_DEFAULT_PARAMETERS_SET is a standard my default parameters set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Default Values 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 my default parameters set FM, simply by entering the name MY_DEFAULT_PARAMETERS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: NIWE
Program Name: SAPLNIWE
Main Program: SAPLNIWE
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MY_DEFAULT_PARAMETERS_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 'MY_DEFAULT_PARAMETERS_SET'"Set Default Values.
EXPORTING
I_BUKRS = "
I_SELC = "
I_NIWEX = "
* I_UCOMM = "Function Code That Triggered PAI
IMPORTING
E_SNIWEFY = "Lowest Value: Fiscal Year ID Data
CHANGING
C_NIWE = "
* C_NIWE0 = "
* C_NIWE1 = "
* C_NIWE2 = "
* C_NIWE3 = "
* C_NIWE8 = "
* C_NIWE9 = "
* C_NIWELS = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLNIWE_001
EXIT_SAPLNIWE_002
EXIT_SAPLNIWE_003
EXIT_SAPLNIWE_004
EXIT_SAPLNIWE_005
IMPORTING Parameters details for MY_DEFAULT_PARAMETERS_SET
I_BUKRS -
Data type: BUKRSOptional: No
Call by Reference: Yes
I_SELC -
Data type: XFELDOptional: No
Call by Reference: Yes
I_NIWEX -
Data type: MY_NIWEXOptional: No
Call by Reference: Yes
I_UCOMM - Function Code That Triggered PAI
Data type: SYUCOMMOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for MY_DEFAULT_PARAMETERS_SET
E_SNIWEFY - Lowest Value: Fiscal Year ID Data
Data type: SNIWEFYOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for MY_DEFAULT_PARAMETERS_SET
C_NIWE -
Data type: SNIWEOptional: No
Call by Reference: Yes
C_NIWE0 -
Data type: SNIWE0Optional: Yes
Call by Reference: Yes
C_NIWE1 -
Data type: SNIWE1Optional: Yes
Call by Reference: Yes
C_NIWE2 -
Data type: SNIWE2Optional: Yes
Call by Reference: Yes
C_NIWE3 -
Data type: SNIWE3Optional: Yes
Call by Reference: Yes
C_NIWE8 -
Data type: SNIWE8Optional: Yes
Call by Reference: Yes
C_NIWE9 -
Data type: SNIWE9Optional: Yes
Call by Reference: Yes
C_NIWELS -
Data type: SNIWELSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MY_DEFAULT_PARAMETERS_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_c_niwe | TYPE SNIWE, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_e_sniwefy | TYPE SNIWEFY, " | |||
| lv_i_selc | TYPE XFELD, " | |||
| lv_c_niwe0 | TYPE SNIWE0, " | |||
| lv_c_niwe1 | TYPE SNIWE1, " | |||
| lv_i_niwex | TYPE MY_NIWEX, " | |||
| lv_c_niwe2 | TYPE SNIWE2, " | |||
| lv_i_ucomm | TYPE SYUCOMM, " | |||
| lv_c_niwe3 | TYPE SNIWE3, " | |||
| lv_c_niwe8 | TYPE SNIWE8, " | |||
| lv_c_niwe9 | TYPE SNIWE9, " | |||
| lv_c_niwels | TYPE SNIWELS. " |
|   CALL FUNCTION 'MY_DEFAULT_PARAMETERS_SET' "Set Default Values |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_SELC | = lv_i_selc | |
| I_NIWEX | = lv_i_niwex | |
| I_UCOMM | = lv_i_ucomm | |
| IMPORTING | ||
| E_SNIWEFY | = lv_e_sniwefy | |
| CHANGING | ||
| C_NIWE | = lv_c_niwe | |
| C_NIWE0 | = lv_c_niwe0 | |
| C_NIWE1 | = lv_c_niwe1 | |
| C_NIWE2 | = lv_c_niwe2 | |
| C_NIWE3 | = lv_c_niwe3 | |
| C_NIWE8 | = lv_c_niwe8 | |
| C_NIWE9 | = lv_c_niwe9 | |
| C_NIWELS | = lv_c_niwels | |
| . " MY_DEFAULT_PARAMETERS_SET | ||
ABAP code using 7.40 inline data declarations to call FM MY_DEFAULT_PARAMETERS_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.Search for further information about these or an SAP related objects