COM_SETTYPE_ATTR_DBTAB_TO_ATTR SAP Function module

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

Associated Function Group: COM_SETTYPE_ATTRIBUTE_TAB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM COM_SETTYPE_ATTR_DBTAB_TO_ATTR - COM SETTYPE ATTR DBTAB TO ATTR

CALL FUNCTION 'COM_SETTYPE_ATTR_DBTAB_TO_ATTR' "
  EXPORTING
    iv_tabname =                " tabname
    iv_fieldname =              " fieldname
  IMPORTING
    ev_settype_id =             " comt_frgtype_id
    ev_settype_guid =           " comt_frgtype_guid
    ev_attribute_id =           " comt_attr_id_30
    ev_multi_value =            " comt_multivalue
  EXCEPTIONS
    INVALID_IMPORT_PARAMETERS = 1  "
    NOT_FOUND = 2               "
    .  "  COM_SETTYPE_ATTR_DBTAB_TO_ATTR

ABAP code example for Function Module COM_SETTYPE_ATTR_DBTAB_TO_ATTR

The ABAP code below is a full code listing to execute function module COM_SETTYPE_ATTR_DBTAB_TO_ATTR 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_ev_settype_id  
 
 TYPE COMT_FRGTYPE_ID
,
ld_ev_settype_guid  
 
 TYPE COMT_FRGTYPE_GUID
,
ld_ev_attribute_id  
 
 TYPE COMT_ATTR_ID_30
,
ld_ev_multi_value  
 
 TYPE COMT_MULTIVALUE
.


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

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

CALL FUNCTION 'COM_SETTYPE_ATTR_DBTAB_TO_ATTR'
  EXPORTING
    iv_tabname =                 ld_iv_tabname
    iv_fieldname =               ld_iv_fieldname
  IMPORTING
    ev_settype_id =              ld_ev_settype_id
    ev_settype_guid =            ld_ev_settype_guid
    ev_attribute_id =            ld_ev_attribute_id
    ev_multi_value =             ld_ev_multi_value
  EXCEPTIONS
    INVALID_IMPORT_PARAMETERS =    1
    NOT_FOUND =                  2
    .  "  COM_SETTYPE_ATTR_DBTAB_TO_ATTR

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
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_ev_settype_id
 
 TYPE COMT_FRGTYPE_ID ,
ld_iv_tabname
 
 TYPE TABNAME ,
ld_ev_settype_guid
 
 TYPE COMT_FRGTYPE_GUID ,
ld_iv_fieldname
 
 TYPE FIELDNAME ,
ld_ev_attribute_id
 
 TYPE COMT_ATTR_ID_30 ,
ld_ev_multi_value
 
 TYPE COMT_MULTIVALUE .


ld_iv_tabname = 'Check type of data required'.
ld_iv_fieldname = 'Check type of data required'.