DATE_GET_PERIOD SAP Function module

DATE_GET_PERIOD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DATE_GET_PERIOD into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MRP4
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM DATE_GET_PERIOD - DATE GET PERIOD

CALL FUNCTION 'DATE_GET_PERIOD' "
  EXPORTING
    iv_date =                   " d
    iv_periodid =               " dqup-abper
*   iv_periods = 1              " i
*   iv_mrppp =                  " t439i-mrppp
*   iv_werks =                  " t439i-werks
*   iv_periv =                  " t009-periv
  IMPORTING
    ev_periodstart =            " d
    ev_periodend =              " d
  EXCEPTIONS
    ERROR = 1                   "
    .  "  DATE_GET_PERIOD

ABAP code example for Function Module DATE_GET_PERIOD

The ABAP code below is a full code listing to execute function module DATE_GET_PERIOD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_periodstart  
 
 TYPE D
,
ld_ev_periodend  
 
 TYPE D
.


DATA(ld_iv_date) = 'Check type of data required'.


DATA(ld_iv_periodid) = some text here

DATA(ld_iv_periods) = 'Check type of data required'.
 

SELECT single MRPPP 
  FROM T439I 
  INTO @DATA(ld_iv_mrppp).

 

SELECT single WERKS 
  FROM T439I 
  INTO @DATA(ld_iv_werks).

 

SELECT single PERIV 
  FROM T009 
  INTO @DATA(ld_iv_periv).

.

CALL FUNCTION 'DATE_GET_PERIOD'
  EXPORTING
    iv_date =                    ld_iv_date
    iv_periodid =                ld_iv_periodid
*   iv_periods =                 ld_iv_periods
*   iv_mrppp =                   ld_iv_mrppp
*   iv_werks =                   ld_iv_werks
*   iv_periv =                   ld_iv_periv
  IMPORTING
    ev_periodstart =             ld_ev_periodstart
    ev_periodend =               ld_ev_periodend
  EXCEPTIONS
    ERROR =                      1
    .  "  DATE_GET_PERIOD

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_periodstart
 
 TYPE D ,
ld_iv_date
 
 TYPE D ,
ld_ev_periodend
 
 TYPE D ,
ld_iv_periodid
 
 TYPE DQUP-ABPER ,
ld_iv_periods
 
 TYPE I ,
ld_iv_mrppp
 
 TYPE T439I-MRPPP ,
ld_iv_werks
 
 TYPE T439I-WERKS ,
ld_iv_periv
 
 TYPE T009-PERIV .


ld_iv_date = 'Check type of data required'.

ld_iv_periodid = some text here
ld_iv_periods = 'Check type of data required'.

SELECT single MRPPP 
  FROM T439I 
  INTO ld_iv_mrppp.


SELECT single WERKS 
  FROM T439I 
  INTO ld_iv_werks.


SELECT single PERIV 
  FROM T009 
  INTO ld_iv_periv.