SAP BPAR_C_TIME_INTERVAL_CHECK Function Module for NOTRANSL: Prüfung von Zeitintervallen
BPAR_C_TIME_INTERVAL_CHECK is a standard bpar c time interval 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üfung von Zeitintervallen 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 bpar c time interval check FM, simply by entering the name BPAR_C_TIME_INTERVAL_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BPC0
Program Name: SAPLBPC0
Main Program: SAPLBPC0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BPAR_C_TIME_INTERVAL_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 'BPAR_C_TIME_INTERVAL_CHECK'"NOTRANSL: Prüfung von Zeitintervallen.
EXPORTING
FIRST_END = "ABAP System Field: Current Date of Application Server
FIRST_START = "ABAP System Field: Current Date of Application Server
* SAME_DAY_END_START = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* SAME_DAY_FIRST_SECOND = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* SECOND_END = '00000000' "ABAP System Field: Current Date of Application Server
* SECOND_START = '00000000' "ABAP System Field: Current Date of Application Server
EXCEPTIONS
BOTH = 1 FIRST = 2 SECOND = 3
IMPORTING Parameters details for BPAR_C_TIME_INTERVAL_CHECK
FIRST_END - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
FIRST_START - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
SAME_DAY_END_START - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SAME_DAY_FIRST_SECOND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
SECOND_END - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMDefault: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SECOND_START - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMDefault: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BOTH - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIRST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SECOND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BPAR_C_TIME_INTERVAL_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.| DATA: | ||||
| lv_both | TYPE STRING, " | |||
| lv_first_end | TYPE SY-DATUM, " | |||
| lv_first | TYPE SY, " | |||
| lv_first_start | TYPE SY-DATUM, " | |||
| lv_second | TYPE SY, " | |||
| lv_same_day_end_start | TYPE SY, " 'X' | |||
| lv_same_day_first_second | TYPE SY, " ' ' | |||
| lv_second_end | TYPE SY-DATUM, " '00000000' | |||
| lv_second_start | TYPE SY-DATUM. " '00000000' |
|   CALL FUNCTION 'BPAR_C_TIME_INTERVAL_CHECK' "NOTRANSL: Prüfung von Zeitintervallen |
| EXPORTING | ||
| FIRST_END | = lv_first_end | |
| FIRST_START | = lv_first_start | |
| SAME_DAY_END_START | = lv_same_day_end_start | |
| SAME_DAY_FIRST_SECOND | = lv_same_day_first_second | |
| SECOND_END | = lv_second_end | |
| SECOND_START | = lv_second_start | |
| EXCEPTIONS | ||
| BOTH = 1 | ||
| FIRST = 2 | ||
| SECOND = 3 | ||
| . " BPAR_C_TIME_INTERVAL_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BPAR_C_TIME_INTERVAL_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.| "SELECT single DATUM FROM SY INTO @DATA(ld_first_end). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_first_start). | ||||
| DATA(ld_same_day_end_start) | = 'X'. | |||
| DATA(ld_same_day_first_second) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_second_end). | ||||
| DATA(ld_second_end) | = '00000000'. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_second_start). | ||||
| DATA(ld_second_start) | = '00000000'. | |||
Search for further information about these or an SAP related objects