Hierarchy
⤷ FI-TV-COS (Application Component) Travel Expenses
⤷ PTRA (Package) Travel Expenses Application Dev. (R/3 Enterprise Core)
Basic Data
Data Element | PTRV_TRVCT_STAT |
Short Description | Statistics Data for Travel Management |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | Statistics |
Medium | 15 | Statist. data |
Long | 20 | Create statistics |
Heading | 22 | Create statistics data |
Documentation
Definition
Here you decide whether and how statistical trip data is created.
The following characteristics are supported:
-0- Statistical data is not created
-1- Statistical data is created immediately after a trip is saved
The statistics data is updated in the database when the
regular trip data is updated.
This procedure should normally be used.
-2- Batch creation of statistical data
When a trip is saved, only the key information of the trip is
stored in table PTRV_SBACKLOG. This table is then processed by the
report RPR_UPDATE_TRAVEL_STATISTICS periodically (setup of
statistical data) and deleted again. System administration must
create a job for this purpose, which starts the report
RPR_UPDATE_TRAVEL_STATISTICS periodically with the
'Process backlog data' parameter.
This procedure should be used if the statistics data is not directly needed for reporting purposes.
With a daily turnover of 1000 - 2000 trips, the report should
be planned to run four times a day, or every six hours.
-3- Statistical data is created by the accounting program (RPRTEC00)
Statistical data is not created until the program RPRTEC00
performs accounting of a trip.
This variant should be chosen if resource consumption is
to be reduced to an absolute minimum and if the time in
which the statistical data is made available is not a
critical factor.
If trip statistics are active (option 1 - 3), two additional fields for reimbursement amount and currency are activated in the travel manager and in the weekly report.
If new trips are created or existing trips are changed, the displayed reimbursement amounts are not updated immediately (Options 2 and 3). The updating of the values depends on the update procedure chosen above.
After a trip has been created or changed, however, an additional pushbutton appears in the menu, which you can use to obtain an immediate update. After the update, the button disappears.
If trip statistics are used, the total amount of the trip is displayed in the trip approval report RPR_APPROVE_TRAVEL_EXPENSES also.
Evaluation of trip statistics
For trip statistics evaluation, there are the following reports available:
Trip framework/Totals data: RPR_TRIP_HEADER_DATA
Trip receipts: RPR_TRIP_RECEIPT_DATA
Trip receipts w/o framework data: RPR_TRIP_RECEIPT_DATA_II
Cost assignment: RPR_TRIP_COST_ASSIGNMENT_DATA
Framework/Totals/Receipt..: RPR_TRIP_DATA_BLOCK_LIST
The above reports can be accessed via the Travel Management reporting tree.
For customer-specific evaluation of trip data (for example, using ABAP Query), the logical database PTRVP is available.
Further information
Documentation of the program RPR_UPDATE_TRAVEL_STATISTICS
History
Last changed by/on | SAP | 19980331 |
SAP Release Created in |