SAP FI_PERIOD_CHECK Function Module for

Search SAP Function Modules

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

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

Function FI_PERIOD_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 'FI_PERIOD_CHECK'"
  EXPORTING
*  I_BUKRS = ' ' "Company code
*  I_LDGRP =  "Ledger Group
*  I_OPVAR = ' ' "Posting period variant
   I_GJAHR =  "Fiscal year
   I_KOART =  "Account type
*  I_KONTO = ' ' "Account number in general ledger
   I_MONAT =  "Period
*  I_SPERI =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_RLDNR =  "
*  I_GLVOR = 'RFBU' "Business Transaction

 IMPORTING
   E_OPER =  "First Posting Period Allowed (in Interval 1)

EXCEPTIONS
   ERROR_PERIOD = 1    ERROR_PERIOD_ACC = 2    INVALID_INPUT = 3 

.

IMPORTING Parameters details for FI_PERIOD_CHECK

I_BUKRS - Company code

Data type: T001-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LDGRP - Ledger Group

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

I_OPVAR - Posting period variant

Data type: T001-OPVAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GJAHR - Fiscal year

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

I_KOART - Account type

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

I_KONTO - Account number in general ledger

Data type: T001B-VKONT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MONAT - Period

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

I_SPERI - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

I_RLDNR -

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

I_GLVOR - Business Transaction

Data type: GLVOR
Default: 'RFBU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FI_PERIOD_CHECK

E_OPER - First Posting Period Allowed (in Interval 1)

Data type: T001B-FRPE1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_PERIOD - Period has not been opened

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

ERROR_PERIOD_ACC - Period has not been opened for G/L account

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

INVALID_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FI_PERIOD_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.

ABAP code using 7.40 inline data declarations to call FM FI_PERIOD_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.

Search for further information about these or an SAP related objects