| Info |
|---|
Learn more about general mileage inbound processing from the diagram on page Mileage. |
Determine values used for activity allocation document posting for recorded mileages, based on company ID and optionally - source cost center, mileage type, ‘chargeable’, 'driver' and ‘private car’ properties. Notice that the first seven fields are used only to retrieve a relevant set of properties on the right, during inbound mileage processing. An entry should match exactly the data received from SAP FSM. The only exception is source cost center - if no entry for the given company ID, cost center, mileage type, charge type, drive and private car properties is found, an entry matching all these properties apart from cost center is searched for.
...
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 |
|---|
https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135037. 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 |
https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135107, 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 | |||||||||||
| Use this field if distance unit (kilometer/mileage) selected during mileage recording on the mobile app should have impact on activity type determination. Based on the distance unit of a mileage entry, as well as its other properties (e.g. chargeable, driver), a relevant mileage configuration entry is selected, including activity type. The retrieved activity type has impact on which unit will be used in the resulting Direct Activity Allocation document (units are assigned to activity types). This field reflects the functionality of https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135129/PACG+ECM+MLGPRP+-+Mileage+definition#MlgTypeFromUDF-(formerly-%E2%80%98Mileage-type%E2%80%99), the only difference is that instead of a UDF, it relies on a standard mileage property. If no matching configuration entry is found for the recorded distance unit (and all other mileage properties), an additional configuration retrieval is performed - this time distance unit is not considered. | ||||||||||
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. See other prerequisites for posting of time documents for mileages: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135032/Mileage#Prerequisites-for-posting-of-a-given-document. | |||||||||
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 https:/ |
/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135241.   Optionally, enter ‘Sales Tax Code’ for additional filter during Expense configuration determination.  |
Payment type |
|---|
Tax code |
Example of posting actual mileage with expenses (travel lump sum) together
...
The expense code in the above example "D" refers to transaction /PACG/ECM_VEXPNS entry below.
Amount = 300 km x 0.15 = 45
Mileage rate = 0.15 (see for further info below).
The calculation for the expense is based on the entries in https:/PACG/ECM_MLGA - Mileage allowance/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135241
...
A figure of 45 is posted as expenses for 300 km mileage submission. The "Ctr" here is checked against the PA30 infotype 0006 (Address) country key.
...