Content Comparison

Background job IDOC processing instead of automatic. The technician can book the times in the future. If this is not set, then a red Idoc(s) will appear if time effort is booked directly as confirmation to the service order.

This checkbox is part of obsolete solution for time effort processing.

If set, then the start and end date of work time & time effort entries in another time zone are not converted in the time zone of the Company but remain as entered in the time zone of the mobile device used. This is to be used if local timestamps are relevant for activity type determination or overtime identification.

If set, then CATS entries will be created for a time effort. Otherwise, an order confirmation will be created. It is not possible to create CATS entries and order confirmation at the same time.

If set, then texts from time effort / worktime are transferred to CATS entries.

Start date from which the current CATS profile is used for postings.

Data entry profile for CATS bookings. The data entry profile determines the method of data entry, the layout of the data entry screen, and the following factors:

• Whether times can be entered for individual employees or for groups of employees

• Which data can be maintained (confirmations, services, and so on)

• Whether time sheet data is entered on a daily, weekly or monthly basis

• Whether or not the data entered is subject to approval

If set, CATS entries are automatically released.

Past option settings indicate which postings should be processed during a specific period of time.  They indicate allowed time effort start dates to limit posting in the past.

The options which allow bookings in the past are:

• No limitations

• One day

• Two days

• Three days

• Four days

• Five days

• Six days

• Seven days

• Closing period at 10th

• Closing period at 15th

• Closing period at 20th

• Closing period at 5^th

Please note that this setting is not relevant in case when Park from and Park to dates are entered and the time effort falls in between their range. In this case all time efforts in the range will be parked for later processing (see https:/PACG/ECM_POST_TIMEF - Rebooking of not booked Work Time and Time Effort/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1203175437) and saved in table /PACG/ECM_ALTEW.

Examples:

If no limitation is set, then all postings will be processed automatically - unless parked from and parked to are set and time effort falls in between their range. In such a case the time entries in the range will be saved in table /PACG/ECM_ALTEW for later processing.

If X days is set, then the days between the current point in time and X days will be booked and the days past the X days will be saved in /PACG/ECM_ALTEW table for later processing.

Future option settings indicate which postings should be processed during a specific period of time. They indicate allowed time effort start dates to limit posting in the future

The options which allow bookings in the future are:

• No limitations

• Until today

• Until tomorrow

Please note that this setting is not relevant in case when Park from and Park to dates are entered and the time effort falls in between their range. In this case all time efforts in the range will be parked for later processing (see https:/PACG/ECM_POST_TIMEF - Rebooking of not booked Work Time and Time Effort/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1203175437) and saved in table /PACG/ECM_ALTEW.

Example:

If no limitation is set, then all postings will be processed automatically - unless parked from and parked to are set and time effort falls in between their range. In such a case the time entries in the range will be saved in table /PACG/ECM_ALTEW for later processing.

If until today is set, then all time efforts entered until today will be processed automatically (unless parked from and parked to are set and time effort falls in between their range) and time efforts entered tomorrow and after tomorrow will not be processed automatically and will be saved in /PACG/ECM_ALTEW table for later processing

Expand
title Please click here to see more detailed example related to past and future options
In the below scenario, the past option is set as two days and the future option is set as until today. Please note that Park from and Park to values are empty: The below time entries have been entered and approved. Please consider the 1st of June 2021 as today’s date. Please also note the dates of time efforts. Only the 3rd time entry (form the 1st of June) was automatically processed: The remaining entries were saved in table /PACG/ECM_ALTEW for later processing. Two of them - from the 2nd of June and the 3rd of June exceed future limit (until today) and the other one from the 29th of May exceeded the past limit (2 days):

Do not create entries in FSM Cloud Connector table /PACG/ECM_ALTEW. This table is used for the functionality of time effort parking. Learn more: https:/PACG/ECM_POST_TIMEF - Rebooking of not booked Work Time and Time Effort/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1203175437

If this option selected the CATS Receiver from the Service Orders settlement rule is determined for CATS entry – it may be sales document item, CO order, PSP element, network item.

If set, then the sending cost center in confirmations/CATS entry entries is filled from persons cost center assignment in infotype 0001, based on rules entered inhttps://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707/PACG+ECM+CTET+-+Time+posting+settings#(S4)PACG-200-SP10-Sending-Cost-Center-for-time-effort-(CATS)-%2F-OLD-LABEL--Sending-Cost-Center-source-for-time-effort

If set, then the receiving receiver cost center in confirmations/CATS entry entries is filled from:

, based on rules entered in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707/PACG+ECM+CTET+-+Time+posting+settings#Receiving-Cost-Center-for-time-effort-(CATS-and-Conf.)-%2F-OLD-LABEL-Receiving-Cost-Center-for-time-effort

For time posting, use the Activity Type assigned to the reporting technician in infotype 0315. It can be used to avoid time task selection by a technician during time effort recording.

Park from and Park to options are available since the 2105 Release.

They indicate the timeframe (date of posting in the system, not time effort dates!), for which the time efforts should be parked for later processing.

Time effort data processed between the specified time range is stored in table /PACG/ECM_ALTEW along with UDF data in /PACG/ECM_ALTEWU and CATS receiver data in /PACG/ECM_ALTEWC. 

Stored data can be posted using report https:/PACG/ECM_POST_TIMEF - Rebooking of not booked Work Time and Time Effort/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1203175437, which is advised to be run as a batch job with relevant parameters.

Image Removed

When options ‘Fill send cctr’/'Fill rec cctr' are activated, these fields are used to determine how the sending/receiver cost center will be retrieved.

Image Added

Actual work/duration values in confirmations created for time efforts will always be rounded to hours. If unchecked, only values divisible by 6 would be rounded to hours and the other would be posted in minutes.

Examples

• Time effort 17:02-18:09 (1 hour 7 minutes) will be posted as 1.12 h of actual work and 1.1 of duration. Without this field checked, it would be 67 minutes in both fields.

• Time effort 10:00-11:06 (1 hour 6 minutes) will be posted as 1.10 h of actual work and 1.1 of duration. Without this field checked, it would be the same values.

• Time effort 08:00-09:00 (1 hour) will be posted as 1h of actual work and 1h of duration. Without this field checked, it would be the same values.

• Time effort 04:00-05:15 (1 hour 15 minutes) will be posted as 1.25 h of actual work and 1.3 of duration. Without this field checked, it would be 1.25h of actual work and 75 min of duration.

• Time effort 03:00-04:12 (1 hour 12 minutes) will be posted as 1.20 h of actual work and 1.2 of duration. Without this field checked, it would be the same values.

• Time effort 02:00-02:30 (30 minutes) will be posted as 0.50 h of actual work and 0.5 h of duration. Without this field checked, it would be the same values.

• Time effort 01:00-01:13 (13 minutes) will be posted as 0.22 h of actual work and 0.2h of duration. Without this field checked, it would be 13 min in both fields.

Split confirmations can also be rounded to hours.

Rounding in SAP FSM

The following SAP FSM settings can be used to round time effort time on the mobile app:

• Company settings CoreSystems.TimeManagement.RoundToMinutes and CoreSystems.TimeEntryInterval

• Permission settings of object TIMEEFFORT - ROUND_TIMEFFORT_NEXT15 (UI permissions)

If a time effort was updated in SAP FSM after synchronization with SAP ECC/S4 (example by a business rule), allow cancellation of the related CATS/confirmation entries. Afterwards, new CATS/confirmation entries will be created following the standard inbound time effort processing. If the setting is disabled, logs informing about the changes will be added to the idoc but no SAP object will be affected.

Learn more: Time efforts updated in SAP FSM

Learn more: Deletion and update of Work Time in FSM

Use the activity type's default unit for confirmation or activity allocation posting (work time posting to an internal order). The default unit is searched for the activity type determined during time effort/work time processing (based on time effort task or work time task type customizing).

Affected units in a time confirmation for a service order: 

Affected unit in an activity allocation document: 

Unit source is communicated in idoc logs: