COM_SETTYPE_GET_MV_STRUCTURE SAP Function module

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

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

Pattern for FM COM_SETTYPE_GET_MV_STRUCTURE - COM SETTYPE GET MV STRUCTURE

CALL FUNCTION 'COM_SETTYPE_GET_MV_STRUCTURE' "
* EXPORTING
*   iv_settype_guid =           " comt_frgtype_guid
*   iv_settype_id =             " comt_frgtype_id  Set Type
*   iv_langu = SY-LANGU         " spras         Language Key
*   iv_with_text = SPACE        " comt_boolean  Checkbox
  IMPORTING
    es_settype =                " comt_settype_ext  Set type
    es_settype_t =              " comt_settype_t_ext  Set Type Text
  EXCEPTIONS
    NOT_FOUND = 1               "
    NO_IMPORT_VALUES = 2        "
    NO_TEXT_FOUND = 3           "
    .  "  COM_SETTYPE_GET_MV_STRUCTURE

ABAP code example for Function Module COM_SETTYPE_GET_MV_STRUCTURE

The ABAP code below is a full code listing to execute function module COM_SETTYPE_GET_MV_STRUCTURE 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_es_settype  
 
 TYPE COMT_SETTYPE_EXT
,
ld_es_settype_t  
 
 TYPE COMT_SETTYPE_T_EXT
.


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

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

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

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

CALL FUNCTION 'COM_SETTYPE_GET_MV_STRUCTURE'
* EXPORTING
*   iv_settype_guid =            ld_iv_settype_guid
*   iv_settype_id =              ld_iv_settype_id
*   iv_langu =                   ld_iv_langu
*   iv_with_text =               ld_iv_with_text
  IMPORTING
    es_settype =                 ld_es_settype
    es_settype_t =               ld_es_settype_t
  EXCEPTIONS
    NOT_FOUND =                  1
    NO_IMPORT_VALUES =           2
    NO_TEXT_FOUND =              3
    .  "  COM_SETTYPE_GET_MV_STRUCTURE

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_es_settype
 
 TYPE COMT_SETTYPE_EXT ,
ld_iv_settype_guid
 
 TYPE COMT_FRGTYPE_GUID ,
ld_es_settype_t
 
 TYPE COMT_SETTYPE_T_EXT ,
ld_iv_settype_id
 
 TYPE COMT_FRGTYPE_ID ,
ld_iv_langu
 
 TYPE SPRAS ,
ld_iv_with_text
 
 TYPE COMT_BOOLEAN .


ld_iv_settype_guid = 'Check type of data required'.
ld_iv_settype_id = 'Check type of data required'.
ld_iv_langu = 'Check type of data required'.
ld_iv_with_text = 'Check type of data required'.