SAP ITOB_GET_CLASS_STANDARD Function Module for NOTRANSL: L1: Lesen Standardklasse zum Technischen Objekt
ITOB_GET_CLASS_STANDARD is a standard itob get class standard SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: L1: Lesen Standardklasse zum Technischen Objekt 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 itob get class standard FM, simply by entering the name ITOB_GET_CLASS_STANDARD into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITO2
Program Name: SAPLITO2
Main Program: SAPLITO2
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ITOB_GET_CLASS_STANDARD 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 'ITOB_GET_CLASS_STANDARD'"NOTRANSL: L1: Lesen Standardklasse zum Technischen Objekt.
EXPORTING
* TPLNR_IMP = "
* EQUNR_IMP = "
* ACTIVITY_IMP = 'A' "Activity Category in Transaction (Cr/Ch/D)
* USE_BUF = 'X' "
* DIALOG_MODE = 'X' "
* DIALOG_CURSOR = ' ' "
* DIALOG_STEPL = 0 "
* INIT_MESSAGE_DATA = 'X' "
* X_MESS_TYPE = 'E' "
IMPORTING
CLASS_EXP = "
CLASSTYPE_EXP = "
CLASSTEXT_EXP = "
EXCEPTIONS
EMPTY_KEY = 1 APPLICATION_ERROR = 2
IMPORTING Parameters details for ITOB_GET_CLASS_STANDARD
TPLNR_IMP -
Data type: ITOB-TPLNROptional: Yes
Call by Reference: No ( called with pass by value option)
EQUNR_IMP -
Data type: ITOB-EQUNROptional: Yes
Call by Reference: No ( called with pass by value option)
ACTIVITY_IMP - Activity Category in Transaction (Cr/Ch/D)
Data type: T370-AKTYPDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
USE_BUF -
Data type: SY-BINPTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG_MODE -
Data type: SY-BINPTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG_CURSOR -
Data type: DD03D-FIELDNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG_STEPL -
Data type: SY-STEPLOptional: Yes
Call by Reference: No ( called with pass by value option)
INIT_MESSAGE_DATA -
Data type: SY-BINPTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MESS_TYPE -
Data type: SY-MSGTYDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ITOB_GET_CLASS_STANDARD
CLASS_EXP -
Data type: KLAH-CLASSOptional: No
Call by Reference: No ( called with pass by value option)
CLASSTYPE_EXP -
Data type: KLAH-KLARTOptional: No
Call by Reference: No ( called with pass by value option)
CLASSTEXT_EXP -
Data type: API_KSSK-KLTXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EMPTY_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ITOB_GET_CLASS_STANDARD 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_exp | TYPE KLAH-CLASS, " | |||
| lv_empty_key | TYPE KLAH, " | |||
| lv_tplnr_imp | TYPE ITOB-TPLNR, " | |||
| lv_equnr_imp | TYPE ITOB-EQUNR, " | |||
| lv_classtype_exp | TYPE KLAH-KLART, " | |||
| lv_application_error | TYPE KLAH, " | |||
| lv_activity_imp | TYPE T370-AKTYP, " 'A' | |||
| lv_classtext_exp | TYPE API_KSSK-KLTXT, " | |||
| lv_use_buf | TYPE SY-BINPT, " 'X' | |||
| lv_dialog_mode | TYPE SY-BINPT, " 'X' | |||
| lv_dialog_cursor | TYPE DD03D-FIELDNAME, " SPACE | |||
| lv_dialog_stepl | TYPE SY-STEPL, " 0 | |||
| lv_init_message_data | TYPE SY-BINPT, " 'X' | |||
| lv_x_mess_type | TYPE SY-MSGTY. " 'E' |
|   CALL FUNCTION 'ITOB_GET_CLASS_STANDARD' "NOTRANSL: L1: Lesen Standardklasse zum Technischen Objekt |
| EXPORTING | ||
| TPLNR_IMP | = lv_tplnr_imp | |
| EQUNR_IMP | = lv_equnr_imp | |
| ACTIVITY_IMP | = lv_activity_imp | |
| USE_BUF | = lv_use_buf | |
| DIALOG_MODE | = lv_dialog_mode | |
| DIALOG_CURSOR | = lv_dialog_cursor | |
| DIALOG_STEPL | = lv_dialog_stepl | |
| INIT_MESSAGE_DATA | = lv_init_message_data | |
| X_MESS_TYPE | = lv_x_mess_type | |
| IMPORTING | ||
| CLASS_EXP | = lv_class_exp | |
| CLASSTYPE_EXP | = lv_classtype_exp | |
| CLASSTEXT_EXP | = lv_classtext_exp | |
| EXCEPTIONS | ||
| EMPTY_KEY = 1 | ||
| APPLICATION_ERROR = 2 | ||
| . " ITOB_GET_CLASS_STANDARD | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_GET_CLASS_STANDARD
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_exp). | ||||
| "SELECT single TPLNR FROM ITOB INTO @DATA(ld_tplnr_imp). | ||||
| "SELECT single EQUNR FROM ITOB INTO @DATA(ld_equnr_imp). | ||||
| "SELECT single KLART FROM KLAH INTO @DATA(ld_classtype_exp). | ||||
| "SELECT single AKTYP FROM T370 INTO @DATA(ld_activity_imp). | ||||
| DATA(ld_activity_imp) | = 'A'. | |||
| "SELECT single KLTXT FROM API_KSSK INTO @DATA(ld_classtext_exp). | ||||
| "SELECT single BINPT FROM SY INTO @DATA(ld_use_buf). | ||||
| DATA(ld_use_buf) | = 'X'. | |||
| "SELECT single BINPT FROM SY INTO @DATA(ld_dialog_mode). | ||||
| DATA(ld_dialog_mode) | = 'X'. | |||
| "SELECT single FIELDNAME FROM DD03D INTO @DATA(ld_dialog_cursor). | ||||
| DATA(ld_dialog_cursor) | = ' '. | |||
| "SELECT single STEPL FROM SY INTO @DATA(ld_dialog_stepl). | ||||
| "SELECT single BINPT FROM SY INTO @DATA(ld_init_message_data). | ||||
| DATA(ld_init_message_data) | = 'X'. | |||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_x_mess_type). | ||||
| DATA(ld_x_mess_type) | = 'E'. | |||
Search for further information about these or an SAP related objects