SAP SD_MC_ROUTE_INTERMED Function Module for NOTRANSL: Selektion einer Route zu Zwischenknoten
SD_MC_ROUTE_INTERMED is a standard sd mc route intermed 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: Selektion einer Route zu Zwischenknoten 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 sd mc route intermed FM, simply by entering the name SD_MC_ROUTE_INTERMED into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56R
Program Name: SAPLV56R
Main Program: SAPLV56R
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_MC_ROUTE_INTERMED 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 'SD_MC_ROUTE_INTERMED'"NOTRANSL: Selektion einer Route zu Zwischenknoten.
EXPORTING
* MCONAME = ' ' "
* SELSTR = ' ' "
TABLES
* VALUES = "
IMPORTING Parameters details for SD_MC_ROUTE_INTERMED
MCONAME -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SELSTR -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_MC_ROUTE_INTERMED
VALUES -
Data type: RSMVAOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_MC_ROUTE_INTERMED 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: | ||||
| lt_values | TYPE STANDARD TABLE OF RSMVA, " | |||
| lv_mconame | TYPE RSMVA, " SPACE | |||
| lv_selstr | TYPE RSMVA. " SPACE |
|   CALL FUNCTION 'SD_MC_ROUTE_INTERMED' "NOTRANSL: Selektion einer Route zu Zwischenknoten |
| EXPORTING | ||
| MCONAME | = lv_mconame | |
| SELSTR | = lv_selstr | |
| TABLES | ||
| VALUES | = lt_values | |
| . " SD_MC_ROUTE_INTERMED | ||
ABAP code using 7.40 inline data declarations to call FM SD_MC_ROUTE_INTERMED
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_mconame) | = ' '. | |||
| DATA(ld_selstr) | = ' '. | |||
Search for further information about these or an SAP related objects