SAP MEREP_MPC_COPY_DEVICE Function Module for









MEREP_MPC_COPY_DEVICE is a standard merep mpc copy device 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 merep mpc copy device FM, simply by entering the name MEREP_MPC_COPY_DEVICE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MEREP_INSTTK_MPC
Program Name: SAPLMEREP_INSTTK_MPC
Main Program: SAPLMEREP_INSTTK_MPC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MEREP_MPC_COPY_DEVICE 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 'MEREP_MPC_COPY_DEVICE'"
EXPORTING
SOURCE_DEVICEID = "
TARGET_DEVICEID = "

EXCEPTIONS
ERROR_CONVID_GENERATION = 1 ERROR_COPY_RDB = 2 ERROR_COPY_FILTERING = 3
.



IMPORTING Parameters details for MEREP_MPC_COPY_DEVICE

SOURCE_DEVICEID -

Data type: MEDEVGUID
Optional: No
Call by Reference: Yes

TARGET_DEVICEID -

Data type: MEDEVGUID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_CONVID_GENERATION -

Data type:
Optional: No
Call by Reference: Yes

ERROR_COPY_RDB -

Data type:
Optional: No
Call by Reference: Yes

ERROR_COPY_FILTERING -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MEREP_MPC_COPY_DEVICE 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_source_deviceid  TYPE MEDEVGUID, "   
lv_error_convid_generation  TYPE MEDEVGUID, "   
lv_error_copy_rdb  TYPE MEDEVGUID, "   
lv_target_deviceid  TYPE MEDEVGUID, "   
lv_error_copy_filtering  TYPE MEDEVGUID. "   

  CALL FUNCTION 'MEREP_MPC_COPY_DEVICE'  "
    EXPORTING
         SOURCE_DEVICEID = lv_source_deviceid
         TARGET_DEVICEID = lv_target_deviceid
    EXCEPTIONS
        ERROR_CONVID_GENERATION = 1
        ERROR_COPY_RDB = 2
        ERROR_COPY_FILTERING = 3
. " MEREP_MPC_COPY_DEVICE




ABAP code using 7.40 inline data declarations to call FM MEREP_MPC_COPY_DEVICE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!