SAP ITOB_CHECK_PARTNER Function Module for NOTRANSL: L1: Partner

Search SAP Function Modules

ITOB_CHECK_PARTNER is a standard itob check partner 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: Partner 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 partner FM, simply by entering the name ITOB_CHECK_PARTNER 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_PARTNER 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_PARTNER'"NOTRANSL: L1: Partner
  EXPORTING
   KUNDE =  "Partner
   PARK =  "Partner Function for Customer in Equipment Usage Period
*  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

EXCEPTIONS
   EMPTY_KEY = 1    APPLICATION_ERROR = 2 

.

IMPORTING Parameters details for ITOB_CHECK_PARTNER

KUNDE - Partner

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

PARK - Partner Function for Customer in Equipment Usage Period

Data type: T370T-PARK3
Optional: No
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)

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)

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_PARTNER 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.

ABAP code using 7.40 inline data declarations to call FM ITOB_CHECK_PARTNER

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.

Search for further information about these or an SAP related objects