SAP DATE_CHECK_WORKINGDAY_MULTIPLE Function Module for Working Day Check for Date for Any Number of Calendars









DATE_CHECK_WORKINGDAY_MULTIPLE is a standard date check workingday multiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Working Day Check for Date for Any Number of Calendars 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 date check workingday multiple FM, simply by entering the name DATE_CHECK_WORKINGDAY_MULTIPLE into the relevant SAP transaction such as SE37 or SE38.

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



Function DATE_CHECK_WORKINGDAY_MULTIPLE 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 'DATE_CHECK_WORKINGDAY_MULTIPLE'"Working Day Check for Date for Any Number of Calendars
EXPORTING
DATE = "Date to Be Checked
MESSAGE_TYPE = "Typ der Meldung, falls Datum kein Geschäftstag

TABLES
FACTORY_CALENDARS = "Factory Calendar Identification

EXCEPTIONS
DATE_AFTER_RANGE = 1 DATE_BEFORE_RANGE = 2 DATE_INVALID = 3 DATE_NO_WORKINGDAY = 4 FACTORY_CALENDAR_NOT_FOUND = 5 MESSAGE_TYPE_INVALID = 6
.



IMPORTING Parameters details for DATE_CHECK_WORKINGDAY_MULTIPLE

DATE - Date to Be Checked

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

MESSAGE_TYPE - Typ der Meldung, falls Datum kein Geschäftstag

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

TABLES Parameters details for DATE_CHECK_WORKINGDAY_MULTIPLE

FACTORY_CALENDARS - Factory Calendar Identification

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

EXCEPTIONS details

DATE_AFTER_RANGE - Date Is After End of Factory Calendar

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

DATE_BEFORE_RANGE - Date Is Before Start of Factory Calendar

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

DATE_INVALID - Date is invalid

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

DATE_NO_WORKINGDAY - Datum ist kein Geschäftstag

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

FACTORY_CALENDAR_NOT_FOUND - Factory Calendar Unknown

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

MESSAGE_TYPE_INVALID - Invalid message type

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

Copy and paste ABAP code example for DATE_CHECK_WORKINGDAY_MULTIPLE 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_date  TYPE SY-DATUM, "   
lv_date_after_range  TYPE SY, "   
lt_factory_calendars  TYPE STANDARD TABLE OF VTBFCAL, "   
lv_message_type  TYPE SY-MSGTY, "   
lv_date_before_range  TYPE SY, "   
lv_date_invalid  TYPE SY, "   
lv_date_no_workingday  TYPE SY, "   
lv_factory_calendar_not_found  TYPE SY, "   
lv_message_type_invalid  TYPE SY. "   

  CALL FUNCTION 'DATE_CHECK_WORKINGDAY_MULTIPLE'  "Working Day Check for Date for Any Number of Calendars
    EXPORTING
         DATE = lv_date
         MESSAGE_TYPE = lv_message_type
    TABLES
         FACTORY_CALENDARS = lt_factory_calendars
    EXCEPTIONS
        DATE_AFTER_RANGE = 1
        DATE_BEFORE_RANGE = 2
        DATE_INVALID = 3
        DATE_NO_WORKINGDAY = 4
        FACTORY_CALENDAR_NOT_FOUND = 5
        MESSAGE_TYPE_INVALID = 6
. " DATE_CHECK_WORKINGDAY_MULTIPLE




ABAP code using 7.40 inline data declarations to call FM DATE_CHECK_WORKINGDAY_MULTIPLE

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_date).
 
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_message_type).
 
 
 
 
 
 


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!