BAPITRMAIN SAP (Header data for a trip; Structure for BAPI interface) Structure details
Description: Header data for a trip; Structure for BAPI interface
Structure field list including key, data, relationships and ABAP select examples
BAPITRMAIN 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 "Header data for a trip; Structure for BAPI interface" 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_BAPITRMAIN TYPE BAPITRMAIN.
The BAPITRMAIN table consists of various fields, each holding specific information or linking keys about Header data for a trip; Structure for BAPI interface data available in SAP. These include DEP_TIME (Beginning Time of Trip Segment), ARR_DATE (End Date of Trip Segment), ARR_TIME (End Time of Trip Segment), CUSTOMER (Reason for Trip (for example, customer/requisitioner)).. 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 (character-type or numeric)
SAP BAPITRMAIN 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 |
| DEP_DATE | Beginning Date of Trip Segment | REBED | DATS | 8 | REDAT | ||||
| DEP_TIME | Beginning Time of Trip Segment | REBEU | TIMS | 6 | REUHR | ||||
| ARR_DATE | End Date of Trip Segment | REEND | DATS | 8 | REDAT | ||||
| ARR_TIME | End Time of Trip Segment | REENU | TIMS | 6 | REUHR | ||||
| CUSTOMER | Reason for Trip (for example, customer/requisitioner) | RKUNDE | CHAR | 59 | RKUNDE | ||||
| LOCATION | Location | RZIELORT | CHAR | 59 | RZIELORT | ||||
| COUNTRY | Trip Country / Trip Country Group | LNDGR | CHAR | 3 | T706O | LNDGR | |||
| REGION | Region of Main Destination | HRGIO | CHAR | 5 | T702O | RGION | |||
| OUT_DATE | Border Crossing (Trip Out): Date | DATGH | DATS | 8 | REDAT | ||||
| OUT_TIME | Time: Border crossing(trip out) | UHRGH | TIMS | 6 | REUHR | ||||
| RET_DATE | Border Crossing (Return Trip): Date | DATGZ | DATS | 8 | REDAT | ||||
| RET_TIME | Time: Border crossing(return trip) | UHRGZ | TIMS | 6 | REUHR | ||||
| RET_COUN | Return trip from country | RET_COUN | CHAR | 3 | T706O | LNDGR | |||
| RET_RGIO | Trip country/trip country group/trip region | RET_RGIO | CHAR | 5 | T702O | RGION | |||
| RET_TTCS | Trip type: Enterprise-specific | RET_TTCS | CHAR | 1 | T702X | BEREI | |||
| T_SCHEMA | Trip schema | RSCHE | CHAR | 2 | T706S | RSCHE | |||
| TT_COMSP | Trip Type: Enterprise-Specific | BEREI | CHAR | 1 | T702X | BEREI | |||
| TT_STATU | Trip Type: Statutory | KZREA | CHAR | 1 | T702G | KZREA | |||
| T_ACTYPE | Trip Activity Type | KZTKT | CHAR | 1 | T702R | KZTKT | |||
| PD_MEALS | Per-Diem Accounting for Meals | VERPA | CHAR | 1 | VERPA | ||||
| PD_ACCOM | Per-Diem Accounting for Accommodations | UEPKZ | CHAR | 1 | UEPKZ | ||||
| NO_NIGHT | Number of Overnight Stays for Per-Diem Settlement | ANUEP | DEC | 2 | ANUEP | ||||
| PSTLZ | Postal Code | PSTLZ | CHAR | 10 | PSTLZ | ||||
| ORT01 | City | PAD_ORT01 | CHAR | 40 | PAD_ORT01 | ||||
| STRAS | Street and House Number | PAD_STRAS | CHAR | 60 | PAD_STRAS | ||||
| STATE | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| REQUEST | Indicator for objects request, plan and expense report | PTRV_OBJEKT | CHAR | 1 | CHAR1 | ||||
| TRAVEL_PLAN | Indicator for objects request, plan and expense report | PTRV_OBJEKT | CHAR | 1 | CHAR1 | ||||
| EXPENSES | Indicator for objects request, plan and expense report | PTRV_OBJEKT | CHAR | 1 | CHAR1 | ||||
| ORT02 | District | PAD_ORT02 | CHAR | 40 | PAD_ORT01 | ||||
| CITY_CODE | City code for city/street file | AD_CITYNUM | CHAR | 12 | Assigned to domain | ALPHA | CITY_CODE | ||
| TAX_PER_DIEM | Automatic Taxation of Meals Per Diems | PTRV_TAX_PER_DIEM_CORE | CHAR | 1 | XFELD | ||||
| TAX_PD_MAN | Manually Triggered Taxation of Meals Per Diems | PTRV_TAX_PD_MAN_CORE | CHAR | 1 | XFELD | ||||
| TAX_OV_MAN | Manually Triggered Taxation of Accommodations Per Diems | PTRV_TAX_OV_MAN_CORE | CHAR | 1 | XFELD | ||||
| EXCHANGE_DATE | Reference Date of Trip | PTRV_DATTN_CORE | DATS | 8 | REDAT | ||||
| ROUNDING | Travel Amounts Are Rounded (Indicator) | PTRV_ROUNDING_CORE | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPITRMAIN using ABAP code?
As BAPITRMAIN 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 BAPITRMAIN as there is no data to select.How to access SAP table BAPITRMAIN
Within an ECC or HANA version of SAP you can also view further information about BAPITRMAIN 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