SAP PTRA_EES_MEMORY_COPY Function Module for Set trip data into EES memory
PTRA_EES_MEMORY_COPY is a standard ptra ees memory copy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set trip data into EES memory processing and below is the pattern details for this FM, 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 ees memory copy FM, simply by entering the name PTRA_EES_MEMORY_COPY into the relevant SAP transaction such as SE37 or SE38.
Function Group: PTRA_EES_MEMORY
Program Name: SAPLPTRA_EES_MEMORY
Main Program: SAPLPTRA_EES_MEMORY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PTRA_EES_MEMORY_COPY 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_EES_MEMORY_COPY'"Set trip data into EES memory.
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
I_TRIPNUMBER_FROM = "Trip Number
I_TRIPNUMBER_TO = "Trip Number
I_START_DATE_TARGET = "Date
I_START_TIME_TARGET = "
I_END_DATE_TARGET = "Date
I_END_TIME_TARGET = "
IMPORTING
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for PTRA_EES_MEMORY_COPY
I_EMPLOYEENUMBER - Personnel Number
Data type: PERNR_DOptional: No
Call by Reference: Yes
I_TRIPNUMBER_FROM - Trip Number
Data type: REINROptional: No
Call by Reference: Yes
I_TRIPNUMBER_TO - Trip Number
Data type: REINROptional: No
Call by Reference: Yes
I_START_DATE_TARGET - Date
Data type: DATUMOptional: No
Call by Reference: Yes
I_START_TIME_TARGET -
Data type: TOptional: No
Call by Reference: Yes
I_END_DATE_TARGET - Date
Data type: DATUMOptional: No
Call by Reference: Yes
I_END_TIME_TARGET -
Data type: TOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PTRA_EES_MEMORY_COPY
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PTRA_EES_MEMORY_COPY 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_et_return | TYPE BAPIRETTAB, " | |||
| lv_i_employeenumber | TYPE PERNR_D, " | |||
| lv_i_tripnumber_from | TYPE REINR, " | |||
| lv_i_tripnumber_to | TYPE REINR, " | |||
| lv_i_start_date_target | TYPE DATUM, " | |||
| lv_i_start_time_target | TYPE T, " | |||
| lv_i_end_date_target | TYPE DATUM, " | |||
| lv_i_end_time_target | TYPE T. " |
|   CALL FUNCTION 'PTRA_EES_MEMORY_COPY' "Set trip data into EES memory |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER_FROM | = lv_i_tripnumber_from | |
| I_TRIPNUMBER_TO | = lv_i_tripnumber_to | |
| I_START_DATE_TARGET | = lv_i_start_date_target | |
| I_START_TIME_TARGET | = lv_i_start_time_target | |
| I_END_DATE_TARGET | = lv_i_end_date_target | |
| I_END_TIME_TARGET | = lv_i_end_time_target | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| . " PTRA_EES_MEMORY_COPY | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_EES_MEMORY_COPY
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.Search for further information about these or an SAP related objects