CRM_IC_SCRIPTING_COPY_OBJECT SAP Function module - Copy an xml document

CRM_IC_SCRIPTING_COPY_OBJECT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CRM_IC_SCRIPTING_COPY_OBJECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CRM_IC_SCRIPTING_PERSIST
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CRM_IC_SCRIPTING_COPY_OBJECT - CRM IC SCRIPTING COPY OBJECT

CALL FUNCTION 'CRM_IC_SCRIPTING_COPY_OBJECT' "Copy an xml document
  EXPORTING
    objecttype =                " crm_ic_isecomp  IS=Regular OS=Objection SU=Survey
    objectname =                " crm_ic_xmlname  XML document name
  IMPORTING
    newobjectname =             " crm_ic_xmlname  New XML document name
  EXCEPTIONS
    TARGET_OBJECT_EXISTS = 1    "               An object with target Id already exists.
    NON_EXISTING_SOURCE_OBJECT = 2  "           An object for the given source Id does not exist.
    COULD_NOT_CARRY_OPERATION = 3  "            Operations could not be performed.
    .  "  CRM_IC_SCRIPTING_COPY_OBJECT

ABAP code example for Function Module CRM_IC_SCRIPTING_COPY_OBJECT

The ABAP code below is a full code listing to execute function module CRM_IC_SCRIPTING_COPY_OBJECT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_newobjectname  
 
 TYPE CRM_IC_XMLNAME
.


DATA(ld_objecttype) = 'Check type of data required'.

DATA(ld_objectname) = 'Check type of data required'.
.

CALL FUNCTION 'CRM_IC_SCRIPTING_COPY_OBJECT'
  EXPORTING
    objecttype =                 ld_objecttype
    objectname =                 ld_objectname
  IMPORTING
    newobjectname =              ld_newobjectname
  EXCEPTIONS
    TARGET_OBJECT_EXISTS =       1
    NON_EXISTING_SOURCE_OBJECT =    2
    COULD_NOT_CARRY_OPERATION =    3
    .  "  CRM_IC_SCRIPTING_COPY_OBJECT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_newobjectname
 
 TYPE CRM_IC_XMLNAME ,
ld_objecttype
 
 TYPE CRM_IC_ISECOMP ,
ld_objectname
 
 TYPE CRM_IC_XMLNAME .


ld_objecttype = 'Check type of data required'.
ld_objectname = 'Check type of data required'.