SAP ITOB_CHECK_CUSTOMER Function Module for NOTRANSL: L1: Kunde
ITOB_CHECK_CUSTOMER is a standard itob check customer 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: Kunde 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 customer FM, simply by entering the name ITOB_CHECK_CUSTOMER 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_CUSTOMER 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_CUSTOMER'"NOTRANSL: L1: Kunde.
EXPORTING
KUNDE = "Customer number
* 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
* X_MESS_TYPE = 'E' "ABAP System Field: Message Type
IMPORTING
KNA1_EXP = "General Data in Customer Master
EXCEPTIONS
EMPTY_KEY = 1 APPLICATION_ERROR = 2
IMPORTING Parameters details for ITOB_CHECK_CUSTOMER
KUNDE - Customer number
Data type: ITOB-KUND1Optional: No
Call by Reference: No ( called with pass by value option)
DIALOG_MODE - ABAP System Field: Batch Input Processing Active
Data type: SY-BINPTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG_CURSOR - Field name
Data type: DD03D-FIELDNAMEDefault: 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-STEPLOptional: Yes
Call by Reference: No ( called with pass by value option)
INIT_MESSAGE_DATA - ABAP System Field: Batch Input Processing Active
Data type: SY-BINPTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MESS_TYPE - ABAP System Field: Message Type
Data type: SY-MSGTYDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ITOB_CHECK_CUSTOMER
KNA1_EXP - General Data in Customer Master
Data type: KNA1Optional: 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_CHECK_CUSTOMER 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_kunde | TYPE ITOB-KUND1, " | |||
| lv_kna1_exp | TYPE KNA1, " | |||
| lv_empty_key | TYPE KNA1, " | |||
| lv_dialog_mode | TYPE SY-BINPT, " 'X' | |||
| lv_application_error | TYPE SY, " | |||
| 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_CHECK_CUSTOMER' "NOTRANSL: L1: Kunde |
| EXPORTING | ||
| KUNDE | = lv_kunde | |
| 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 | ||
| KNA1_EXP | = lv_kna1_exp | |
| EXCEPTIONS | ||
| EMPTY_KEY = 1 | ||
| APPLICATION_ERROR = 2 | ||
| . " ITOB_CHECK_CUSTOMER | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_CHECK_CUSTOMER
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 KUND1 FROM ITOB INTO @DATA(ld_kunde). | ||||
| "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