SAP PTRM_UTIL_REQUEST_SERVICE_GET Function Module for
PTRM_UTIL_REQUEST_SERVICE_GET is a standard ptrm util request service get 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 ptrm util request service get FM, simply by entering the name PTRM_UTIL_REQUEST_SERVICE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: PTRM_WEB_REQUEST
Program Name: SAPLPTRM_WEB_REQUEST
Main Program: SAPLPTRM_WEB_REQUEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PTRM_UTIL_REQUEST_SERVICE_GET 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 'PTRM_UTIL_REQUEST_SERVICE_GET'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
* I_TRIPNUMBER = "Trip Number
* I_LANGUAGE = "Language Key
I_TRIP_BEGIN = "Start of Leg of Trip
I_TRIP_END = "End of Leg of Trip
IMPORTING
E_DOCUMENT_DELIVERY = "Delivery of Requested Travel Service Documents -> Web UI
ET_SERVICE = "Table Type for Travel Service Requests - Web UI
ET_OTHER_SERVICE_CUST = "Table Type Customizing Other Travel Services
ET_RETURN = "Table with BAPI Return Information
E_NEXT_REQUEST_NR = "Request number (sequential number
EXCEPTIONS
CUSTOMIZING_ERROR = 1
IMPORTING Parameters details for PTRM_UTIL_REQUEST_SERVICE_GET
I_EMPLOYEENUMBER - Personnel Number
Data type: BAPIEMPL-PERNROptional: No
Call by Reference: Yes
I_TRIPNUMBER - Trip Number
Data type: BAPITRIP-TRIPNOOptional: Yes
Call by Reference: Yes
I_LANGUAGE - Language Key
Data type: BAPITRVXXX-LANGUOptional: Yes
Call by Reference: Yes
I_TRIP_BEGIN - Start of Leg of Trip
Data type: BEGIN_OF_TRIPOptional: No
Call by Reference: Yes
I_TRIP_END - End of Leg of Trip
Data type: END_OF_TRIPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PTRM_UTIL_REQUEST_SERVICE_GET
E_DOCUMENT_DELIVERY - Delivery of Requested Travel Service Documents -> Web UI
Data type: FTPS_WEB_REQ_DOC_DELIVERY_OUTOptional: No
Call by Reference: Yes
ET_SERVICE - Table Type for Travel Service Requests - Web UI
Data type: FTPS_WEB_REQUEST_SERVICE_TOptional: No
Call by Reference: Yes
ET_OTHER_SERVICE_CUST - Table Type Customizing Other Travel Services
Data type: FTPS_OTHER_SERVICES_TOptional: No
Call by Reference: Yes
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
E_NEXT_REQUEST_NR - Request number (sequential number
Data type: REQUEST_NROptional: No
Call by Reference: Yes
EXCEPTIONS details
CUSTOMIZING_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PTRM_UTIL_REQUEST_SERVICE_GET 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_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lv_customizing_error | TYPE BAPIEMPL, " | |||
| lv_e_document_delivery | TYPE FTPS_WEB_REQ_DOC_DELIVERY_OUT, " | |||
| lv_et_service | TYPE FTPS_WEB_REQUEST_SERVICE_T, " | |||
| lv_i_tripnumber | TYPE BAPITRIP-TRIPNO, " | |||
| lv_i_language | TYPE BAPITRVXXX-LANGU, " | |||
| lv_et_other_service_cust | TYPE FTPS_OTHER_SERVICES_T, " | |||
| lv_et_return | TYPE BAPIRETTAB, " | |||
| lv_i_trip_begin | TYPE BEGIN_OF_TRIP, " | |||
| lv_i_trip_end | TYPE END_OF_TRIP, " | |||
| lv_e_next_request_nr | TYPE REQUEST_NR. " |
|   CALL FUNCTION 'PTRM_UTIL_REQUEST_SERVICE_GET' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER | = lv_i_tripnumber | |
| I_LANGUAGE | = lv_i_language | |
| I_TRIP_BEGIN | = lv_i_trip_begin | |
| I_TRIP_END | = lv_i_trip_end | |
| IMPORTING | ||
| E_DOCUMENT_DELIVERY | = lv_e_document_delivery | |
| ET_SERVICE | = lv_et_service | |
| ET_OTHER_SERVICE_CUST | = lv_et_other_service_cust | |
| ET_RETURN | = lv_et_return | |
| E_NEXT_REQUEST_NR | = lv_e_next_request_nr | |
| EXCEPTIONS | ||
| CUSTOMIZING_ERROR = 1 | ||
| . " PTRM_UTIL_REQUEST_SERVICE_GET | ||
ABAP code using 7.40 inline data declarations to call FM PTRM_UTIL_REQUEST_SERVICE_GET
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 PERNR FROM BAPIEMPL INTO @DATA(ld_i_employeenumber). | ||||
| "SELECT single TRIPNO FROM BAPITRIP INTO @DATA(ld_i_tripnumber). | ||||
| "SELECT single LANGU FROM BAPITRVXXX INTO @DATA(ld_i_language). | ||||
Search for further information about these or an SAP related objects