PTRA_WEB_EES_GET SAP Function module - Get express expense sheet

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

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

Pattern for FM PTRA_WEB_EES_GET - PTRA WEB EES GET

CALL FUNCTION 'PTRA_WEB_EES_GET' "Get express expense sheet
  EXPORTING
    i_employeenumber =          " bapiempl-pernr  Personnel Number
    i_period_from =             " datum         Date
    i_period_to =               " datum         Date
*   i_language = SY-LANGU       " bapitrvxxx-langu  Language Key
  IMPORTING
    et_ees =                    " ptrv_web_ees_ext_t  Express expense sheet
    e_period_from =             " datum         Date
    e_period_to =               " datum         Date
    et_return =                 " bapirettab    Table with BAPI Return Information
    .  "  PTRA_WEB_EES_GET

ABAP code example for Function Module PTRA_WEB_EES_GET

The ABAP code below is a full code listing to execute function module PTRA_WEB_EES_GET 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_et_ees  
 
 TYPE PTRV_WEB_EES_EXT_T
,
ld_e_period_from  
 
 TYPE DATUM
,
ld_e_period_to  
 
 TYPE DATUM
,
ld_et_return  
 
 TYPE BAPIRETTAB
.



DATA(ld_i_employeenumber) = Check type of data required

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

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


DATA(ld_i_language) = Check type of data required
.

CALL FUNCTION 'PTRA_WEB_EES_GET'
  EXPORTING
    i_employeenumber =           ld_i_employeenumber
    i_period_from =              ld_i_period_from
    i_period_to =                ld_i_period_to
*   i_language =                 ld_i_language
  IMPORTING
    et_ees =                     ld_et_ees
    e_period_from =              ld_e_period_from
    e_period_to =                ld_e_period_to
    et_return =                  ld_et_return
    .  "  PTRA_WEB_EES_GET

IF SY-SUBRC EQ 0.
  "All OK
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_et_ees
 
 TYPE PTRV_WEB_EES_EXT_T ,
ld_i_employeenumber
 
 TYPE BAPIEMPL-PERNR ,
ld_e_period_from
 
 TYPE DATUM ,
ld_i_period_from
 
 TYPE DATUM ,
ld_e_period_to
 
 TYPE DATUM ,
ld_i_period_to
 
 TYPE DATUM ,
ld_et_return
 
 TYPE BAPIRETTAB ,
ld_i_language
 
 TYPE BAPITRVXXX-LANGU .



ld_i_employeenumber = Check type of data required
ld_i_period_from = 'Check type of data required'.
ld_i_period_to = 'Check type of data required'.

ld_i_language = Check type of data required