SAP UDM_RSM_GET_REASONS Function Module for
UDM_RSM_GET_REASONS is a standard udm rsm get reasons 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 udm rsm get reasons FM, simply by entering the name UDM_RSM_GET_REASONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: UDMV_RSM_REASON
Program Name: SAPLUDMV_RSM_REASON
Main Program: SAPLUDMV_RSM_REASON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UDM_RSM_GET_REASONS 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 'UDM_RSM_GET_REASONS'".
EXPORTING
I_LANG = "Language Key
IMPORTING
RETURN = "Return Parameter(s)
TABLES
ET_RSM_REASONS = "
IMPORTING Parameters details for UDM_RSM_GET_REASONS
I_LANG - Language Key
Data type: LANGUOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UDM_RSM_GET_REASONS
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for UDM_RSM_GET_REASONS
ET_RSM_REASONS -
Data type: BDM_S_RSM_REASONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UDM_RSM_GET_REASONS 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_lang | TYPE LANGU, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lt_et_rsm_reasons | TYPE STANDARD TABLE OF BDM_S_RSM_REASON. " |
|   CALL FUNCTION 'UDM_RSM_GET_REASONS' " |
| EXPORTING | ||
| I_LANG | = lv_i_lang | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| ET_RSM_REASONS | = lt_et_rsm_reasons | |
| . " UDM_RSM_GET_REASONS | ||
ABAP code using 7.40 inline data declarations to call FM UDM_RSM_GET_REASONS
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