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

Function PTRA_WEB_ADVANCES_FIELDS 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_ADVANCES_FIELDS'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
* I_TRIPNUMBER = "Trip Number
* I_PERIODNUMBER = "Number of Trip Period
* I_PERIODVERSION = "Sequential Number of Period
* I_TRIP_SCHEMA = "Trip Schema
* I_TRIP_ACTION = 'MOD' "Function Code for Function Modules in PTRA_WEB_INTERFACE
* I_TRIP_COMPONENT = ' ' "Plan Request Indicator
* I_LANGUAGE = SY-LANGU "Language Key
TABLES
* ET_FIELD_CONTROL = "Table Single Field Control for Dialog
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for PTRA_WEB_ADVANCES_FIELDS
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: Yes
Call by Reference: No ( called with pass by value option)
I_PERIODNUMBER - Number of Trip Period
Data type: BAPITRVXXX-PERIODOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PERIODVERSION - Sequential Number of Period
Data type: PTRV_PERIO-PDVRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TRIP_SCHEMA - Trip Schema
Data type: HEAD_PERIO-SCHEMOptional: Yes
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_SDefault: 'MOD'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRIP_COMPONENT - Plan Request Indicator
Data type: PLAN_REQUESTDefault: SPACE
Optional: 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)
TABLES Parameters details for PTRA_WEB_ADVANCES_FIELDS
ET_FIELD_CONTROL - Table Single Field Control for Dialog
Data type: PTRV_WEB_FIELD_CONTROL_TOptional: Yes
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_ADVANCES_FIELDS 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_field_control | TYPE STANDARD TABLE OF PTRV_WEB_FIELD_CONTROL_T, " | |||
| lv_i_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_tripnumber | TYPE BAPITRIP-TRIPNO, " | |||
| lv_i_periodnumber | TYPE BAPITRVXXX-PERIOD, " | |||
| lv_i_periodversion | TYPE PTRV_PERIO-PDVRS, " | |||
| lv_i_trip_schema | TYPE HEAD_PERIO-SCHEM, " | |||
| lv_i_trip_action | TYPE PTRV_TRIP_ACTION_S, " 'MOD' | |||
| lv_i_trip_component | TYPE PLAN_REQUEST, " SPACE | |||
| lv_i_language | TYPE BAPITRVXXX-LANGU. " SY-LANGU |
|   CALL FUNCTION 'PTRA_WEB_ADVANCES_FIELDS' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_TRIPNUMBER | = lv_i_tripnumber | |
| I_PERIODNUMBER | = lv_i_periodnumber | |
| I_PERIODVERSION | = lv_i_periodversion | |
| I_TRIP_SCHEMA | = lv_i_trip_schema | |
| I_TRIP_ACTION | = lv_i_trip_action | |
| I_TRIP_COMPONENT | = lv_i_trip_component | |
| I_LANGUAGE | = lv_i_language | |
| TABLES | ||
| ET_FIELD_CONTROL | = lt_et_field_control | |
| ET_RETURN | = lt_et_return | |
| . " PTRA_WEB_ADVANCES_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_WEB_ADVANCES_FIELDS
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 SCHEM FROM HEAD_PERIO INTO @DATA(ld_i_trip_schema). | ||||
| 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