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

Function PTRA_WEB_CCC_BUFFER_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 'PTRA_WEB_CCC_BUFFER_GET'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
I_TRIPNUMBER = "Trip Number
* I_TRIP_ACTION = 'MOD' "Function Code for Function Modules in PTRA_WEB_INTERFACE
* I_TRIP_COMPONENT = ' ' "Dependent screen number for field control
* I_TRIP_APPLICATION = "
* I_LANGUAGE = SY-LANGU "Language Key
IMPORTING
E_EXPTYPES_PER_SCHEME = "
TABLES
ET_CCC_BUFFER = "Selection of Credit Card Docs from Doc Buffer Ext Represent.
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for PTRA_WEB_CCC_BUFFER_GET
I_EMPLOYEENUMBER - Personnel Number
Data type: BAPIEMPL-PERNROptional: No
Call by Reference: No ( called with pass by value option)
I_TRIPNUMBER - Trip Number
Data type: BAPITRIP-TRIPNOOptional: No
Call by Reference: No ( called with pass by value option)
I_TRIP_ACTION - Function Code for Function Modules in PTRA_WEB_INTERFACE
Data type: PTRV_TRIP_ACTION_MDefault: 'MOD'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRIP_COMPONENT - Dependent screen number for field control
Data type: PLAN_REQUESTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRIP_APPLICATION -
Data type: RDYNNUOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - Language Key
Data type: BAPITRVXXX-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PTRA_WEB_CCC_BUFFER_GET
E_EXPTYPES_PER_SCHEME -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PTRA_WEB_CCC_BUFFER_GET
ET_CCC_BUFFER - Selection of Credit Card Docs from Doc Buffer Ext Represent.
Data type: PTRV_WEB_CCC_SELECTION_EXT_TOptional: No
Call by Reference: Yes
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PTRA_WEB_CCC_BUFFER_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: | ||||
| lt_et_ccc_buffer | TYPE STANDARD TABLE OF PTRV_WEB_CCC_SELECTION_EXT_T, " | |||
| lv_i_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lv_e_exptypes_per_scheme | TYPE XFELD, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_tripnumber | TYPE BAPITRIP-TRIPNO, " | |||
| lv_i_trip_action | TYPE PTRV_TRIP_ACTION_M, " 'MOD' | |||
| lv_i_trip_component | TYPE PLAN_REQUEST, " SPACE | |||
| lv_i_trip_application | TYPE RDYNNU, " | |||
| lv_i_language | TYPE BAPITRVXXX-LANGU. " SY-LANGU |
|   CALL FUNCTION 'PTRA_WEB_CCC_BUFFER_GET' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER | = lv_i_tripnumber | |
| I_TRIP_ACTION | = lv_i_trip_action | |
| I_TRIP_COMPONENT | = lv_i_trip_component | |
| I_TRIP_APPLICATION | = lv_i_trip_application | |
| I_LANGUAGE | = lv_i_language | |
| IMPORTING | ||
| E_EXPTYPES_PER_SCHEME | = lv_e_exptypes_per_scheme | |
| TABLES | ||
| ET_CCC_BUFFER | = lt_et_ccc_buffer | |
| ET_RETURN | = lt_et_return | |
| . " PTRA_WEB_CCC_BUFFER_GET | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_WEB_CCC_BUFFER_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). | ||||
| DATA(ld_i_trip_action) | = 'MOD'. | |||
| DATA(ld_i_trip_component) | = ' '. | |||
| "SELECT single LANGU FROM BAPITRVXXX INTO @DATA(ld_i_language). | ||||
| DATA(ld_i_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects