/PACG/ECM_MLU – UDF for Mileage
- Szymon Baraniuk (Unlicensed)
- proaxia
Specify which mileage UDF should be treated as source of the mileage type.
The UDF should be created beforehand in transaction /PACG/ECM_UDF_CONF - UDF Configuration and transferred to SAP FSM. Its cloud message type should be ‘MILEAGE’ and its length should be 1 character.
The found 1-character long mileage type value, together with other properties - company ID, source cost center, ‘chargeable’, ‘driver’ and ‘private car’ - will be used to retrieve a relevant Mileage configuration entry from transaction /PACG/ECM_MLGPRP - Mileage definition, during processing of inbound mileage.
Keep in mind that the mileage type value entered during mileage recording serves only as an additional filter for retrieving more precise Mileage configuration entry (transaction /PACG/ECM_MLGPRP - Mileage definition). It is not used in any cost document in further processing but helps to retrieve other properties which will be. If a mileage type is found, there must exist an entry with this specific mileage type maintained.
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.