E2HRTR3 SAP (HR-TRV: Transfer FI/CO - travel information) Structure details
Description: HR-TRV: Transfer FI/CO - travel information
Structure field list including key, data, relationships and ABAP select examples
E2HRTR3 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 "HR-TRV: Transfer FI/CO - travel information" 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_E2HRTR3 TYPE E2HRTR3.
The E2HRTR3 table consists of various fields, each holding specific information or linking keys about HR-TRV: Transfer FI/CO - travel information data available in SAP. These include ABKR2 (Payroll Area), PERM2 (Period modifier), ABRP2 (Payroll Period), ABRJ2 (Payroll Year).. 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 E2HRTR3 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 |
REINR | Trip Number | REINR | NUMC | 10 | REINR | ||||
ABKR2 | Payroll Area | ABKRS | CHAR | 2 | Assigned to domain | ABKRS | ABK | ||
PERM2 | Period modifier | IPERM | CHAR | 2 | CHAR2 | ||||
ABRP2 | Payroll Period | PABRP | NUMC | 2 | PABRP | ||||
ABRJ2 | Payroll Year | PABRJ | NUMC | 4 | GJAHR | GJAHR | |||
BEGP2 | Start Date | BEGDA | DATS | 8 | DATUM | ||||
ENDP2 | End Date | ENDDA | DATS | 8 | DATUM | ||||
MOLGA | Country Grouping | MOLGA | CHAR | 2 | Assigned to domain | MOLGA | MOL | ||
MOREI | Trip Provision Variant | MOREI | CHAR | 2 | Assigned to domain | MOREI | MOR | ||
SCHEM | Trip schema | RSCHE | CHAR | 2 | Assigned to domain | RSCHE | |||
BEREI | Trip Type: Enterprise-Specific | BEREI | CHAR | 1 | Assigned to domain | BEREI | |||
ZORT1 | City of the payee | DZORT1 | CHAR | 35 | TEXT35 | ||||
ZLAND | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
ZLND2 | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
KUNDE | Reason for trip (e.g. customer/requisitioner) | RKUND | CHAR | 17 | RKUND | ||||
DATV1 | Beginning Date of Trip Segment | REBED | DATS | 8 | REDAT | ||||
UHRV1 | Beginning Time of Trip Segment | REBEU | TIMS | 6 | REUHR | ||||
DATB1 | End Date of Trip Segment | REEND | DATS | 8 | REDAT | ||||
UHRB1 | End Time of Trip Segment | REENU | TIMS | 6 | REUHR | ||||
KZREA | Trip Type: Statutory | KZREA | CHAR | 1 | Assigned to domain | KZREA | |||
KZTKT | Trip Activity Type | KZTKT | CHAR | 1 | Assigned to domain | KZTKT | |||
DRUCK | Trip Print Status | P_PRINT | CHAR | 1 | P_PRINT | ||||
ANTRG | Travel Request or Trip Approved (Indicator) | ANTRG | CHAR | 1 | ANTRG | ||||
ABREC | Open / To be Settled / Settled (Indicator) | ABREC | CHAR | 1 | ABREC | ||||
UEBLG | HR Payroll Transfer (Indicator) | UEBLG | CHAR | 1 | UEBLG | ||||
UEBRF | FI Transfer (Indicator) | UEBRF | CHAR | 1 | UEBRF | ||||
UEBDT | Data Medium Exchange Transfer (Indicator) | UEBDT | CHAR | 1 | UEBDT |
Key field | Non-key field |
How do I retrieve data from SAP structure E2HRTR3 using ABAP code?
As E2HRTR3 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 E2HRTR3 as there is no data to select.How to access SAP table E2HRTR3
Within an ECC or HANA version of SAP you can also view further information about E2HRTR3 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