During inbound time effort processing, time records for confirmation and CATS can be split into two and more postings, each with different activity type and attendance/absence type.
Prerequisites
Time splitting should be enabled in transaction /PACG/ECM_SCTD – Service Call types definition: Overview and Detail, field ‘Split conf’.
Determination criteria
During processing of inbound time efforts, relevant splitting rules (meaning ‘Actual start/finish' or ‘Duration’ time frames, as well as Activity and Attendance/Absence types to be used) are determined based on the following criteria:
plant of the service order related to the time effort (required)
country key (optional)
Country key is determined based on company ID, order type and order partners. Partner role used to determine which partner should serve as source of country information should be maintained in transaction /PACG/ECM_SOAD – Service Order Address Determination, if in transaction /PACG/ECM_SCTD – Service Call types definition: Overview and Detail the ‘Assign. address’ is set to ‘Service order address determination’. In other cases the ‘SHIP-TO’ function will be used to determine the relevant partner and then its country key.
Source activity type (optional)
Source activity type is determined from time task or operation (if not found in time task).
Weekday - weekday of the time effort, calculated based on the date entered on the mobile app
The weekday can be set as ‘Public holiday’. In such a case first a relevant holiday calendar is determined. This is done using the calendar ID entered in the field ‘Holiday calendar ID'. If no value is found, it is determined based on the service order’s plant’s factory calendar. It is then checked if the time effort’s date is a holiday and if so, the time splitting entry for public holiday days will apply.
Fields ‘REGION’ and ‘LUMPSUM’ can be considered obsolete and should not be used.
Actual start/finish
Time efforts will be split based on the entered Actual start/finish time frames and will receive activity type and/or attendance/absence type entered for a specific entry.
For the actual finish time use 23:59:00 instead of 24:00.
Actual start/finish time frames - example
The following time effort was added on the mobile app:
The following time splitting entries are maintained for plant 1200, source activity type 101 and weekday Wednesday:
The time effort fits into three time frames (05:00 - 07:00 into the first one, 07:00 - 16:30 into the second one and 16:30 - 22:00 into the third one), therefore the posting will be split into three CATS entries, each with different activity type and Attendance/absence type:
Duration
Duration time frames are used to split time posting if the duration of time effort exceeds the specified number of hours/minutes. In addition to the work duration entered on the mobile app, CATS entries or service order data can be added. Set the ‘DuratSOpt' field as:
Person - retrieve the number of hours already entered in CATS for the technician on a given day and add this number to the length of time effort. Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort into two parts - the first one lasting the amount of entered duration time, the second one will be all the time left.
Order - retrieve the number of hours already entered in CATS for the technician AND THE SERVICE ORDER on a given day and add this number to the length of time effort. Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort into two parts - the first one lasting the amount of entered duration time, the second one will be all the time left.
Empty - duration time is not considered
If the field DuratSOpt is filled either with Person or Order, the overtime will receive a surcharge, as explained in /PACG/ECM_VWRKTC - Work Time Task Definition.
Duration time frames - example
The following time effort was added on the mobile app:
The following time splitting entries are maintained for plant 1200, source activity type 101 and weekday Wednesday:
The time posting was split into two - the first one lasting the duration of the first customizing entry (3 hours), and the second one lasting the rest.
The actual start/finish times in the customizing entry didn’t influence the time splitting in this case.
Related customizing transactions
Default break start time for time splitting - https://proaxia-prod-doc.atlassian.net/wiki/pages/resumedraft.action?draftId=37137803.
Default pause sequence for time splitting - /PACG/ECM_PSEQN - Break sequence
Activity types excluded from time splitting - /PACG/ECM_ATEXC - Activities excluded from duration