SAP TEVP_CHECK_TYPE Function Module for
TEVP_CHECK_TYPE is a standard tevp check type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 tevp check type FM, simply by entering the name TEVP_CHECK_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TEVP_TYPE_ACCESS
Program Name: SAPLTEVP_TYPE_ACCESS
Main Program: SAPLTEVP_TYPE_ACCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEVP_CHECK_TYPE 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 'TEVP_CHECK_TYPE'".
EXPORTING
IF_EVENT_TYPE_APPL = "Application: Date Type
IF_EVENT_TYPE = "Date Type
IMPORTING
EF_IS_EVENT_TYPE = "
IMPORTING Parameters details for TEVP_CHECK_TYPE
IF_EVENT_TYPE_APPL - Application: Date Type
Data type: EV_TYPE_APPLOptional: No
Call by Reference: Yes
IF_EVENT_TYPE - Date Type
Data type: EV_TYPEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for TEVP_CHECK_TYPE
EF_IS_EVENT_TYPE -
Data type: XFLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TEVP_CHECK_TYPE 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_ef_is_event_type | TYPE XFLAG, " | |||
| lv_if_event_type_appl | TYPE EV_TYPE_APPL, " | |||
| lv_if_event_type | TYPE EV_TYPE. " |
|   CALL FUNCTION 'TEVP_CHECK_TYPE' " |
| EXPORTING | ||
| IF_EVENT_TYPE_APPL | = lv_if_event_type_appl | |
| IF_EVENT_TYPE | = lv_if_event_type | |
| IMPORTING | ||
| EF_IS_EVENT_TYPE | = lv_ef_is_event_type | |
| . " TEVP_CHECK_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM TEVP_CHECK_TYPE
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