SDOK_M_ATTR_CREATE SAP Function module

SDOK_M_ATTR_CREATE 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 SDOK_M_ATTR_CREATE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM SDOK_M_ATTR_CREATE - SDOK M ATTR CREATE

CALL FUNCTION 'SDOK_M_ATTR_CREATE' "
  EXPORTING
    name =                      " sdokmcls-io_class  Model: Entity Name
    description =               " sdokmet-descript  Short Description
    modelspace =                " sdokme-modelspace  Model: Document Model Area
*   dev_data =                  " sdokmdev      SDOK/Model: Definitions for Development Objects
*   trkorr =                    " e070-trkorr   Request/Task
*   avoid_tr_record =           " sdok_sglfl
  EXCEPTIONS
    BAD_NAME = 1                "
    BAD_MODELSPACE = 2          "
    MISSING_DESCRIPTION = 3     "               Short description missing
    CTS_FAILED = 4              "
    .  "  SDOK_M_ATTR_CREATE

ABAP code example for Function Module SDOK_M_ATTR_CREATE

The ABAP code below is a full code listing to execute function module SDOK_M_ATTR_CREATE 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_name) = some text here
 

SELECT single DESCRIPT 
  FROM SDOKMET 
  INTO @DATA(ld_description).

 

SELECT single MODELSPACE 
  FROM SDOKME 
  INTO @DATA(ld_modelspace).


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

SELECT single TRKORR 
  FROM E070 
  INTO @DATA(ld_trkorr).


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

CALL FUNCTION 'SDOK_M_ATTR_CREATE'
  EXPORTING
    name =                       ld_name
    description =                ld_description
    modelspace =                 ld_modelspace
*   dev_data =                   ld_dev_data
*   trkorr =                     ld_trkorr
*   avoid_tr_record =            ld_avoid_tr_record
  EXCEPTIONS
    BAD_NAME =                   1
    BAD_MODELSPACE =             2
    MISSING_DESCRIPTION =        3
    CTS_FAILED =                 4
    .  "  SDOK_M_ATTR_CREATE

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
ELSEIF SY-SUBRC EQ 4. "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_name
 
 TYPE SDOKMCLS-IO_CLASS ,
ld_description
 
 TYPE SDOKMET-DESCRIPT ,
ld_modelspace
 
 TYPE SDOKME-MODELSPACE ,
ld_dev_data
 
 TYPE SDOKMDEV ,
ld_trkorr
 
 TYPE E070-TRKORR ,
ld_avoid_tr_record
 
 TYPE SDOK_SGLFL .



ld_name = some text here

SELECT single DESCRIPT 
  FROM SDOKMET 
  INTO ld_description.


SELECT single MODELSPACE 
  FROM SDOKME 
  INTO ld_modelspace.

ld_dev_data = 'Check type of data required'.

SELECT single TRKORR 
  FROM E070 
  INTO ld_trkorr.

ld_avoid_tr_record = 'Check type of data required'.