SAP SDOK_M_ENT_COPY Function Module for









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

Function Group: SDC_MODEL
Program Name: SAPLSDC_MODEL
Main Program: SAPLSDC_MODEL
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SDOK_M_ENT_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 'SDOK_M_ENT_COPY'"
  EXPORTING
   ORIGINAL =  "
   COPY =  "
*  DESCRIPTION = ' ' "Short Description
*  MODEL' ' = ' ' "Model: Document Model Area
*  DEV_DATA =  "SDOK/Model: Definitions for Development Objects
*  X_DESCRS = ' ' "
*  X_REPLACE = ' ' "
*  TRKORR =  "Request/Task
*  AVOID_TR_RECORD =  "

EXCEPTIONS
   BAD_ENTITY = 1    BAD_COPY = 2    BAD_ENTITY_TYPE = 3    BAD_MODELSPACE = 4    CTS_FAILED = 5
.



IMPORTING Parameters details for SDOK_M_ENT_COPY

ORIGINAL -

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

COPY -

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

DESCRIPTION - Short Description

Data type: SDOKMET-DESCRIPT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODELSPACE - Model: Document Model Area

Data type: SDOKME-MODELSPACE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEV_DATA - SDOK/Model: Definitions for Development Objects

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

X_DESCRS -

Data type: SY-DATAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_REPLACE -

Data type: SY-DATAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRKORR - Request/Task

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

AVOID_TR_RECORD -

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

EXCEPTIONS details

BAD_ENTITY -

Data type:
Optional: No
Call by Reference: Yes

BAD_COPY -

Data type:
Optional: No
Call by Reference: Yes

BAD_ENTITY_TYPE -

Data type:
Optional: No
Call by Reference: Yes

BAD_MODELSPACE -

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

CTS_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SDOK_M_ENT_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_original  TYPE SDOKMENT, "   
lv_bad_entity  TYPE SDOKMENT, "   
lv_copy  TYPE SDOKMENT, "   
lv_bad_copy  TYPE SDOKMENT, "   
lv_description  TYPE SDOKMET-DESCRIPT, "   SPACE
lv_bad_entity_type  TYPE SDOKMET, "   
lv_modelspace  TYPE SDOKME-MODELSPACE, "   SPACE
lv_bad_modelspace  TYPE SDOKME, "   
lv_dev_data  TYPE SDOKMDEV, "   
lv_cts_failed  TYPE SDOKMDEV, "   
lv_x_descrs  TYPE SY-DATAR, "   SPACE
lv_x_replace  TYPE SY-DATAR, "   SPACE
lv_trkorr  TYPE E070-TRKORR, "   
lv_avoid_tr_record  TYPE SDOK_SGLFL. "   

  CALL FUNCTION 'SDOK_M_ENT_COPY'  "
    EXPORTING
         ORIGINAL = lv_original
         COPY = lv_copy
         DESCRIPTION = lv_description
         MODELSPACE = lv_modelspace
         DEV_DATA = lv_dev_data
         X_DESCRS = lv_x_descrs
         X_REPLACE = lv_x_replace
         TRKORR = lv_trkorr
         AVOID_TR_RECORD = lv_avoid_tr_record
    EXCEPTIONS
        BAD_ENTITY = 1
        BAD_COPY = 2
        BAD_ENTITY_TYPE = 3
        BAD_MODELSPACE = 4
        CTS_FAILED = 5
. " SDOK_M_ENT_COPY




ABAP code using 7.40 inline data declarations to call FM SDOK_M_ENT_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 DESCRIPT FROM SDOKMET INTO @DATA(ld_description).
DATA(ld_description) = ' '.
 
 
"SELECT single MODEL' ' FROM SDOKME INTO @DATA(ld_modelspace).
DATA(ld_modelspace) = ' '.
 
 
 
 
"SELECT single DATAR FROM SY INTO @DATA(ld_x_descrs).
DATA(ld_x_descrs) = ' '.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_x_replace).
DATA(ld_x_replace) = ' '.
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_trkorr).
 
 


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!