FTPS_API_RAIL_FIN_IN SAP (Structure to format pricing entry) Structure details
Dictionary Type: Structure
Description: Structure to format pricing entry
Description: Structure to format pricing entry
ABAP Code to SELECT data from FTPS_API_RAIL_FIN_IN
Related tables to FTPS_API_RAIL_FIN_IN
Access table FTPS_API_RAIL_FIN_IN
Related tables to FTPS_API_RAIL_FIN_IN
Access table FTPS_API_RAIL_FIN_IN
Structure field list including key, data, relationships and ABAP select examples
FTPS_API_RAIL_FIN_IN 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 "Structure to format pricing entry" 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_API_RAIL_FIN_IN TYPE FTPS_API_RAIL_FIN_IN.
The FTPS_API_RAIL_FIN_IN table consists of various fields, each holding specific information or linking keys about Structure to format pricing entry data available in SAP. These include TARIFF_TYPE (1 = ONE WAY ; 21 = RETURN (use table GDEB)), REDUCTION (Ticket Reduction (use table ZUSE)), FOREIGN_TRAFFIC_TYPE (), FOREIGN_TARIFF_TYPE ().. 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 FTPS_API_RAIL_FIN_IN 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 |
| TRAFFIC_TYPE | 1=Standard ; 2=ICE (use table GDEB) | 0 | |||||||
| TARIFF_TYPE | 1 = ONE WAY ; 21 = RETURN (use table GDEB) | 0 | |||||||
| REDUCTION | Ticket Reduction (use table ZUSE) | 0 | |||||||
| FOREIGN_TRAFFIC_TYPE | 0 | ||||||||
| FOREIGN_TARIFF_TYPE | 0 | ||||||||
| FOREIGN_EDUCTION | 0 | ||||||||
| TRAIN_CLASS | Class of service (1 or 2) | 0 | |||||||
| NUMBER_OF_TICKETS | Number of identical tickets to issue | 0 | |||||||
| NUMBER_OF_ADULTS | Number of adult using the ticket | 0 | |||||||
| NUMBER_OF_CHLDREN | Number of child using ticket | 0 | |||||||
| FORM_OF_PAYMENT | (use table ZART) | 0 | |||||||
| MWST | Not used | 0 | |||||||
| VALID_FROM_DAYS | Ticket validity from : day | 0 | |||||||
| VALID_FROM_MONTH | Ticket validaty from : month | 0 | |||||||
| VALID_FROM_YEAR | ticket validity from : year | 0 | |||||||
| VALID_TO_DAYS | Ticket validity to : day | 0 | |||||||
| VALID_TO_MONTH | Ticket validaty to : month | 0 | |||||||
| VALID_TO_YEAR | ticket validity to : year | 0 | |||||||
| VALIDITY_MONTH_NUMBER | ticket validity month | 0 | |||||||
| VALIDITY_WEEK_NUMBER | ticket vlaiadity week | 0 | |||||||
| SALES_GUIDE_NUMBER | (use table VFGA) | 0 | |||||||
| TRAIN_NUMBER | TRain number for which tkt is valid | 0 | |||||||
| TRAIN_TYPE | train type for which tkt is valid | 0 | |||||||
| STUNDE | Not used | 0 | |||||||
| COMBINE_STATION_INDICATOR | Usage of city code instead of stations | 0 | |||||||
| DEPARTURE_STATION | Departure station (use table EHBF) | 0 | |||||||
| DESTINATION_STATION | Destination (use table EHBF) | 0 | |||||||
| OUTWARD_ICE_DEPARTURE_STATION | ice first leg route departure station (use table EHBF) | 0 | |||||||
| OUTWARD_ICE_DESTINATION_STATIO | ice first leg route arrival station (use table EHBF) | 0 | |||||||
| OUTWARD_ICE_VIA_STATION_ROUTE1 | ice first leg route via point 1 (use table EHBF) | 0 | |||||||
| OUTWARD_ICE_VIA_STATION_ROUTE2 | ice first leg route via point 2 | 0 | |||||||
| OUTWARD_ICE_BREAKPOINT_ROUTE1 | 0 | ||||||||
| OUTWARD_ICE_BREAKPOINT_ROUTE2 | 0 | ||||||||
| OUTWARD_ICE_OPERATION_CODE | Operation Code | 0 | |||||||
| RETURN_ICE_DEPARTURE_STATION | ice return leg route departure station (use table EHBF) | 0 | |||||||
| RETURN_ICE_DESTINATION_STATIO | ice return leg route arrival station (use table EHBF) | 0 | |||||||
| RETURN_ICE_VIA_STATION_ROUTE1 | ice return leg route via point 1 (use table EHBF) | 0 | |||||||
| RETURN_ICE_VIA_STATION_ROUTE2 | ice feturn leg route via point 2 | 0 | |||||||
| RETURN_ICE_BREAKPOINT_ROUTE1 | 0 | ||||||||
| RETURN_ICE_BREAKPOINT_ROUTE2 | 0 | ||||||||
| RETURN_ICE_OPERATION_CODE | Operation code | 0 | |||||||
| BUS_INTERELATIONS | Number of bus interelations | 0 | |||||||
| BUS_LINE_NUMBER | bus line number | 0 | |||||||
| BUS_DEPARTURE | Not used | 0 | |||||||
| BUS_DESTINATION | Not used | 0 | |||||||
| BEZIRK | Not used | 0 | |||||||
| NUMBER_MONTHLY_TICKET | 0 | ||||||||
| HPTK_NR | Not Used | 0 | |||||||
| HPT_BEZ | Not used | 0 | |||||||
| HPT_NETZ | Not used | 0 | |||||||
| BETRAG | Not used | 0 | |||||||
| NUMBER_OF_DB_SALES_OFFICE | 0 | ||||||||
| BEZ_KM_DB | Not usedot used | 0 | |||||||
| BEZ_KM_FREMD | Not usedNot used | 0 | |||||||
| ZONEN_KM_FREMD | Not usedNot used | 0 | |||||||
| ANG_GRUPPE | Not usedNot used | 0 | |||||||
| TRAVELLER_NAME | Name of passenger | 0 | |||||||
| AIRLINE_TICKET_NUMBER | When used in joint offer | 0 | |||||||
| ID_NUMBER | ID Card number | 0 | |||||||
| STELLPL | Not usedNot used | 0 | |||||||
| KFZ | Not usedNot used | 0 | |||||||
| DATE_OF_BIRTH | 0 | ||||||||
| VERS | Not usedNot used | 0 | |||||||
| SPOUSE_NAME | Name of spouse or companion | 0 | |||||||
| STREET | street | 0 | |||||||
| ZIP_CODE | 0 | ||||||||
| ADDRESS | Resident address (City) | 0 | |||||||
| DIRECTION | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure FTPS_API_RAIL_FIN_IN using ABAP code?
As FTPS_API_RAIL_FIN_IN 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_API_RAIL_FIN_IN as there is no data to select.How to access SAP table FTPS_API_RAIL_FIN_IN
Within an ECC or HANA version of SAP you can also view further information about FTPS_API_RAIL_FIN_IN 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