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

Function FOT_CHECK_PERIOD 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 'FOT_CHECK_PERIOD'".
EXPORTING
ID_TBUKRS = "Dominant Enterprise/Company Code
ID_BUKRS = "Company Code
ID_PERIV = "
ID_DECL_CTRY = "
ID_DECL_TYPE = "
IS_DATE_PARAM = "
* ID_VATDT_LOW = "Tax Reporting Date
* ID_VATDT_HIGH = "Tax Reporting Date
IMPORTING
ED_DECL_YEAR = "
ED_DECL_PER = "Reporting Period Electronic Data Transmission
ED_PER_TYPE = "
IMPORTING Parameters details for FOT_CHECK_PERIOD
ID_TBUKRS - Dominant Enterprise/Company Code
Data type: FOT_TBUKRSOptional: No
Call by Reference: No ( called with pass by value option)
ID_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
ID_PERIV -
Data type: PERIVOptional: No
Call by Reference: No ( called with pass by value option)
ID_DECL_CTRY -
Data type: FOT_DCCTRYOptional: No
Call by Reference: No ( called with pass by value option)
ID_DECL_TYPE -
Data type: FOT_DCLTYPOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATE_PARAM -
Data type: FOT_S_DATE_PARAMOptional: No
Call by Reference: No ( called with pass by value option)
ID_VATDT_LOW - Tax Reporting Date
Data type: VATDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_VATDT_HIGH - Tax Reporting Date
Data type: VATDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FOT_CHECK_PERIOD
ED_DECL_YEAR -
Data type: FOT_DEYEAROptional: No
Call by Reference: No ( called with pass by value option)
ED_DECL_PER - Reporting Period Electronic Data Transmission
Data type: FOT_DCLPEROptional: No
Call by Reference: No ( called with pass by value option)
ED_PER_TYPE -
Data type: FOT_PERTYPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FOT_CHECK_PERIOD 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_id_tbukrs | TYPE FOT_TBUKRS, " | |||
| lv_ed_decl_year | TYPE FOT_DEYEAR, " | |||
| lv_id_bukrs | TYPE BUKRS, " | |||
| lv_ed_decl_per | TYPE FOT_DCLPER, " | |||
| lv_id_periv | TYPE PERIV, " | |||
| lv_ed_per_type | TYPE FOT_PERTYP, " | |||
| lv_id_decl_ctry | TYPE FOT_DCCTRY, " | |||
| lv_id_decl_type | TYPE FOT_DCLTYP, " | |||
| lv_is_date_param | TYPE FOT_S_DATE_PARAM, " | |||
| lv_id_vatdt_low | TYPE VATDATE, " | |||
| lv_id_vatdt_high | TYPE VATDATE. " |
|   CALL FUNCTION 'FOT_CHECK_PERIOD' " |
| EXPORTING | ||
| ID_TBUKRS | = lv_id_tbukrs | |
| ID_BUKRS | = lv_id_bukrs | |
| ID_PERIV | = lv_id_periv | |
| ID_DECL_CTRY | = lv_id_decl_ctry | |
| ID_DECL_TYPE | = lv_id_decl_type | |
| IS_DATE_PARAM | = lv_is_date_param | |
| ID_VATDT_LOW | = lv_id_vatdt_low | |
| ID_VATDT_HIGH | = lv_id_vatdt_high | |
| IMPORTING | ||
| ED_DECL_YEAR | = lv_ed_decl_year | |
| ED_DECL_PER | = lv_ed_decl_per | |
| ED_PER_TYPE | = lv_ed_per_type | |
| . " FOT_CHECK_PERIOD | ||
ABAP code using 7.40 inline data declarations to call FM FOT_CHECK_PERIOD
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.Search for further information about these or an SAP related objects