SAP TB_FACTORYCALENDAR_CHECK Function Module for Check for Existence of Factory Calendar









TB_FACTORYCALENDAR_CHECK is a standard tb factorycalendar 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 Check for Existence of Factory Calendar 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 tb factorycalendar check FM, simply by entering the name TB_FACTORYCALENDAR_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function TB_FACTORYCALENDAR_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 'TB_FACTORYCALENDAR_CHECK'"Check for Existence of Factory Calendar
EXPORTING
I_SKALID = "Calendar ID

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for TB_FACTORYCALENDAR_CHECK

I_SKALID - Calendar ID

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

EXCEPTIONS details

NOT_FOUND - Does Not Exist

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

Copy and paste ABAP code example for TB_FACTORYCALENDAR_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_i_skalid  TYPE TFACD-IDENT, "   
lv_not_found  TYPE TFACD. "   

  CALL FUNCTION 'TB_FACTORYCALENDAR_CHECK'  "Check for Existence of Factory Calendar
    EXPORTING
         I_SKALID = lv_i_skalid
    EXCEPTIONS
        NOT_FOUND = 1
. " TB_FACTORYCALENDAR_CHECK




ABAP code using 7.40 inline data declarations to call FM TB_FACTORYCALENDAR_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 IDENT FROM TFACD INTO @DATA(ld_i_skalid).
 
 


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!