FTPS_REQUEST SAP (Adobe form: Travel Plan Requests) Structure details
Description: Adobe form: Travel Plan Requests
Structure field list including key, data, relationships and ABAP select examples
FTPS_REQUEST 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 "Adobe form: Travel Plan Requests" 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_FTPS_REQUEST TYPE FTPS_REQUEST.
The FTPS_REQUEST table consists of various fields, each holding specific information or linking keys about Adobe form: Travel Plan Requests data available in SAP. These include MANDT (Client), PERNR (Personnel Number), REINR (Trip Number), PLANNR (Travel Plan Number (Sequential Number)).. 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: Can Be Enhanced (Deep)
SAP FTPS_REQUEST 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
REINR | Trip Number | REINR | NUMC | 10 | REINR | ||||
PLANNR | Travel Plan Number (Sequential Number) | PLAN_NR | NUMC | 2 | Assigned to domain | FTPD_PLAN_NR | |||
VARIANTE | Plan variant number (sequential number) | VARIANT_NR | NUMC | 2 | FTPD_VARIANT_NR | ||||
VARIANTVRS | Version of travel plan | VARIANT_VERSION | NUMC | 2 | Assigned to domain | FTPD_VARIANT_VERSION | |||
REQUESTVRS | Version of travel request | REQUEST_VERSION | NUMC | 2 | FTPD_REQUEST_VERSION | ||||
PLAN_REQUEST | Plan Request Indicator | PLAN_REQUEST | CHAR | 1 | FTPD_PLAN_REQUEST | ||||
REQUEST | Request number (sequential number | REQUEST_NR | NUMC | 2 | FTPD_REQUEST_NR | ||||
ITINERARY_NUMBER | Number of trip segment | ITINERARY_NUMBER | NUMC | 2 | PTRVNUMC2 | ||||
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 | ||||
LOCATION_BEG | Starting location of trip segment | REQUEST_LOC_BEG | CHAR | 59 | RZIELORT | ||||
COUNTRY_BEG | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
LOCATION_END | End location of trip segment | REQUEST_LOC_END | CHAR | 59 | RZIELORT | ||||
COUNTRY_END | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
REQUEST_TYPE | Travel Item Type | REQUEST_TYPE | CHAR | 2 | FTPD_REQUEST_TYPE | ||||
DEP_ARR | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
ITEM | Travel Request Item Number (Sequential Number) | ITEMPOS_NR | NUMC | 3 | Assigned to domain | FTPD_ITEM_ID | |||
REASON | Reason for trip (e.g. customer/requisitioner) | RKUND | CHAR | 17 | RKUND | ||||
ACTIVITY | Trip Activity Type | PLAN_ACTIVITY | CHAR | 1 | Assigned to domain | FTPD_PLAN_ACTIVITY | |||
NAME | Description of trip activity type - Travel Planning | PLAN_ACTIVITY_NAME | CHAR | 30 | TEXT30 | ||||
OFFICE_FIND | Grouping for Sales Office Determination | OFFICE_FIND | CHAR | 2 | Assigned to domain | OFFICE_FIND | |||
OS_CODE | Other Travel Service: Code | OTHER_SERVICE_CODE | CHAR | 1 | FTPD_OS_CODE | ||||
LOC_BEG_IATA | Start Location of Trip Segment (IATA) | REQUEST_LOC_BEG_IATA | CHAR | 3 | Assigned to domain | FTPD_IATA_LOCATION | S_IATA_LOCATION | ||
LOC_END_IATA | End Location of Trip Segment (IATA) | REQUEST_LOC_END_IATA | CHAR | 3 | Assigned to domain | FTPD_IATA_LOCATION | S_IATA_LOCATION | ||
OS_STATUS | Status of Other Service | OS_STATUS | CHAR | 1 | FTPD_OTHER_SERVICE_STATUS | ||||
OS_CONF_NUMBER | Confirmation Code of Other Service | OS_CONF_NUMBER | NUMC | 16 | FTPD_OS_CONF_NR | ||||
PRICE | Price of Request | REQUEST_PRICE | CURR | 10(2) | FTPD_PRICE | ||||
CURRENCY | Currency of Request | REQUEST_CURRENCY | CUKY | 5 | Assigned to domain | WAERS | |||
COMMENT1 | Comment About Request | REQUEST_COMMENT | CHAR | 255 | FTPD_REQUEST_COMMENT | ||||
OS_NAME | Other Travel Service: Name | OTHER_SERVICE_NAME | CHAR | 30 | TEXT30 | ||||
OS_STATUS_TEXT | Short Text for Fixed Values | VAL_TEXT | CHAR | 60 | DDTEXT | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | T005S | REGIO | |||
CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
POST_CODE | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
HOUSE_NUM | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
ADDRESS | Texts used in travel management | FITV_TEXT | STRG | 0 | STRING | ||||
TRIP_BREAK | Trip Break | PTRA_WEB_FORM_TRIP_BREAK | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure FTPS_REQUEST using ABAP code?
As FTPS_REQUEST 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 FTPS_REQUEST as there is no data to select.How to access SAP table FTPS_REQUEST
Within an ECC or HANA version of SAP you can also view further information about FTPS_REQUEST 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