PTRM_WEB_REQUEST_SERVICE_GET SAP Function module

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

Associated Function Group: PTRM_WEB_REQUEST
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM PTRM_WEB_REQUEST_SERVICE_GET - PTRM WEB REQUEST SERVICE GET

CALL FUNCTION 'PTRM_WEB_REQUEST_SERVICE_GET' "
  EXPORTING
    i_employeenumber =          " bapiempl-pernr  Personnel Number
*   i_tripnumber =              " bapitrip-tripno  Trip Number
*   i_language =                " bapitrvxxx-langu  Language Key
    i_trip_begin =              " begin_of_trip  Start of Leg of Trip
    i_trip_end =                " end_of_trip   End of Leg of Trip
  IMPORTING
    e_document_delivery =       " ftps_web_req_doc_delivery_out  Delivery of Requested Travel Service Documents -> Web UI
    e_next_request_nr =         " request_nr    Request number (sequential number
  TABLES
    et_service =                " ftps_web_request_service_t  Table Type for Travel Service Requests - Web UI
    et_other_service_cust =     " ftps_other_services_t  Table Type Customizing Other Travel Services
    et_return =                 " bapirettab    Table with BAPI Return Information
    .  "  PTRM_WEB_REQUEST_SERVICE_GET

ABAP code example for Function Module PTRM_WEB_REQUEST_SERVICE_GET

The ABAP code below is a full code listing to execute function module PTRM_WEB_REQUEST_SERVICE_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_e_document_delivery  
 
 TYPE FTPS_WEB_REQ_DOC_DELIVERY_OUT
,
ld_e_next_request_nr  
 
 TYPE REQUEST_NR
,
it_et_service  
 
 TYPE STANDARD TABLE OF FTPS_WEB_REQUEST_SERVICE_T,"TABLES PARAM
wa_et_service
 
 LIKE LINE OF it_et_service
,
it_et_other_service_cust  
 
 TYPE STANDARD TABLE OF FTPS_OTHER_SERVICES_T,"TABLES PARAM
wa_et_other_service_cust
 
 LIKE LINE OF it_et_other_service_cust
,
it_et_return  
 
 TYPE STANDARD TABLE OF BAPIRETTAB,"TABLES PARAM
wa_et_return
 
 LIKE LINE OF it_et_return
.



DATA(ld_i_employeenumber) = Check type of data required


DATA(ld_i_tripnumber) = Check type of data required


DATA(ld_i_language) = Check type of data required

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

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

"populate fields of struture and append to itab
append wa_et_service to it_et_service.
 

"populate fields of struture and append to itab
append wa_et_other_service_cust to it_et_other_service_cust.
 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
.

CALL FUNCTION 'PTRM_WEB_REQUEST_SERVICE_GET'
  EXPORTING
    i_employeenumber =           ld_i_employeenumber
*   i_tripnumber =               ld_i_tripnumber
*   i_language =                 ld_i_language
    i_trip_begin =               ld_i_trip_begin
    i_trip_end =                 ld_i_trip_end
  IMPORTING
    e_document_delivery =        ld_e_document_delivery
    e_next_request_nr =          ld_e_next_request_nr
  TABLES
    et_service =                 it_et_service
    et_other_service_cust =      it_et_other_service_cust
    et_return =                  it_et_return
    .  "  PTRM_WEB_REQUEST_SERVICE_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_e_document_delivery
 
 TYPE FTPS_WEB_REQ_DOC_DELIVERY_OUT ,
ld_i_employeenumber
 
 TYPE BAPIEMPL-PERNR ,
it_et_service
 
 TYPE STANDARD TABLE OF FTPS_WEB_REQUEST_SERVICE_T ,
wa_et_service
 
 LIKE LINE OF it_et_service,
ld_e_next_request_nr
 
 TYPE REQUEST_NR ,
ld_i_tripnumber
 
 TYPE BAPITRIP-TRIPNO ,
it_et_other_service_cust
 
 TYPE STANDARD TABLE OF FTPS_OTHER_SERVICES_T ,
wa_et_other_service_cust
 
 LIKE LINE OF it_et_other_service_cust,
ld_i_language
 
 TYPE BAPITRVXXX-LANGU ,
it_et_return
 
 TYPE STANDARD TABLE OF BAPIRETTAB ,
wa_et_return
 
 LIKE LINE OF it_et_return,
ld_i_trip_begin
 
 TYPE BEGIN_OF_TRIP ,
ld_i_trip_end
 
 TYPE END_OF_TRIP .



ld_i_employeenumber = Check type of data required 

"populate fields of struture and append to itab
append wa_et_service to it_et_service.

ld_i_tripnumber = Check type of data required 

"populate fields of struture and append to itab
append wa_et_other_service_cust to it_et_other_service_cust.

ld_i_language = Check type of data required 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
ld_i_trip_begin = 'Check type of data required'.
ld_i_trip_end = 'Check type of data required'.