SAP ISU_M_EVENT_COPY Function Module for IS-U Migration: Copy Events









ISU_M_EVENT_COPY is a standard isu m event 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 IS-U Migration: Copy Events 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 event copy FM, simply by entering the name ISU_M_EVENT_COPY into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_M_EVENT_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_EVENT_COPY'"IS-U Migration: Copy Events
EXPORTING
X_FIRMA = "Company (Client) for IS-U Migration
X_OBJECT = "Migration Object
X_CLASS = "Migration Class
.



IMPORTING Parameters details for ISU_M_EVENT_COPY

X_FIRMA - Company (Client) for IS-U Migration

Data type: TEMOB-FIRMA
Optional: No
Call by Reference: Yes

X_OBJECT - Migration Object

Data type: TEMOB-OBJECT
Optional: No
Call by Reference: Yes

X_CLASS - Migration Class

Data type: TEMOB-CLASS
Optional: No
Call by Reference: Yes

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

DATA:
lv_x_firma  TYPE TEMOB-FIRMA, "   
lv_x_object  TYPE TEMOB-OBJECT, "   
lv_x_class  TYPE TEMOB-CLASS. "   

  CALL FUNCTION 'ISU_M_EVENT_COPY'  "IS-U Migration: Copy Events
    EXPORTING
         X_FIRMA = lv_x_firma
         X_OBJECT = lv_x_object
         X_CLASS = lv_x_class
. " ISU_M_EVENT_COPY




ABAP code using 7.40 inline data declarations to call FM ISU_M_EVENT_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.

"SELECT single FIRMA FROM TEMOB INTO @DATA(ld_x_firma).
 
"SELECT single OBJECT FROM TEMOB INTO @DATA(ld_x_object).
 
"SELECT single CLASS FROM TEMOB INTO @DATA(ld_x_class).
 


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!