WRF_POTB_GET_PERIOD SAP Function module - Read OTB Period for Schedule Record

WRF_POTB_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 WRF_POTB_GET_PERIOD into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM WRF_POTB_GET_PERIOD - WRF POTB GET PERIOD

CALL FUNCTION 'WRF_POTB_GET_PERIOD' "Read OTB Period for Schedule Record
* EXPORTING
*   i_date_from =               " wrf_budg_date_from  Start Date of a Planning Period
*   i_date_to =                 " wrf_budg_date_to  End Date of a Planning Period
*   i_total_in_period =         " wrf_potb_total_in_period  Export Period Includes Complete Import Period
  IMPORTING
    e_date_from =               " wrf_budg_date_from  Start Date of a Planning Period
    e_date_to =                 " wrf_budg_date_to  End Date of a Planning Period
  EXCEPTIONS
    ERROR = 1                   "               schwerer Fehler mit entspr. Fehlermeldung
    .  "  WRF_POTB_GET_PERIOD

ABAP code example for Function Module WRF_POTB_GET_PERIOD

The ABAP code below is a full code listing to execute function module WRF_POTB_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_e_date_from  
 
 TYPE WRF_BUDG_DATE_FROM
,
ld_e_date_to  
 
 TYPE WRF_BUDG_DATE_TO
.


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

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

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

CALL FUNCTION 'WRF_POTB_GET_PERIOD'
* EXPORTING
*   i_date_from =                ld_i_date_from
*   i_date_to =                  ld_i_date_to
*   i_total_in_period =          ld_i_total_in_period
  IMPORTING
    e_date_from =                ld_e_date_from
    e_date_to =                  ld_e_date_to
  EXCEPTIONS
    ERROR =                      1
    .  "  WRF_POTB_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_e_date_from
 
 TYPE WRF_BUDG_DATE_FROM ,
ld_i_date_from
 
 TYPE WRF_BUDG_DATE_FROM ,
ld_e_date_to
 
 TYPE WRF_BUDG_DATE_TO ,
ld_i_date_to
 
 TYPE WRF_BUDG_DATE_TO ,
ld_i_total_in_period
 
 TYPE WRF_POTB_TOTAL_IN_PERIOD .


ld_i_date_from = 'Check type of data required'.
ld_i_date_to = 'Check type of data required'.
ld_i_total_in_period = 'Check type of data required'.