SAP ISU_M_OBJECT_COPY Function Module for INTERNAL: IS-U Migration - Delete Migration Object

Search SAP Function Modules

ISU_M_OBJECT_COPY is a standard isu m object copy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Migration - Delete Migration Object 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 isu m object copy FM, simply by entering the name ISU_M_OBJECT_COPY into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_M_OBJECT_COPY 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 'ISU_M_OBJECT_COPY'"INTERNAL: IS-U Migration - Delete Migration Object
  EXPORTING
   X_SRC_FIRMA =  "Company (Client) for IS-U Migration
   X_SRC_OBJECT =  "Migration Object
   X_DST_FIRMA =  "Company (Client) for IS-U Migration
   X_DST_OBJECT =  "Migration Object
*  X_DST_KUERZL =  "
*  X_DST_OBJBEZ = ' ' "Text for migration object
*  X_COMMIT = ' ' "

EXCEPTIONS
   INVALID_COMPANY = 1    INVALID_OBJECT = 2    NOT_AUTHORIZED = 3    OBJECT_IS_HYPER_OBJECT = 4    OBJECT_ALREADY_EXIST = 5    KUERZL_ALREADY_EXIST = 6    MISSING_DEVCLASS = 7 

.

IMPORTING Parameters details for ISU_M_OBJECT_COPY

X_SRC_FIRMA - Company (Client) for IS-U Migration

Data type: TEMOB-FIRMA
Optional: No
Call by Reference: No ( called with pass by value option)

X_SRC_OBJECT - Migration Object

Data type: TEMOB-OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

X_DST_FIRMA - Company (Client) for IS-U Migration

Data type: TEMOB-FIRMA
Optional: No
Call by Reference: No ( called with pass by value option)

X_DST_OBJECT - Migration Object

Data type: TEMOB-OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

X_DST_KUERZL -

Data type: TEMOB-KUERZL
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_DST_OBJBEZ - Text for migration object

Data type: TEMOBT-OBJBEZ
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_COMMIT -

Data type: C
Default: ' '
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_COMPANY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_OBJECT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_IS_HYPER_OBJECT -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_ALREADY_EXIST -

Data type:
Optional: No
Call by Reference: Yes

KUERZL_ALREADY_EXIST -

Data type:
Optional: No
Call by Reference: Yes

MISSING_DEVCLASS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_M_OBJECT_COPY 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.

ABAP code using 7.40 inline data declarations to call FM ISU_M_OBJECT_COPY

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