The FSM Connector Integration enables mileage postings in three different ways:
Controlling area as an activity allocation document (KB16N transaction)
Controlling area as a manual allocation document (KB23N transaction)
Confirmation posting in reference to an S4 Service Order (only applicable in the Fiori environment)
All scenarios can be configured and customized based on user requirements in /PACG/ECM_MLGG and /PACG/ECM_MLGPRP.
The most significant difference compared to PM/CS orders is the Confirmation posting process for S4 Service Orders.
Mileage with confirmation - process flow
Prerequisites configuration in FSM Cloud Connector::
CATS/Conf must be activated in /PACG/ECM_MLGPRP
A confirmation specific settings must be provided in /PACG/ECM_MLGPRP:
Product name
Mileage condition type
Mileage rate
Currency
When technician is posting mileage in FSM application, the relevant properties must be entered according to settings in configuration for mileages in the back-end system:
Depending on the selected values in the highlighted orange frame, the system will recognize specific data for posting after data synchronization:
When the IDoc is processed successfully, a new confirmation will be created for the referenced Service Order’s activity. The mileage posting adds three positions to the confirmation:n:
Item 10 - related activity for mileage execution
Item 20 - Distance posting
Item 30 - Time posting for travel time (if ‘Travel duration’ is entered on the FSM side)
