SAP MM_ARRANG_GET_NODE_SELECTION Function Module for NOTRANSL: Liest Daten zum selektierten Eintrag im Baum
MM_ARRANG_GET_NODE_SELECTION is a standard mm arrang get node selection SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Liest Daten zum selektierten Eintrag im Baum 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 mm arrang get node selection FM, simply by entering the name MM_ARRANG_GET_NODE_SELECTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: WN40
Program Name: SAPLWN40
Main Program: SAPLWN40
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_GET_NODE_SELECTION 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 'MM_ARRANG_GET_NODE_SELECTION'"NOTRANSL: Liest Daten zum selektierten Eintrag im Baum.
EXPORTING
I_HANDLE = "
IMPORTING
E_VAKE = "Sample Structure for the Variable Key
IMPORTING Parameters details for MM_ARRANG_GET_NODE_SELECTION
I_HANDLE -
Data type: CNTL_HANDLEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for MM_ARRANG_GET_NODE_SELECTION
E_VAKE - Sample Structure for the Variable Key
Data type: VAKEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_ARRANG_GET_NODE_SELECTION 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_e_vake | TYPE VAKE, " | |||
| lv_i_handle | TYPE CNTL_HANDLE. " |
|   CALL FUNCTION 'MM_ARRANG_GET_NODE_SELECTION' "NOTRANSL: Liest Daten zum selektierten Eintrag im Baum |
| EXPORTING | ||
| I_HANDLE | = lv_i_handle | |
| IMPORTING | ||
| E_VAKE | = lv_e_vake | |
| . " MM_ARRANG_GET_NODE_SELECTION | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_GET_NODE_SELECTION
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