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

Function PTRA_UTIL_GENERAL_DATA_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_UTIL_GENERAL_DATA_FIELDS'".
EXPORTING
I_EMPLOYEENUMBER = "Personnel Number
* I_HEAD = "General Information and Period Data of a Trip
* 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_TRIP_TCODE = 'WEBE' "Dependent screen number for field control
* I_LANGUAGE = SY-LANGU "Language Key
IMPORTING
ET_FIELD_CONTROL = "Table Single Field Control for Dialog
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for PTRA_UTIL_GENERAL_DATA_FIELDS
I_EMPLOYEENUMBER - Personnel Number
Data type: BAPIEMPL-PERNROptional: No
Call by Reference: Yes
I_HEAD - General Information and Period Data of a Trip
Data type: HEAD_PERIOOptional: Yes
Call by Reference: Yes
I_TRIPNUMBER - Trip Number
Data type: BAPITRIP-TRIPNOOptional: Yes
Call by Reference: Yes
I_PERIODNUMBER - Number of Trip Period
Data type: BAPITRVXXX-PERIODOptional: Yes
Call by Reference: Yes
I_PERIODVERSION - Sequential Number of Period
Data type: PTRV_PERIO-PDVRSOptional: Yes
Call by Reference: Yes
I_TRIP_SCHEMA - Trip Schema
Data type: HEAD_PERIO-SCHEMOptional: Yes
Call by Reference: Yes
I_TRIP_ACTION - Function Code for Function Modules in PTRA_WEB_INTERFACE
Data type: PTRV_TRIP_ACTION_SDefault: 'MOD'
Optional: Yes
Call by Reference: Yes
I_TRIP_COMPONENT - Plan Request Indicator
Data type: PLAN_REQUESTOptional: Yes
Call by Reference: Yes
I_TRIP_TCODE - Dependent screen number for field control
Data type: T706Z1-RDYNNRDefault: 'WEBE'
Optional: Yes
Call by Reference: Yes
I_LANGUAGE - Language Key
Data type: BAPITRVXXX-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PTRA_UTIL_GENERAL_DATA_FIELDS
ET_FIELD_CONTROL - Table Single Field Control for Dialog
Data type: PTRV_UTIL_FIELD_CONTROL_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED - Errors have occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PTRA_UTIL_GENERAL_DATA_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: | ||||
| lv_error_occurred | TYPE STRING, " | |||
| lv_et_field_control | TYPE PTRV_UTIL_FIELD_CONTROL_T, " | |||
| lv_i_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lv_i_head | TYPE HEAD_PERIO, " | |||
| 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, " | |||
| lv_i_trip_tcode | TYPE T706Z1-RDYNNR, " 'WEBE' | |||
| lv_i_language | TYPE BAPITRVXXX-LANGU. " SY-LANGU |
|   CALL FUNCTION 'PTRA_UTIL_GENERAL_DATA_FIELDS' " |
| EXPORTING | ||
| I_EMPLOYEENUMBER | = lv_i_employeenumber | |
| I_HEAD | = lv_i_head | |
| 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_TRIP_TCODE | = lv_i_trip_tcode | |
| I_LANGUAGE | = lv_i_language | |
| IMPORTING | ||
| ET_FIELD_CONTROL | = lv_et_field_control | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| . " PTRA_UTIL_GENERAL_DATA_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM PTRA_UTIL_GENERAL_DATA_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'. | |||
| "SELECT single RDYNNR FROM T706Z1 INTO @DATA(ld_i_trip_tcode). | ||||
| DATA(ld_i_trip_tcode) | = 'WEBE'. | |||
| "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