Page Comparison

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.

Image Modified

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

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707 (when enabled, a CATS entry is created, otherwise an order confirmation).

Image Modified

Image Modified

The CATS posting is performed based on customizing in transaction https:/

/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707, e.g. the entry profile type determination.

Activity type is retrieved from ‘ActTypeTrav’ field in /PACG/ECM_MLGPRP - Mileage definition.

See also https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135032/Mileage#Prerequisites-for-posting-of-a-given-document

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

Image Modified

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

Image Modified

a) CATS scenario:

Image Modified

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

Image Modified

Idoc processed correctly.

Image Modified

A CATS entry created correctly.

Image Modified

b) Confirmation scenario:

Image Modified

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

Image Modified

Idoc processed correctly.

Image Modified

Confirmation created correctly.

Image Modified

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

Image Modified

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

Image Modified

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

Image Modified

Used to determine a cost center which will be checked against the field ‘Source cost center’ in transaction https:/

/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135129 to retrieve a relevant configuration entry for inbound processing.

Image Modified

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.

Image Modified

Employee’s cost center

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

Image Modified

Convert travel time for CATS/order confirmation posting based on the technician’s mobile device’s time zone. Note that transaction https:/

/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/72843268 must be additionally maintained. It contains mapping between FSM time zone format (e.g. Europe/Warsaw) and SAP time zone format (e.g. CET).