SAP ITOB_OBJECT_READ Function Module for NOTRANSL: ITOB Puffer API: Lesen Technischer Objekte
ITOB_OBJECT_READ is a standard itob object read 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: ITOB Puffer API: Lesen Technischer Objekte 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 object read FM, simply by entering the name ITOB_OBJECT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITO3
Program Name: SAPLITO3
Main Program: SAPLITO3
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ITOB_OBJECT_READ 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_OBJECT_READ'"NOTRANSL: ITOB Puffer API: Lesen Technischer Objekte.
EXPORTING
I_HANDLE = "Handle for the ITOB buffer
I_ITOB_FLAGS = "Read buffer control info (Type of ITOB object)
* I_LOCK_ONLY = "No read, just global lock on all records
* I_SINGLE_MODE = "
* I_AUTH_TCODE = "
* I_PARMS_TAB = "
IMPORTING
E_COUNT_NOT_READ = "Number of objects that were not read
E_ITOB_TAB = "Read buffer table (Object/control data)
CHANGING
C_OBJECT_TAB = "Table with data of the technical objects
* C_ERR_TAB = "
EXCEPTIONS
NOT_SUCCESSFUL = 1
IMPORTING Parameters details for ITOB_OBJECT_READ
I_HANDLE - Handle for the ITOB buffer
Data type: ITOB_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
I_ITOB_FLAGS - Read buffer control info (Type of ITOB object)
Data type: ITOB_FLAGS_RECOptional: No
Call by Reference: No ( called with pass by value option)
I_LOCK_ONLY - No read, just global lock on all records
Data type: ITOB_TYPES-INDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SINGLE_MODE -
Data type: ITOB_TYPES-BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AUTH_TCODE -
Data type: SY-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARMS_TAB -
Data type: ITOB_PARMS_TABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ITOB_OBJECT_READ
E_COUNT_NOT_READ - Number of objects that were not read
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
E_ITOB_TAB - Read buffer table (Object/control data)
Data type: ITOB_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for ITOB_OBJECT_READ
C_OBJECT_TAB - Table with data of the technical objects
Data type: ITOB_OBJECT_TABOptional: No
Call by Reference: Yes
C_ERR_TAB -
Data type: ITOB_READ_INFO_TABOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_SUCCESSFUL - Error when reading technical objects
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ITOB_OBJECT_READ 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_i_handle | TYPE ITOB_HANDLE, " | |||
| lv_c_object_tab | TYPE ITOB_OBJECT_TAB, " | |||
| lv_not_successful | TYPE ITOB_OBJECT_TAB, " | |||
| lv_e_count_not_read | TYPE I, " | |||
| lv_c_err_tab | TYPE ITOB_READ_INFO_TAB, " | |||
| lv_e_itob_tab | TYPE ITOB_TAB, " | |||
| lv_i_itob_flags | TYPE ITOB_FLAGS_REC, " | |||
| lv_i_lock_only | TYPE ITOB_TYPES-IND, " | |||
| lv_i_single_mode | TYPE ITOB_TYPES-BOOL, " | |||
| lv_i_auth_tcode | TYPE SY-TCODE, " | |||
| lv_i_parms_tab | TYPE ITOB_PARMS_TAB. " |
|   CALL FUNCTION 'ITOB_OBJECT_READ' "NOTRANSL: ITOB Puffer API: Lesen Technischer Objekte |
| EXPORTING | ||
| I_HANDLE | = lv_i_handle | |
| I_ITOB_FLAGS | = lv_i_itob_flags | |
| I_LOCK_ONLY | = lv_i_lock_only | |
| I_SINGLE_MODE | = lv_i_single_mode | |
| I_AUTH_TCODE | = lv_i_auth_tcode | |
| I_PARMS_TAB | = lv_i_parms_tab | |
| IMPORTING | ||
| E_COUNT_NOT_READ | = lv_e_count_not_read | |
| E_ITOB_TAB | = lv_e_itob_tab | |
| CHANGING | ||
| C_OBJECT_TAB | = lv_c_object_tab | |
| C_ERR_TAB | = lv_c_err_tab | |
| EXCEPTIONS | ||
| NOT_SUCCESSFUL = 1 | ||
| . " ITOB_OBJECT_READ | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_OBJECT_READ
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 IND FROM ITOB_TYPES INTO @DATA(ld_i_lock_only). | ||||
| "SELECT single BOOL FROM ITOB_TYPES INTO @DATA(ld_i_single_mode). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_i_auth_tcode). | ||||
Search for further information about these or an SAP related objects