SAP CTMS_CLASS_DDB Function Module for Dynamic database set up for class entered









CTMS_CLASS_DDB is a standard ctms class ddb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dynamic database set up for class entered processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ctms class ddb FM, simply by entering the name CTMS_CLASS_DDB into the relevant SAP transaction such as SE37 or SE38.

Function Group: CTMS
Program Name: SAPLCTMS
Main Program: SAPLCTMS
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CTMS_CLASS_DDB pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'CTMS_CLASS_DDB'"Dynamic database set up for class entered
EXPORTING
CLASS = "
* INIT_CONF = ' ' "
* READONLY = ' ' "
* I_CALLED_FROM_DDB = ' ' "
CLASSTYPE = "
* MODE = ' ' "
* LANGUAGE = SY-LANGU "
* KEY_DATE = SY-DATUM "
* OBJECTID = "
* OBJECT = "
* I_ADD_ON_CHAR = ' ' "
* I_TABS_ACTIVE = ' ' "

EXCEPTIONS
NOT_FOUND = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCTMS_001 Set Default Values
EXIT_SAPLCTMS_002 Check for Same Classification
EXIT_SAPLCTMS_003 Object Dependencies When Finding Objects
EXIT_SAPLCTMS_999 Dummy User Exit

IMPORTING Parameters details for CTMS_CLASS_DDB

CLASS -

Data type: KLAH-CLASS
Optional: No
Call by Reference: No ( called with pass by value option)

INIT_CONF -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

READONLY -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CALLED_FROM_DDB -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLASSTYPE -

Data type: KLAH-KLART
Optional: No
Call by Reference: No ( called with pass by value option)

MODE -

Data type:
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY_DATE -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECTID -

Data type: TCLA-OBTAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT -

Data type: KSSK-OBJEK
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ADD_ON_CHAR -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TABS_ACTIVE -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CTMS_CLASS_DDB Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_class  TYPE KLAH-CLASS, "   
lv_not_found  TYPE KLAH, "   
lv_init_conf  TYPE KLAH, "   SPACE
lv_readonly  TYPE KLAH, "   SPACE
lv_i_called_from_ddb  TYPE C, "   SPACE
lv_classtype  TYPE KLAH-KLART, "   
lv_mode  TYPE KLAH, "   ' '
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_key_date  TYPE SY-DATUM, "   SY-DATUM
lv_objectid  TYPE TCLA-OBTAB, "   
lv_object  TYPE KSSK-OBJEK, "   
lv_i_add_on_char  TYPE KSSK, "   SPACE
lv_i_tabs_active  TYPE KSSK. "   SPACE

  CALL FUNCTION 'CTMS_CLASS_DDB'  "Dynamic database set up for class entered
    EXPORTING
         CLASS = lv_class
         INIT_CONF = lv_init_conf
         READONLY = lv_readonly
         I_CALLED_FROM_DDB = lv_i_called_from_ddb
         CLASSTYPE = lv_classtype
         MODE = lv_mode
         LANGUAGE = lv_language
         KEY_DATE = lv_key_date
         OBJECTID = lv_objectid
         OBJECT = lv_object
         I_ADD_ON_CHAR = lv_i_add_on_char
         I_TABS_ACTIVE = lv_i_tabs_active
    EXCEPTIONS
        NOT_FOUND = 1
. " CTMS_CLASS_DDB




ABAP code using 7.40 inline data declarations to call FM CTMS_CLASS_DDB

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single CLASS FROM KLAH INTO @DATA(ld_class).
 
 
DATA(ld_init_conf) = ' '.
 
DATA(ld_readonly) = ' '.
 
DATA(ld_i_called_from_ddb) = ' '.
 
"SELECT single KLART FROM KLAH INTO @DATA(ld_classtype).
 
DATA(ld_mode) = ' '.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_key_date).
DATA(ld_key_date) = SY-DATUM.
 
"SELECT single OBTAB FROM TCLA INTO @DATA(ld_objectid).
 
"SELECT single OBJEK FROM KSSK INTO @DATA(ld_object).
 
DATA(ld_i_add_on_char) = ' '.
 
DATA(ld_i_tabs_active) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!