Hierarchy
⤷ FI-TV-COS (Application Component) Travel Expenses
⤷ PTRA (Package) Travel Expenses Application Dev. (R/3 Enterprise Core)
Basic Data
Data Element | PTRV_TRVCT_R_18 |
Short Description | Procedure for Trips to Same Destination |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PTRV_TRVCT_R_18 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Value |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
You want to group together recurring trips to a destination for tax reasons so that you can change the accounting and taxation method after a certain length of time (such as three months). For the recurring destinations to be identified as such, they must be entered in detail. This means that you can only enter the destinations using input help. The input help shows the destinations that have been visited for the current personnel number. If a destination is traveled to again, you can then select that destination from the list. New destinations can be created by entering the street and location details in the lower part of the list. This ensures that recurring trips to a specific destination are always created with the same destination name and details.
You have the following options:
0 = The accounting and taxation method is not changed if recurring trips to the same destination take place (example: three-month rule in Germany).
1 = The accounting and taxation method is changed if recurring trips to the same destination take place (example: three-month rule in Germany). The company pays the tax for the old tax-exempt amount.
2 = The accounting and taxation method is changed if recurring trips to the same destination take place (example: three-month rule in Germany). The employee pays the tax for the old tax-exempt amount.
3 = Table PTRV_TRIP_CHAIN, which contains all trips and their destinations, is maintained for statistical purposes only.
4 = Public Sector Austria (obsolete): Chaining together of trips based on 30-day rule in accordance with Austrian travel expense regulations (RGV) and generation of stopovers or update of automatically generated stopovers (with respect to modeling the lower reimbursement for rate 2)
5 = Austria: Chaining together of business trips based on 183-day rule (taxation). Taxation of meals per diem and accomodations per diem is carried out automatically.
6 = Public Sector Austria: Chaining together of trips and duty allocation based on 30-day rule in accordance with Austrian travel expense regulations (RGV) and chaining together of trips and duty allocation based on 183-day rule (see explanation for points 4 and 5).
7 = 60-day rule for Denmark: If, within 12 months, more than 60 business trips take place from or to the employee's home, to or from the same destination, reimbursement is to be taxed as of the 61st business trip. If, within 60 days, no business trips take place from or to this destination, the trip chain is broken. Taxation is not carried out automatically and instead, only a statistical evaluation is carried out.
Notes on Values 1 to 3:
If you select 1, 2, or 3, enter the duration in months and/or days (constants REIDM or REIDD) in table T706_CONST. The duration used by the system is then the number of months in REIDM plus the number of days in REIDD. Enter the maximum allowed gap between two trips to the same destination in the constant REIGP.
The change becomes effective with the date (DATUM field) that you assign to the constant REIDM in addition to the duration. This means that the first change of the accounting and taxation method will take place after the defined duration (such as three months) from the effective date.
Warning: In the current version, all three settings fill table PTRV_TRIP_CHAIN with all trip destinations. If a destination is found for which the accounting and taxation method must be changed on a specific date, that date is saved in table PTRV_TRIP_CHAIN in the field ACTION_DATE_REQ for all trips to that destination.
However, the accounting program does not currently react to this date. In this case the user can use method SET_DIFFERENT_WAGETYPE from the BAdI TRIP_RECURRENT_DEST (transaction SE19) to assign the settlement amounts that are after the specified date to a separate wage type.
The Travel Calendar (transaction PR02), the Weekly Report (PR04), and the automatic assignment of credit card receipts to a trip during the credit card import are not supported.
Notes on Values 5 to 6:
If you select 5, enter the duration in months or days (constant REIDM or REIDD) in table T706_CONST for taxation according to the 183-day rule. The duration used by the system is then equal to the number of months specified in REIDM plus the number of days specified in REIDD. Finally, enter the maximum allowed gap between two trips to the same destination in the constant REIGP.
If you select 6, enter the duration in months or days (constant REPSM or REPSD) in table T706_CONST for the trip chain based on the 30-day rule in accordance with the Austrian travel expense regulations (RGV). The duration used by the system is then equal to the number of months specified in REPSM plus the number of days specified in REPSD. Finally, you enter the maximum allowed gap between two trips to the same destination in the constant REPSP.
In the standard system, the constants are maintained correctly for the public sector (trip provision variant AT).
Notes on Value 7:
The 60-day rule for Denmark is applied if you select 7. Here, table PTRV_TRIP_CHAIN is filled with all trips and any stopovers and serves as a basis for evaluating these trips using report RPR_ALV_DENMARK. This report determines all outbound and return trips that begin or end at the employee's home and for which reimbursements are to be taxed according to the 60-day rule in Denmark. The report is used only for statistical evaluations of such trips. The tax amount is not calculated when the trips are settled.
If you select 7, create constant REIDD in table T706_CONST with the value 60 as the maximum number of business trips with tax-free reimbursement.
If you select 7, also create constant REIGP with the value 60 in table T706_CONST. This breaks the trip chain if, within 60 days, no business trips take place from or to the respective destination.
If not all calendar days are to be taken into account when the interruption period is determined, you can use the method 'CALCULATE_WORKING_DAYS' in the BAdI 'BADI_PTRM_CALC_WORK_DAYS' to determine the employee-specific workdays.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |