| Note | ||||
|---|---|---|---|---|
When maintaining entries here, please keep in mind the following: 1) time splitting must be additionally enabled in https://proaxia-prod-doc.atlassian.net/wiki/x/AQDbf, field “Split conf”.
2) actual start/finish time is obligatory, even if duration is entered. If start/finish are not relevant and only duration matters, enter 00:00 - 24:00. 3) make sure that the entire day (or all possible time frames) are covered, if a technician enters time which is relevant for time splitting but only some hours are covered by customizing, such a time record will fail |
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
...
| Table of Contents |
|---|
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
...
https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136264, if in transaction
...
https://proaxia-prod-doc.atlassian.net/wiki/x/AQDbf the ‘Activity 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.
| Note |
|---|
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.
| Info |
|---|
To set the end of the day as actual finish time, use 24:00:00 instead of 23:59:59. |
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.
| Info |
|---|
Duration-based calculation is impacted by the following setting: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515/PACG+ECM+CPROP+-+General+Properties+of+FSM+Cloud+Connector#(S4)-PACG-200-SP12-ExclBrkSplitDur |
In addition to the work duration entered on the mobile app, CATS entries or service order data can be added
...
, depending on the value in field DuratSOpt.
Duration re-calculation based on existing CATS entries data
The following actions apply, depending on the value of field DuratSOpt:
Person - retrieve the number of hours already entered in CATS for the technician on a given day and add this number to the
...
duration of time effort. Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort
...
.
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
...
duration of time effort. Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort
...
.
Empty - duration time is not considered
| Info | ||||
|---|---|---|---|---|
If the field DuratSOpt is filled either with Person or Order, the overtime will receive a surcharge, as explained in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137870.
|
| Status | ||
|---|---|---|
|
...
|
Used when posting to CATS is not activated in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707. The following actions apply, depending on the value of field DuratSOpt:
Person - to the duration of time effort, add the sum of actual work hours from confirmations where:
Personnel nr. = technician reporting a time effort
work start = start date of time effort
activity type is not excluded in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137792
confirmation is not cancelled
Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort.
Order - to the duration of time effort, add the sum of actual work hours from confirmations where:
personnel nr. = technician reporting a time effort
work start = start date of time effort
order no. = receiver order
activity type not excluded in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137792
confirmation is not cancelled
Compare the overall number with the allowed duration time. If the number is exceeded, split the time effort.
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 effort fits into three duration time frames (the first three hours into the first one
...
, the next 5 hours into the second one and the last 11 hours into the last one), therefore the posting will be split into three CATS entries, each with different activity type and Attendance/absence type:
The actual start/finish times in the customizing entry didn’t influence the time splitting in this case.
| Status | ||
|---|---|---|
|
Use the button ‘Consistency check’ to verify if your time split customizing is correct.
The consistency checks will verify the following:
The entire day (24h) is covered by ‘Actual start time’ and ‘Actual finish’ dates (no gaps left)
Actual start/finish does not overlap with other time slot entries for the same key
For each entry where “duration to” is not initial (00:00:00), any non-initial actual finish is entered
Duration time fits between start and end time
All Activity Types provided in Time Confirmation Split was maintained accordingly in /PACG/ECM_PSEQN - Break sequence
| Status | ||
|---|---|---|
|
Use the button ‘Copy to another company’ to easily copy split configuration entries from one plant to another.
With the option ‘Keep the source properties’ selected, all entries for a given source plant will be copied to another, keeping all the other fields unchanged.
With the option ‘Use the mapping below’ selected, a user maps source properties (activity type, country, region, holiday calendar) with the target values. At least one property must be mapped. FSM Cloud Connector then retrieves all entries from the source plant which match the entered set of source properties and copies them into the target plant, additionally adjusting the relevant properties, based on the provided mapping. Properties which are not mapped, are ignored during retrieving of entries relevant for copy.
Related customizing transactions
Default break start time for time splitting - https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/
...
...
/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137814
Activity types excluded from time splitting - https:/
...