SAP ILART_CHECK Function Module for NOTRANSL: Prüfen der IH-Leistungsart (ggf. in Abhängigkeit von der Auftrag

Search SAP Function Modules

ILART_CHECK is a standard ilart check 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: Prüfen der IH-Leistungsart (ggf. in Abhängigkeit von der Auftrag 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 ilart check FM, simply by entering the name ILART_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: INST
Program Name: SAPLINST
Main Program:
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ILART_CHECK 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 'ILART_CHECK'"NOTRANSL: Prüfen der IH-Leistungsart (ggf. in Abhängigkeit von der Auftrag
  EXPORTING
*  AUART = ' ' "Order type (for combination check)
   ILART =  "Maintenance activity type
*  MTYPE = 'E' "

 IMPORTING
   T353I_T_WA =  "T353I_T (name of the maintenance activity type)
   T353I_WA =  "T353I

EXCEPTIONS
   AUART_NOT_DEFINED = 1    ILART_AUART_WRONG = 2    ILART_NOT_DEFINED = 3 

.

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_SAPLINST_001 111

IMPORTING Parameters details for ILART_CHECK

AUART - Order type (for combination check)

Data type: T350-AUART
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ILART - Maintenance activity type

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

MTYPE -

Data type: SY-MSGTY
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ILART_CHECK

T353I_T_WA - T353I_T (name of the maintenance activity type)

Data type: T353I_T
Optional: No
Call by Reference: No ( called with pass by value option)

T353I_WA - T353I

Data type: T353I
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

AUART_NOT_DEFINED - Order type not defined (T350)

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

ILART_AUART_WRONG - Combination is invalid (T350I)

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

ILART_NOT_DEFINED - Maintenance activity type is not defined in T353I

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

Copy and paste ABAP code example for ILART_CHECK 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 ILART_CHECK

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