| Info |
|---|
Learn more about general mileage inbound processing from the diagram on page Mileage. |
...
Configuration entry determination (key based on which a specific entry is retrieved for inbound mileage processing) | Source cost center | During inbound mileage processing the source cost center is determined based on setting ‘CC booking' in transaction /PACG/ECM_MLGG – Mileage – General Settings. The retrieved value is then compared with the content of the ‘Source cost center’ field in the Mileage Definition transaction to find a relevant configuration entry (the combination of all other properties received from SAP FSM should also be matched). This field serves only as an optional, additional ‘filter' for mileage configuration determination.
| |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| This property is hidden from the view starting from
| ||||||||||
MlgTypeFromUDF (formerly ‘Mileage type’) | The mileage type value to be retrieved from a special mileage type UDF. It serves as an additional criterion to determine the proper activity type, cost center and other mileage properties. This field is optional. The UDF ID used to hold the values should be entered beforehand in transaction /PACG/ECM_MLU – UDF for Mileage, sent to FSM and placed on the relevant mileage screen. You use this special UDF for instance to allow technicians to select distance unit during mileage recording, in case you use one FSM company for multiple regions. For each value of the special UDF (e.g. ‘K' for kilometers, ‘BM’ for British miles, 'UM’ for American miles) you can enter a different activity type in the mileage customizing - cost documents will be posted with the unit assigned to the found activity type (transaction KL03).   | ||||||||||
Chargeable | Mileage properties set during mileage recording on the SAP FSM mobile app. | ||||||||||
Driver | |||||||||||
Private car | |||||||||||
Cost document properties | Material | [obsolete] | |||||||||
Activity type | Activity type to be used for activity allocation document posting. 
| ||||||||||
Cost center | Cost center to be used for activity allocation document posting.  | ||||||||||
Operation level | [obsolete] Activate posting on Operation level. | ||||||||||
Fixed cost document | Set quantity | Post a fixed KB21N cost document. If the ‘Set quantity’ setting is unchecked, the distance entered in SAP FSM will be used. Otherwise, the fixed quantity and unit from fields ‘Activity quantity’ and ‘Activity unit’ will be used. | |||||||||
Activity quantity | |||||||||||
Activity unit | |||||||||||
Travel time | ActiTypTravTime /
| Activity type from this field will be used for travel time posting, in CATS or confirmation entry. | |||||||||
Mileage allowance / mileage as expense | Expense code | In addition to the mileage booking, a booking can be made via Expenses in order to post kilometers and a travel lump sum. The ‘Expense code' field is required to fill and the 'Payment type’ is optional. An expense is calculated based on the rate entered in transaction /PACG/ECM_MLGA - Mileage allowance.   Optionally, enter ‘Sales Tax Code’ for additional filter during Expense configuration determination.  | |||||||||
Payment type | |||||||||||
Tax code |
...