SAP DATE_TO_PERIOD_CONVERT Function Module for
DATE_TO_PERIOD_CONVERT is a standard date to period convert 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 date to period convert FM, simply by entering the name DATE_TO_PERIOD_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADAT
Program Name: SAPLADAT
Main Program: SAPLADAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function DATE_TO_PERIOD_CONVERT 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_TO_PERIOD_CONVERT'".
EXPORTING
I_DATE = "Posting date
* I_MONMIT = 00 "
I_PERIV = "Period version
IMPORTING
E_BUPER = "determined posting period
E_GJAHR = "determined fiscal year
EXCEPTIONS
INPUT_FALSE = 1 T009_NOTFOUND = 2 T009B_NOTFOUND = 3
IMPORTING Parameters details for DATE_TO_PERIOD_CONVERT
I_DATE - Posting date
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_MONMIT -
Data type: GJVAR-MONMITDefault: 00
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PERIV - Period version
Data type: T009B-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DATE_TO_PERIOD_CONVERT
E_BUPER - determined posting period
Data type: T009B-POPEROptional: No
Call by Reference: No ( called with pass by value option)
E_GJAHR - determined fiscal year
Data type: T009B-BDATJOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_FALSE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
T009_NOTFOUND - Version period determination not i
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
T009B_NOTFOUND - Version period determination not m
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DATE_TO_PERIOD_CONVERT 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_date | TYPE SY-DATUM, " | |||
lv_e_buper | TYPE T009B-POPER, " | |||
lv_input_false | TYPE T009B, " | |||
lv_e_gjahr | TYPE T009B-BDATJ, " | |||
lv_i_monmit | TYPE GJVAR-MONMIT, " 00 | |||
lv_t009_notfound | TYPE GJVAR, " | |||
lv_i_periv | TYPE T009B-PERIV, " | |||
lv_t009b_notfound | TYPE T009B. " |
  CALL FUNCTION 'DATE_TO_PERIOD_CONVERT' " |
EXPORTING | ||
I_DATE | = lv_i_date | |
I_MONMIT | = lv_i_monmit | |
I_PERIV | = lv_i_periv | |
IMPORTING | ||
E_BUPER | = lv_e_buper | |
E_GJAHR | = lv_e_gjahr | |
EXCEPTIONS | ||
INPUT_FALSE = 1 | ||
T009_NOTFOUND = 2 | ||
T009B_NOTFOUND = 3 | ||
. " DATE_TO_PERIOD_CONVERT |
ABAP code using 7.40 inline data declarations to call FM DATE_TO_PERIOD_CONVERT
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_i_date). | ||||
"SELECT single POPER FROM T009B INTO @DATA(ld_e_buper). | ||||
"SELECT single BDATJ FROM T009B INTO @DATA(ld_e_gjahr). | ||||
"SELECT single MONMIT FROM GJVAR INTO @DATA(ld_i_monmit). | ||||
DATA(ld_i_monmit) | = 00. | |||
"SELECT single PERIV FROM T009B INTO @DATA(ld_i_periv). | ||||
Search for further information about these or an SAP related objects