SAP MCP_RFC_DEST Function Module for NOTRANSL: Auswahl möglicher Destinations
MCP_RFC_DEST is a standard mcp rfc dest 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: Auswahl möglicher Destinations 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 mcp rfc dest FM, simply by entering the name MCP_RFC_DEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCP6
Program Name: SAPLMCP6
Main Program: SAPLMCP6
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function MCP_RFC_DEST 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 'MCP_RFC_DEST'"NOTRANSL: Auswahl möglicher Destinations.
IMPORTING
E_DEST = "Structure for host list
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_SAPLMCP6_001 User Exit for Extrapolating Sales for OTB
EXIT_SAPLMCP6_002 User Exit for Checking OTB Within a Purchase Order
EXPORTING Parameters details for MCP_RFC_DEST
E_DEST - Structure for host list
Data type: RFCHOSTSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCP_RFC_DEST 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_dest | TYPE RFCHOSTS. " |
  CALL FUNCTION 'MCP_RFC_DEST' "NOTRANSL: Auswahl möglicher Destinations |
IMPORTING | ||
E_DEST | = lv_e_dest | |
. " MCP_RFC_DEST |
ABAP code using 7.40 inline data declarations to call FM MCP_RFC_DEST
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