SAP PTRA_UTIL_MEM_KEY_SAVE Function Module for
PTRA_UTIL_MEM_KEY_SAVE is a standard ptra util mem key save 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 ptra util mem key save FM, simply by entering the name PTRA_UTIL_MEM_KEY_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PTRA_UTIL_MEMORY
Program Name: SAPLPTRA_UTIL_MEMORY
Main Program: SAPLPTRA_UTIL_MEMORY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PTRA_UTIL_MEM_KEY_SAVE 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 'PTRA_UTIL_MEM_KEY_SAVE'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
I_TRIPNUMBER = "Trip Number
I_PERIODNUMBER = "Number of Trip Period
I_PERIODVERSION = "Sequential Number of Period
* I_BEGIN_OF_TRIP = "Start Date of Trip Segment
* I_TRIP_SCHEMA = "Trip Schema
* I_CURRENT_VERSION = "Checkbox
* I_REQUEST_ITEMS_EXIST = "
IMPORTING Parameters details for PTRA_UTIL_MEM_KEY_SAVE
I_EMPLOYEENUMBER - Personnel Number
Data type: BAPIEMPL-PERNROptional: No
Call by Reference: Yes
I_TRIPNUMBER - Trip Number
Data type: BAPITRIP-TRIPNOOptional: No
Call by Reference: Yes
I_PERIODNUMBER - Number of Trip Period
Data type: BAPITRVXXX-PERIODOptional: No
Call by Reference: Yes
I_PERIODVERSION - Sequential Number of Period
Data type: PTRV_PERIO-PDVRSOptional: No
Call by Reference: Yes
I_BEGIN_OF_TRIP - Start Date of Trip Segment
Data type: HEAD_PERIO-DATV1Optional: Yes
Call by Reference: Yes
I_TRIP_SCHEMA - Trip Schema
Data type: HEAD_PERIO-SCHEMOptional: Yes
Call by Reference: Yes
I_CURRENT_VERSION - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
I_REQUEST_ITEMS_EXIST -
Data type: XFELDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PTRA_UTIL_MEM_KEY_SAVE 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_i_tripnumber | TYPE BAPITRIP-TRIPNO, " | |||
| lv_i_periodnumber | TYPE BAPITRVXXX-PERIOD, " | |||
| lv_i_periodversion | TYPE PTRV_PERIO-PDVRS, " | |||
| lv_i_begin_of_trip | TYPE HEAD_PERIO-DATV1, " | |||
| lv_i_trip_schema | TYPE HEAD_PERIO-SCHEM, " | |||
| lv_i_current_version | TYPE XFELD, " | |||
| lv_i_request_items_exist | TYPE XFELD. " |
|   CALL FUNCTION 'PTRA_UTIL_MEM_KEY_SAVE' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER | = lv_i_tripnumber | |
| I_PERIODNUMBER | = lv_i_periodnumber | |
| I_PERIODVERSION | = lv_i_periodversion | |
| I_BEGIN_OF_TRIP | = lv_i_begin_of_trip | |
| I_TRIP_SCHEMA | = lv_i_trip_schema | |
| I_CURRENT_VERSION | = lv_i_current_version | |
| I_REQUEST_ITEMS_EXIST | = lv_i_request_items_exist | |
| . " PTRA_UTIL_MEM_KEY_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_UTIL_MEM_KEY_SAVE
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 PERIOD FROM BAPITRVXXX INTO @DATA(ld_i_periodnumber). | ||||
| "SELECT single PDVRS FROM PTRV_PERIO INTO @DATA(ld_i_periodversion). | ||||
| "SELECT single DATV1 FROM HEAD_PERIO INTO @DATA(ld_i_begin_of_trip). | ||||
| "SELECT single SCHEM FROM HEAD_PERIO INTO @DATA(ld_i_trip_schema). | ||||
Search for further information about these or an SAP related objects