SAP ITOB_CHECK_UPDATE_FLEET Function Module for NOTRANSL: Check Update Flottenobjektsegment (FLEET)
ITOB_CHECK_UPDATE_FLEET is a standard itob check update fleet 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: Check Update Flottenobjektsegment (FLEET) 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 update fleet FM, simply by entering the name ITOB_CHECK_UPDATE_FLEET into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITO4
Program Name: SAPLITO4
Main Program:
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ITOB_CHECK_UPDATE_FLEET 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_UPDATE_FLEET'"NOTRANSL: Check Update Flottenobjektsegment (FLEET).
EXPORTING
I_ACTIVITY_TYPE = "Activity category in transaction (Cr/Ch/D)
* I_OLD_FLEET = "Fleet Attributes
* I_OLD_ITOB = "Generated Table for View
* I_OLD_EQUI = "Equipment master data
* I_CONVERT_FLEET = ITOB_BOOL-TRUE "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
E_FLEET_ACTIVITY = "Generic Type
E_REC_FLEET_NOCNV = "Fleet Attributes
CHANGING
C_REC_FLEET = "Fleet Attributes
* C_REC_ITOB = "Generated Table for View
* C_REC_EQUI = "Equipment master data
IMPORTING Parameters details for ITOB_CHECK_UPDATE_FLEET
I_ACTIVITY_TYPE - Activity category in transaction (Cr/Ch/D)
Data type: T370-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_OLD_FLEET - Fleet Attributes
Data type: FLEETOptional: Yes
Call by Reference: Yes
I_OLD_ITOB - Generated Table for View
Data type: ITOBOptional: Yes
Call by Reference: Yes
I_OLD_EQUI - Equipment master data
Data type: EQUIOptional: Yes
Call by Reference: Yes
I_CONVERT_FLEET - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ITOB_TYPES-BOOLDefault: ITOB_BOOL-TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ITOB_CHECK_UPDATE_FLEET
E_FLEET_ACTIVITY - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
E_REC_FLEET_NOCNV - Fleet Attributes
Data type: FLEETOptional: No
Call by Reference: Yes
CHANGING Parameters details for ITOB_CHECK_UPDATE_FLEET
C_REC_FLEET - Fleet Attributes
Data type: FLEETOptional: No
Call by Reference: Yes
C_REC_ITOB - Generated Table for View
Data type: ITOBOptional: Yes
Call by Reference: Yes
C_REC_EQUI - Equipment master data
Data type: EQUIOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ITOB_CHECK_UPDATE_FLEET 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_c_rec_fleet | TYPE FLEET, " | |||
| lv_i_activity_type | TYPE T370-AKTYP, " | |||
| lv_e_fleet_activity | TYPE C, " | |||
| lv_c_rec_itob | TYPE ITOB, " | |||
| lv_i_old_fleet | TYPE FLEET, " | |||
| lv_e_rec_fleet_nocnv | TYPE FLEET, " | |||
| lv_c_rec_equi | TYPE EQUI, " | |||
| lv_i_old_itob | TYPE ITOB, " | |||
| lv_i_old_equi | TYPE EQUI, " | |||
| lv_i_convert_fleet | TYPE ITOB_TYPES-BOOL. " ITOB_BOOL-TRUE |
|   CALL FUNCTION 'ITOB_CHECK_UPDATE_FLEET' "NOTRANSL: Check Update Flottenobjektsegment (FLEET) |
| EXPORTING | ||
| I_ACTIVITY_TYPE | = lv_i_activity_type | |
| I_OLD_FLEET | = lv_i_old_fleet | |
| I_OLD_ITOB | = lv_i_old_itob | |
| I_OLD_EQUI | = lv_i_old_equi | |
| I_CONVERT_FLEET | = lv_i_convert_fleet | |
| IMPORTING | ||
| E_FLEET_ACTIVITY | = lv_e_fleet_activity | |
| E_REC_FLEET_NOCNV | = lv_e_rec_fleet_nocnv | |
| CHANGING | ||
| C_REC_FLEET | = lv_c_rec_fleet | |
| C_REC_ITOB | = lv_c_rec_itob | |
| C_REC_EQUI | = lv_c_rec_equi | |
| . " ITOB_CHECK_UPDATE_FLEET | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_CHECK_UPDATE_FLEET
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 AKTYP FROM T370 INTO @DATA(ld_i_activity_type). | ||||
| "SELECT single BOOL FROM ITOB_TYPES INTO @DATA(ld_i_convert_fleet). | ||||
| DATA(ld_i_convert_fleet) | = ITOB_BOOL-TRUE. | |||
Search for further information about these or an SAP related objects