SAP RM_DETERMINE_USER_SETTINGS Function Module for
RM_DETERMINE_USER_SETTINGS is a standard rm determine user settings 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 rm determine user settings FM, simply by entering the name RM_DETERMINE_USER_SETTINGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PTRM
Program Name: SAPLPTRM
Main Program: SAPLPTRM
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DETERMINE_USER_SETTINGS 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 'RM_DETERMINE_USER_SETTINGS'".
EXPORTING
* T437A_FL = ' ' "
* INSIDE_PT = 'X' "
* RM61R_FL = "
* UMD04_IM = "
* AKT = 'V' "
IMPORTING
NO_CHANGE = "
UMD04_EX = "
TABLES
* SORTY = "
EXCEPTIONS
ERROR = 1
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_SAPLPTRM_001 User Exit for Lead Column in REM Planning Table
IMPORTING Parameters details for RM_DETERMINE_USER_SETTINGS
T437A_FL -
Data type: T437ADefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
INSIDE_PT -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
RM61R_FL -
Data type: RM61ROptional: Yes
Call by Reference: No ( called with pass by value option)
UMD04_IM -
Data type: UMD04Optional: Yes
Call by Reference: No ( called with pass by value option)
AKT -
Data type: UMD04-MDAKTDefault: 'V'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_DETERMINE_USER_SETTINGS
NO_CHANGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UMD04_EX -
Data type: UMD04Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RM_DETERMINE_USER_SETTINGS
SORTY -
Data type: RESORTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_DETERMINE_USER_SETTINGS 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_error | TYPE STRING, " | |||
| lt_sorty | TYPE STANDARD TABLE OF RESORT, " | |||
| lv_t437a_fl | TYPE T437A, " ' ' | |||
| lv_no_change | TYPE T437A, " | |||
| lv_umd04_ex | TYPE UMD04, " | |||
| lv_inside_pt | TYPE UMD04, " 'X' | |||
| lv_rm61r_fl | TYPE RM61R, " | |||
| lv_umd04_im | TYPE UMD04, " | |||
| lv_akt | TYPE UMD04-MDAKT. " 'V' |
|   CALL FUNCTION 'RM_DETERMINE_USER_SETTINGS' " |
| EXPORTING | ||
| T437A_FL | = lv_t437a_fl | |
| INSIDE_PT | = lv_inside_pt | |
| RM61R_FL | = lv_rm61r_fl | |
| UMD04_IM | = lv_umd04_im | |
| AKT | = lv_akt | |
| IMPORTING | ||
| NO_CHANGE | = lv_no_change | |
| UMD04_EX | = lv_umd04_ex | |
| TABLES | ||
| SORTY | = lt_sorty | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " RM_DETERMINE_USER_SETTINGS | ||
ABAP code using 7.40 inline data declarations to call FM RM_DETERMINE_USER_SETTINGS
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_t437a_fl) | = ' '. | |||
| DATA(ld_inside_pt) | = 'X'. | |||
| "SELECT single MDAKT FROM UMD04 INTO @DATA(ld_akt). | ||||
| DATA(ld_akt) | = 'V'. | |||
Search for further information about these or an SAP related objects