Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »

Learn more about general mileage inbound processing from the diagram on page Mileage.


Define how the posting date for mileage-related CO-documents is determined.

Use act. date

If checked, the system date (SY-DATUM) will be used for cost documents posting. Otherwise, the date recorded by a technician on the mobile app will be used.

System date is used always if no date is found in the idoc.   

CATS/CONF

If enabled, attempt to post mileage (travel) time. The travel time can be posted as a CATS entry or confirmation, this depends on setting “CATS active” in /PACG/ECM_CTET - Time posting settings (when enabled, a CATS entry is created, otherwise an order confirmation).

The CATS posting is performed based on customizing in transaction /PACG/ECM_CTET - Time posting settings, e.g. the entry profile type determination.

CO Posting

If no distance is entered for a mileage on the mobile app (e.g. because this field is purposely hidden), a direct activity allocation document cannot be created in SAP. By default, further processing would be stopped and CATS/confirmation couldn't be created either.

Skip posting CO documents for mileages with empty distance

If option ''[X] Skip posting CO documents for mileages with empty distance' is set, mileages with missing distance do not run into an error. No cost document is posted but if CATS or confirmations are activated for mileages, such documents are created.

Example with distance hidden on the mileage recording screen

1. Field ‘CO Posting’ set to ‘Skip posting CO documents for mileages with empty distance’:

a) CATS scenario:

Create a mileage record without distance, only with travel time.

Idoc processed correctly.

A CATS entry created correctly.

b) Confirmation scenario:

Create a mileage record without distance, only with travel time.

Idoc processed correctly.

Confirmation created correctly.

2) Field ‘CO Posting’ set to ‘Always’:

Create a mileage record without distance, only with travel time.

Idoc processing runs into errors because direct activity allocation cannot be created without quantity (mileage distance).

CC booking

Used to determine a cost center which will be checked against the field ‘Source cost center’ in transaction /PACG/ECM_MLGPRP - Mileage definition to retrieve a relevant configuration entry for inbound processing.

Work center’s cost center

Find the technician’s work center’s cost center. Keep in mind that if a technician is assigned to more than 1 work center, the cost center of the first one will be retrieved.

Work center’s cost center can be found in transaction IR03.

Employee’s cost center

Employee’s work center can be found in transaction PA30, infotype 0001.

If no matching source cost center is found in transaction /PACG/ECM_MLGPRP - Mileage definition for the cost center determined based on this setting, a matching entry with empty ‘source cost center’ field will be used for inbound processing (e.g. generation of a cost document).

(S4)PACG 200 SP06

Use TimeZoneId

Convert travel time for CATS/order confirmation posting based on the technician’s mobile device’s time zone. Note that transaction /PACG/ECM_TZCNV - Time zone conversion must be additionally maintained. It contains mapping between FSM time zone format (e.g. Europe/Warsaw) and SAP time zone format (e.g. CET).

Mileage submission

FSM_SAP_Mileage_Submission.mp4

  • No labels