Hierarchy
⤷ FI-TV-COS (Application Component) Travel Expenses
⤷ PTRC (Package) Customizing for Travel Management
IMG Activity
ID | SIMG_OHR0050 | Create Travel Expense Types for Individual Receipts |
Transaction Code | S_AHR_61009843 | IMG Activity: SIMG_OHR0050 |
Created on | 19981221 | |
Customizing Attributes | SIMG_OHR0050 | Create travel expense types for individual receipts |
Customizing Activity | SIMG_OHR0050 | Create travel expense types for individual receipts |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OHR0050 |
Individual statements for travel expenses are processed in Travel Expenses via receipts. Every receipt is stored in the system with a travel expense type, an amount and the issue date.
In this IMG activity, you define the valid entry values for the travel expense types and store the corresponding long names.
The travel expense type must be defined using an alphanumeric key with a maximum of 4 characters and a validity period.
You can not change the end date of the validity period at a later time.
Receipt Wizard
You can decide whether each travel expense type can be split into
individual receipt lines (receipt itemization) using the Receipt Wizard. This may be helpful if, for example private shares have to be deducted from a hotel receipt, or if you want to split the receipt into separate accommodation and meals amounts.
Public Sector Germany:
For the German Public Sector you can specify, here, the usage of travel expense types in accordance with the BRKG (German Federal Travel Expenses Law). For settlement of travel expenses according to the BRKG, there must be at least one travel expense type for capping documents and one travel expense type for allowance documents.
For this purpose you can make additional settings in the Comparison calculation field for travel expense types for the German Public Sector
Note
In the section Screen layout for trip data entry in the later chapter Dialog and accounting control, you can specify, for each travel expense type, which additional receipt information can or must be maintained in dialog. This is done in the IMG activity Field control for additional receipt information.
In the later chapter Input tax and wage types for interfaces, you must assign wage types to the travel expense types defined here, in the IMG activity Assign wage types to travel expense types for individual receipts.
Recommendation
SAP recommends that you set the end date of the validity period of a travel expense type to the date 12/31/9999, since:
- The end date can not be changed later
- In this way no restrictions are placed on delimiting
Caution
Before you delete travel expense types, check whether they are assigned to credit card transactions. If this is the case, you must define a new assignment for the transaction key involved.
Activities
- Choose the trip provision variant for which you want to create a travel expense type.
- Assign a key in the Travel expense type field for the travel expense type and a corresponding long name.
- Define the validity period in which the travel expense type is valid via the beginning and end fields.
Note
Except for the long name and the beginning date, you can not change the settings made here at a later stage after they have been saved.
- Define the parameters for the travel expense type that may affect online dialog.
- Assign a travel expense category to the travel expense type in the Travel expense category field.
- Assign a sales tax code to the travel expense type in the Tax code field.
- In the Travel expense type permissibility field, define the employee grouping for travel expense type for which this travel expense type is to be valid.
- You can now set the paid by company indicator.
- Choose the entry types for which the travel expense type can be used.
- You can specify the order for the weekly report.
Travel expense type German Public Sector : Additional settings
Activities
Check the travel expense types in the standard system for the German Public Sector.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_OHR0050 | 0 | HLA0006755 | Travel Expenses |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_T706B1 | V - View | SM30 | 0000000000 | Generated Table Maintenance: V_T706B1 |
History
Last changed by/on | SAP | 19981221 |
SAP Release Created in |