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

Function PTRA_UTIL_CCC_TRANSFER_BACK 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_CCC_TRANSFER_BACK'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
I_TRIPNUMBER = "Trip Number
* I_TRIP_ACTION = 'MOD' "Function Code for Function Modules in PTRA_WEB_INTERFACE
* I_TRIP_TCODE = "Dependent screen number for field control
IT_CCC_BELEG_BACK = "Table for DB Structures PTK03 and PTK33
* I_LANGUAGE = SY-LANGU "Language Key
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for PTRA_UTIL_CCC_TRANSFER_BACK
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_TRIP_ACTION - Function Code for Function Modules in PTRA_WEB_INTERFACE
Data type: PTRV_TRIP_ACTION_MDefault: 'MOD'
Optional: No
Call by Reference: Yes
I_TRIP_TCODE - Dependent screen number for field control
Data type: RDYNNUOptional: Yes
Call by Reference: Yes
IT_CCC_BELEG_BACK - Table for DB Structures PTK03 and PTK33
Data type: PTRV_UTIL_BELEG_TOptional: No
Call by Reference: Yes
I_LANGUAGE - Language Key
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PTRA_UTIL_CCC_TRANSFER_BACK 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_error_occurred | TYPE STRING, " | |||
| lv_i_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lv_i_tripnumber | TYPE BAPITRIP-TRIPNO, " | |||
| lv_i_trip_action | TYPE PTRV_TRIP_ACTION_M, " 'MOD' | |||
| lv_i_trip_tcode | TYPE RDYNNU, " | |||
| lv_it_ccc_beleg_back | TYPE PTRV_UTIL_BELEG_T, " | |||
| lv_i_language | TYPE SY-LANGU. " SY-LANGU |
|   CALL FUNCTION 'PTRA_UTIL_CCC_TRANSFER_BACK' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER | = lv_i_tripnumber | |
| I_TRIP_ACTION | = lv_i_trip_action | |
| I_TRIP_TCODE | = lv_i_trip_tcode | |
| IT_CCC_BELEG_BACK | = lv_it_ccc_beleg_back | |
| I_LANGUAGE | = lv_i_language | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| . " PTRA_UTIL_CCC_TRANSFER_BACK | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_UTIL_CCC_TRANSFER_BACK
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). | ||||
| DATA(ld_i_trip_action) | = 'MOD'. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_language). | ||||
| DATA(ld_i_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects