SAP COMPOSITE_EDITOR_COPY Function Module for









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

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



Function COMPOSITE_EDITOR_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 'COMPOSITE_EDITOR_COPY'"
  EXPORTING
   I_OPERATION =  "
   I_OBJECT =  "
   I_COMPOSITE =  "
   I_REF =  "

EXCEPTIONS
   DELETION_NOT_POSSIBLE = 1    ACTION_CANCELLED = 2
.



IMPORTING Parameters details for COMPOSITE_EDITOR_COPY

I_OPERATION -

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

I_OBJECT -

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

I_COMPOSITE -

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

I_REF -

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

EXCEPTIONS details

DELETION_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

ACTION_CANCELLED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COMPOSITE_EDITOR_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_i_operation  TYPE SEU_ACTION, "   
lv_deletion_not_possible  TYPE SEU_ACTION, "   
lv_i_object  TYPE SEU_OBJKEY, "   
lv_action_cancelled  TYPE SEU_OBJKEY, "   
lv_i_composite  TYPE ENHCOMPHEADER, "   
lv_i_ref  TYPE CL_ENH_COMPOSITE_EDITOR. "   

  CALL FUNCTION 'COMPOSITE_EDITOR_COPY'  "
    EXPORTING
         I_OPERATION = lv_i_operation
         I_OBJECT = lv_i_object
         I_COMPOSITE = lv_i_composite
         I_REF = lv_i_ref
    EXCEPTIONS
        DELETION_NOT_POSSIBLE = 1
        ACTION_CANCELLED = 2
. " COMPOSITE_EDITOR_COPY




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



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!