SAP ITOB_CHECK_FLEET_CATEGORY Function Module for NOTRANSL: L1: Flottenobjektart (Flottenobjekt = Techn.Platz, Equipment)









ITOB_CHECK_FLEET_CATEGORY is a standard itob check fleet category 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: Flottenobjektart (Flottenobjekt = Techn.Platz, Equipment) 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 check fleet category FM, simply by entering the name ITOB_CHECK_FLEET_CATEGORY 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_CHECK_FLEET_CATEGORY 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_CHECK_FLEET_CATEGORY'"NOTRANSL: L1: Flottenobjektart (Flottenobjekt = Techn.Platz, Equipment)
EXPORTING
ITOBTYPE_IMP = "Technical object types in plant maintenance
* X_MESS_TYPE = 'E' "ABAP System Field: Message Type
* READ_TEXT_TABLES = ' ' "ABAP System Field: Batch Input Processing Active
FLEETCAT_IMP = "Fleet Object Type
* OBJCAT_IMP = "Generic Type
* USE_BUF = 'X' "ABAP System Field: Batch Input Processing Active
* LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* DIALOG_MODE = 'X' "ABAP System Field: Batch Input Processing Active
* DIALOG_CURSOR = ' ' "Field name
* DIALOG_STEPL = 0 "ABAP System Field: Current Step Loop or Table Control Line
* INIT_MESSAGE_DATA = 'X' "ABAP System Field: Batch Input Processing Active

IMPORTING
NUM_EXP = "Predefined Type
T370FLT_EXP = "Fleet Types
T370K_T_EXP = "Language-Dependent Texts for Object Type
T370FLT_R_EXP = "Fleet Types: Reference to Technical Object Types (Equi/FL)

EXCEPTIONS
EMPTY_KEY = 1 APPLICATION_ERROR = 2
.



IMPORTING Parameters details for ITOB_CHECK_FLEET_CATEGORY

ITOBTYPE_IMP - Technical object types in plant maintenance

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

X_MESS_TYPE - ABAP System Field: Message Type

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

READ_TEXT_TABLES - ABAP System Field: Batch Input Processing Active

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

FLEETCAT_IMP - Fleet Object Type

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

OBJCAT_IMP - Generic Type

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

USE_BUF - ABAP System Field: Batch Input Processing Active

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

LANGU - ABAP System Field: Language Key of Text Environment

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

DIALOG_MODE - ABAP System Field: Batch Input Processing Active

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

DIALOG_CURSOR - Field name

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

DIALOG_STEPL - ABAP System Field: Current Step Loop or Table Control Line

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

INIT_MESSAGE_DATA - ABAP System Field: Batch Input Processing Active

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

EXPORTING Parameters details for ITOB_CHECK_FLEET_CATEGORY

NUM_EXP - Predefined Type

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

T370FLT_EXP - Fleet Types

Data type: T370FLT
Optional: No
Call by Reference: Yes

T370K_T_EXP - Language-Dependent Texts for Object Type

Data type: T370K_T
Optional: No
Call by Reference: Yes

T370FLT_R_EXP - Fleet Types: Reference to Technical Object Types (Equi/FL)

Data type: T370FLT_R
Optional: No
Call by Reference: Yes

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_CHECK_FLEET_CATEGORY 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_num_exp  TYPE I, "   
lv_empty_key  TYPE I, "   
lv_itobtype_imp  TYPE ITOBTYP, "   
lv_x_mess_type  TYPE SY-MSGTY, "   'E'
lv_read_text_tables  TYPE SY-BINPT, "   ' '
lv_t370flt_exp  TYPE T370FLT, "   
lv_fleetcat_imp  TYPE T370FLT-FLEET_CAT, "   
lv_application_error  TYPE T370FLT, "   
lv_objcat_imp  TYPE C, "   
lv_t370k_t_exp  TYPE T370K_T, "   
lv_use_buf  TYPE SY-BINPT, "   'X'
lv_t370flt_r_exp  TYPE T370FLT_R, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
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'

  CALL FUNCTION 'ITOB_CHECK_FLEET_CATEGORY'  "NOTRANSL: L1: Flottenobjektart (Flottenobjekt = Techn.Platz, Equipment)
    EXPORTING
         ITOBTYPE_IMP = lv_itobtype_imp
         X_MESS_TYPE = lv_x_mess_type
         READ_TEXT_TABLES = lv_read_text_tables
         FLEETCAT_IMP = lv_fleetcat_imp
         OBJCAT_IMP = lv_objcat_imp
         USE_BUF = lv_use_buf
         LANGU = lv_langu
         DIALOG_MODE = lv_dialog_mode
         DIALOG_CURSOR = lv_dialog_cursor
         DIALOG_STEPL = lv_dialog_stepl
         INIT_MESSAGE_DATA = lv_init_message_data
    IMPORTING
         NUM_EXP = lv_num_exp
         T370FLT_EXP = lv_t370flt_exp
         T370K_T_EXP = lv_t370k_t_exp
         T370FLT_R_EXP = lv_t370flt_r_exp
    EXCEPTIONS
        EMPTY_KEY = 1
        APPLICATION_ERROR = 2
. " ITOB_CHECK_FLEET_CATEGORY




ABAP code using 7.40 inline data declarations to call FM ITOB_CHECK_FLEET_CATEGORY

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 MSGTY FROM SY INTO @DATA(ld_x_mess_type).
DATA(ld_x_mess_type) = 'E'.
 
"SELECT single BINPT FROM SY INTO @DATA(ld_read_text_tables).
DATA(ld_read_text_tables) = ' '.
 
 
"SELECT single FLEET_CAT FROM T370FLT INTO @DATA(ld_fleetcat_imp).
 
 
 
 
"SELECT single BINPT FROM SY INTO @DATA(ld_use_buf).
DATA(ld_use_buf) = 'X'.
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"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'.
 


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!