SAP GET_CHECK_INTERVAL Function Module for
GET_CHECK_INTERVAL is a standard get check interval 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 get check interval FM, simply by entering the name GET_CHECK_INTERVAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCHKCORE
Program Name: SAPLFCHKCORE
Main Program: SAPLFCHKCORE
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_CHECK_INTERVAL 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 'GET_CHECK_INTERVAL'".
EXPORTING
I_CHECK = "Check number whose sequence number
I_HBKID = "Bank (key in PCEC)
I_HKTID = "Account (key in PCEC)
I_ZBUKR = "Paying company code (key in PCEC)
IMPORTING
E_PCEC = "Found entry
EXCEPTIONS
NOT_FOUND = 1 NOT_NUMERIC = 2 NOT_VALID = 3
IMPORTING Parameters details for GET_CHECK_INTERVAL
I_CHECK - Check number whose sequence number
Data type: PCEC-CHECLOptional: No
Call by Reference: No ( called with pass by value option)
I_HBKID - Bank (key in PCEC)
Data type: PCEC-HBKIDOptional: No
Call by Reference: No ( called with pass by value option)
I_HKTID - Account (key in PCEC)
Data type: PCEC-HKTIDOptional: No
Call by Reference: No ( called with pass by value option)
I_ZBUKR - Paying company code (key in PCEC)
Data type: PCEC-ZBUKROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GET_CHECK_INTERVAL
E_PCEC - Found entry
Data type: PCECOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No appropriate entry found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_NUMERIC - Numeric part of the check number i
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_VALID - Check number does not match the ba
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_CHECK_INTERVAL 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_e_pcec | TYPE PCEC, " | |||
| lv_i_check | TYPE PCEC-CHECL, " | |||
| lv_not_found | TYPE PCEC, " | |||
| lv_i_hbkid | TYPE PCEC-HBKID, " | |||
| lv_not_numeric | TYPE PCEC, " | |||
| lv_i_hktid | TYPE PCEC-HKTID, " | |||
| lv_not_valid | TYPE PCEC, " | |||
| lv_i_zbukr | TYPE PCEC-ZBUKR. " |
|   CALL FUNCTION 'GET_CHECK_INTERVAL' " |
| EXPORTING | ||
| I_CHECK | = lv_i_check | |
| I_HBKID | = lv_i_hbkid | |
| I_HKTID | = lv_i_hktid | |
| I_ZBUKR | = lv_i_zbukr | |
| IMPORTING | ||
| E_PCEC | = lv_e_pcec | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NOT_NUMERIC = 2 | ||
| NOT_VALID = 3 | ||
| . " GET_CHECK_INTERVAL | ||
ABAP code using 7.40 inline data declarations to call FM GET_CHECK_INTERVAL
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 CHECL FROM PCEC INTO @DATA(ld_i_check). | ||||
| "SELECT single HBKID FROM PCEC INTO @DATA(ld_i_hbkid). | ||||
| "SELECT single HKTID FROM PCEC INTO @DATA(ld_i_hktid). | ||||
| "SELECT single ZBUKR FROM PCEC INTO @DATA(ld_i_zbukr). | ||||
Search for further information about these or an SAP related objects