OO_CLASS_CREATE SAP Function module - Create Class

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

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

Pattern for FM OO_CLASS_CREATE - OO CLASS CREATE

CALL FUNCTION 'OO_CLASS_CREATE' "Create Class
* EXPORTING
*   superclass =                " seoclsref
*   commit = SEOX_FALSE         " seox_boolean
*   category = SEOC_CATEGORY_GENERAL  " seocategry  Class/Interface Category
*   clsaddon =                  " seoclsname    Object Type Name
*   locked_dynpro_fields =      " tdtab_c132    Table With a Width of 132 Characters
  IMPORTING
    classdef =                  " vseoclass     Generated table for view VSEOCLASS
* CHANGING
*   class =                     " seoclskey
  EXCEPTIONS
    CANCELLED = 1               "
    .  "  OO_CLASS_CREATE

ABAP code example for Function Module OO_CLASS_CREATE

The ABAP code below is a full code listing to execute function module OO_CLASS_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_classdef  
 
 TYPE VSEOCLASS
.


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

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

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

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

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

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

CALL FUNCTION 'OO_CLASS_CREATE'
* EXPORTING
*   superclass =                 ld_superclass
*   commit =                     ld_commit
*   category =                   ld_category
*   clsaddon =                   ld_clsaddon
*   locked_dynpro_fields =       ld_locked_dynpro_fields
  IMPORTING
    classdef =                   ld_classdef
* CHANGING
*   class =                      ld_class
  EXCEPTIONS
    CANCELLED =                  1
    .  "  OO_CLASS_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_class
 
 TYPE SEOCLSKEY ,
ld_classdef
 
 TYPE VSEOCLASS ,
ld_superclass
 
 TYPE SEOCLSREF ,
ld_commit
 
 TYPE SEOX_BOOLEAN ,
ld_category
 
 TYPE SEOCATEGRY ,
ld_clsaddon
 
 TYPE SEOCLSNAME ,
ld_locked_dynpro_fields
 
 TYPE TDTAB_C132 .


ld_class = 'Check type of data required'.
ld_superclass = 'Check type of data required'.
ld_commit = 'Check type of data required'.
ld_category = 'Check type of data required'.
ld_clsaddon = 'Check type of data required'.
ld_locked_dynpro_fields = 'Check type of data required'.