SAP PERIOD_DAY_DETERMINE Function Module for









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

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



Function PERIOD_DAY_DETERMINE 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 'PERIOD_DAY_DETERMINE'"
EXPORTING
I_GJAHR = "Fiscal year
I_MONAT = "Posting period
I_PERIV = "Period version

IMPORTING
E_FDAY = "First day of period
E_LDAY = "Last Day of Period
E_SPERIOD = "Special period indicator

EXCEPTIONS
ERROR_PERIOD = 1 ERROR_PERIOD_VERSION = 2 FIRSTDAY_NOT_DEFINED = 3 PERIOD_NOT_DEFINED = 4 YEAR_INVALID = 5
.



IMPORTING Parameters details for PERIOD_DAY_DETERMINE

I_GJAHR - Fiscal year

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

I_MONAT - Posting period

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

I_PERIV - Period version

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

EXPORTING Parameters details for PERIOD_DAY_DETERMINE

E_FDAY - First day of period

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

E_LDAY - Last Day of Period

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

E_SPERIOD - Special period indicator

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

EXCEPTIONS details

ERROR_PERIOD - Period not Valid

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

ERROR_PERIOD_VERSION - Period version not defined in T009

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

FIRSTDAY_NOT_DEFINED - Previous period does not exist

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

PERIOD_NOT_DEFINED - Period not defined in T009B

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

YEAR_INVALID -

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

Copy and paste ABAP code example for PERIOD_DAY_DETERMINE 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_e_fday  TYPE BKPF-BUDAT, "   
lv_i_gjahr  TYPE BKPF-GJAHR, "   
lv_error_period  TYPE BKPF, "   
lv_e_lday  TYPE BKPF-BUDAT, "   
lv_i_monat  TYPE BKPF-MONAT, "   
lv_error_period_version  TYPE BKPF, "   
lv_i_periv  TYPE T001-PERIV, "   
lv_e_speriod  TYPE BKPF-BSTAT, "   
lv_firstday_not_defined  TYPE BKPF, "   
lv_period_not_defined  TYPE BKPF, "   
lv_year_invalid  TYPE BKPF. "   

  CALL FUNCTION 'PERIOD_DAY_DETERMINE'  "
    EXPORTING
         I_GJAHR = lv_i_gjahr
         I_MONAT = lv_i_monat
         I_PERIV = lv_i_periv
    IMPORTING
         E_FDAY = lv_e_fday
         E_LDAY = lv_e_lday
         E_SPERIOD = lv_e_speriod
    EXCEPTIONS
        ERROR_PERIOD = 1
        ERROR_PERIOD_VERSION = 2
        FIRSTDAY_NOT_DEFINED = 3
        PERIOD_NOT_DEFINED = 4
        YEAR_INVALID = 5
. " PERIOD_DAY_DETERMINE




ABAP code using 7.40 inline data declarations to call FM PERIOD_DAY_DETERMINE

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 BUDAT FROM BKPF INTO @DATA(ld_e_fday).
 
"SELECT single GJAHR FROM BKPF INTO @DATA(ld_i_gjahr).
 
 
"SELECT single BUDAT FROM BKPF INTO @DATA(ld_e_lday).
 
"SELECT single MONAT FROM BKPF INTO @DATA(ld_i_monat).
 
 
"SELECT single PERIV FROM T001 INTO @DATA(ld_i_periv).
 
"SELECT single BSTAT FROM BKPF INTO @DATA(ld_e_speriod).
 
 
 
 


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!