SAP Function Modules
PTRA_UTIL_CCC_TRANSFER SAP Function module
PTRA_UTIL_CCC_TRANSFER 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 PTRA_UTIL_CCC_TRANSFER into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
PTRA_UTIL_CCC
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM PTRA_UTIL_CCC_TRANSFER - PTRA UTIL CCC TRANSFER
CALL FUNCTION 'PTRA_UTIL_CCC_TRANSFER' "
EXPORTING
i_employeenumber = " bapiempl-pernr Personnel Number
i_tripnumber = " bapitrip-tripno Trip Number
* i_periodnumber = " bapitrvxxx-period Number of Trip Period
* i_periodversion = " ptrv_perio-pdvrs Sequential Number of Period
* i_trip_schema = " ptrv_web_general_data_int-t_schema Trip Schema
* i_trip_action = 'MOD' " ptrv_trip_action_m Function Code for Function Modules in PTRA_WEB_INTERFACE
* i_trip_component = 'WEBE' " plan_request Plan Request Indicator
* i_trip_tcode = 'WEBE' " rdynnu Dependent screen number for field control
* i_no_receipt_messages = 'X' " xfeld Single-Character Indicator
* i_head = " head_perio General Information and Period Data of a Trip
* it_mem_ccc_rec_upd = " ptrv_util_ccc_buf_t Documents Taken from Credit Card Buffer
* i_language = " sy-langu Language Key
* i_insert_position = '000' " numc3
IMPORTING
e_head = " head_perio General Information and Period Data of a Trip
et_beleg = " ptrv_util_beleg_t Table for DB Structures PTK03 and PTK33
et_editor = " ptrv_util_editor_t Table for DB Structure PTP71
EXCEPTIONS
ERROR_OCCURRED = 1 "
. " PTRA_UTIL_CCC_TRANSFER
ABAP code example for Function Module PTRA_UTIL_CCC_TRANSFER
The ABAP code below is a full code listing to execute function module PTRA_UTIL_CCC_TRANSFER 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).
| ld_e_head | TYPE HEAD_PERIO , |
| ld_et_beleg | TYPE PTRV_UTIL_BELEG_T , |
| ld_et_editor | TYPE PTRV_UTIL_EDITOR_T . |
DATA(ld_i_employeenumber) = Check type of data required
DATA(ld_i_tripnumber) = Check type of data required
DATA(ld_i_periodnumber) = Check type of data required
SELECT single PDVRS
FROM PTRV_PERIO
INTO @DATA(ld_i_periodversion).
DATA(ld_i_trip_schema) = some text here
DATA(ld_i_trip_action) = 'Check type of data required'.
DATA(ld_i_trip_component) = 'Check type of data required'.
DATA(ld_i_trip_tcode) = 'Check type of data required'.
DATA(ld_i_no_receipt_messages) = 'Check type of data required'.
DATA(ld_i_head) = 'Check type of data required'.
DATA(ld_it_mem_ccc_rec_upd) = 'Check type of data required'.
DATA(ld_i_language) = 'Check type of data required'.
DATA(ld_i_insert_position) = 'Check type of data required'. . CALL FUNCTION 'PTRA_UTIL_CCC_TRANSFER' EXPORTING i_employeenumber = ld_i_employeenumber i_tripnumber = ld_i_tripnumber * i_periodnumber = ld_i_periodnumber * i_periodversion = ld_i_periodversion * i_trip_schema = ld_i_trip_schema * i_trip_action = ld_i_trip_action * i_trip_component = ld_i_trip_component * i_trip_tcode = ld_i_trip_tcode * i_no_receipt_messages = ld_i_no_receipt_messages * i_head = ld_i_head * it_mem_ccc_rec_upd = ld_it_mem_ccc_rec_upd * i_language = ld_i_language * i_insert_position = ld_i_insert_position IMPORTING e_head = ld_e_head et_beleg = ld_et_beleg et_editor = ld_et_editor EXCEPTIONS ERROR_OCCURRED = 1 . " PTRA_UTIL_CCC_TRANSFER
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_head | TYPE HEAD_PERIO , |
| ld_i_employeenumber | TYPE BAPIEMPL-PERNR , |
| ld_et_beleg | TYPE PTRV_UTIL_BELEG_T , |
| ld_i_tripnumber | TYPE BAPITRIP-TRIPNO , |
| ld_et_editor | TYPE PTRV_UTIL_EDITOR_T , |
| ld_i_periodnumber | TYPE BAPITRVXXX-PERIOD , |
| ld_i_periodversion | TYPE PTRV_PERIO-PDVRS , |
| ld_i_trip_schema | TYPE PTRV_WEB_GENERAL_DATA_INT-T_SCHEMA , |
| ld_i_trip_action | TYPE PTRV_TRIP_ACTION_M , |
| ld_i_trip_component | TYPE PLAN_REQUEST , |
| ld_i_trip_tcode | TYPE RDYNNU , |
| ld_i_no_receipt_messages | TYPE XFELD , |
| ld_i_head | TYPE HEAD_PERIO , |
| ld_it_mem_ccc_rec_upd | TYPE PTRV_UTIL_CCC_BUF_T , |
| ld_i_language | TYPE SY-LANGU , |
| ld_i_insert_position | TYPE NUMC3 . |
ld_i_employeenumber = Check type of data required
ld_i_tripnumber = Check type of data required
ld_i_periodnumber = Check type of data required
SELECT single PDVRS
FROM PTRV_PERIO
INTO ld_i_periodversion.
ld_i_trip_schema = some text here
ld_i_trip_action = 'Check type of data required'.
ld_i_trip_component = 'Check type of data required'.
ld_i_trip_tcode = 'Check type of data required'.
ld_i_no_receipt_messages = 'Check type of data required'.
ld_i_head = 'Check type of data required'.
ld_it_mem_ccc_rec_upd = 'Check type of data required'.
ld_i_language = 'Check type of data required'.
ld_i_insert_position = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name PTRA_UTIL_CCC_TRANSFER or its description.