SAP BUR_CHECK_VALID_DATES Function Module for









BUR_CHECK_VALID_DATES is a standard bur check valid dates 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 bur check valid dates FM, simply by entering the name BUR_CHECK_VALID_DATES into the relevant SAP transaction such as SE37 or SE38.

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



Function BUR_CHECK_VALID_DATES 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 'BUR_CHECK_VALID_DATES'"
EXPORTING
I_DATE_FROM = "Valid From
I_DATE_TO = "Valid To

EXCEPTIONS
DATE_NOT_ALLOWED = 1
.



IMPORTING Parameters details for BUR_CHECK_VALID_DATES

I_DATE_FROM - Valid From

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

I_DATE_TO - Valid To

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

EXCEPTIONS details

DATE_NOT_ALLOWED - Invalid date

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUR_CHECK_VALID_DATES 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_i_date_from  TYPE BUT050-DATE_FROM, "   
lv_date_not_allowed  TYPE BUT050, "   
lv_i_date_to  TYPE BUT050-DATE_TO. "   

  CALL FUNCTION 'BUR_CHECK_VALID_DATES'  "
    EXPORTING
         I_DATE_FROM = lv_i_date_from
         I_DATE_TO = lv_i_date_to
    EXCEPTIONS
        DATE_NOT_ALLOWED = 1
. " BUR_CHECK_VALID_DATES




ABAP code using 7.40 inline data declarations to call FM BUR_CHECK_VALID_DATES

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 DATE_FROM FROM BUT050 INTO @DATA(ld_i_date_from).
 
 
"SELECT single DATE_TO FROM BUT050 INTO @DATA(ld_i_date_to).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!