SEO_CLASS_GET SAP Function module - Read Class

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

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

Pattern for FM SEO_CLASS_GET - SEO CLASS GET

CALL FUNCTION 'SEO_CLASS_GET' "Read Class
  EXPORTING
    clskey =                    " seoclskey
*   version = SEOC_VERSION_INACTIVE  " seoversion
*   state = '0'                 " seostate
*   description_bypassing_buffer = ABAP_FALSE  " abap_bool  Kurztext nicht vom AppServer Puffer
  IMPORTING
    superclass =                " seoclsref
    class =                     " vseoclass
  EXCEPTIONS
    NOT_EXISTING = 1            "
    DELETED = 2                 "
    IS_INTERFACE = 3            "
    MODEL_ONLY = 4              "
    .  "  SEO_CLASS_GET

ABAP code example for Function Module SEO_CLASS_GET

The ABAP code below is a full code listing to execute function module SEO_CLASS_GET 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_superclass  
 
 TYPE SEOCLSREF
,
ld_class  
 
 TYPE VSEOCLASS
.


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

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

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

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

CALL FUNCTION 'SEO_CLASS_GET'
  EXPORTING
    clskey =                     ld_clskey
*   version =                    ld_version
*   state =                      ld_state
*   description_bypassing_buffer =    ld_description_bypassing_buffer
  IMPORTING
    superclass =                 ld_superclass
    class =                      ld_class
  EXCEPTIONS
    NOT_EXISTING =               1
    DELETED =                    2
    IS_INTERFACE =               3
    MODEL_ONLY =                 4
    .  "  SEO_CLASS_GET

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_superclass
 
 TYPE SEOCLSREF ,
ld_clskey
 
 TYPE SEOCLSKEY ,
ld_class
 
 TYPE VSEOCLASS ,
ld_version
 
 TYPE SEOVERSION ,
ld_state
 
 TYPE SEOSTATE ,
ld_description_bypassing_buffer
 
 TYPE ABAP_BOOL .


ld_clskey = 'Check type of data required'.
ld_version = 'Check type of data required'.
ld_state = 'Check type of data required'.
ld_description_bypassing_buffer = 'Check type of data required'.