FITV_REQ_HEAD SAP (Travel Request Overview) Structure details
Description: Travel Request Overview
Related tables to FITV_REQ_HEAD
Access table FITV_REQ_HEAD
Structure field list including key, data, relationships and ABAP select examples
FITV_REQ_HEAD is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Travel Request Overview" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_FITV_REQ_HEAD TYPE FITV_REQ_HEAD.
The FITV_REQ_HEAD table consists of various fields, each holding specific information or linking keys about Travel Request Overview data available in SAP. These include REINR (Trip Number), NAME (Formatted Name of Employee or Applicant), LOCATION_END (Trip Destination), COUNTRY_END (Country Key).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP FITV_REQ_HEAD structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
REINR | Trip Number | REINR | NUMC | 10 | REINR | ||||
NAME | Formatted Name of Employee or Applicant | EMNAM | CHAR | 40 | TEXT40 | ||||
LOCATION_END | Trip Destination | REQUEST_END | CHAR | 59 | RZIELORT | ||||
COUNTRY_END | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
COUNTRY_TXT | Name of Trip Country/Country Group/Region | TEXT_RGION | CHAR | 25 | TRV25 | ||||
REGION | Region of Main Destination | HRGIO | CHAR | 5 | Assigned to domain | RGION | |||
REQUEST_REASON | Reason for Trip | REQUEST_REASON | CHAR | 59 | RKUNDE | ||||
DATE_BEG | Beginning Date of Trip Segment | REQUEST_DATEBEG | DATS | 8 | DATUM | ||||
TIME_BEG | Start Time of Trip Segment | REQUEST_TIMEBEG | TIMS | 6 | TIME | ||||
DATE_END | End Date of Trip Segment | REQUEST_DATEEND | DATS | 8 | DATUM | ||||
TIME_END | End Time of Trip Segment | REQUEST_TIMEEND | TIMS | 6 | TIME | ||||
TRIPDUR | Trip Duration in Days | PTRV_TRIPDUR | DEC | 4 | DEC4 | ||||
ACTIVITY_TYPE | Trip Activity Type | PLAN_ACTIVITY | CHAR | 1 | Assigned to domain | FTPD_PLAN_ACTIVITY | |||
ACTIVITY_TXT | Name for trip activity type | TEXT_KZTKT | CHAR | 30 | REITX | ||||
ESTIMATED_COST | Estimated Total Cost of Trip | FITV_ESTIMATED_COST | CURR | 13(2) | WERTV7 | ||||
SUM_ADVANC | Total Advances for a Trip | PTRV_SUM_ADVANC | CURR | 13(2) | WERTV7 | ||||
CURRENCY | Currency Key | TRVWAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
APPROVED | Travel Request or Trip Approved (Indicator) | ANTRG | CHAR | 1 | ANTRG | ||||
APPR_TXT | Text for Approval Status of a Trip | APPR_TXT | CHAR | 15 | CHAR15 | ||||
ACCOUNT | Open / To be Settled / Settled (Indicator) | ABREC | CHAR | 1 | ABREC | ||||
TRAN_PAY | HR Payroll Transfer (Indicator) | UEBLG | CHAR | 1 | UEBLG | ||||
TRAN_FI | FI Transfer (Indicator) | UEBRF | CHAR | 1 | UEBRF | ||||
TRAN_DME | Data Medium Exchange Transfer (Indicator) | UEBDT | CHAR | 1 | UEBDT | ||||
ACC_TEXT | Text for Settlement Status of a Trip | ACC_TEXT | CHAR | 17 | CHAR17 | ||||
PRINTED | Trip Print Status | P_PRINT | CHAR | 1 | P_PRINT | ||||
PRIN_TXT | Text for Print Status of a Trip | PRIN_TXT | CHAR | 15 | CHAR15 | ||||
CH_ON | Changed On | AEDAT | DATS | 8 | DATUM | ||||
CH_ON_TIME | Time of Last Change | AEUHR | TIMS | 6 | ATIME | ||||
CHANGED_BY | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM |
Key field | Non-key field |
How do I retrieve data from SAP structure FITV_REQ_HEAD using ABAP code?
As FITV_REQ_HEAD is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on FITV_REQ_HEAD as there is no data to select.How to access SAP table FITV_REQ_HEAD
Within an ECC or HANA version of SAP you can also view further information about FITV_REQ_HEAD and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects