SAP ITOB_TABSCREENS_GET Function Module for NOTRANSL: Get tabstrip customizing + adapt TABSTRIP_TAB
ITOB_TABSCREENS_GET is a standard itob tabscreens get 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: Get tabstrip customizing + adapt TABSTRIP_TAB 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 tabscreens get FM, simply by entering the name ITOB_TABSCREENS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITO0
Program Name: SAPLITO0
Main Program: SAPLITO0
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ITOB_TABSCREENS_GET 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_TABSCREENS_GET'"NOTRANSL: Get tabstrip customizing + adapt TABSTRIP_TAB.
EXPORTING
I_OBJECT_TYPE = "Technical object types in plant maintenance
* I_REC_T370F = "Functional Location Category
* I_REC_T370T = "Equipment categories
* I_REC_T370FLT = "Fleet Types
* I_LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* I_REC_EQUI = "Equipment master data
* I_STANDARD_VIEW = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
E_CHANGED = "DE-EN-LANG-SWITCH-NO-TRANSLATION
TABLES
T_TABSTRIP_TAB = "DE-EN-LANG-SWITCH-NO-TRANSLATION
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_SAPLITO0_001 Customer Include ITO0: Data Import (Initiator => Include)
EXIT_SAPLITO0_002 Customer Include ITO0: Data Export (Include => Caller)
EXIT_SAPLITO0_003 Customer Include Additional Fleet Data: Data Import (Caller => Include)
EXIT_SAPLITO0_004 Customer Include Additional Fleet Data: Data Export (Include => CAller)
EXIT_SAPLITO0_005 Customer Exit Fleet Identification Data: Checks
IMPORTING Parameters details for ITOB_TABSCREENS_GET
I_OBJECT_TYPE - Technical object types in plant maintenance
Data type: ITOBTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_REC_T370F - Functional Location Category
Data type: T370FOptional: Yes
Call by Reference: Yes
I_REC_T370T - Equipment categories
Data type: T370TOptional: Yes
Call by Reference: Yes
I_REC_T370FLT - Fleet Types
Data type: T370FLTOptional: Yes
Call by Reference: Yes
I_LANGU - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REC_EQUI - Equipment master data
Data type: EQUIOptional: Yes
Call by Reference: Yes
I_STANDARD_VIEW - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ITOB_TYPES-BOOLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ITOB_TABSCREENS_GET
E_CHANGED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ITOB_TYPES-BOOLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ITOB_TABSCREENS_GET
T_TABSTRIP_TAB - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ITO0T_TABSTRIP_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ITOB_TABSCREENS_GET 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_e_changed | TYPE ITOB_TYPES-BOOL, " | |||
| lv_i_object_type | TYPE ITOBTYP, " | |||
| lt_t_tabstrip_tab | TYPE STANDARD TABLE OF ITO0T_TABSTRIP_TAB, " | |||
| lv_i_rec_t370f | TYPE T370F, " | |||
| lv_i_rec_t370t | TYPE T370T, " | |||
| lv_i_rec_t370flt | TYPE T370FLT, " | |||
| lv_i_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_i_rec_equi | TYPE EQUI, " | |||
| lv_i_standard_view | TYPE ITOB_TYPES-BOOL. " |
|   CALL FUNCTION 'ITOB_TABSCREENS_GET' "NOTRANSL: Get tabstrip customizing + adapt TABSTRIP_TAB |
| EXPORTING | ||
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_REC_T370F | = lv_i_rec_t370f | |
| I_REC_T370T | = lv_i_rec_t370t | |
| I_REC_T370FLT | = lv_i_rec_t370flt | |
| I_LANGU | = lv_i_langu | |
| I_REC_EQUI | = lv_i_rec_equi | |
| I_STANDARD_VIEW | = lv_i_standard_view | |
| IMPORTING | ||
| E_CHANGED | = lv_e_changed | |
| TABLES | ||
| T_TABSTRIP_TAB | = lt_t_tabstrip_tab | |
| . " ITOB_TABSCREENS_GET | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_TABSCREENS_GET
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 BOOL FROM ITOB_TYPES INTO @DATA(ld_e_changed). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_langu). | ||||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| "SELECT single BOOL FROM ITOB_TYPES INTO @DATA(ld_i_standard_view). | ||||
Search for further information about these or an SAP related objects